Attribute Mapping

Attribute Mapping

Attribute Mapping aligns supported source values with target values that represent the same operational meaning. Next-Cart pre-fills supported mappings where possible; review those defaults and change only the mappings that need a different target result.

Mapping categories

Only categories supported for the active Source-to-Target path are displayed.

Store, catalog, and customer context

Mapping category	What it aligns
Site Mapping	Source site contexts with the intended target sites.
Language Mapping	Source languages with target languages.
Inventory Location Mapping	Source inventory locations with target locations.
Attribute Set Mapping	Source attribute sets with compatible target attribute sets.
Root Category Mapping	The migrated catalog with the intended target root category.
Customer Group Mapping	Source Customer Groups with target groups.

Order lifecycle

Mapping category	What it aligns
Order Payment Status Mapping	Historical source payment states with target payment states that represent the same payment meaning.
Order Fulfillment Status Mapping	Historical source fulfillment states with target fulfillment states that represent the same fulfillment meaning.

Payment and fulfillment statuses are separate mapping problems

Payment status and fulfillment status describe different parts of an Order lifecycle. A payment status records the financial state of the Order, while a fulfillment status records what has happened to the goods or fulfillment process. Do not map one dimension by using the other as a shortcut.

When both mapping categories are available, review them independently. Match each source value to the target value that preserves its business meaning, then validate representative Orders that cover paid, pending, refunded, canceled, fulfilled, partially fulfilled, and exception cases that exist in the source. Use the values shown by the active migration rather than assuming another platform’s status list applies.

Shopify payment and fulfillment status meaning

For Shopify-bound Order history, keep payment state and fulfillment state as separate business dimensions. A source label such as Complete, Processing, or Shipped can combine meanings that Shopify represents separately.

When the active migration exposes the applicable mappings:

1. interpret what the source status actually means financially and operationally;
2. map payment meaning through Order Payment Status Mapping;
3. map fulfillment meaning through Order Fulfillment Status Mapping;
4. validate representative historical Orders that cover the states present in the Source Store.

Do not force one source label into one target status when the Target Platform requires separate financial and fulfillment interpretation.

Configure the mappings

1. Review each mapping category displayed for the active migration.
2. Confirm that each pre-filled target value represents the intended source meaning.
3. Change a target selection when another supported value is required. Select Skip only when that source value should not transfer to the Target Store.
4. Review the remaining source values for missing or inappropriate target choices.
5. Click Next when Add-ons, Custom, or both follow. If neither screen is included, click Go to Migration.

Map operational meaning, not just similar labels

Two labels can look alike while representing different payment, fulfillment, language, customer-group, inventory, or site behavior. Choose the target value that preserves what the source value actually means in the business process.

Example: Order Payment Status Mapping

Consider an OpenCart-to-OpenCart migration where Order Payment Status Mapping is available. A Source Store can contain payment-status values such as Processing, Shipped, Complete, Canceled, Denied, Failed, Canceled Reversal, Refunded, Reversed, Chargeback, Pending, Voided, Processed, and Expired.

These values are examples of payment states that may need configuration, not a fixed status inventory for every store. Review the actual source payment values shown in the active migration and map each one to the Target Store payment status that preserves the intended meaning. For example, a source status representing a completed payment should map to the target state used for completed payments, even when the labels are not identical.

Attribute Mapping and Add-on mapping serve different needs

Requirement	Use
Align supported standard sites, languages, locations, groups, or order states	Attribute Mapping
Change a supported value before mapping	Data Transformation
Route a supported field to a different compatible target field	Advanced Data Mapping
Route supported data through an eligible database field or column destination	Advanced Database Mapping, subject to platform and schema eligibility

A missing Attribute Mapping category is not automatically solved by an Add-on. Use the capability that matches the requirement and its supported scope.

When a mapping cannot be completed

Situation	Next action
A required mapping category is not displayed	Confirm the active Source-to-Target path. Do not infer support from another path.
The required target value does not exist	Where the Target Platform supports creating it, prepare the target value and review the mapping choices again.
No equivalent target meaning exists	Define an acceptable fallback or have the requirement reviewed before processing.
The requirement is field redirection or value transformation	Use the applicable purchased Add-on only when its supported scope covers the requirement.

Next Steps

If Add-ons is included, continue to Add-ons. If only approved Custom requirements follow, continue to Custom. When neither screen is included, use Go to Migration after the mapping review passes.