Working template: ERP data migration: plan cutover and prove the opening state

ERP data migration: plan cutover and prove the opening state

Editorial working template
https://www.ecommerce.spot/en/guides/erp-data-migration-cutover-checklist
Reviewed: 2026-10-29

Record your systems, decisions and acceptance evidence. Use this template for the brief, then confirm demonstrated capabilities and unresolved limits in the actual proposal.

Project / owners / date:
________________________________________

ERP data migration establishes the business state your replacement system will start from. It is a different job from keeping a live store connected to an ERP. At cutover, product identities, remaining order work, reservations and financial opening values must agree. Plan the evidence and decision points before moving the data.

1. Scope
List configuration, master records, open transactions and historical evidence with their destination.
Your inputs / decision:
________________________________________
Evidence / owner / unresolved issue:
________________________________________

2. Identity crosswalk
Record source IDs, target IDs and relationships that must survive.
Your inputs / decision:
________________________________________
Evidence / owner / unresolved issue:
________________________________________

3. Transformations
Specify units, rounding, currency, timestamps and duplicate-resolution decisions.
Your inputs / decision:
________________________________________
Evidence / owner / unresolved issue:
________________________________________

4. Remaining work
Record open quantities, payments, reservations and accepted external activities at the boundary.
Your inputs / decision:
________________________________________
Evidence / owner / unresolved issue:
________________________________________

5. Cutover sequence
Name the extract, delta method, writing boundary, owners and pause authority.
Your inputs / decision:
________________________________________
Evidence / owner / unresolved issue:
________________________________________

6. Acceptance
Define expected reconciliations and the business workflow each owner must approve.
Your inputs / decision:
________________________________________
Evidence / owner / unresolved issue:
________________________________________

7. Recovery and support
Separate pre-launch rollback from recovery after new target transactions; assign early-life monitoring.
Your inputs / decision:
________________________________________
Evidence / owner / unresolved issue:
________________________________________

Acceptance checklist
[ ] Migration scope and access to necessary history are approved.
[ ] Old and new identities and transformation rules are retained.
[ ] Open work has line-level remaining quantities and external references.
[ ] Opening stock and reservations use the same definitions.
[ ] The writing boundary, delta process and pause decision are rehearsed.
[ ] Business owners approve quantities, balances, relationships and operating cases.
[ ] Early-life support and the end of parallel operation have owners.

Article references
Microsoft Learn: data migration for Dynamics 365 projects: https://learn.microsoft.com/en-us/dynamics365/guidance/resources/migrate-data
Microsoft Learn: cutover strategy and rehearsal: https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/prepare-go-live-cutover-strategy
Microsoft Learn: implementation test types: https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/testing-strategy-test-types
Microsoft Learn: data entities and field mapping: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/build-consuming-data-entities