Importing and exporting data
This section lists the best practices recommended to optimize importing, exporting, or migrating your data within Sitecore Content Hub.
Import and export Content Hub data
-
When migrating from a previous assets management system to Content Hub, make sure to lock assets for edit or mark them as migrated. The migration takes time, and any changes made to the source environment after migration begins will not be carried over to the destination. After the migration, update your assets only in Content Hub.
-
Migrate the data outside business hours, to avoid slowing down the application. However, the Excel import priority is lower than UI operations, so users should not see delays in file preview generations or bulk download orders, even if you perform the data migration during business hours.
-
When importing portal pages, some or all pages might return a 403 or 404 error.
-
Always have one source environment and one target environment. Complete a full export from the source environment and import the entire package to the target environment.
-
To prevent conflicts resulting from mismatched identifiers, avoid manually creating entities in the target environment that duplicate those in the source environment.
-
If you need to make changes to the source environment, make them before creating the export package, to avoid having to export again afterwards.
-
Check the files you want to migrate and their renditions. Large image formats, like TIF or PSD, can be difficult to render with the default 8GB memory media processing agents.
-
Add a batchID property to your entity definition and a corresponding column in the Excel file, to easily retrieve the batch and delete the related item if necessary.
-
The maximum number of items in a selection is 2,000. If any Excel file you want to import has more than this, split it into smaller files containing no more than 2,000 rows each.
-
Ensure import settings are set to
rawImport
to bypass triggers logic and reduce data processing time. To avoid issues with mass edit in table operations, turn off the rawImport flag when the import finishes. -
For taxonomies, you can disable the Triggers extract archive setting for asset types whose subfiles you don't need to extract. Archive files can be large, and extracting their subfiles increases the load on media processing.
-
When importing data, we recommend you clear the Extract content check box on the Parameters tab for the processing task to avoid impacting performance.
For more information on data migration, see Migrate changes between environments.