Overview
Configure purchased Data Filter, Advanced Data Mapping, Advanced Database Mapping, and Data Transformation Add-ons before migration execution.
Configure Add-ons
Section titled “Configure Add-ons”Purchased Add-ons extend the standard migration configuration when the required result needs record filtering, supported field or database-column mapping, or target-value transformation. Configure only the Add-ons included in the purchased service, follow their processing order, and verify their combined result before migration execution.
Choose the required Add-on
Section titled “Choose the required Add-on”| Requirement | Standard Add-on | What it changes | Fixed price |
|---|---|---|---|
| Include or exclude records by supported field-based conditions | Data Filter | Which records continue through migration processing | $50 |
| Send a supported source field to a different compatible target field | Advanced Data Mapping | The supported field destination; the mapped value itself is unchanged by mapping | $50 |
| Map a supported source field or database column to a compatible target field or column on an eligible Open-Source-to-Open-Source path | Advanced Database Mapping | The supported field or database-column destination; the mapped value itself is unchanged by mapping | $100 |
| Change the resulting value of a supported target field | Data Transformation | The selected target-field value after applicable mapping stages | $50 |
When one Add-on is enough
Section titled “When one Add-on is enough”A requirement does not need to use several Add-ons to benefit from the Add-on stage. Start with the business result and use only the capability that owns the required change. The individual guides include fuller examples and verification steps.
| Standalone requirement | Add-on | Continue with |
|---|---|---|
| Migrate only the approved active Product population | Data Filter | Configure Data Filter |
| Keep a supported Product value unchanged but place it in another compatible target field | Advanced Data Mapping | Configure Advanced Data Mapping |
| On an eligible Open-Source-to-Open-Source path, preserve a supported database value in another compatible field or column | Advanced Database Mapping | Configure Advanced Database Mapping |
| Apply an approved calculation or normalization rule to a known resulting target field | Data Transformation | Configure Data Transformation |
The standalone examples isolate one function. The combined example later in this page shows how several independently valid functions can work together when one business outcome needs multiple stages.
Follow the Add-on processing order
Section titled “Follow the Add-on processing order”When several Add-ons apply to the same migration, configure and review them in this order:
Data Filter → Advanced Data Mapping → Advanced Database Mapping → Data Transformation
The order matters because each later applicable stage works with the result established by the earlier stages.
| Stage | Operational question | Result to carry forward |
|---|---|---|
| Data Filter | Which records should continue? | The eligible record set |
| Advanced Data Mapping | Which compatible target field should receive a supported source field? | The approved field destination |
| Advanced Database Mapping | On an eligible Open-Source-to-Open-Source path, which compatible target field or database column should receive a supported source field or column? | The approved field or column destination |
| Data Transformation | What should the resulting selected target-field value become? | The final supported transformed value |
Do not configure a later Add-on to compensate for an incorrect earlier rule. Correct the earlier record scope or destination first, then recheck the later result.
Review availability and scope before configuring rules
Section titled “Review availability and scope before configuring rules”Add-on purchase and Add-on applicability are separate checks. A purchased Add-on can still depend on the selected migration path, supported data type, supported field or column, operator, destination, or value compatibility.
Advanced Database Mapping has an additional path prerequisite: both the Source Platform and Target Platform must be Open-Source. An Open-Source platform on only one side is not sufficient.
A custom field or database column does not automatically require Custom Service. First determine whether the required operation fits supported Advanced Data Mapping or, when the path qualifies, Advanced Database Mapping.
Know when Custom Service is required
Section titled “Know when Custom Service is required”Use the supported Standard Add-on without modification when the requirement fits its available controls and supported scope.
| Requirement state | Treatment |
|---|---|
| A Standard Add-on can produce the required result with supported controls | Configure the Standard Add-on. |
| A Standard Add-on function needs tuning, modification, or expanded scope | Prepare a Tailored Add-on requirement for review and quotation through Custom Service. |
| The required Add-on functionality is bespoke and outside the Standard catalog | Prepare a Custom Add-on requirement for review and quotation through Custom Service. |
| The requirement depends on unsupported extraction, relationships, scripts, APIs, or target behavior beyond Add-on scope | Prepare the non-standard requirement for Custom Service assessment. |
Review interactions before migration
Section titled “Review interactions before migration”| Scenario | What to confirm |
|---|---|
| A filter excludes records that also have mapping or transformation rules | Excluded records are not expected to receive later Add-on processing. |
| Advanced Data Mapping and Advanced Database Mapping affect related destinations | Each source value has one approved compatible destination and the rules do not conflict. |
| A mapped field is later transformed | The transformation applies to the intended resulting target field and produces the expected value. |
| Several rules affect one data type | The combined record scope, destinations, and target values match the approved requirement. |
| An identifier or relationship field is filtered, mapped, or transformed | Related Products, Customers, Orders, Reviews, and supporting records remain linkable. |
| A database column is mapped | The stored result and every required target-side consumer are validated separately. |
Example: combine Add-ons for one Product requirement
Section titled “Example: combine Add-ons for one Product requirement”Consider an OpenCart → WooCommerce migration where both platforms satisfy the Open-Source prerequisite and the purchased migration includes all four Standard Add-ons. The business requirement is to migrate only active Products with stock, place the source short description in the WooCommerce description field, use a supported regional base-price field or database column as the destination price input, and increase the resulting Regular Price by 12%.
The configuration should be reasoned through in the fixed Add-on order:
| Stage | Example requirement | What to verify |
|---|---|---|
| Data Filter | Include Products that meet the approved active/in-stock conditions. | The final migrated Product set contains the intended records and required relationships remain usable. |
| Advanced Data Mapping | Redirect the supported source Short Description field to the compatible WooCommerce Description field without changing the value as part of mapping. | Representative Products contain the complete source description in the approved destination. |
| Advanced Database Mapping | If the source regional_base_price field or database column is confirmed supported, map it to a compatible WooCommerce Regular Price destination. | Both platforms are Open-Source, the specific source and target locations are supported, the value is compatible, and the required WooCommerce behavior can use the stored result. |
| Data Transformation | Apply the approved 12% increase to the resulting Regular Price value. | Normal, boundary, decimal, and empty-value cases produce the approved final price without breaking Product relationships or downstream use. |
If the regional price field or database column is not supported, do not force the Advanced Database Mapping step merely because both platforms are Open-Source. Keep the supported Standard rules, then prepare only the unsupported portion for review.
The example illustrates one combined requirement. Configure only the Add-ons actually purchased and needed for the migration, and validate the final result against the approved business rule rather than copying the example values into unrelated migrations.
Expected result
Section titled “Expected result”After completing Add-ons:
- every configured Add-on is included in the purchased service and applicable to the selected migration path;
- Data Filter rules produce the intended record scope;
- mapping rules use supported sources and compatible target destinations;
- Data Transformation rules produce valid target-field values after applicable mapping stages;
- rule interactions do not create conflicting destinations, invalid values, or broken relationships;
- any requirement outside Standard Add-on scope is separated for Custom Service review;
- the configuration is ready for Customization, when applicable, or final configuration review.
Verify the Add-ons
Section titled “Verify the Add-ons”| Check | Pass condition |
|---|---|
| Entitlement | Every configured Add-on is included in the purchased service. |
| Applicability | The selected path, data type, field or column, and required operation are supported. |
| Processing order | The combined rules are reviewed in Data Filter → Advanced Data Mapping → Advanced Database Mapping → Data Transformation order. |
| Record scope | Filters include and exclude the intended records. |
| Field destinations | Mapping rules use compatible target fields or columns. |
| Value compatibility | Mapped or transformed values can be represented correctly by the selected target field or column. |
| Relationships | Identifiers and dependencies remain intact. |
| Target behavior | Required admin, storefront, app, extension, integration, or business behavior is verified when it depends on the migrated value. |
| Combined result | Representative normal, boundary, and exception records produce the approved migration result. |
If this does not work
Section titled “If this does not work”| Issue | What to do |
|---|---|
| Add-ons is unavailable | Review the purchased service and migration details to confirm that an Add-on is included. |
| An expected Add-on is missing | Confirm the purchased Add-on and selected migration path, then submit a ticket with the migration and order details if the control should be available. |
| A required field, column, operator, or destination is unavailable | Do not approximate the requirement with an unrelated control. Confirm supported Standard handling or prepare the unsupported portion for Custom Service review. |
| Advanced Database Mapping is unavailable | Confirm that both the Source Platform and Target Platform are Open-Source. If either side is Non-Open-Source, use another supported approach or prepare a non-standard requirement for review. |
| Rules conflict | Correct the earlier scope or destination rule first, then re-evaluate later Add-ons. |
| The expected result is uncertain | Test representative normal, boundary, and exception records before migration execution. |
Next step
Section titled “Next step”If Custom appears, continue to Select Customization.
Otherwise, continue to Review the Full Migration Configuration.