Overview
Prepare scope, access, service details, Custom Service requirements, acceptance criteria, and security responsibilities before migration work begins.
Prepare Your Migration
Section titled “Prepare Your Migration”Preparation turns business requirements into a controlled migration plan before settings are applied or processing begins.
Preparation separates business requirements from the configuration controls used to implement them. Record the required data types, standard options, filter rules, field and database mapping requirements, value transformations, Custom Service needs, dependencies, and acceptance criteria before execution.
What to prepare
Section titled “What to prepare”| Area | What you need to confirm |
|---|---|
| Purchased service | Migration path, Migration Service, Add-ons, Entity Points Plan, and Order status. |
| Data scope | Required Taxes, Manufacturers, Categories, Products, Customers, Orders, Reviews, Coupons, and Pages where supported. |
| 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/database-column destinations to evaluate through Advanced Database Mapping when both platforms are Open-Source. |
| Value changes | Resulting target-field values to change through Data Transformation when purchased. |
| Custom Service | 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” Before You Begin Confirm purchase details, ownership, security responsibilities, and readiness before migration work starts.
Define Migration Scope Document data types, standard options, Add-on requirements, dependencies, exclusions, and validation samples.
Prepare Source and Target Store Access Identify who owns account, admin, API, hosting, file, approval, and cleanup responsibilities.
Prepare Custom Service Requirements Document Tailored or Custom Add-on needs and other requirements that remain outside standard configuration and the four Standard Add-ons.
Define Acceptance Criteria Set representative samples, pass conditions, evidence requirements, issue severity, and sign-off rules.
Recommended preparation order
Section titled “Recommended preparation order”| Order | Task | Outcome |
|---|---|---|
| 1 | Review the Order and purchased migration. | The migration path, Migration Service, Add-ons, Entity Points Plan, and expiration are known. |
| 2 | Define data and behavior requirements. | Required data types and standard configuration expectations are documented. |
| 3 | Identify filtering, field-mapping, database-mapping, and transformation requirements. | Data Filter, Advanced Data Mapping, Advanced Database Mapping, and Data Transformation needs are separated and applicability is checked. |
| 4 | Identify unsupported requirements. | Custom Service 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. |
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 Service;
- documented dependencies and exclusions;
- named access and decision owners;
- representative validation samples;
- measurable acceptance criteria.
Next step
Section titled “Next step”Open Define Migration Scope to translate business requirements into configuration-ready scope notes.