---
title: Import data to CMS 13
slug: cms-13/docs/import-data-to-cms-13
docTags: 
createdAt: 2026-07-30T20:22:09.640Z
---

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

Import a single `.episerverdata` package into Optimizely CMS 13 to move content items, content types, and linked files between environments. Administrators use import to promote work from development to test or production without rebuilding content manually. Sign in with an account in the Content Admins group or an equivalent Opti ID role before starting.

Use **Import Data** to load content exported from the same or another Optimizely application.

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

1. Go to **Settings** > **Import Data**.
2. Click **Choose File** and select the file to import. Files must end with `.episerverdata` for the import to work. Export packages created using [Export data from CMS 13](docId\:jC7Q0rOTdYYa_w06HheRu) use this format.

:::hint{type="info"}
**Note**
The maximum supported file size is 500 MB.
:::

3. Click **Select Content** to choose the destination for the imported files.

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

4. Select **Update existing content items with matching ID** to keep the same globally unique identifiers (GUIDs) for imported items (such as pages, shared blocks, and files) as they had on the source application.
   The import function checks whether a GUID already exists. If it does, the item is updated when the imported item has a later changed date than the existing item. Content items with the same IDs are replaced instead of added.
   If the exported pages contain links to shared blocks and media, select **Export files that pages link to** when exporting so those assets are updated during import.
5. Clear **Update existing content items with matching ID** to import items with new IDs.
   If you import to the same application you exported from, shared blocks and media merge into folders with the same name in the assets panel.
   Duplicated items receive a number appended to the name. For example, exporting `ABC` and importing it as a copy on the same application results in two items: `ABC` and `ABC2`. This also affects the URL, which in the case of the copied item would be `www.exampleapplication.com/abc2`.
6. From the **Language** drop-down list, select **All** if the export package contains multiple language versions. To import one language, select that language.
7. Click **Upload and Verify File** to verify the file content. The files are read and checked, and verification information displays. If the verification report shows errors, resolve the issues in the source before importing. Common causes are missing content types in the target environment and file sizes exceeding the limit.

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

8. Click **Begin Import**.