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. The Configuration step later applies the controls available for the purchased migration service.

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 purchased migration path is known	Available data types and configuration controls depend on the selected Source Platform and Target Platform.
The Migration Service is known	Standard Service, Managed Service, and Custom Service have different responsibilities.
Purchased Add-ons are known	Data Filter, Advanced Data Mapping, Advanced Database Mapping, and Data Transformation appear only when purchased and applicable.
Estimated data volumes are available	Volumes help confirm whether the Entity Points Plan is sufficient.
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.
Field destination mapping	Advanced Data Mapping Add-on	Redirect a supported source field to a different compatible target field without changing the value as part of mapping.
Database field/column mapping	Advanced Database Mapping Add-on	On an Open-Source-to-Open-Source path, map a supported field or database column to a compatible target field or column.
Value transformation	Data Transformation Add-on	Change a supported resulting target-field value after applicable mapping stages.
Non-standard handling	Custom Service	Third-party app data, unsupported source fields, bespoke logic, custom platform behavior, or unsupported transformations.

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 field mappings Record the data type, supported source field, intended compatible target field, value type, relationship risk, and samples. These mappings are implemented through Advanced Data Mapping when purchased and supported.

6. Define database mappings when the path qualifies If both the Source Platform and Target Platform are Open-Source, record any supported source field or database column that must map to a compatible target field or column. Include value-type compatibility and the target-side behavior that depends on the stored value.

7. Define value transformations Record the data type, resulting target field, required expression, expected transformed value, and sample records. These transformations are implemented through Data Transformation after applicable mapping stages.

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 Compare expected successfully migrated eligible records with the purchased Entity Points Plan.

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.

Current 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.
Advanced Data Mapping	Redirect supported source fields to compatible target fields without changing the value as part of mapping.	The required source field or destination is unsupported, or value compatibility cannot be satisfied.
Advanced Database Mapping	Map supported fields/database columns on an Open-Source-to-Open-Source path.	One platform is Non-Open-Source, the required field/column is unsupported, or bespoke schema behavior is required.
Data Transformation	Change supported resulting target-field values after applicable mapping stages.	The required transformation behavior is unsupported or depends on bespoke/external logic.

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.
Advanced Data Mapping	Data type, source field, compatible target field, value type, relationship risk, and samples.
Advanced Database Mapping	Open-Source path confirmation, data type, source field/column, target field/column, value type, consumer behavior, and samples.
Data Transformation	Data type, resulting target field, expression, expected transformed value, and edge cases.
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;
• configuration-ready Add-on requirements where purchased;
• 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 Entity Points Plan covers the expected eligible records or an 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 was not purchased	Review the Order and request the appropriate purchase or service update 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 step

Open Prepare Custom Service Requirements for requirements that are not fully covered by standard configuration or the purchased Add-ons.