Add-ons, Customization, and Custom Service Boundaries

Add-ons, Customization, and Custom Service Boundaries

Choose the narrowest supported capability that can produce the required migration result. Standard configuration, purchased Standard Add-ons, approved Customization, and new Custom Service work are separate layers. Using the correct layer prevents duplicated requirements, unsupported rules, and incorrect assumptions about what a purchased migration includes.

Add-ons and Customization are independent

A purchased migration may include Add-ons, approved Customization, both, or neither. Several Standard Add-ons can work together without becoming Customization or automatically requiring Custom Service.

Capability layers

Capability layer	Primary purpose	Availability	Where to complete the task
Standard Data, Options, and Attribute Mapping	Select supported data types, apply supported migration options, and align standard operational values.	Shown according to the selected migration path and both platform data models.	Configure Your Migration
Standard Add-ons	Apply bounded record filtering, supported field or database-column mapping, or supported target-value transformation.	Add-ons appears only when the purchased migration includes an applicable Add-on.	Configure Add-ons
Approved Customization	Select tailored work already assessed, approved, and attached to the purchased Custom Service.	Custom appears only when approved Customization is included and available for selection.	Select Customization
Tailored or Custom Add-on requirement	Modify/expand a Standard Add-on function or create bespoke Add-on functionality.	Reviewed and quoted through Custom Service.	Prepare Custom Service Requirements
Other new or changed Custom Service requirement	Assess unsupported extraction, scripts, APIs, non-standard relationships, schema engineering, or target behavior outside Standard scope.	Requires requirement definition, assessment, and agreed scope.	Prepare Custom Service Requirements

Standard Service and Managed Service can include purchased Standard Add-ons. Custom Service can include Standard Add-ons, Tailored or Custom Add-on work, and approved Customization. Service type and Add-on scope are separate decisions.

Current Standard Add-ons

Add-on	Fixed price	Operational function	Standard boundary
Data Filter	$50	Selects records within a data type through supported field-based conditions.	Does not add unsupported source data or bespoke filtering logic.
Advanced Data Mapping	$50	Redirects a supported source field to a compatible target field without changing the value as part of mapping.	Tax excluded; does not provide database-column mapping.
Advanced Database Mapping	$100	Maps supported fields and underlying database columns to compatible target fields or columns.	Available only when both platforms are Open-Source; Tax excluded; database placement does not guarantee target-side consumption.
Data Transformation	$50	Changes selected resulting target-field values after applicable mapping stages.	Does not replace mapping or implement unrestricted custom code.

Add-on processing order

When several Standard Add-ons apply, review them in this order:

Data Filter → Advanced Data Mapping → Advanced Database Mapping → Data Transformation

The sequence matters because later applicable stages work with the result established earlier. Validate the observable record scope, destination, stored value, and final transformed value at the appropriate stage.

Mapping layers and value changes

Requirement	Correct layer
Align supported sites, languages, inventory locations, attribute sets, root categories, customer groups, payment statuses, or fulfillment statuses	Standard Attribute Mapping
Redirect a supported source field to a different compatible target field	Advanced Data Mapping
Map a supported source field or database column to a compatible target field or column when both platforms are Open-Source	Advanced Database Mapping
Change the resulting selected target-field value	Data Transformation
Extract unsupported data or implement bespoke schema, relationship, script, API, or target behavior	Custom Service assessment

Advanced Data Mapping and Advanced Database Mapping preserve the value as part of the mapping operation. Data Transformation is the Add-on that changes the resulting selected target-field value.

Open-Source path eligibility is necessary but not sufficient

Advanced Database Mapping requires an Open-Source Source Platform and an Open-Source Target Platform. The specific source field or column, target destination, and value compatibility must still be supported. A stored database value also does not prove that the Target Platform admin interface, storefront, theme, app, extension, integration, or business logic will use it.

Standard, Tailored, and Custom Add-on scope

Scope tier	Meaning	Commercial treatment
Standard Add-on	Pre-built fixed-scope capability used without modification.	Fixed catalog price shown above.
Tailored Add-on	A Standard Add-on function that needs tuning, modification, or expanded scope.	Reviewed and quoted through Custom Service.
Custom Add-on	Bespoke Add-on functionality outside the Standard catalog.	Reviewed and quoted through Custom Service.

A custom field, database column, or combination of several Standard Add-ons does not by itself make the requirement Custom Service. Test supported Standard handling first, then escalate only the unsupported portion.

Approved Customization

Approved Customization is tailored work already included through Custom Service. It represents a defined requirement with an agreed source location, target result, rules, examples, dependencies, and acceptance conditions.

The Custom stage allows the customer to select applicable approved work items when the current migration activity permits configuration changes. It does not make an unassessed new requirement part of the service.

Situation	Correct treatment
The approved item is present and the requirement is unchanged	Select and validate the approved Customization.
The approved item is missing, inactive, or behaves differently from the approved result	Treat it as an implementation or service-attachment issue and preserve evidence for support.
The source, target, rules, dependency, or expected result changed	Submit the changed requirement for Custom Service scope review.
The requirement was never assessed or approved	Prepare a new Custom Service requirement.

When Custom Service assessment is required

Use Custom Service assessment when the required result cannot be produced safely through the supported migration path, standard configuration, Standard Add-ons, or existing approved Customization.

Typical thresholds include:

• unsupported source fields, tables, apps, plugins, modules, files, API properties, or external systems;
• filtering, mapping, or transformation behavior beyond supported Standard controls;
• bespoke relationships or dependencies between records;
• schema engineering, scripts, APIs, or non-standard target behavior;
• modification or expansion of a Standard Add-on function;
• bespoke Add-on functionality outside the Standard catalog;
• material changes to previously approved Customization.

A malfunction is not automatically Custom Service

When a supported feature or approved implementation does not behave as documented, preserve reproducible evidence and troubleshoot the supported feature first. Custom Service applies to new, changed, or non-standard requirements, not to avoid diagnosing a supported-feature defect.

Interaction boundaries

Several layers can affect the same data type. Verify the combined result rather than approving each control in isolation.

Interaction	What to confirm
Data selection and Data Filter	The data type is selected and the filter produces the intended record scope.
Data Filter and mapping	Only intended records continue to the mapping stages.
Advanced Data Mapping and Advanced Database Mapping	Each supported source value has one approved compatible destination and rules do not conflict.
Mapping and Data Transformation	The transformation applies to the intended resulting target field.
Add-ons and approved Customization	Dependencies, affected records, and expected results match the approved requirement.
Database mapping and target-side components	The stored value and the required consuming behavior are validated separately.

Availability by migration activity

Activity	Add-ons and Customization behavior
Demo Migration	Add-ons and Customization are unavailable.
First Full Migration	Configure purchased Add-ons and select approved Customization when included and displayed.
Continue the Migration with the Last Used Configuration	Reuses the recorded configuration unchanged; it does not provide a path for changing Add-on rules or Customization selections.
Continue the Migration with a New Configuration	Allows supported configuration changes, including applicable Add-on rules and approved Customization selections.
Perform a New Migration	Starts a fresh configuration path on the same purchased Source Platform-to-Target Platform path; included capabilities remain limited to the purchased migration and agreed scope.

A different Source Platform-to-Target Platform path requires a separate purchased Migration Service.

Related tasks

• Use Configure Add-ons to configure purchased Standard Add-ons.
• Use Configure Advanced Database Mapping for eligible field or database-column mapping.
• Use Select Customization to select approved tailored work already attached to Custom Service.
• Use Prepare Custom Service Requirements to define Tailored Add-on, Custom Add-on, or other new non-standard requirements.
• Use Entity Points Plans and Service Pricing for current capacity and service-pricing rules.
• Use Add-on and Customization Issues when an included capability is missing or produces an unexpected result.
• Use Custom Service Escalation to prepare evidence for assessment or correction.