Continue Migration Issues

Continue Migration Issues

Restore the intended continued result without stacking another migration activity on an unexplained outcome. First confirm which continuation action was used, which configuration it applied, and which source records it was instructed to read.

Use this page for issues after either:

• Continue the Migration with the Last Used Configuration;
• Continue the Migration with a New Configuration.

A continuation action does not define the source-data window

Continue the previous migration and Migrate only newly added entities are separate Source Platform Options. Diagnose their state independently from the selected migration action.

Observable problems

Use this page when one or more of these conditions applies:

• a continuation action is unavailable;
• the loaded configuration is not the one you expected;
• approved configuration changes do not appear in the target result;
• no records, too few records, or the wrong records are processed;
• updated existing source records remain unchanged in the target store;
• processing resumes from an unexpected point;
• duplicate or conflicting records appear after continued activity;
• the migration pauses, stops, or finishes with unexpected Failed or Skipped records;
• previously accepted target records or relationships change unexpectedly;
• Entity Points usage does not match the records you expected to process.

What the problem usually means

Symptom	Most likely meaning
The Last Used Configuration action is unavailable	No previous completed migration activity recorded a reusable configuration, the wrong purchased service is open, or the service is not Active.
The loaded settings are unexpected	A different completed activity supplied the recorded configuration, or the earlier configuration was not suitable for the intended activity.
New settings are not reflected	The Last Used Configuration action was selected, a configuration difference was not applied, the affected records were outside the source-data window, or the result is hidden by target-store conditions.
No records are processed	The source-reading window contains no eligible records, the selected data scope excludes them, processing is already complete, access changed, or Entity Points capacity blocks eligible records.
Existing records were updated in the source but not processed	Migrate only newly added entities was enabled. That option reads records added after the last successful migration run; it does not include existing records merely because they were updated.
Processing starts from the wrong point	Continue the previous migration does not match the interruption being recovered, or the activity and History entry were identified incorrectly.
Duplicates appear	The source window overlapped earlier processed records, the target already contained equivalent records, record identity changed, or a display issue is presenting one stored record more than once.
Earlier accepted data changes	A new configuration affected existing relationships or target-writing behavior, target clearing was enabled, or overlapping target automation modified the result.
Browser processing pauses	Run in Browser was used and the migration tab was closed or navigation interrupted processing.

Diagnose the activity before changing anything

1. Preserve the current evidence

   Do not start another migration activity. Record the activity date, final state, data-type counts, Success, Failed, and Skipped results, migration log where available, and representative source and target identifiers.

2. Confirm the purchased service and migration path

   In Account -> Migrations -> My Migrations, verify that you opened the intended Active service and the correct Source Platform to Target Platform path.

3. Confirm the exact action in History

   Identify whether History records Continue the Migration with the Last Used Configuration or Continue the Migration with a New Configuration. Do not infer the action from the target result.

4. Identify the configuration that should have applied

   For the Last Used Configuration action, compare the loaded settings with the configuration recorded by the relevant earlier completed activity.

   For the New Configuration action, compare the completed configuration with the approved change list. Check Data, Options, Mapping, purchased Add-ons, and approved Customization where applicable.

5. Verify Source Platform Options separately

   Confirm whether Continue the previous migration or Migrate only newly added entities was enabled.

   Determine the exact intended source-data window: interrupted records, newly added records, or the normal configured scope.

6. Reconcile processing evidence

   Compare the intended scope with progress and Success, Failed, and Skipped results for every selected data type. A completed activity can still contain failed, skipped, or out-of-scope records.

7. Check target identity and visibility

   Search representative records by stable identifiers. Confirm that the correct target environment, site, language, channel, status, filters, cache, and indexing state are being reviewed.

8. Classify target impact

   Confirm whether earlier migrated records, manual records, test records, and application-created records remained intact. Stop further activity if deletion, replacement, or relationship changes exceed the approved scope.

Apply the correction that matches the cause

Confirmed cause	Safest corrective action
No earlier completed activity recorded a reusable configuration	Use the standard Full Migration workflow. Do not treat a first migration as a continuation.
The recorded configuration remains correct	Use Continue the Migration with the Last Used Configuration only after the source-data window and target state are confirmed.
Any selected data, option, mapping, Add-on rule, or Customization must change	Use Continue the Migration with a New Configuration and document every intentional difference.
The earlier result should no longer remain the basis for the target result	Review Perform a New Migration and its replacement risks before selecting it.
Interrupted processing must resume	Use Continue the previous migration only for the verified interrupted activity and expected stop point.
Only records added after the last successful run should be read	Use Migrate only newly added entities and confirm that updates to existing records are outside the intended scope.
Existing updated records must also be processed	Do not use newly-added-only behavior for that activity. Select the appropriate action and configuration after confirming the target impact.
A connection credential or access condition changed	Correct the connection and verify it. Do not select a different migration action solely to compensate for a connection problem.
The target result is correct in storage but not visible	Correct the target-side status, channel, theme, cache, index, or navigation condition, then revalidate without another migration activity.
Failed or Skipped records explain the gap	Correct the responsible source data, access, platform constraint, configuration, or capacity issue before deciding on another activity.
Entity Points capacity or usage is the blocker	Follow Entity Points Issues before selecting another migration action.
Duplicates or conflicting records appear	Follow Duplicate Data before deleting records or changing the action.
Expected records are absent	Follow Missing Data after confirming the action and source-data window.

Stop when the earlier accepted result is at risk

If continued activity deletes protected records, changes accepted relationships beyond the approved configuration, or creates broad duplication, preserve the target state and migration evidence. Do not attempt bulk cleanup or another migration activity before support review.

Verify the correction

The issue is resolved when:

• History records the intended continuation action;
• the applied configuration matches either the verified last used settings or the approved change list;
• Source Platform Options match the intended record window;
• every selected data type has reviewed Success, Failed, and Skipped results;
• representative records and their relationships are correct;
• the earlier accepted target result remains intact except for approved changes;
• Entity Points usage is explainable;
• no unexplained duplicate, deletion, or replacement remains.

Complete Validate Results After a Migration Action after the correction.

Evidence to collect

Provide:

• purchased service and migration path;
• activity date, completion time, and History entry;
• exact continuation action;
• earlier completed activity that supplied the recorded configuration;
• approved configuration change list, when applicable;
• state of Continue the previous migration and Migrate only newly added entities;
• intended source-data window;
• selected data types and Run Mode;
• Success, Failed, and Skipped counts;
• Entity Points Statistics before and after the activity;
• source and target identifiers for affected and unaffected samples;
• expected result and actual result;
• screenshots of customer-facing errors where useful;
• migration log where available.

Do not include passwords, full secret keys, private keys, payment-card data, or unnecessary customer personal data.

Escalate when

Open a ticket when:

• the action or recorded configuration differs from the approved behavior;
• a verified correction still produces the same failure;
• the interruption point or source-data window cannot be determined safely;
• protected target records or relationships changed unexpectedly;
• duplicate or destructive impact prevents safe testing;
• a purchased Add-on or approved Customization behaves differently from its documented rule;
• internal intervention or platform-specific analysis is required;
• a security incident is suspected.

Prevent the issue next time

Before continued migration activity:

1. identify the exact earlier completed activity;
2. decide whether the recorded configuration remains correct;
3. document every required configuration change;
4. choose the migration action separately from Source Platform Options;
5. define the intended source-data window;
6. protect target records and pause conflicting automation where needed;
7. prepare representative records for immediate validation.

Next step

Use Compare Migration Action Options when the correct next action is still unclear.