---
title: Export data from CMS 13
slug: cms-13/docs/export-data-from-cms-13
docTags: 
createdAt: 2026-07-30T20:22:07.892Z
---

:::hint{type="info"}
**Note**
This topic is for CMS administrators and developers with administrative access rights.
:::

Export data from Optimizely Content Management System (CMS) applications. Developers use this function frequently when building functionality in a test or development environment. When work is complete, use export and import to transfer data between environments. CMS exports content as `.episerverdata` files. Import them to another CMS application. See [Import data to CMS 13](docId\:wKoAE_Zes4TQHDtxbPd9T).

Export one or more of the following items to customize the exported content: content items, content types, tabs, blueprints, and style settings. The process is similar for each.

:::hint{type="info"}
**Note**
Each export type supports an optional test run. See [Test run with error log](docId\:jC7Q0rOTdYYa_w06HheRu) to validate the package before committing to the export.
:::

## Export content items

Export content items to move pages, blocks, and folders between Optimizely CMS environments. Use this to seed a target site with curated content or to back up a portion of the content tree.

1. Go to **Settings** > **Export Data**.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/G8GmuRzPMFK1zBQRzwIrL_aa45305e3cb018d7c04f4e450fe7ee848d7fa0d9e73f92bf7d6b091bcfcbe2f1-image.png)

2. Click **Export content items**.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/uj5qhZsXj0HTHKEMgVHz5_76ac5154d18ede288f081207e3624a82d880c34ce06b1308561abdec3ec769c1-image.png)

3. Click **Select part of a structure** to limit the export to a section of the content tree. The following image shows the *Mosey Bank* branch selected as the export scope.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/RgJM9CRvfxdaXtyVQY7-7_edf510476eb3952ccfc09d3484805f44999cd6e7024112172b6bcaab819b23d3-image.png)

4. (Optional) Select any of the checkboxes:
   - **Include sub items** – Exports the item's children also.
   - **Export files that pages link to** – Exports global assets such as shared blocks and images that the selected item links to.

:::hint{type="info"}
**Note**
CMS includes local assets saved under **For this Page** in the export automatically.
:::

:::Paragraph{listStyleType="disc" indent="2"}
**Automatically export dependent content types** – Includes the content type in the export. Use this for older untyped pages. For typed pages, or when the target application already has this content type, skip this option.
:::

5. Click **Export** to download the file package. The export package downloads to the browser's default download location.

:::hint{type="info"}
**Note**
To update a single content item through export and import, deselect **Include sub items** and export the item. Then import the item and make sure **Update existing content items with matching ID** is selected.
:::

## Export content types

Export content types to share page, block, and media type definitions across environments. Use this to keep schemas in sync between development, test, and production.

1. Go to **Settings** > **Export Data**.
2. Click **Export content types**. Select any or all content types to export.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/ufn_WWAcYVW8yL8O4ejeA_a54bb21396a276b5829a7111ce7d26fd822a18f5ddda22766e5a5d855e63b0e8-image.png)

3. Select **Export property settings** at the bottom of the list. This option includes property settings (such as drop-down list or choice field values) in the export.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/8nVxzqLQqN2FEEL7zjPqm_406311a7a404acb7b36d79ee2d997410b479f21bd1b06ca58c461f0a68c23834-image.png)

4. Click **Export** to download the file package. The export package downloads to the browser's default download location.

## Export frames

Exporting frames transfers the metadata, properties, and structural definitions of layout components or templates. Use this to migrate layouts, back up configurations, and share common structures.

1. Go to **Settings** > **Export Data**.
2. Click **Export frames**. Select any or all frames to export.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/qrZBeG-TGMh6ey5LzMOr9_aebf28b60757f6d72b17675354279608b480fc4a4b66bd7abc67b8ac5a77a80f-image.png)

3. Click **Export** to download the file package. The export package downloads to the browser's default download location.

## Export tabs

Export tabs to reuse tab definitions across CMS instances. Use this to keep editing layouts consistent when promoting work between environments.

1. Go to **Settings** > **Export Data**.
2. Click **Export tabs**. Select any or all tabs to export.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/WlkQ3jHxlVen6dWXn4YgI_c155f0283862b84f5d2fc0fcdc8b79993809257389d2734e81bcce1bd8f7da66-image.png)

3. Click **Export** to download the file package. The export package downloads to the browser's default download location.

## Export blueprints

Export blueprints to transfer reusable page layouts between CMS instances. Use this to standardize page composition patterns across environments.

1. Go to **Settings** > **Export Data**.
2. Click **Export blueprints**. Select any or all blueprints to export.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/FdBBYc3OtL4gdo_1M9Qfm_197f4b918be40316902b25ad66c9e93f1db338060ea588ebb1918984228be744-image.png)

3. Click **Export** to download the file package. The export package downloads to the browser's default download location.

## Export categories

Export categories to share content classification taxonomies between CMS instances. Use this to maintain consistent tagging when content moves across environments.

1. Go to **Settings** > **Export Data**.
2. Click **Export categories**. Select any or all categories to export.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/sYcJdgaW-ctbYg2RjKQ0u_44fa042a0358f5e527409eeab80985ef17288d6f564972b3244f42de5cc99c3c-image.png)

3. Click **Export** to download the file package. The export package downloads to the browser's default download location.

## Export audiences

Export audiences to move visitor group definitions between environments. Use this to apply the same personalization rules in test and production sites.

1. Go to **Settings** > **Export Data**.
2. Click **Export audiences**. Select any or all audiences to export.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/vwjXZtSN6jjv_3blaRHu9_45c3640cbf7a79bb35ab00a9110d93300b587cc1c974b42ec3da32270873ff4d-image.png)

3. Click **Export** to download the file package. The export package downloads to the browser's default download location.

## Export style settings

Export style settings to share visual styling configurations between CMS instances. Use this to keep formatting options consistent across environments.

1. Go to **Settings** > **Export Data**.
2. Click **Export style settings**. Select any or all style settings to export.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/dAsU9rLs1gcm_-1kKQEtL_9bf58f10c9f1509860f05468aef99b062b54ce88c97d76a4b62dde5c7f58359e-image.png)

3. Click **Export** to download the file package. The export package downloads to the browser's default download location.

## Test run with error log

A test run validates the export package before committing to it. Use this to catch missing dependencies or invalid items and avoid failed imports in the destination environment.

Click **Test Run with Error Log** to preview the export result before committing.