Skip to content
Back to Site

Define Migration Scope

Set the migration boundary before purchase or configuration by translating business requirements into data types, volumes, dependencies, exclusions, Add-ons, and validation samples.

Define the migration scope before configuration so every required data type, option, Add-on configuration, 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 Migration scoping. After purchase, Configuration applies the controls available for that purchased migration.

Before defining scope, confirm that:

RequirementWhy it matters
The intended or purchased migration path is knownAvailable data types and configuration controls depend on the selected Source Platform and Target Platform.
The required Migration Service is understoodStandard Migration, Managed Migration, and Custom Migration have different responsibilities and order paths.
Planned or purchased Add-ons are knownEach required Add-on must be included and supported for both platforms. Confirm its exact data and field scope.
Estimated data volumes are availableVolumes calculate Entity Points and support selection of a sufficient Entity Points Plan.
Business owners can approve exclusions and fallbacksScope decisions affect completeness, relationships, and validation.

Use the correct scope category for each requirement.

Requirement typeWhere it is implementedExamples
Data selectionStandard configurationProducts, Categories, Customers, Orders, Reviews, Coupons, Pages.
Additional OptionsStandard configurationClear selected target data, strip HTML from names, import description images, preserve Customer IDs, preserve Order IDs, migrate SEO URLs.
Standard attribute mappingAttribute MappingLanguages, Customer Groups, Order Statuses.
Record-level filteringData Filter Add-onApply field-level conditions per data type, such as including Orders with approved statuses or Products that meet defined source-field conditions.
Value transformationData Transformation Add-onChange a supported value on a retained record before mapping.
Field destination mappingAdvanced Data Mapping Add-onRedirect a supported source or transformed value to a different compatible target field without changing it again as part of mapping.
Database field/column mappingAdvanced Database Mapping Add-onOn a path where both selected sides support Advanced Database Mapping, map a supported source or transformed value through an approved field/table/column destination.
Existing-record field refreshData Update Add-onRefresh selected supported fields on previously migrated records whose Target counterparts still exist; preserve non-selected fields and unassociated data.
Non-standard handlingCustom MigrationThird-party app data, unsupported source fields, bespoke logic, custom platform behavior, or unsupported transformations.

When CSV, XLS, or XML is the Source Platform, the included file workflow migrates Products only and the migration uses Custom Migration. 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.

  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 Target Field, visible Operator, required Value when applicable, 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 Add-on Platform Compatibility 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. Define existing-field updates when required For Data Update, identify eligible previously migrated records, surviving Target counterparts, supported fields and the Target edits that must remain outside the update scope.

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

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

  11. 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.

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

RequirementCorrect control
Exclude an entire supported data typeClear that data type in Select Data.
Include only records that match supported field-level conditionsUse Data Filter when purchased and when the required field/operator combination is exposed for that data type.
Change supported values on retained recordsUse Data Transformation when the required transformation is supported.
Route supported values to another compatible fieldUse Advanced Data Mapping when the required source and target fields are supported.
Refresh selected supported fields on eligible previously migrated recordsUse Data Update; it does not create new or missing Target records.
Apply a non-standard rule, relationship, source, destination, or unsupported conditionDefine the requirement through Custom Migration.

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

A migration can be intentionally narrower than the complete Source Store. Match each requirement to the control that actually owns it:

  • Only Products and Categories: select those data types and exclude Customers and Orders in Select Data.
  • Products from selected Categories only: keep the required data types selected, then use Data Filter when the Product-to-Category condition is supported. Use Custom Migration when the condition cannot be represented by the active filter.
  • Additional new Source data after the most recent migration: pair a Continue action with Continue the previous migration when the project needs the next one-way pass to carry the most recent migration state forward. In the Connect Stores step, select Continue previous migration to reuse the last saved configuration or Continue previous + reconfigure to reopen the Configuration step. Then enable Continue the previous migration in Additional Options and select the supported data types required for that pass.
  • Data from third-party extensions or apps: define the extension/app data, expected target representation, sample records, and pass conditions as Custom Migration scope.

These controls solve different problems. Whole-data-type selection, record-level filtering, later-new-data processing, and third-party/custom data handling should not be substituted for one another.

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

A filter requirement should identify:

InputExample
Data typeProducts
FieldStatus
Operatorequals
ValueEnabled
Additional conditionQuantity does not equal 0
Logical connectorAND
Expected included sampleProduct SKU ABC-100
Expected excluded sampleProduct SKU ABC-200
Relationship checkIncluded Orders must not reference excluded Products.

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.

Add-onUse it forEscalate to Custom Migration when
Data FilterFilter which records migrate by applying supported field-based conditions within a data type.Required fields, operators, or condition behavior remain unsupported.
Data TransformationChange supported values on retained records before mapping.The required transformation behavior is unsupported or depends on bespoke/external logic.
Advanced Data MappingRedirect 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 MappingMap 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.
Data UpdateRefresh selected supported fields on records previously migrated by Next-Cart that still exist on the Target Store.The migration path does not support the required data or fields, or the required update behavior is outside Data Update’s supported scope.
Scope areaDecision to record
Data typesRequired migration data types and supporting data.
ExclusionsIntentionally omitted data types, record groups, or data areas.
Additional OptionsStandard behaviors required in configuration.
Attribute MappingRequired Language, Customer Group, and Order Status mappings.
Data FilterData type, field, operator, comparison value, samples, and relationship expectations.
Data TransformationData type, Target Field, Operator, Value when required, expected transformed value, and edge cases.
Advanced Data MappingData type, source or transformed value, compatible target field, value type, relationship risk, and samples.
Advanced Database MappingSource and Target compatibility, data type, source or transformed value/column, target field/column, value type, consumer behavior, and samples.
Data UpdateEligible existing previously migrated records, selected supported fields, time restriction where available, and preservation samples. See Configure Data Update.
Custom MigrationUnsupported data, logic, transformation, mapping, or platform behavior.
Entity PointsExpected counted records and required plan capacity.
ValidationSamples, pass conditions, blockers, and approved fallbacks.

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 Migration requirements separated from standard configuration and Add-ons;
  • documented dependencies and exclusions;
  • representative validation samples;
  • confirmed Entity Points planning.
CheckPass condition
Data coverageEvery required data type is listed.
Relationship coverageSupporting data and relationship risks are documented.
Configuration classificationStandard options, mappings, Add-ons, and Custom Migration are separated correctly.
Filter readinessEach selective rule has a data type, field, operator, comparison value, samples, and dependency review.
Transformation readinessEach value change has a defined input and expected output.
Mapping readinessEach field or database mapping uses a supported source, compatible target destination, and compatible field/column value type.
CapacityThe planned or purchased Entity Points Plan covers the expected requirement, or a higher plan or upgrade is planned.
ValidationRepresentative and edge-case samples are identified.
IssueWhat to do
The required filter field or operator is unknownRecord the business requirement and confirm Data Filter availability during configuration.
A required Add-on is not in the planned or purchased scopeInclude it before a new order is submitted, or use the supported upgrade path for an existing migration before execution.
The requirement exceeds an Add-onPrepare a Custom Migration requirement with source evidence, expected target output, and pass conditions.
Dependencies cannot be preserved safelyBroaden the scope or define an approved target-side fallback.
Actual volume exceeds the Entity Points PlanUpgrade the Entity Points Plan rather than manually importing remaining data.

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