Configure Attribute Mapping

Configure Attribute Mapping

Attribute Mapping aligns standard source values with compatible target values so sites, languages, locations, groups, and order states retain their intended operational meaning after migration. Review the suggested mappings before changing them, and use an approved fallback when no exact target value exists.

Use the correct mapping control

Use Attribute Mapping for standard values such as languages, locations, groups, and order states. Use Advanced Data Mapping when a supported source field must be written to a different compatible target field. Use Advanced Database Mapping only for supported field/database-column destinations when both platforms are Open-Source.

Before you start

Confirm that:

• Data and Options are complete;
• required target sites, languages, locations, Product types, root Categories, Customer Groups, and order states exist where applicable;
• the business meaning of each source value is understood;
• any fallback or consolidation rule has been approved.

Review the available mapping groups

Available groups depend on the migration path.

Mapping group	Match	Key decision
Site Mapping	Source sites or stores to target sites or store views	Preserve the correct domain, language, catalog, and regional context.
Language Mapping	Source locales to target languages	Do not combine unrelated languages unless an approved fallback exists.
Inventory Location Mapping	Source warehouses or locations to target inventory locations	Decide whether stock remains separated or is consolidated.
Attribute Set Mapping	Source attribute sets to target Product types or equivalent structures	Confirm required attributes, variants, and validation rules remain available.
Root Category Mapping	Source root Categories to target roots or top-level catalog structures	Preserve the intended hierarchy and navigation ownership.
Customer Group Mapping	Source Customer Groups to target groups or segments	Verify pricing, tax, visibility, permissions, and B2B behavior separately.
Order Payment Status Mapping	Source payment statuses to target payment states	Preserve the financial meaning of paid, pending, failed, refunded, and related states.
Order Fulfillment Status Mapping	Source fulfillment statuses to target order or fulfillment states	Preserve distinctions such as unfulfilled, partial, shipped, delivered, returned, and cancelled.

Configure the mappings

1. Open Mapping

   Open Mapping in the migration configuration.

2. Review every available group

   Check each source value that requires a target counterpart.

3. Select the operationally equivalent target value

   Base the choice on behavior and business meaning, not label similarity.

4. Prepare missing target values

   Create or configure the required target value where supported, then return to Mapping.

5. Review consolidated mappings

   When several source values map to one target value, confirm that no required regional, inventory, pricing, tax, reporting, or order-state distinction is lost.

6. Continue after all required values are mapped

   Select Next only after every available group is complete or has an approved fallback.

Match behavior, not wording

Similar labels can trigger different payment, inventory, fulfillment, reporting, or notification behavior. Confirm the operational result before selecting the target value.

Expected result

After completing Mapping:

• every required source value has an approved target counterpart;
• sites, languages, locations, catalog structures, groups, and order states preserve their intended meaning;
• missing or approximate target values have an approved resolution;
• the configuration is ready for the next available stage.

Verify the mappings

Check	Pass condition
Coverage	Every required source value has a target selection.
Sites and languages	Regional, catalog, and language context remains correct.
Inventory	Stock is assigned to the intended target locations.
Catalog structure	Attribute sets and root Categories produce the intended Product and navigation structure.
Customer classification	Customer Groups retain the required operational distinction.
Order states	Payment and fulfillment mappings preserve their financial and operational meaning.
Fallbacks	Every consolidated or approximate mapping is documented and approved.

If this does not work

Issue	What to do
A mapping group is unavailable	Confirm that the related data type and platform feature apply to the migration path.
A required target value is missing	Prepare it on the target store where supported or submit a ticket for guidance.
No exact equivalent exists	Select an approved operational fallback and document the limitation.
Several values must map to one	Confirm the loss of detail with the affected business owner before execution.
A selection is not retained	Repeat the mapping and confirm it remains selected before continuing.
A supported source field must be redirected to another compatible target field	Use Advanced Data Mapping when purchased and supported.
A supported field or database column needs another compatible destination and both platforms are Open-Source	Use Advanced Database Mapping when purchased and supported.

Next step

If Add-ons appears, continue to Configure Add-ons.

If Custom appears without Add-ons, continue to Select Customization.

If neither stage appears, continue to Review the Full Migration Configuration.