Supported Data Types and Processing Order
Look up the customer-facing data types, understand path-dependent availability and relationships, and interpret the complete processing sequence.
Supported Data Types and Processing Order
Section titled “Supported Data Types and Processing Order”The selected migration path determines which customer-facing data types appear 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.
Customer-facing data types
Section titled “Customer-facing data types”| Data type | Typical supported content | Relationship or validation focus |
|---|---|---|
| Taxes | Tax classes, rates, and jurisdiction-related values where supported | Confirm Product and historical Order tax meaning separately from the target store’s future tax configuration. |
| Manufacturers | Brand and manufacturer records | Confirm that Products retain the intended brand or target-platform equivalent. |
| Categories | Product category trees, hierarchy, and grouping relationships | Confirm parent-child structure, Product membership, and any approved target grouping model. |
| Products | Product records, variants, options, attributes, images, prices, and inventory where supported | Confirm identity, structure, availability, and relationships to Categories, Manufacturers, Taxes, and inventory locations. |
| Customers | Customer accounts, addresses, groups, and related supported account data | Confirm identity, address ownership, group meaning, and the approved customer-access behavior. |
| Orders | Historical Orders, line items, quantities, totals, shipping, discounts, tax values, and status information where supported | Confirm Customer and Product relationships, financial composition, identifiers, and mapped payment and fulfillment meaning. |
| Reviews | Product reviews, ratings, and supported review relationships | Confirm association with the correct Product and Customer where applicable. |
| Coupons | Discount codes, vouchers, promotions, and supported rule data | Confirm that the target representation preserves the approved business rule or documented equivalent. |
| CMS Pages | Static pages, landing-page content, supported metadata, and related media | Confirm required content and links separately from theme, page-builder, widget, or script presentation. |
| Blog Posts | Blog articles and related supported blog content | Confirm titles, body content, authors, Categories, dates, media, and target content-model equivalents where applicable. |
The table describes the complete customer-facing taxonomy. It does not mean that every migration path exposes every data type or every listed detail.
Conditional availability
Section titled “Conditional availability”Data-type availability is determined by the supported migration path, not by a universal Next-Cart catalog.
| Situation | Operational meaning |
|---|---|
| A data type appears in Data | It is available for the current migration path and can be selected for the current configuration. |
| A data type does not appear | The standard path does not currently 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 represented | The field can be unsupported, mapped to a different target structure, transformed through an approved rule, or require Custom Service assessment. |
| The source contains app, plugin, module, or external-system data | Do 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 available | The Add-on can filter, transform, or redirect supported data within its defined boundary; it does not create a new supported data type. |
Use Add-ons, Customization, and Custom Service Boundaries when the required source or target behavior extends beyond standard data-type support.
Relationship-dependent data
Section titled “Relationship-dependent data”Some selected records require parent or related records to preserve usable relationships. Next-Cart can select required dependencies automatically when the current 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.
Complete processing sequence
Section titled “Complete processing sequence”The customer-facing 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.
How to interpret the sequence
Section titled “How to interpret the sequence”| Observation | Correct interpretation |
|---|---|
| An earlier data type is still processing | A later data type can remain pending because the activity has not reached it. |
| An earlier supporting data type is Failed or unexpectedly Skipped | Later records can exist but contain incomplete relationships. Classify the supporting failure before approving the result. |
| A data type reaches Success | Its processing completed successfully according to the activity result; validation is still required to confirm accuracy and usability. |
| A data type is Failed | Processing 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 Skipped | Next-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 progress | It was unavailable, unselected, or not included in the current 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:
| Control | Question it answers |
|---|---|
| Data selection | Which supported data types are included? |
| Data Filter | Which supported records inside a selected data type meet the configured field-level conditions? |
| Migration action | Which configuration path and earlier-result treatment apply? |
| Source Platform Options | Does the activity resume interrupted processing or read only newly added source records, when available? |
| Entity Points Plan | How 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:
- Confirm the correct Source Platform, Target Platform, purchased service, and migration path.
- Confirm that the expected data type is not already represented under the approved customer-facing name.
- Review the current platform-specific guide and source-access setup for required data exposure.
- 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.
- Use standard mapping or a purchased Add-on only when the current path supports the required source and target fields.
- Prepare a Custom Service 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.
Related tasks
Section titled “Related tasks”- Use Select Data to Migrate to select available data types and review dependencies.
- Use Run a Full Migration to monitor the processing sequence and results.
- Use Entity Points to understand counted-record capacity and consumption.
- Use Platform Data Model and Migration Boundaries to classify expected target transformations and requirements outside data migration.
- Use Missing Data when a selected record or relationship is absent or cannot be found.