Define Migration Scope

Define Migration Scope

Define the migration scope before configuration so every required data type, option, Add-on rule, dependency, exclusion, and expected result is clear.

Scope preparation records what the business needs. Before purchase, it supports Service selection, volume sizing, Add-on selection, and Custom Service scoping. After purchase, Configuration applies the controls available for that purchased migration.

Entered purchase quantities are not filters

Data volumes entered during purchase help calculate Entity Points and recommend an Entity Points Plan. They do not limit which source records are processed during migration.

Prerequisites

Before defining scope, confirm that:

Requirement	Why it matters
The intended or purchased migration path is known	Available data types and configuration controls depend on the selected Source Platform and Target Platform.
The required Migration Service is understood	Standard Service, Managed Service, and Custom Service have different responsibilities and order paths.
Planned or purchased Add-ons are known	Data Filter, Data Transformation, Advanced Data Mapping, and Advanced Database Mapping must be included in the purchased scope before they can appear when applicable.
Estimated data volumes are available	Volumes calculate Entity Points and support selection of a sufficient Entity Points Plan.
Business owners can approve exclusions and fallbacks	Scope decisions affect completeness, relationships, and validation.

Scope categories

Use the correct scope category for each requirement.

Requirement type	Where it is implemented	Examples
Data selection	Standard configuration	Products, Categories, Customers, Orders, Reviews, Coupons, Pages.
Additional Options	Standard configuration	Clear selected target data, strip HTML from names, import description images, preserve Customer IDs, preserve Order IDs, migrate SEO URLs.
Standard attribute mapping	Advanced Attributes Mapping	Languages, Customer Groups, Order Statuses.
Record-level filtering	Data Filter Add-on	Apply field-level conditions per data type, such as including Orders with approved statuses or Products that meet defined source-field conditions.
Value transformation	Data Transformation Add-on	Change a supported value on a retained record before mapping.
Field destination mapping	Advanced Data Mapping Add-on	Redirect a supported source or transformed value to a different compatible target field without changing it again as part of mapping.
Database field/column mapping	Advanced Database Mapping Add-on	On a path where both selected sides support Advanced Database Mapping, map a supported source or transformed value through an approved field/table/column destination.
Non-standard handling	Custom Service	Third-party app data, unsupported source fields, bespoke logic, custom platform behavior, or unsupported transformations.

File-based Source scope

When CSV, XLS, or XML is the Source Platform, the included file workflow migrates Products only and the migration uses Custom Service. If Customers, Orders, another entity type, or special business logic is required, record it as explicit Custom scope so the additional handling can be approved and developed for that migration. Do not treat additional files as automatically supported data inputs.

Define the scope

1. List the required data types Record every required data type. Include supporting data needed to preserve relationships.

2. Record intentional exclusions State which data types, record groups, or data areas are intentionally excluded and why.

3. Document standard Additional Option requirements Record requirements for target-data clearing, HTML removal from names, description images, identifier preservation, and SEO URLs where supported.

4. Define record-level conditions For each selective requirement, record the data type, source field, operator, value, and relationship dependencies. These conditions are implemented through Data Filter when purchased and supported.

5. Define value transformations Record the data type, supported field or value, required expression, expected transformed value, and sample records. These transformations are implemented through Data Transformation on records retained by Data Filter before later mapping stages.

6. Define field mappings Record the data type, supported source or transformed value, intended compatible target field, value type, relationship risk, and samples. These mappings are implemented through Advanced Data Mapping when purchased and supported.

7. Define database mappings when the path qualifies When Advanced Database Mapping Platform Eligibility confirms support for the selected Source and Target, record any supported source or transformed value or database column that must map to a compatible target field or column. Use the Schema Registry for standard structures and include Value Type compatibility plus the target-side behavior that depends on the stored value.

8. Identify Custom Service requirements Move any unsupported extraction, third-party data, bespoke transformation, unsupported filter logic, or custom platform behavior into a separate Custom Service requirement.

9. Select validation samples Choose representative and edge-case records for every high-risk data type or configuration requirement.

10. Confirm Entity Points capacity Use the estimated Products, Customers, Orders, and Blog Posts volumes to calculate the required Entity Points. Before purchase, select a sufficient Plan in Checkout. For an existing migration, compare the requirement with the purchased Entity Points Plan.

Migrate only the required scope

A migration does not have to include every supported data type or every eligible record. Use the control that matches the requirement.

Requirement	Correct control
Exclude an entire supported data type	Clear that data type in Select Data.
Include only records that match supported field-level conditions	Use Data Filter when purchased and when the required field/operator combination is exposed for that data type.
Change supported values on retained records	Use Data Transformation when the required transformation is supported.
Route supported values to another compatible field	Use Advanced Data Mapping when the required source and target fields are supported.
Apply a non-standard rule, relationship, source, destination, or unsupported condition	Define the requirement through Custom Service.

Entity Points determine purchased capacity for counted records. They do not replace scope selection, filtering, or approved Custom requirements.

Record-level filtering requirements

Use Data Filter to apply supported field-level conditions that determine which records migrate for each selected data type.

A filter requirement should identify:

Input	Example
Data type	Products
Field	Status
Operator	equals
Value	Enabled
Additional condition	Quantity does not equal 0
Logical connector	AND
Expected included sample	Product SKU ABC-100
Expected excluded sample	Product SKU ABC-200
Relationship check	Included Orders must not reference excluded Products.

Selective scope can break relationships

Filtering Products, Customers, Orders, Categories, or Reviews can remove records needed by related data. Define relationship expectations before approving a filter.

Standard options are not Add-ons

Do not classify these requirements as Add-ons:

• clear selected target-store data before migration;
• strip HTML tags from Category and Product names;
• import images embedded in supported descriptions;
• preserve supported Customer IDs;
• preserve supported Order IDs;
• migrate supported SEO URL information.

These are standard Additional Options when shown for the migration configuration.

Standard Add-ons

Add-on	Use it for	Escalate to Custom Service when
Data Filter	Filter which records migrate by applying supported field-based conditions within a data type.	Required fields, operators, or condition behavior remain unsupported.
Data Transformation	Change supported values on retained records before mapping.	The required transformation behavior is unsupported or depends on bespoke/external logic.
Advanced Data Mapping	Redirect supported source or transformed values to compatible target fields without changing them again as part of mapping.	The required source field or destination is unsupported, or value compatibility cannot be satisfied.
Advanced Database Mapping	Map supported source or transformed values through eligible field/table/column destinations when the selected Source setup is supported and the Target Platform supports database-mapping destinations.	The selected Source setup or Target Platform is unsupported, the required field/table/column is unavailable, or bespoke schema behavior is required.

Scope worksheet

Scope area	Decision to record
Data types	Required migration data types and supporting data.
Exclusions	Intentionally omitted data types, record groups, or data areas.
Additional Options	Standard behaviors required in configuration.
Advanced Attributes Mapping	Required Language, Customer Group, and Order Status mappings.
Data Filter	Data type, field, operator, comparison value, samples, and relationship expectations.
Data Transformation	Data type, supported field or value, expression, expected transformed value, and edge cases.
Advanced Data Mapping	Data type, source or transformed value, compatible target field, value type, relationship risk, and samples.
Advanced Database Mapping	Source and Target compatibility, data type, source or transformed value/column, target field/column, value type, consumer behavior, and samples.
Custom Service	Unsupported data, logic, transformation, mapping, or platform behavior.
Entity Points	Expected counted records and required plan capacity.
Validation	Samples, pass conditions, blockers, and approved fallbacks.

Expected result

After defining scope, you should have:

• an approved list of data types;
• documented standard Additional Option requirements;
• purchase-ready or configuration-ready Add-on requirements;
• Custom Service requirements separated from standard configuration and Add-ons;
• documented dependencies and exclusions;
• representative validation samples;
• confirmed Entity Points planning.

Verify the scope

Check	Pass condition
Data coverage	Every required data type is listed.
Relationship coverage	Supporting data and relationship risks are documented.
Configuration classification	Standard options, mappings, Add-ons, and Custom Service are separated correctly.
Filter readiness	Each selective rule has a data type, field, operator, comparison value, samples, and dependency review.
Transformation readiness	Each value change has a defined input and expected output.
Mapping readiness	Each field or database mapping uses a supported source, compatible target destination, and compatible field/column value type.
Capacity	The planned or purchased Entity Points Plan covers the expected requirement, or a higher plan or upgrade is planned.
Validation	Representative and edge-case samples are identified.

Failure handling

Issue	What to do
The required filter field or operator is unknown	Record the business requirement and confirm Data Filter availability during configuration.
A required Add-on is not in the planned or purchased scope	Include it before a new order is submitted, or use the supported upgrade path for an existing migration before execution.
The requirement exceeds an Add-on	Prepare a Custom Service requirement with source evidence, expected target output, and pass conditions.
Dependencies cannot be preserved safely	Broaden the scope or define an approved target-side fallback.
Actual volume exceeds the Entity Points Plan	Upgrade the Entity Points Plan rather than manually importing remaining data.

Next Steps

Open Prepare Custom Service Requirements for requirements that are not fully covered by standard configuration or Standard Add-ons. If the scope is ready for a new Standard or Managed purchase, continue to Purchase a Migration.