This is the early access documentation preview for Custom Views. This documentation might not be in sync with our official documentation.
Plan migration of data
A data migration plan maps out the data types, the source of truth for the data, and what needs to be migrated manually from the other system.
We recommend a data cleansing process to take place before the migration happens.
Here are a few considerations as you create the plan:
- Customer profiles are the main focus and take the most amount of effort since customer passwords cannot be copied over to commercetools Composable Commerce. Find more guidance on how to migrate customer accounts in this guide.
- You do not need to manually migrate types of data where the source of truth is not commercetools. For example, if you have a PIM, you use an integration with commercetools to sync the Product data initially. The same goes for Orders, Inventory, Pricing, etc.
- It is not recommended to migrate all of your historical orders to commercetools. If the source of truth for your orders is another system, the data in commercetools is redundant. The recommendation is to migrate only the orders that are still in the return period or not migrate orders at all.
- Generative AI can significantly reduce the effort of mapping data to the commercetools format. You can generate the import format automatically and all you need to do is execute the script.