Overview

Add-ons

Add-ons extends a paid migration with supported record filtering, value transformation, field mapping, and database-level mapping. Configure only the Add-ons included in the active migration and supported for its Source-to-Target path. If a required Add-on is not included in the active package, use Purchase a Migration Upgrade to add it before configuration.

Choose the Add-on to configure

Data Filter Include or exclude records through supported Field, Operator, and Value conditions.

Data Transformation Change supported values before the mapping stages that follow.

Advanced Data Mapping Route supported source or transformed values to compatible target fields.

Advanced Database Mapping Route supported data to eligible database fields or columns after platform and schema qualification.

Processing sequence

When several Add-ons are active, they process data in this fixed order:

1. Data Filter determines which records remain in scope.
2. Data Transformation changes supported values on those active records.
3. Advanced Data Mapping routes supported source or transformed values to compatible target fields.
4. Advanced Database Mapping applies eligible database-level routing after the earlier applicable stages.

Rule order also matters inside an Add-on

Rules within an Add-on are evaluated in the order shown for that Add-on. Review dependent rules together when an earlier condition or transformation changes the data received by a later rule.

Combined example

A Product can remain in scope because it passes Data Filter, have its name or another supported value adjusted through Data Transformation, and then have that resulting value routed to a compatible destination through Advanced Data Mapping. If Advanced Database Mapping is also supported for the exact Source setup, Target Platform, and requested schema destination, database-level routing follows the earlier applicable stages.

The fields, operators, mappings, and database destinations available in an active migration depend on the selected entity, field type, platform path, and purchased Add-ons. The dedicated guides contain the field and operator references needed for each Add-on rather than sending the customer to a detached lookup page.

Next Steps

Open the dedicated guide for each included Add-on and configure them in the sequence above. After the last included Add-on, continue to Custom when approved Custom requirements are present; otherwise use Go to Migration.