Add-ons, Customization, and Custom Migration Boundaries
Distinguish Standard Add-ons, approved Customization, and Custom Migration requirements, including the fixed Add-on processing order.
Add-ons, Customization, and Custom Migration Boundaries
Section titled “Add-ons, Customization, and Custom Migration Boundaries”Compare the capability layers below, then configure the supported option in your active migration.
All Add-ons require support from both Source and Target platforms.
Capability layers
Section titled “Capability layers”| Capability | Use it for | Availability |
|---|---|---|
| Standard Select Data, Additional Options, and Attribute Mapping | Supported data selection, migration options, and standard operational value alignment | Displayed according to the active Source-to-Target migration path |
| Standard Add-ons | Supported record filtering, value transformation, field mapping, database-level mapping, or selective updates | Add-ons appears only when the purchased migration includes the applicable Add-on |
| Approved Customization | Tailored work already assessed and attached to Custom Migration | Custom appears only when approved Customization is available |
| Tailored or Custom Add-on work | Modified Standard Add-on behavior or bespoke Add-on logic | Reviewed and quoted through Custom Migration |
| Other Custom Migration requirements | Unsupported extraction, schema, API, relationship, script, or target behavior | Requires scope review and approval |
Standard Add-ons
Section titled “Standard Add-ons”| Add-on | Fixed price | Function | Concrete use case |
|---|---|---|---|
| Data Filter | $50 | Filters records inside selected data types using supported field-based rules. | Products: Status equals Enabled AND Quantity does not equal 0. |
| Data Transformation | $50 | Changes supported values on the active dataset. | Increase Product Regular Price by 12% with Regular Price x 1.12; 80.00 becomes 89.60. |
| Advanced Data Mapping | $50 | Routes a supported source or transformed value to a compatible target field without changing that value during mapping. | Products: Short Description -> Description, with the text unchanged. |
| Advanced Database Mapping | $100 | Routes supported data through eligible standard Entity tables or columns when the selected Source setup and Target Platform are supported. | OpenCart -> Adobe Commerce: product.location -> New Column catalog_product_entity.legacy_warehouse_location, preserving WH-A-03. |
| Data Update | $50 | Independently refreshes selected supported fields on existing records previously migrated by Next-Cart. | Refresh a supported Order status on a previously migrated Order whose Target counterpart still exists. |
The examples describe intended outcomes, not expressions to paste into every Add-on. Only Data Filter provides direct Expression editing; use the other Add-ons’ structured controls.
Data Update
Section titled “Data Update”Data Update separately refreshes selected supported fields on existing records previously migrated by Next-Cart. It uses default mappings, preserves non-selected fields and unassociated data, and does not create or recreate records. Selected fields can replace manual Target edits.
Fixed Add-on processing order
Section titled “Fixed Add-on processing order”Data Filter -> Data Transformation -> Advanced Data Mapping -> Advanced Database Mapping
The four stages below do not include Data Update. Each stage receives the active source dataset produced by the preceding stage. Rules within each Add-on also run from top to bottom. Review both levels; an earlier operation can affect the records or values that a later operation receives. AND/OR within a Data Filter defines condition matching, not the Add-on execution sequence.
Data Filter updates only the entity set it filters. For example, consider a migration containing 100 Products, 100 Orders, 100 Customers, and 100 Blog Posts.
If a Product filter matches 50 Products, the next Add-on receives those 50 Products together with the unchanged 100 Orders, 100 Customers, and 100 Blog Posts.
Example: one OpenCart Product requirement using four processing Add-ons
Section titled “Example: one OpenCart Product requirement using four processing Add-ons”An OpenCart -> Adobe Commerce migration needs to prepare the Product catalog for a new web-sales and ERP model. One source Product starts with:
- Status: Enabled
- Quantity: 25
- Model:
TSHIRT-001 - Location:
WH-A-03
The required configuration is:
| Processing stage | Exact requirement | Result |
|---|---|---|
| Data Filter | Products: Status equals Enabled AND Quantity does not equal 0 | The Product remains in scope. Disabled or zero-stock Products are excluded. |
| Data Transformation | Prepend WEB- to Product Model | TSHIRT-001 becomes WEB-TSHIRT-001. |
| Advanced Data Mapping | Product Model -> SKU | The transformed value becomes target SKU WEB-TSHIRT-001. |
| Advanced Database Mapping | product.location -> catalog_product_entity New Column legacy_warehouse_location | WH-A-03 is retained unchanged in the approved custom database column. |
The four processing Add-ons solve different parts of one requirement: record selection, value modification, field destination, and database-level storage. Other selected data types remain in the active dataset unless their own rules change them.
Use Add-ons for the configuration sequence. The dedicated Data Filter, Data Transformation, and Advanced Data Mapping guides include their applicable operator and field references directly with the procedure.
Capability boundaries
Section titled “Capability boundaries”| Requirement | Correct capability |
|---|---|
| Align languages, sites, locations, groups, or order states | Attribute Mapping |
| Filter selected entity records | Data Filter |
| Change a supported value | Data Transformation |
| Route a supported value to another target field | Advanced Data Mapping |
| Route supported data through an eligible standard field, table, or column mapping | Advanced Database Mapping |
| Refresh selected supported fields on existing previously migrated records | Data Update, independently of the four-stage sequence |
| Implement unsupported extraction, schema logic, scripts, APIs, relationships, or target behavior | Custom Migration assessment |
Availability within migration actions
Section titled “Availability within migration actions”| Migration activity | Add-on and Customization behavior |
|---|---|
| Demo Migration | Add-ons and Customization are unavailable. |
| First Full Migration | Configure purchased Add-ons and approved Customization as the active Configuration workflow reaches those stages. |
| Continue the Migration with Last Saved Configuration | Loads the most recent configuration and routes directly to the Migration step. It is unchanged unless edited through Edit Config before starting. |
| Continue the Migration with a New Configuration | Allows supported configuration changes, including applicable Add-ons and approved Customization. |
| Perform a New Migration | Starts a fresh Configuration workflow on the same purchased Source-to-Target migration path. The interface label is Start a new migration. |
Standard versus Custom Migration
Section titled “Standard versus Custom Migration”A custom field, database column, or use of several Standard Add-ons does not automatically require Custom Migration. Use the supported Standard capability first. Escalate only the portion that cannot be configured through the controls exposed for the active migration.
Use Add-ons for execution. Use Advanced Database Mapping Schema Registry for supported standard data structures, and Prepare Custom Migration Requirements for unsupported or bespoke requirements.