Skip to content
Back to Site

Overview

Lock down scope, access, ownership, Custom requirements, and acceptance evidence before setup so later configuration and validation rest on explicit decisions.

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.

AreaWhat you need to confirm
Purchase contextIntended or purchased migration path, Migration Service, Add-ons, Entity Points requirement or Plan, and Order status when an order already exists.
Data scopeRequired data types and volumes supported for the intended Source-to-Target migration path.
Standard optionsRequirements for target-data clearing, HTML removal from names, description images, identifier preservation, and SEO URLs where supported.
Selective requirementsField-based conditions within a data type to implement through Data Filter when purchased and supported.
Field mappingSupported source fields to redirect through Advanced Data Mapping when purchased.
Database mappingSupported field/table/column destinations to evaluate through Add-on Platform Compatibility and the Schema Registry.
Value changesSupported values to change through Data Transformation before mapping when purchased.
Custom MigrationUnsupported data, Tailored or Custom Add-on needs, bespoke logic, relationships, or target behavior requiring scope review.
AccessAccount, store, credential, hosting, export, and approval ownership.
Acceptance criteriaSamples, pass conditions, blockers, acceptable differences, and sign-off ownership.
OrderTaskOutcome
1Define 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.
2Define data and behavior requirements.Required data types and standard configuration expectations are documented.
3Identify 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.
4Identify unsupported requirements.Custom Migration scope is documented with evidence and pass conditions.
5Confirm access and ownership.The right people can provide access, approve changes, and validate results.
6Define acceptance criteria.The team knows what must pass before sign-off.
  • 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.

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.

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.