Skip to content
Back to Site

Compare Migration Action Options

Choose the correct migration action after previous migration activity has completed.

Choose the action that matches the intended target-store result after previous migration activity has completed under an Active purchased service. Before the first migration completes, there is no earlier result or recorded configuration to continue or replace; use the Full Migration workflow instead.

  1. Decide whether the earlier result should remain useful

    Keep the earlier result as the basis for the next activity only when its accepted records and relationships should remain. If the result must be replaced by a fresh configured result, choose Perform a New Migration.

  2. Decide whether configuration must change

    Use Continue the Migration with the Last Used Configuration only when every recorded setting remains correct. Use Continue the Migration with a New Configuration when selected Data, Options, Mapping, purchased Add-ons, or approved Customization must change.

  3. Confirm source-reading behavior separately

    Review Continue the previous migration and Migrate only newly added entities independently. These Source Platform Options control the source-data window; they do not select the migration action.

DecisionLast Used ConfigurationNew ConfigurationNew Migration
Earlier resultRemains useful.Remains useful.Should be replaced.
ConfigurationReused unchanged.Completed again with intentional changes.Completed for a fresh result.
Main riskReusing settings that are no longer suitable.Changed behavior affecting accepted records or relationships.Unintended replacement or deletion of protected target data.
Validation focusNewly processed scope and continued integrity of the earlier result.Newly processed scope, every changed setting, and affected earlier records.Complete fresh result, replacement scope, and protected target records.
ControlSeparate decision
Continue the previous migrationWhether interrupted source processing should resume from the supported stop point.
Migrate only newly added entitiesWhether only records added after the last successful migration run should be read. Existing updated records are not newly added records.
Clear data on Target Store before MigrationWhether selected target data types can be deleted before processing. This is destructive and is not implied by a new migration action.
Run ModeWhether processing depends on the browser tab or continues on Next-Cart servers.
Entity Points PlanWhether sufficient counted-record capacity remains. The action does not reset Entity Points history.

Use Migration Actions and Source Platform Options when you need the complete stable definitions and control boundaries.

Intended outcomeAction
Continue without changing any recorded settingContinue the Migration with the Last Used Configuration.
Change selected Data, Options, Mapping, Add-ons, or approved Customization while retaining useful earlier workContinue the Migration with a New Configuration.
Replace the earlier migrated result with a fresh configured resultPerform a New Migration.
Resume an interrupted migrationChoose the action that matches the intended result, then review Continue the previous migration separately.
Process only records added after the last successful runChoose the action that matches the intended result, then review Migrate only newly added entities separately.
Correct only a connection credentialCorrect and verify the connection; do not change the action solely for that reason.
Correct target-side tax, shipping, payment, theme, channel, or application settingsCorrect the target store and revalidate before starting another migration activity.
Add non-standard data handlingConfirm Custom Service scope before starting another activity.

Before selecting the action, confirm that:

  • previous migration activity completed;
  • the purchased service is Active;
  • the intended earlier result is identified;
  • every required configuration change is documented;
  • Source Platform Options match the intended source-data window;
  • target records that must remain are protected;
  • Entity Points capacity covers newly eligible counted records;
  • the validation scope matches the selected action.

Do not start another migration activity. Compare the earlier result with the intended result, document every required configuration change, and decide whether the earlier result should remain. Open a ticket when replacement behavior, protected target data, or approved Customization scope cannot be determined safely.

Open the procedure for the selected action: