Migration Continuation Issues
Separate additional-data processing from execution recovery, then trace configuration, Continue-action and **Continue the previous migration** settings, Entity Points, or target side effects before another migration activity.
Migration Continuation Issues
Section titled “Migration Continuation Issues”A continuation problem can belong to one of two different mechanisms:
- Later migration activity uses Continue previous migration or Continue previous + reconfig in the Connect Stores step, corresponding to Continue the Migration with Last Saved Configuration and Continue the Migration with a New Configuration. When the next pass must carry the most recent migration state forward, pair that action with Continue the previous migration in Additional Options so selected supported data types process records not transferred in that previous state while supported relationships use the carried context.
- Execution recovery resumes or revisits an activity that was already running or manually stopped. It follows the Run Mode, Stop Migration, Resume Migration, and return-flow rules.
Do not use one mechanism to diagnose the other.
Observable problems
Section titled “Observable problems”Apply these checks when:
- Continue the Migration with Last Saved Configuration or Continue the Migration with a New Configuration is unavailable or routes differently from what you expected;
- the loaded configuration is not the intended one;
- additional new Source data is missing, duplicated, or linked incorrectly;
- an updated Source record expected in the later activity is not reflected in the Target Store;
- the migration pauses after the browser tab is closed or navigation leaves the Migration page;
- a manually stopped activity does not continue as expected;
- a background activity is still running after the page was closed and the customer needs to monitor or stop it;
- Failed or Skipped records, Entity Points, or target-side changes explain an incomplete continued result.
Identify which mechanism failed
Section titled “Identify which mechanism failed”| Symptom | Most likely area to investigate |
|---|---|
| Continue actions are non-selectable | A paid Migration has not run yet, the wrong purchased Migration is open, or the service/activity state does not provide a previous result to continue. |
| Continue the Migration with Last Saved Configuration loads an unexpected state | The last recorded project state differs from the state the customer expected. Review the activity and configuration before starting. |
| Continue the Migration with a New Configuration does not produce the intended changes | The changed Configuration was incomplete, unsupported for the path, or not applied to the records being checked. |
| Additional new Source data is missing | additional-data processing was not fully configured, selected data types excluded the records, the path does not support the intended update behavior, or Failed/Skipped/capacity conditions prevented processing. |
| Relationships between later and earlier migrated data are incorrect | Review the Continue action and Continue the previous migration configuration, identifiers, selected data types, mappings, Add-ons, and target-side changes. |
| Browser processing pauses after leaving the page | Run in Browser depends on the active browser tab. Closing the tab or navigating away pauses processing. |
| A background activity continues after leaving the page | This is expected for Run in Background. Reopen the project to return to the active Migration step. |
| A manually stopped activity cannot be continued from a closed page | Re-enter the full workflow and use an applicable Continue action. Continue the previous migration in Additional Options is not the stopped-run resume control. |
| Duplicate or conflicting records appear after a later activity | The additional-data scope overlapped existing target records, record identity changed, target automation wrote to the same scope, or the wrong action/configuration was used. |
Diagnose the activity before changing anything
Section titled “Diagnose the activity before changing anything”-
Preserve the evidence
Do not immediately start another activity. Record the activity time, Run Mode, status, data-type counts, Success, Failed, and Skipped results, migration log where available, and representative source and target identifiers.
-
Confirm the purchased Migration and fixed path
Open My Migrations, select the intended project, and verify the Source Platform → Target Platform path, service status, and applicable Store URL locks.
-
Confirm the Connect Stores action
Identify which Connect Stores UI label was used: Continue previous migration, Continue previous + reconfig, or Start a new migration. A first paid run and Demo Migration use Start a new migration; after a paid Migration has run, all three actions can be available.
-
Confirm the configuration route
For Continue the Migration with Last Saved Configuration, review the loaded state and use Edit Config when configuration inspection or adjustment is needed before starting. For Continue the Migration with a New Configuration, compare the completed Configuration with the approved change list.
-
Confirm additional-data processing separately
If additional new Source data was intended, verify that the activity used a Continue action and Continue the previous migration was enabled in Additional Options. Confirm the selected data types and every path-specific Source Store or Target Store option that affects the data being checked.
-
If the problem is interruption recovery, inspect Run Mode instead
- Run in Browser: closing or leaving the active page pauses processing. While the activity remains open, Stop Migration and Resume Migration control execution. After page exit, return through My Migrations → project → Start, continue through the Connect Stores step → Configuration step → Migration step, and choose an applicable Continue action.
- Run in Background: processing continues after the browser or computer closes. If it is still running, My Migrations → project → Start returns to the active Migration step. If it was manually stopped and the page was then closed, return through the full flow and choose a Continue action.
-
Reconcile processing and capacity
Compare the intended data scope with Success, Failed, and Skipped results for every selected data type. Review Entity Points when eligible counted records remain unprocessed.
-
Check target identity and side effects
Confirm the correct target environment, site, language, channel, status, cache, index, and target automation. Classify earlier migrated, manual, test, and application-created records before cleanup.
Apply the correction that matches the cause
Section titled “Apply the correction that matches the cause”| Confirmed cause | Safest corrective action |
|---|---|
| No earlier paid activity exists to continue | Use the standard first paid workflow with Start a new migration. |
| The previous result and settings remain useful | Use Continue the Migration with Last Saved Configuration after confirming the intended data scope and target state. |
| The previous result remains useful but settings must change | Use Continue the Migration with a New Configuration and document every intentional Configuration change. |
| Additional new Source data must be transferred | Use additional-data processing: a Continue action plus Continue the previous migration in Additional Options, with the required supported data types selected. |
| A browser-mode activity paused because the page was closed or navigation left the page | Reopen the project and use the documented full return flow. Do not substitute the Additional Options control for execution recovery. |
| The activity is stopped but the Migration page is still open | Use Resume Migration when that control is available for the stopped execution session. |
| A background activity is still running after page exit | Reopen the project to return to the active Migration step. Monitor it or use Stop Migration when stopping is required. |
| A manually stopped activity was exited | Re-enter through the Connect Stores step → Configuration step → Migration step and use an applicable Continue action. |
| New Source records are missing | Verify selected data types, the Continue action, ordinary additional-data scope, Failed/Skipped records and capacity before another activity. |
| Data Update did not refresh an existing record | Check prior migration eligibility, the surviving Target record, selected supported fields and any available time restriction in Configure Data Update. Other Add-on rules do not extend its scope. |
| Duplicates or conflicts appear | Follow Duplicate Data before deleting records or starting another activity. |
| Entity Points block the remaining eligible records | Follow Entity Points Issues before choosing another activity. |
Verify the correction
Section titled “Verify the correction”The issue is resolved when:
- the intended Connect Stores action is confirmed;
- the Configuration matches the intended later activity;
- Continue the previous migration matches the intended ordinary new-record scope and is enabled when Data Update is used;
- Browser/Background execution recovery is handled independently from this additional-data processing;
- selected data types have reviewed Success, Failed, and Skipped results;
- representative later records and relationships to earlier migrated data are correct;
- when Data Update is used, selected field values are correct, Target clearing is disabled, and non-selected fields and unassociated data are preserved;
- the accepted Target result remains intact except for intended changes;
- Entity Points usage is explainable;
- no unexplained duplication, omission, deletion, or replacement remains.
Complete Validate Results After a Migration Action after the correction.
Evidence to collect
Section titled “Evidence to collect”Provide:
- purchased Migration and fixed path;
- activity time, status, and Run Mode;
- Connect Stores action used;
- whether Continue the previous migration was enabled in Additional Options;
- selected data types and relevant Source Store / Target Store options;
- Success, Failed, and Skipped counts;
- Entity Points evidence where capacity is relevant;
- representative source and target identifiers;
- target-side automation or manual changes that overlap the affected scope;
- migration log and screenshots when useful.
Do not include passwords, full secret keys, private keys, payment-card data, or unrelated personal data.