Continue the Migration with a New Configuration

Continue the Migration with a New Configuration

Preserve useful earlier migration results while applying approved configuration changes to the next activity. Choose this action only after previous migration activity has completed and the earlier target result remains a valid basis for continued work.

When to use it

Use this action to change:

• selected data types;
• source, target, or general Additional Options;
• Attribute Mapping;
• purchased Add-on rules;
• purchased Customization selections.

The action continues from useful earlier work. It is not the correct choice when the earlier result should be replaced entirely.

When not to use it

Do not use this action when:

• no migration has completed under the service;
• the recorded configuration remains correct;
• the earlier result should no longer remain the basis for the target result;
• a target-side setting can be corrected without changing migration output;
• the required behavior falls outside available configuration and approved Custom Service.

Before you start

Prepare:

• the correct Active service and previous completed activity;
• a written change list;
• the expected effect of each change;
• protected target records and controlled automation;
• sufficient Entity Points capacity;
• samples that test both newly processed data and every changed behavior.

Define the changes

Requirement	Configuration area
Change data types	Data
Resume interrupted source processing	Options -> Continue the previous migration
Read only records added after the last successful run	Options -> Migrate only newly added entities
Change target-writing or general migration behavior	Options
Change standard operational values	Mapping
Change record filters	Add-ons -> Data Filter
Change supported field destinations	Add-ons -> Advanced Data Mapping
Change eligible supported field/database-column destinations	Add-ons -> Advanced Database Mapping
Change resulting supported target-field values	Add-ons -> Data Transformation
Select approved tailored handling	Custom

Continue with a new configuration

1. Review the earlier activity

   Open History and identify the configuration and target result that will remain the basis for continued work.

2. Confirm the change list

   Document each setting that will change, why it must change, and which records or relationships it can affect.

3. Open the action

   From Account -> Migrations -> My Migrations, select Start and choose Continue the Migration with a New Configuration.

4. Verify Connect Stores

   Confirm that both stores pass the required connection checks.

5. Complete Configuration

   Review every standard stage and each purchased conditional stage. Apply only the approved changes.

   Select source-reading options according to the intended source scope. A continuation action does not automatically mean interrupted processing or newly-added-only processing.

6. Compare the new and previous settings

   Confirm that every difference is intentional. Pay particular attention to destructive target options, dependencies, mapping changes, filter scope, transformed unique values, field destinations, and selected Customization.

7. Open the Migration step

   Review the migration path, selected data types, Entity Points usage, readiness state, and deletion warning.

8. Select a Run Mode

   Choose browser or background processing according to operational needs.

9. Start and monitor processing

   Select Start Migration and track progress, successful records, failed records, and skipped records by data type.

10. Save validation evidence

    Record the completed action, configuration changes, source scope, counts, migration log, and representative target identifiers.

Validate changed behavior, not only new records

A setting change can affect relationships or previously accepted data. Test each changed option, mapping, filter, transformation, field destination, and Customization outcome.

Entity Points handling

New eligible counted records consume Entity Points when they migrate successfully for the first time. Previously counted records do not consume points again merely because the new configuration processes them. A broader filter or selected scope can consume points when it includes eligible records that have not migrated before.

Expected result

The activity completes from the useful earlier result using the approved new configuration. The intended source scope and changed behavior are visible on the target store without unapproved target impact.

Verify the result

Check	Pass condition
Action	History records the New Configuration action.
Changes	The completed configuration matches the approved change list.
Source scope	Resume, newly-added-only, or normal source reading matches the intended activity.
Changed behavior	Representative records demonstrate each changed setting.
Earlier result	Accepted records remain usable unless an approved change was expected to affect them.
Entity Points	Usage reflects newly migrated eligible counted records.

If it does not work

Return to the responsible configuration stage only after documenting the failed behavior and affected examples. Do not stack another migration activity on top of an unclassified result.

Open a ticket when the setting behaves differently from the documented rule, a Customization item is unavailable, or the target impact cannot be corrected safely.

Common mistakes

• changing settings without a written comparison;
• assuming the action automatically limits source records;
• combining target-data clearing with a narrow source scope without reviewing the result;
• validating only newly added records;
• using configuration changes to compensate for a target-platform setup problem.

Next step

Continue to Validate Results After a Migration Action.