Configure Advanced Database Mapping

Configure Advanced Database Mapping

Advanced Database Mapping routes supported database values to compatible Target Store fields or columns.

Both Source and Target platforms must support this Add-on.

Also confirm the requested schema destination and Value Type before adding rules.

Screenshots illustrate the procedure. Available entities, fields, values, and controls depend on your migration path and platform versions.

Configure a mapping

1. In the Configuration step, expand Advanced Database Mapping, select the entity, and click Add Mapping.

   

2. Select the supported Source Field for the database value to route.

   

3. Select the supported Target Field that should receive the value.

   

4. When the verified target schema allows a new database field, select New Column and enter the Custom Target Field. Do not use this branch unless the exact target schema location and Value Type are supported.

   

5. Click Add Rule when another supported database mapping is required for the same entity.

   

Example: map a database field to the corresponding target field

When the active migration exposes the supported Manufacturers fields, configure:

Setting	Value
Entity	Manufacturers
Source Field	Column name
Target Field	Column name

This routes the supported source database value to the corresponding target database field without changing the value.

New Column does not make an arbitrary schema supported

Selecting New Column is valid only when the exact Target Platform, schema location, and Value Type are supported for the intended destination. Database placement also does not guarantee that a Target Store theme, app, extension, or business rule will consume the new value automatically.

Verify the mapping

Before continuing, check that every rule uses a supported Source field, a supported Target field or verified New Column destination, and compatible Value Types. If the intended destination is unavailable, do not substitute another database location; have the requirement reviewed through Custom Migration.

Rule order and removal

Advanced Database Mapping rules run from top to bottom.

• Click x to remove an individual mapping rule.

  

• Use the remove control for the Entity Mapping to delete the entire mapping group.

  

Next Steps

Before leaving Add-ons, configure any other included capability, including Data Update. Data Update runs independently; it is not another database-mapping stage.

If Custom follows Add-ons, continue to Custom. If Add-ons is the final Configuration screen, use Go to Migration, then continue to Start and Monitor a Migration.