commercetools Migration: Move Catalog & Order Data Without Losing Trust
Migrate into commercetools with an inventory, field map, pilot import, dual-run week, and validation — so history survives and operators trust the new system.
Quick answer
Migrate into commercetools with an inventory of products, prices, customers, and order history, a field map, a pilot import, a dual-run week, and validation with the people who live in the data — so history survives and the team trusts the new system.
- Inventory source objects
- Map fields before bulk load
- Pilot one site / one role / one team
- Dual-run for a week
- Validate with sceptic users
commercetools migration rules
- Inventory first — Typical objects: products, prices, customers, and order history.
- Pilot beats big-bang — Prove a small commercetools import before you move everything.
- Integrations after the pilot — Research names Stripe, PayPal, and Zapier on the commercetools side — confirm the connectors your commerce loop depends on.
- Do not migrate the wrong job — commercetools is composable enterprise commerce platform. Do not import a CRM pipeline or a marketing course catalogue and expect it to become composable enterprise commerce platform.
commercetools migration map
1. Inventory and map
List products, prices, customers, and order history. Map required fields and owners. Never invent list prices here — confirm plans, processing, and quote terms on /pricing/commercetools/. Worked example: Northline Enterprise (MACH / headless programme) discovers duplicate SKUs or customer IDs in the spreadsheet before the first import — and fixes identity before volume.
2. Pilot import
Import one site, one role, or one team. Run stand up a project, model a catalog via APIs, and complete a test order on a composed storefront on the pilot set. Worked example: Northline Enterprise (MACH / headless programme) will not schedule a cutover until the pilot can a merchandiser can update a SKU via the commerce engine and a test order completes.
3. Dual-run and cutover
Run old and new in parallel for a week. Spot-check records sceptic users care about, then freeze the legacy source. Worked example: Northline Enterprise (MACH / headless programme) keeps the old store or spreadsheet until commercetools matches for seven consecutive days.
commercetools checklist
Bring these questions to every demo
Ask vendors to show the workflow live, not just describe it.
- 1Inventory source objectsproducts, prices, customers, and order history
- 2Run a pilot importOne segment first; fix mapping before bulk.
- 3Validate with operatorsSpot-check records they care about before cutover.
4. Inventory what must move into commercetools
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: Mid-market and enterprise brands assembling composable storefronts migrates active records only and archives the rest as read-only exports.
5. Run parallel cutover with a rollback path
Keep the old system read-only until commercetools passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: Mid-market and enterprise brands assembling composable storefronts caps parallel run at two weeks with daily checkpoint notes.
6. Verify counts and permissions after import
Reconcile user counts, role permissions, and a sample of migrated records. Research lists Stripe, PayPal, and Zapier for commercetools. Confirm which are native vs API before go-live.
7. Inventory what must move into commercetools
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: Mid-market and enterprise brands assembling composable storefronts migrates active records only and archives the rest as read-only exports.
8. Run parallel cutover with a rollback path
Keep the old system read-only until commercetools passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: Mid-market and enterprise brands assembling composable storefronts caps parallel run at two weeks with daily checkpoint notes.
9. Verify counts and permissions after import
Reconcile user counts, role permissions, and a sample of migrated records. Research lists Stripe, PayPal, and Zapier for commercetools. Confirm which are native vs API before go-live.
10. Inventory what must move into commercetools
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: Mid-market and enterprise brands assembling composable storefronts migrates active records only and archives the rest as read-only exports.
11. Run parallel cutover with a rollback path
Keep the old system read-only until commercetools passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: Mid-market and enterprise brands assembling composable storefronts caps parallel run at two weeks with daily checkpoint notes.
12. Verify counts and permissions after import
Reconcile user counts, role permissions, and a sample of migrated records. Research lists Stripe, PayPal, and Zapier for commercetools. Confirm which are native vs API before go-live.
13. Before you sign with commercetools
Confirm the qualifying plan, non-admin proof, and integration owners in writing. Store quotes next to /pricing/commercetools/ and the evaluation scorecard so finance can audit the same assumptions at renewal.
14. Write the decision memo
Name the job, the qualifying commercetools configuration, and what you are not buying yet. If stakeholders cannot explain why an alternative lost, the trial was not fair.
Frequently asked questions
Can we skip the dual-run?
Only if the dataset is tiny and reversible. Most SMB/mid teams regret skipping a week of parallel use.
What if history will not map cleanly?
Import active records first. Archive messy history as files rather than poisoning the new system of record.
Was this article helpful?
Have more questions? Contact our support team.
SoftwareGlimpse Updates
Want clearer software shortlists? Get buying guides and comparisons by email.
Newsletter coming soon.