Data migration

Sitecore Content Hub™ allows you to import and export data between various environments. This section lists best practices to optimize your data migration.

To optimize your data migration, apply the following best practices:

  • Make sure to check the data you want to migrate and the renditions needed. Images like TIF or PSD can be too heavy 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.

  • Split sizeable Excel migration files into smaller files. 6k items per file is a good size for data ingestion. As the maximum quantity of items in a selection is 2k, you always split your file into multiples of 2k items.

  • Set the Excel import as raw to bypass triggers logic and reduce the data processing time. Indeed, triggers set on a save event for the definition you are migrating might cause extra data processing and performance impact on the migration process.

  • Disable the Triggers extract archive setting for the asset types you do not need to extract the sub-files from. Archive files can be heavy, and extracting their sub-files increases the load on media processing. You can set the Triggers extract archive setting from the Manage menu, in the Taxonomy section.

  • Use the Current activity tab in the Stats section of the Manage menu to follow the migration progress. A healthy state shows the number of completed jobs increase with few or no job failure.

  • Take time to understand why a fetch job or a rendition failed to fix it and avoid similar failures in the future.

  • Perform data migration outside business hours to avoid slowness in 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 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 if a user modifies an asset in the old system while the migration is in progress, Content Hub will not receive the changes. After the migration, asset updates should only happen in Content Hub.


For more information on data migration, see Migrate changes between environments.

Read more about data migration best practices:

Can we improve this article ? Provide feedback