Compare Migration Action Options
Choose the correct migration action after previous migration activity has completed.
Compare Migration Action Options
Section titled “Compare Migration Action Options”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.
Make the decision
Section titled “Make the decision”-
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.
-
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.
-
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.
Compare the actions
Section titled “Compare the actions”| Decision | Last Used Configuration | New Configuration | New Migration |
|---|---|---|---|
| Earlier result | Remains useful. | Remains useful. | Should be replaced. |
| Configuration | Reused unchanged. | Completed again with intentional changes. | Completed for a fresh result. |
| Main risk | Reusing settings that are no longer suitable. | Changed behavior affecting accepted records or relationships. | Unintended replacement or deletion of protected target data. |
| Validation focus | Newly 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. |
Check controls that remain separate
Section titled “Check controls that remain separate”| Control | Separate decision |
|---|---|
| Continue the previous migration | Whether interrupted source processing should resume from the supported stop point. |
| Migrate only newly added entities | Whether 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 Migration | Whether selected target data types can be deleted before processing. This is destructive and is not implied by a new migration action. |
| Run Mode | Whether processing depends on the browser tab or continues on Next-Cart servers. |
| Entity Points Plan | Whether 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.
Common decisions
Section titled “Common decisions”| Intended outcome | Action |
|---|---|
| Continue without changing any recorded setting | Continue the Migration with the Last Used Configuration. |
| Change selected Data, Options, Mapping, Add-ons, or approved Customization while retaining useful earlier work | Continue the Migration with a New Configuration. |
| Replace the earlier migrated result with a fresh configured result | Perform a New Migration. |
| Resume an interrupted migration | Choose the action that matches the intended result, then review Continue the previous migration separately. |
| Process only records added after the last successful run | Choose the action that matches the intended result, then review Migrate only newly added entities separately. |
| Correct only a connection credential | Correct and verify the connection; do not change the action solely for that reason. |
| Correct target-side tax, shipping, payment, theme, channel, or application settings | Correct the target store and revalidate before starting another migration activity. |
| Add non-standard data handling | Confirm Custom Service scope before starting another activity. |
Verify the decision
Section titled “Verify the decision”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.
If the choice is unclear
Section titled “If the choice is unclear”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.
Next step
Section titled “Next step”Open the procedure for the selected action: