Configure Advanced Data Mapping

Configure Advanced Data Mapping

Advanced Data Mapping redirects a supported source field to a different compatible target field. The mapping changes the destination, not the field value itself. Use this Add-on when the standard migration path supports both fields but the source value needs to arrive in another target field.

Mapping and transformation are different

Advanced Data Mapping changes where a supported value is written. Data Transformation changes the resulting target-field value. When both apply, establish the destination first and then validate the transformation against that resulting target field.

Before you start

Prepare:

• the selected data type;
• the supported source field;
• the intended compatible target field;
• the source value type and target field type;
• uniqueness and relationship requirements;
• representative normal, boundary, and exception records.

Tax data is excluded from Standard Advanced Data Mapping scope. If the requirement involves Tax fields, stop and confirm the supported handling before configuring a mapping.

Mapping controls

Each mapping can include the supported controls needed to select:

Control	Purpose
Source Field	Selects the supported source field whose value will be redirected.
Target Field	Selects a different compatible target field.
Add Rule	Adds another supported field mapping.
Delete	Removes a mapping rule.

Available fields and destinations depend on the migration path, selected data, and supported target model.

Configure a field mapping

1. Open Advanced Data Mapping

   In Add-ons, locate Advanced Data Mapping.

2. Select the data type

   Locate or create the mapping group for the selected supported data type.

3. Select the source field

   Choose the field whose value must be written to another destination.

4. Select the target field

   Choose a supported target field that can represent the source value correctly.

5. Review value compatibility

   Confirm that the target field type can represent the complete source value, not only a convenient sample.

6. Add other required mappings

   Keep one clear approved destination for each mapped source value and remove conflicting rules.

7. Test representative records

   Verify normal, boundary, and exception values in the intended target field.

Practical use cases

Use Advanced Data Mapping when the value is already correct and only the supported field destination needs to change.

Requirement	Advanced Data Mapping role	What to verify
Put a supported Product Short Description value into the compatible target Description field	Redirect the supported source field to the approved target field without changing the value as part of mapping.	Representative Products contain the complete source text in the intended destination, and any target-side presentation that depends on that field is checked separately.
Place a supported Customer contact value in a different compatible target contact field	Redirect the supported source contact field to the approved target field while preserving the complete value.	The value belongs to the correct Customer, remains complete, and does not break uniqueness, account, or relationship behavior that depends on the destination field.

Choose the correct mapping layer

Requirement	Use
Align supported sites, languages, locations, groups, or order states	Standard Attribute Mapping
Redirect a supported source field to a different compatible target field	Advanced Data Mapping
Map a supported field or underlying database column on an eligible Open-Source-to-Open-Source path	Advanced Database Mapping
Change the resulting selected target-field value	Data Transformation
Implement unsupported extraction, bespoke schema logic, scripts, APIs, or relationships	Custom Service assessment

Do not use Advanced Data Mapping as a general replacement for Attribute Mapping, and do not use it to imply database-column support that belongs to Advanced Database Mapping.

Review high-risk fields

Treat these as high risk:

• primary identifiers;
• foreign keys and relationship fields;
• Product, Category, Customer, Order, Review, and address IDs;
• language, site, location, group, and status identifiers;
• unique SKUs, emails, order numbers, and external references;
• numeric fields used in totals, inventory, weight, dimensions, or other business calculations.

Compatibility must be proven by the complete value range

A Number value can often be represented by a sufficiently capable Text field. Arbitrary Text should not be mapped to a Number field merely because a few samples contain digits. If compatibility is uncertain, treat it as a validation requirement rather than a support guarantee.

Interaction with other Add-ons

• Data Filter establishes which records continue before mapping matters.
• Advanced Data Mapping establishes the supported field destination.
• Advanced Database Mapping, when applicable, follows field-level mapping and handles eligible supported field or database-column destinations.
• Data Transformation runs after the mapping stages and changes the selected resulting target value.

If several mapping rules affect the same destination, resolve the conflict before migration execution.

Expected result

After configuring Advanced Data Mapping:

• every mapping uses a supported source field and compatible target field;
• the value remains unchanged by the mapping operation;
• Tax data is not included in Standard mapping rules;
• duplicate or conflicting target destinations are removed;
• identifiers and relationship fields retain valid references;
• representative records place the complete source value in the intended target field.

Verify the mapping

Check	Pass condition
Source field	The intended supported source value is selected.
Target field	The selected target destination is supported and operationally correct.
Value compatibility	The target field can represent normal, boundary, and exception source values.
Value preservation	The mapped value is unchanged unless a separate Data Transformation rule intentionally changes it later.
Tax exclusion	No Standard Advanced Data Mapping rule is used for Tax data.
Uniqueness	Unique fields do not receive conflicting values.
Relationships	Related records remain connected.
Sample result	Representative records place the value in the expected target field.

If this does not work

Issue	What to do
A required source or target field is unavailable	Confirm whether the requirement fits Advanced Database Mapping on an eligible path or prepare the unsupported portion for Custom Service review.
Source and target field types are incompatible	Choose a compatible target destination. Use Data Transformation only when the business requirement is to change the resulting value, not to bypass an incompatible mapping.
A duplicate destination is rejected or produces conflicting results	Remove one mapping or choose another compatible destination.
A relationship field is unclear	Do not map it until its identifier and dependency role are understood.
The requirement concerns a database column	Use Configure Advanced Database Mapping if both platforms are Open-Source and the required column mapping is supported.
The requirement needs bespoke extraction, schema engineering, scripts, APIs, or relationships	Prepare the non-standard portion for Custom Service review.

Next step

Return to Configure Add-ons and review this mapping together with any applicable database mapping and transformation rules.