Overview
Lock down scope, access, ownership, Custom requirements, and acceptance evidence before setup so later configuration and validation rest on explicit decisions.
Prepare Your Migration
Section titled “Prepare Your Migration”Before purchase or configuration, define the data scope and volume, assign project and access owners, identify dependencies and non-standard requirements, and agree on validation conditions. Resolve gaps before execution.
For projects with several owners, decision gates, or evidence streams, use the Migration Project Toolkit to turn these preparation decisions into accountable tasks, risks, validation records, and sign-off evidence.
What to prepare
Section titled “What to prepare”| Area | What you need to confirm |
|---|---|
| Purchase context | Intended or purchased migration path, Migration Service, Add-ons, Entity Points requirement or Plan, and Order status when an order already exists. |
| Data scope | Required data types and volumes supported for the intended Source-to-Target migration path. |
| Standard options | Requirements for target-data clearing, HTML removal from names, description images, identifier preservation, and SEO URLs where supported. |
| Selective requirements | Field-based conditions within a data type to implement through Data Filter when purchased and supported. |
| Field mapping | Supported source fields to redirect through Advanced Data Mapping when purchased. |
| Database mapping | Supported field/table/column destinations to evaluate through Add-on Platform Compatibility and the Schema Registry. |
| Value changes | Supported values to change through Data Transformation before mapping when purchased. |
| Custom Migration | Unsupported data, Tailored or Custom Add-on needs, bespoke logic, relationships, or target behavior requiring scope review. |
| Access | Account, store, credential, hosting, export, and approval ownership. |
| Acceptance criteria | Samples, pass conditions, blockers, acceptable differences, and sign-off ownership. |
Preparation tasks
Section titled “Preparation tasks”Recommended preparation order
Section titled “Recommended preparation order”| Order | Task | Outcome |
|---|---|---|
| 1 | Define or review the migration purchase context. | The intended or purchased migration path, Migration Service, Add-ons, Entity Points requirement or Plan, and relevant order state are known. |
| 2 | Define data and behavior requirements. | Required data types and standard configuration expectations are documented. |
| 3 | Identify processing adjustments and existing-field refresh requirements. | Applicable processing Add-ons and Data Update are distinguished; supported fields, eligible records and preservation requirements are known. |
| 4 | Identify unsupported requirements. | Custom Migration scope is documented with evidence and pass conditions. |
| 5 | Confirm access and ownership. | The right people can provide access, approve changes, and validate results. |
| 6 | Define acceptance criteria. | The team knows what must pass before sign-off. |
Choose the Appropriate Walkthrough
Section titled “Choose the Appropriate Walkthrough”- Use the Demo walkthrough for a limited preparatory test, not as a substitute for the first paid configuration.
- Use the Full Migration walkthrough for the first run under the intended Active purchased migration.
- Use Migration Action Options to plan later paid activity after reviewing its previous result and state.
- Use Run Your Migration for live execution and monitoring.
Expected result
Section titled “Expected result”After completing preparation, you should have:
- an approved data scope;
- a clear distinction between standard configuration, Add-ons, and Custom Migration;
- documented dependencies and exclusions;
- named access and decision owners;
- representative validation samples;
- measurable acceptance criteria.
Next Steps
Section titled “Next Steps”Open Define Migration Scope to translate business requirements into purchase-ready and configuration-ready scope notes. When a new purchase is ready, continue to Purchase a Migration.