Export data from CMS 13

You can 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 using Import data to CMS 13.

You can export from 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. See also Import data to CMS 13.

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.

   
   

2. Select Export content items. 

   

3. Click Select part of a structure to limit the exported data to part of the content tree. The following image shows that exporting occurs only for the Mosey Bank branch.

   

4. (Optional) Select any of the checkboxes:

   • Include sub items – Exports the item's children also.

   • Export files that the pages link to – Exports global assets (such as shared blocks and images and so on) that the selected item links to.

     📘

     Note

     Local assets (saved under For this Page) are included in the export.

   • Automatically export dependent content types – This option is mostly used for older untyped pages and specifies that the content type is included in the export. For newer, typed pages or if the import application already has this content type, selecting this option is unnecessary.

5. Optional. See Test run with error log in this article.

6. Click Export to download the file package. Your export package is saved to your web browser's default download location. 

📘

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. Select Export content types. Select any or all content types to export.

   

3. Select the Export property settings option that appears at the bottom of the list when you select one or more content types. Selecting this option ensures that property settings, such as dropdown or choice field values, are included in the export.

   

4. Optional. See Test run with error log in this article.

5. Click Export to download the file package. Your export package is saved to your web browser's default download location.

Export frames

When you export frames, you export the metadata, properties, and structural definitions of layout components or templates. This lets you migrate layouts, backup configurations, and share common structures.

1. Go to Settings > Export data.

2. Select Export frames. Select any or all frames to export.

   

3. Optional. See Test run with error log in this article.

4. Click Export to download the file package. Your export package is saved to your web 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. Select Export tabs. Select any or all tabs to export.

   

3. Optional. See Test run with error log in this article.

4. Click Export to download the file package. Your export package is saved to your web 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. Select Export blueprints. Select any or all blueprints to export.

   

3. Optional. See Test run with error log in this article.

4. Click Export to download the file package. Your export package is saved to your web 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. Select Export categories. Select any or all categories to export.

   

3. Optional. See Test run with error log in this article.

4. Click Export to download the file package. Your export package is saved to your web 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. Select Export audiences. Select any or all audiences to export.

   

3. Optional. See Test run with error log in this article.

4. Click Export to download the file package. Your export package is saved to your web 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. Select Export style settings. Select any or all style settings to export.

   

3. Optional. See Test run with error log in this article.

4. Click Export to download the file package. Your export package is saved to your web 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 how the export will turn out before you export the content.