Skip to content
Back to Site

Supported Data Types and Processing Order

Determine what the selected path can process, why availability varies, how data relationships constrain selection, and the sequence Next-Cart uses for supported data.

The selected migration path determines which data types appear in Select Data and the sequence in which Next-Cart processes them.

Selecting a data type includes that kind of supported source data in the migration scope. It does not set a record quantity, create a record-level filter, or guarantee that every source field and relationship has a direct target equivalent.

The active migration path determines which data types can be selected. The following top-level types can appear when supported by the exact Source Platform, Target Platform, migration path, and selected activity. Reviews and Coupons are unavailable in Demo Migration.

  • Taxes
  • Manufacturers
  • Categories
  • Products
  • Customers
  • Orders
  • Reviews: unavailable in Demo Migration.
  • Coupons: unavailable in Demo Migration.
  • CMS Pages
  • Blog Posts

Treat the list as a top-level scope guide, not proof that every field, relationship, extension-owned record, or platform-specific subtype is included. Select Data shows what is available for the active migration. For variants, options, relationships, media, subscriptions, downloadable assets, app/plugin data, or other specialized structures, qualify the exact requirement against the active path and use Custom Migration when the required source or target representation falls outside Standard scope.

Common fields and relationships within supported data types

Section titled “Common fields and relationships within supported data types”

When the active path supports the applicable data type, migration scope can include the following source data. Exact availability still depends on the Source Platform, Target Platform, and path.

Data typeCommon included data
ProductsTitles, descriptions, images, prices, SKUs, stock levels, variants, and attributes.
CustomersNames, emails, phone numbers, shipping addresses, and billing addresses. Password continuity is not a generic Customer field; use the exact Customer Password Plugin pair matrix when password continuity is required.
OrdersOrder details, line items, Customer information or Customer links, Order statuses, payment details, and shipping details.
CategoriesCategories and subcategories, descriptions, images, and Product-Category relationships when supported by the active path.
ReviewsReview records and Product ratings where their source and target representation is supported.
Blog Posts / CMS PagesArticles, pages, and other supported content.
Coupons / TaxesDiscount-code and tax-rule data when available for the path.
Custom dataAdditional custom fields or non-standard structures only when they are covered by supported mapping/Add-on scope or an approved Custom Migration requirement.

Migrating the participating records does not remove the need to validate relationships. Product-Category, Order-Customer, Order-Product, Review-Product, and other relationship data must still point to the intended Target Store records.

Data-type availability is determined by the supported migration path, not by a universal Next-Cart catalog.

SituationOperational meaning
A data type can be selected in Select DataIt is available for the selected migration path and active configuration.
A data type does not appearThe standard path does not expose it for selection. Confirm the platform guides and purchased scope before treating the absence as an interface defect.
A data type appears but a source field is not representedThe field can be unsupported, mapped to a different target structure, transformed through an approved rule, or require Custom Migration assessment.
The source contains app, plugin, module, or external-system dataDo not assume that selecting a related standard data type includes that separate data source. Confirm the supported source location and agreed scope.
A purchased Add-on is availableThe Add-on can filter, transform, redirect or refresh supported data within its own boundary. Data Update refreshes only selected supported fields on eligible existing records; no Add-on creates a new supported data type.

Use Add-ons, Customization, and Custom Migration Boundaries when the required source or target behavior extends beyond standard data-type support.

How to qualify a migration-capability question

Section titled “How to qualify a migration-capability question”

A question such as “Can this be migrated?” often refers to more than the top-level data type. Qualify the exact requirement before treating a selected data type as proof of complete support.

Requirement patternWhat to verify
Entire data type, such as Products, Customers, Orders, Reviews, or Blog PostsThe data type appears for the active migration path and is included in Select Data.
Product variants, options, attributes, Manufacturers, brands, multilingual values, or multi-store scopeThe source structure is accessible, the selected path represents the required fields or structure, and the Target Platform has an approved representation that preserves the required meaning.
Relationship data, such as Product-Category, related Products, Customer-Order, Review-Product, or parent-child structuresBoth required records and the relationship itself must be supported and validated. Migrating both record types does not by itself prove that every relationship is preserved.
Invoices, shipments, credit documents, subscriptions, gift cards, abandoned carts, downloadable assets, attachments, or other specialized structuresDo not infer support from Orders, Products, or another related top-level type. Confirm the exact source structure and agreed path or Custom scope.
App, plugin, module, custom-table, or external-system dataConfirm that the source location is exposed through the supported connection and included in the agreed scope. A related standard entity does not automatically include extension-owned data.
Images, video references, downloadable media, or other assetsVerify both the data reference and asset accessibility, then validate the Target Platform representation and association with the correct parent record.
Target notifications, email automation, storefront behavior, tax behavior, payment behavior, or application behaviorTreat this as target-store operation unless the migration scope explicitly owns the behavior. Migrating historical records does not automatically configure future target behavior.

Use Platform Data Models and Migration Boundaries when the source and target represent the same business concept differently. Use Prepare Custom Migration Requirements when the required data, relationship, extraction, or target behavior remains outside the Standard migration path.

Some selected records require parent or related records to preserve usable relationships. Next-Cart can select required dependencies automatically when the selected path establishes them.

Common relationship patterns include:

  • Products can depend on Manufacturers, Categories, Taxes, attributes, options, and inventory structures;
  • Orders can depend on Customers, Products, Taxes, Coupons, shipping values, and historical status information;
  • Reviews can depend on Products and Customers;
  • content media can depend on the parent Product, Category, CMS Page, or Blog Post record.

Platform-specific and specialized qualification

Section titled “Platform-specific and specialized qualification”

The top-level data types above have platform-specific behavior that should remain visible rather than being compressed into generic capability statements.

Shopify Products, variants, options, and attributes

Section titled “Shopify Products, variants, options, and attributes”

When a Product is migrated to Shopify:

  • source custom options or variants are transferred as Shopify variants;
  • custom attributes are transferred as Product metafields;
  • multilingual data attached to custom options and custom attributes is migrated;
  • when the Product exceeds 2,048 variants or three options, the source structure requires an alternative Shopify representation or an approved tailored migration approach;
  • when the source Product cannot fit those limits, use a Shopify Product Option application and scope the required migration adaptation through Custom Migration.

Validate representative high-variation Products after migration, including option values, SKUs, prices, inventory, media, metafields, and multilingual values.

For Shopify Category hierarchy and collection representation, use Platform Data Models and Migration Boundaries.

Shopify does not allow invoices to be created through its API, so invoice migration to Shopify is not supported by the standard Order migration workflow.

If the Shopify Target Store uses a third-party application to create or send invoices, Next-Cart can adapt the migration through Custom Migration so invoice data is migrated into the selected Shopify invoice application. Treat that invoice application and its required data model separately from ordinary Order migration.

Magento invoices, shipments, and credit memos

Section titled “Magento invoices, shipments, and credit memos”

Next-Cart supports migrating invoices, shipments, and credit memos to Magento together with the associated Order history. Validate representative records and their Order relationships after migration.

Product images are downloaded and saved to the Target Store during the supported migration workflow. The migrated image scope includes Product featured images and gallery images.

Images embedded in supported descriptions are also downloaded and saved to the Target Store, including images used in:

  • Product descriptions;
  • Category descriptions;
  • Blog Post descriptions;
  • CMS Page descriptions.

Validate both the saved asset and its association with the intended target record. If an expected image is missing after migration, use Image Issues to diagnose source accessibility, path/naming, transfer, association, or target-display problems.

WooCommerce bundle, composite, and custom-option Products

Section titled “WooCommerce bundle, composite, and custom-option Products”

WooCommerce does not provide the source Magento bundle Product type as a default equivalent. To preserve Magento bundle behavior on WooCommerce, install the Target Store component that will own the bundle/composite model and scope the migration adaptation through Custom Migration.

Two supported reference choices from the migration workflow are:

  1. WooCommerce Composite Products, officially provided through WooCommerce. It supports Product packages built from variable Products and custom-option Products.
  2. WPC Composite Products for WooCommerce, provided by WPClever. It provides a separate composite-product implementation with its own target structure and presentation.

The selected Target Store component determines the target fields and relationships the migration must populate. Preserve component Products, option relationships, quantities, pricing rules, and other bundle behavior required by the project rather than flattening the bundle into an ordinary simple Product.

Next-Cart migrates Products together with their variations and custom options. A parent Product with all of its variations is counted as one Product for Entity Points; variations do not create a separate weighted Entity Points data type.

Validate the parent-child relationship, option combinations, SKUs, prices, stock, media, and target variant behavior rather than approving only the parent Product record.

Starting with WooCommerce 9.6, WooCommerce includes Brands as a built-in feature. Next-Cart imports manufacturer data as WooCommerce Brands and links those Brands to the corresponding Products.

If the Target Store uses a third-party brand plugin instead of the built-in Brands feature, install the compatible plugin first and scope any required migration adaptation through Custom Migration so manufacturer data is written to the plugin-owned structure.

Next-Cart supports multilingual WooCommerce migrations using WPML and Polylang in both directions: from another multilingual website into multilingual WooCommerce, and from multilingual WooCommerce to another multilingual e-commerce website.

For TranslatePress or another multilingual plugin whose data model is not covered by the standard workflow, the migration can be adapted through Custom Migration. Preserve translation records and the relationships between language variants, then validate representative Products and content in every required language.

Next-Cart supports transferring multilingual data to Shopify and from Shopify. For a Shopify Target Store:

  1. enable the required languages under Settings > Languages;
  2. run the migration with the multilingual data in scope;
  3. after migration, use the Shopify Translate & Adapt app to review and manage the transferred multilingual content;
  4. validate representative Products, collections, and content in each required language.

Supported Categories are migrated and assigned to their corresponding Products. Other supported data types that are not separately weighted for Entity Points can still be migrated in full for the active path.

Entity Points capacity and migration scope are different controls. Products, Customers, Orders, and Blog Posts are the weighted Entity Points types; Categories and other supported data do not become additional weighted types merely because they are included.

Data from third-party modules, extensions, or non-standard structures requires the applicable Custom Migration scope rather than a blanket entitlement to every module-owned record.

BigCommerce variants and option combinations

Section titled “BigCommerce variants and option combinations”

BigCommerce Products can have up to 600 variants.

BigCommerce automatically creates variations for every possible Product option combination, and all Product options can be shown even when a corresponding SKU is not listed. When unavailable option combinations must be hidden, the migration workaround is to customize the migration so that it:

  1. tracks inventory on all variants;
  2. creates SKUs for variants that do not exist in the Source Store; and
  3. assigns stock quantity 0 to those manufactured unavailable variants.

Scope this migration adaptation through Custom Migration, then validate both sellable and unavailable combinations on representative Products.

Next-Cart supports migrating both custom options and variants to BigCommerce.

Next-Cart supports OpenCart multi-store and multi-language migration. Define the participating stores and languages, then validate store assignments, Product/Category relationships, and representative translated data after migration.

Next-Cart supports PrestaShop multi-store and multi-language migration. Define the participating shop/group contexts and languages, then validate shop-specific assignments and representative translated data after migration.

Next-Cart supports all CS-Cart versions represented by the migration workflow, including CS-Cart B2C, CS-Cart B2B, and CS-Cart Multi-Vendor. Multi-Vendor migration should preserve the vendor ownership and related marketplace data required by the project.

Wix API does not support Blog content in the approved Wix migration workflow, so Next-Cart cannot migrate Blog Posts to Wix through that workflow. Do not substitute Product or CMS Page migration for Wix Blog data.

Joomla is a CMS and requires an e-commerce module to own commerce data. Next-Cart supports migrating commerce data to Joomla through these modules:

  • VirtueMart;
  • J2Store;
  • EShop.

Confirm the installed Target Store module before migration so Products and related commerce data are written to the expected component.

Next-Cart supports special characters, including symbols, non-alphabetic characters, and Latin, Greek, Arabic, Chinese, and other supported scripts.

If migrated text is encoded incorrectly and displays as error characters on the Target Store, convert the affected text to a compatible character encoding and validate representative records again. Correct record counts do not compensate for corrupted text.

Downloadable Product migration requires additional manual handling because large downloadable files cannot be transferred over HTTP in this workflow.

Use the two-step process:

  1. migrate the Product information to the Target Store through Next-Cart;
  2. manually copy the downloadable files to the Target Store through SSH.

After both steps, the relationships between downloadable files, Products, and Orders are preserved. Validate representative Products and historical Order entitlements after the file copy.

For an Open-Source Target Store, migrate Product videos through the same process used for downloadable Products.

For a cloud-based Target Store, use the same downloadable-Product handling for the Product relationship, but upload the video files to an external media location such as YouTube, Google Drive, or a self-hosted server. Validate the resulting Product-video links and playback/presentation on representative Products.

Shopify downloadable files and Product videos

Section titled “Shopify downloadable files and Product videos”

By default, Next-Cart preserves URLs for supported downloadable files and Product-video references on Shopify as Product metafields, maintaining the relationship between the migrated Product and the source asset reference.

When the project requires the actual files or videos to be moved into Shopify, define the destination behavior before migration:

  • Public/storefront assets: Shopify Content → Files can store public files, images, videos, PDFs, CSV files, and other supported assets. Do not use public Files storage for confidential or private customer content.
  • Sellable digital downloads: use Shopify’s Digital Products app or another approved digital-delivery application when customers must receive protected downloadable files or access links after purchase.
  • Product media: use Shopify Product media when the video or media belongs in the Product presentation rather than in a digital-delivery entitlement.

If the migration must upload assets and map them into one of these target structures, scope the required transfer through Custom Migration. A migrated URL or metafield alone does not create a working digital-delivery workflow. Validate representative Product associations, storefront/media presentation, and post-purchase access separately.

Shopify taxes and Product-price adjustment

Section titled “Shopify taxes and Product-price adjustment”

Shopify uses an automatic tax calculation system. Configure Target Store sales taxes under Settings > Taxes and duties.

Separately, Next-Cart can add tax to all Product prices during migration. Treat that migration-time Product-price adjustment separately from Shopify’s tax calculation for future transactions and validate representative Product prices after migration.

When a Product is migrated to Shopify, Next-Cart automatically identifies and links it to related Products that were also migrated. Cross-sell and up-sell Product relationships are also supported.

Install Shopify Search & Discovery before starting migration when related Products must be displayed accurately on the Shopify storefront. After migration, validate representative related, cross-sell, and up-sell relationships and their storefront presentation.

Shopify supports up to 2,048 variants per Product and up to three Product options. Apply those limits per Product, not as a 2,048-variant limit for the entire store. Shopify documents the native limits and related considerations in Adding variants.

Shopify can also apply method-specific upload, import, and API throttling that affects execution throughput for high-volume catalogs. Treat those limits as execution-method constraints rather than as a universal Product-model limit, and verify the active migration method before applying a numeric rate to a project.

For Product option migration, a source Product that requires more than 2,048 variants or more than three options cannot be represented natively by one standard Shopify Product without redesign. Use an appropriate Shopify Product Option application, Product splitting, line-item/custom-input design, or an approved tailored migration approach when the source structure exceeds the native model.

Validate representative high-variation Products after migration, including SKUs, prices, inventory, media, option values, and multilingual option/attribute data. Being below 2,048 variants does not by itself prove that the Product was modeled correctly.

Next-Cart preserves the following platform-specific Product-relationship behavior:

Target PlatformSupported relationship behavior
BigCommerceRelated Product relationships are transferred. BigCommerce does not support Cross-sell or Up-sell Product links in this migration model.
Magento / Adobe CommerceRelated Products, Cross-sell Products, and Up-sell Products are transferred and the Product links are preserved on the Magento Target Store.
OpenCartRelated Product relationships are transferred, preserved, and displayed on the OpenCart Target Store.
PrestaShopRelated Product relationships are transferred and remain functional on the PrestaShop Target Store.
ShopifyRelated Products are automatically identified and linked when the participating Products are migrated. Cross-sell and up-sell relationships are supported. Install Shopify Search & Discovery before migration when the storefront must display the related Products accurately.
WooCommerceRelated Products are migrated as Up-sell Products by default. Cross-sell and Up-sell links are also transferred, and the migrated links appear on the WooCommerce Target Store.

Validate representative relationships after migration, including the intended Product pairs and storefront result. Do not reduce Related, Cross-sell, and Up-sell relationships to one generic field when the target behavior distinguishes them.

The processing sequence is:

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

The progress list contains only the data types included and available for the migration activity. A shorter visible list does not change the relative order of the data types that are processed.

ObservationCorrect interpretation
An earlier data type is still processingA later data type can remain pending because the activity has not reached it.
An earlier supporting data type is Failed or unexpectedly SkippedLater records can exist but contain incomplete relationships. Classify the supporting failure before approving the result.
A data type reaches SuccessIts processing completed successfully according to the activity result; validation is still required to confirm accuracy and usability.
A data type is FailedProcessing did not complete successfully for the affected scope. Review the activity evidence and correct the cause before relying on related results.
A data type is SkippedNext-Cart did not process the affected scope. Determine whether the skip was expected from selection, filtering, source conditions, dependencies, or platform constraints.
A data type is absent from progressIt was unavailable, unselected, or not included in the migration activity. Confirm the configuration rather than assuming it completed silently.

Processing completion is not migration-result approval. Use the Validation section to confirm record identity, values, relationships, target behavior, and accepted limitations.

Data selection, filtering, actions, and capacity

Section titled “Data selection, filtering, actions, and capacity”

These controls answer different questions:

ControlQuestion it answers
Select Data selectionWhich supported data types are included?
Data FilterWhich supported records inside a selected data type meet the configured field-level conditions?
Migration actionWhich Connect Stores action, configuration path, and earlier-result treatment apply?
Additional OptionsDoes the activity pair a Continue action with Continue the previous migration or another supported processing option for the active Source-to-Target path?
Execution stateIs a running Browser or Background activity being started, stopped, resumed, or revisited after page exit?
Entity Points PlanHow much counted-record capacity is available to the purchased migration service?

Entity Points are calculated from eligible Products, Customers, Orders, and Blog Posts. The presence of Taxes, Manufacturers, Categories, Reviews, Coupons, or CMS Pages does not make those data types independently counted merely because they are processed.

When a required data type or field is unavailable

Section titled “When a required data type or field is unavailable”

Use this decision sequence:

  1. Confirm the correct Source Platform, Target Platform, purchased service, and migration path.
  2. Confirm that the expected data is not already represented by another supported data type shown in Select Data.
  3. Review the platform-specific guide and source-access setup for required data exposure.
  4. Determine whether the requirement is a standard field, a different target-model representation, app or plugin data, a custom source field, or a non-standard relationship.
  5. Use standard mapping or a purchased Add-on only when the selected path supports the required source and target fields.
  6. Prepare a Custom Migration requirement when the required data or behavior remains outside the supported path and is essential to the accepted result.

Do not start another migration activity merely because a data type is missing from the configuration. First determine whether the requirement is unsupported, inaccessible, incorrectly scoped, or attached to another source system.