Continue the Migration with a New Configuration

Continue the Migration with a New Configuration

Use Continue the Migration with a New Configuration when the earlier paid migration result remains useful but the next run requires intentional supported configuration changes. On Connect Stores, the corresponding UI label is Continue previous + reconfig.

Selecting this action opens the Configuration step so the next run can keep valid settings and change only what the intended result requires.

Use this action when

Choose this action when the purchased migration path remains correct but one or more supported configuration areas need to change, such as:

• selected data types;
• Additional Options;
• Attribute Mapping;
• purchased Add-on rules;
• approved Custom requirements.

Use Continue the Migration with Last Saved Configuration when the most recent configuration should be reused without intentional changes. Use Perform a New Migration when the earlier migrated result should no longer be the basis of the next run.

Before you start

• Open the correct Active purchased migration.
• Review the previous Target Store result and record each configuration change that is required.
• For every planned change, define the expected target effect and a representative sample that will prove it.
• Identify previously accepted records or relationships that could be affected by the revised configuration.

Select Continue previous + reconfig

1. In the Next-Cart Dashboard, expand Migrations, open My Migrations, and select the intended purchased migration.
2. In the Connect Stores step, confirm that the stored Source and Target details still identify the intended stores. Use Connect Your Source and Target Platforms or Troubleshoot Connection Setup when a connection needs attention.
3. In the migration-action dropdown, select Continue previous + reconfig. Next-Cart opens the Configuration step for the next run.

Test Connection is optional and does not establish or clear a Store URL lock. Follow Store URL Locking and Store Identity when store identity is uncertain.

Apply only the intended configuration changes

Review the loaded configuration and change only the areas required for this run. The exact procedures remain owned by:

• Select Data
• Additional Options
• Attribute Mapping
• Add-ons
• Custom
• Review Migration Configuration

Keep Continue the previous migration separate from this Migration Action. It is an Additional Option with its own new-data-delta and relationship-continuity behavior.

Configuration changes expand the revalidation scope

A changed filter, mapping, data selection, option, Add-on rule, or Custom requirement can affect both later eligible records and records whose earlier result was already accepted. Revalidate the changed rule and representative regression samples before relying on the next result.

When configuration is complete, click Go to Migration.

Run and validate the revised result

Use Start and Monitor a Migration for Run Mode, execution status, interruption behavior, and migration-log handling.

After processing finishes:

• validate every configuration area that changed;
• validate later eligible records affected by the revised configuration;
• recheck representative previously accepted records and relationships that the change could influence;
• investigate failed and skipped records;
• complete Validate Results After a Migration Action.

Completed means processing finished. It does not prove that the revised configuration produced an acceptable business result.

Entity Points and continuity boundaries

Changing configuration does not reset the purchased migration path, established Store URL locks, or Entity Points history. Records already recognized under the same purchased migration and fixed migration path do not consume Entity Points again merely because another supported migration action processes them. Newly eligible counted records consume Entity Points when they are successfully migrated for the first time.

Demo Migration and a paid migration that has never run cannot use this action. See Run a Demo or Full Migration for first-run procedures.

Resolve a problem

• The required change is not supported by Configuration: stop and classify whether the requirement needs an available supported representation, an approved Add-on, or Custom Migration.
• The earlier result should no longer be the basis of the next run: use Perform a New Migration.
• The changed result is unexpected: preserve the migration log and target evidence, identify which changed rule could affect the record, and correct that owner before another run.

Next Steps

Continue with Validate Results After a Migration Action after the migration activity finishes and the log has been preserved.