Skip to content
Back to Site

Select Data to Migrate

Choose the supported data types included in the migration and review their dependencies.

Select the data types that belong in the migration before configuring options, mappings, or purchased features. This defines which kinds of records Next-Cart can process; it does not set record quantities or create record-level filter rules.

Confirm that:

  • the migration scope is approved;
  • both store connections are working;
  • representative validation records are identified;
  • relationship-dependent data has been considered;
  • the Entity Points Plan has enough capacity for the intended counted records.
Data typeTypical data included
TaxesTax classes, rates, and jurisdiction rules.
ManufacturersBrand and manufacturer records.
CategoriesProduct category tree and hierarchy.
ProductsProduct catalog, variants, options, images, and inventory where supported.
CustomersCustomer accounts, addresses, and groups.
OrdersOrder history, line items, totals, shipping, and related states.
ReviewsProduct reviews and customer ratings.
CouponsDiscount codes, vouchers, and promotions.
CMS PagesStatic pages and landing-page content.
Blog PostsBlog articles, categories, and authors.

As a result, the available list can differ between migration paths.

When a selected data type requires supporting data, Next-Cart selects the dependency automatically.

For example, Reviews can require Products because each Review must remain connected to a Product.

Other relationship considerations include:

  • Products can depend on Manufacturers, Categories, and Taxes;
  • Orders can depend on Customers, Products, Taxes, and Coupons;
  • Reviews can depend on Products and Customers.

Next-Cart’s core processing sequence is:

Taxes → Manufacturers → Categories → Products → Customers → Orders → Reviews → Coupons → CMS Pages → Blog Posts

  1. Open Data

    Open Data in the migration configuration.

  2. Review the available data types

    Confirm that the displayed data types match the approved migration scope.

  3. Select the required data types

    Select each data type that must be included. Use Select All only when the full supported scope is required.

  4. Review automatically selected dependencies

    Check each dependency notice and confirm that the required parent data should remain selected.

  5. Check the selection count

    Confirm that the selection count matches the intended number of data types.

  6. Continue to Options

    Select Next after the data selection is complete.

Selecting a data type does not reserve a fixed record quantity. Entity Points are calculated from eligible counted records covered by the service, not from the number of data types selected. Support data such as Taxes, Manufacturers, and Categories does not consume Entity Points independently.

Records already counted under the same purchased migration service do not consume Entity Points again merely because they are processed during another supported migration activity.

After completing Data:

  • at least one supported data type is selected;
  • the selection matches the approved scope;
  • required dependencies are included;
  • the displayed selection count is correct;
  • the configuration is ready for Additional Options.
CheckPass condition
ScopeEvery selected data type is required for the intended result.
DependenciesEvery required parent dependency remains selected or already exists on the target store with reliable matching.
CountThe selection count matches the intended number of data types.
Entity PointsThe expected counted-record scope fits the available Entity Points Plan.
ValidationRepresentative records are identified for each selected data type.
IssueWhat to do
A required data type is not shownThe source or target data model may not support that data type for the migration path. Submit a ticket if the requirement is essential.
Next is unavailableSelect at least one data type and resolve any dependency or connection warning.
An unexpected parent is selected automaticallyReview the dependency notice. Keep it selected unless the relationship is already satisfied on the target store.
The scope exceeds the Entity Points PlanUpgrade the plan or revise the approved scope before execution.
You need only certain records within a data typeUse the Data Filter Add-on when purchased. Data selection alone cannot filter individual records.

Continue to Configure Additional Options.