Migration FAQ
Migrating system and schema configurations and moving or copying data is a complex undertaking with various cost implications.
Note
To evaluate the best migration approach for you, contact Sitecore professional services or a certified Sitecore partner.
What is the best way to migrate Content Hub data?
The following table summarizes the methods available to migrate data.
| Tool | Use |
|---|---|
| Import/Export | Use for portal pages, complex UI layouts, entity definitions, and schemas. Use packages instead of the CLI for layout migrations because pages and components have strict order dependencies. Does not have CI/CD automation. |
| Content Hub CLI | Use for settings, triggers, scripts, and action rules. Best option for CI/CD pipeline integrations. Supports CI/CD automation. |
| Support request | Use when you need a full environment clone (data and configuration) in cases where you want production assets in lower environments. |
Are there any other resources available to help me?
Information architects and technical users can find more detailed guidance about domain modeling and data migration in the Accelerate Cookbook for Content Hub, a collection of recipes that provides information to help you successfully set up, configure, and implement Content Hub.
Additional information about moving data between Content Hub environments is available in the Sitecore Support Knowledgebase.
If you have suggestions for improving this article, let us know!