Skip to content
Back to Site

Continue the Migration with Last Saved Configuration

Reuse the most recent paid migration configuration, preserve the purchased migration context, and validate later eligible source activity against the accepted setup.

Continue the Migration with Last Saved Configuration

Section titled “Continue the Migration with Last Saved Configuration”

Use Continue the Migration with Last Saved Configuration when the most recent paid migration configuration remains the correct basis for the next run. On Connect Stores, the corresponding UI label is Continue previous migration.

Selecting this action reuses the most recent Select Data, Additional Options, Attribute Mapping, purchased Add-on, and approved Customization configuration and routes directly to the Migration step.

Choose this action when:

  • the accepted migration configuration remains valid;
  • later eligible Source Store activity should follow the same supported setup;
  • no intentional configuration change is required to achieve the next result.

Use Continue the Migration with a New Configuration when supported filters, mappings, data selection, Additional Options, Add-ons, or approved Customization need to change.

  • Open the correct Active purchased migration.
  • Confirm that the previous result and configuration are still the intended basis for the next run.
  • Identify the later eligible records or relationships that need validation after processing.
  • Confirm that no configuration change is required for the intended outcome.
  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 migration. Next-Cart opens the Migration step with the most recent configuration loaded.

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.

Inspect the loaded configuration only when needed

Section titled “Inspect the loaded configuration only when needed”

If you need to confirm the loaded parameters before processing, use Edit Config and inspect the applicable Configuration sections. The detailed procedures remain owned by:

If the intended outcome depends on deliberately changing the configuration, use Continue the Migration with a New Configuration so the action matches the reason for the next run.

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

After processing finishes:

  • validate later eligible Products, Customers, Orders, Blog Posts, or other supported data that should follow the accepted configuration;
  • verify relationships to records migrated earlier where continuity matters;
  • review representative regression samples from the previously accepted result;
  • investigate failed and skipped records;
  • complete Validate Results After a Migration Action.

Completed means processing finished. It does not prove that every later record or relationship is acceptable.

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.

This action does not change the purchased migration path, established Store URL locks, or the meaning of the separate Continue the previous migration Additional Option.

  • The configuration no longer matches the intended result: use Continue the Migration with a New Configuration.
  • The stored connection identity is wrong or unclear: stop and resolve the connection or Store URL identity before processing.
  • Later records do not follow the accepted result: preserve the migration log and target evidence, classify whether the cause is source data, configuration, target behavior, or an unsupported requirement, and correct the owner before another run.

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