Perform New Migration Issues

Perform New Migration Issues

Protect the target store and determine whether the fresh result can be retained before taking further action. A new migration can replace earlier migrated data for the affected scope, while target-data clearing is a separate destructive control with broader consequences.

Use this page after Perform a New Migration when the result is incomplete, duplicated, unexpectedly destructive, or inconsistent with the approved fresh-result plan.

Do not repeat destructive activity to test the result

Stop overlapping migration activity, manual imports, and target automation when replacement or deletion is unclear. Preserve the current target state, migration log, and available backup, export, snapshot, or recovery reference before attempting correction.

Observable problems

Use this page when:

• Perform a New Migration is unavailable;
• the result contains earlier, duplicate, or conflicting records;
• records that should have remained were deleted or replaced;
• the fresh result contains only part of the intended source scope;
• the complete new configuration was not applied as expected;
• target-data clearing affected more records than approved;
• manual, test, or application-created target records were changed;
• processing pauses or ends with unexpected Failed or Skipped records;
• the result appears unchanged despite selecting a new migration;
• Entity Points usage does not match the intended fresh result.

What the problem usually means

Symptom	Most likely meaning
The action is unavailable	No previous migration activity completed under the service, the wrong service is open, or the service is not Active. A first migration uses the standard Full Migration workflow.
Earlier records remain	Replacement applied only to the supported affected scope, broader target clearing was not enabled, the remaining records were not created by earlier migration activity, or target cache and indexing still display older content.
Duplicate or conflicting records appear	Equivalent records already existed, source duplicates were included, record identity changed, target clearing did not apply to that scope, or presentation layers show one stored record more than once.
Protected target records disappear	Clear data on Target Store before Migration affected selected data types, replacement scope was broader than approved, or protected records were not classified before starting.
Only a partial fresh result appears	A Source Platform Option, selected data scope, filter, dependency, connection, failed or skipped result, or Entity Points capacity limited the source-data window.
The result uses unexpected settings	The complete fresh configuration differs from the approved plan, a conditional Add-on or Customization was not selected, or target-side behavior is being mistaken for migration configuration.
Processing pauses	Run in Browser was selected and the tab was closed or navigation interrupted processing.
Entity Points usage seems to reset or increase unexpectedly	Replacement does not reset Entity Points history. Usage depends on newly eligible records that migrate successfully for the first time under the same purchased service and migration path.

Diagnose the fresh result

1. Stop further target changes

   Pause overlapping migration activity, imports, catalog automation, order synchronization, and manual cleanup when they can change the affected records or destroy evidence.

2. Preserve recovery evidence

   Record the target environment and time. Preserve the available backup, export, snapshot, database copy, or other approved recovery reference before destructive correction.

3. Confirm the exact History entry

   Verify that History records Perform a New Migration, the intended purchased service, migration path, activity date, and Run Mode.

4. Compare the complete configuration with the fresh-result plan

   Review Data, Options, Mapping, purchased Add-ons, and approved Customization. A new migration requires a complete configuration; do not assume the earlier configuration was reused or replaced correctly without comparison.

5. Verify Source Platform Options separately

   Confirm whether Continue the previous migration or Migrate only newly added entities was enabled. Neither option is automatically required by a new migration action.

   A partial source-reading option can produce a partial fresh result when a complete scope was intended.

6. Separate replacement from target-data clearing

   Identify which earlier migrated records could be replaced by the action and whether Clear data on Target Store before Migration was enabled for selected data types.

   Do not assume that a fresh result automatically deletes every existing target record.

7. Classify target records by origin

   Separate earlier migrated records from manual records, test records, imported records, and records created by applications or integrations. Record which groups were approved for replacement or deletion.

8. Reconcile processing evidence

   Review progress and Success, Failed, and Skipped results for every selected data type. Compare the actual source-data window with the intended complete fresh scope.

9. Check stored records and presentation separately

   Search by stable identifiers in the target admin area. Confirm whether the issue is stored duplication or omission, relationship conflict, or only a theme, channel, cache, index, or navigation problem.

10. Assess whether the current result can be retained

    Determine whether the result is complete and safe enough to correct, whether protected data must be restored, or whether support must define a recovery and replacement plan.

Apply the safest correction

Confirmed cause	Safest corrective action
This was the first migration under the service	Use the standard Full Migration workflow. Do not use Perform a New Migration as the first-run path.
The earlier result should remain useful	Stop and use Compare Migration Action Options to choose a continuation action instead.
The complete configuration is wrong	Document the differences and target impact before selecting any next action. Correct the responsible configuration only after deciding whether the current fresh result can remain.
A Source Platform Option created a partial source window	Define the intended window, classify the current target result, and select the appropriate action and configuration before further processing.
Expected earlier records remain	Determine whether they are outside the supported replacement scope, were created manually or by an application, or are only visible through cache or indexing. Do not delete them by assumption.
True duplicates exist	Follow Duplicate Data to establish record identity and relationship impact before cleanup.
Expected records are absent	Follow Missing Data after confirming configuration, source scope, and processing status.
Target-data clearing deleted protected records	Stop activity, preserve evidence, use the approved recovery source, and contact support. Do not start another migration to compensate for deletion.
Target clearing was expected but not applied	Confirm whether the option was enabled, supported, and scoped to the intended data types. Do not broaden deletion without classifying all target records.
Target storage is correct but storefront output is stale or duplicated	Correct the target theme, channel, cache, index, or navigation condition and revalidate without another migration activity.
Entity Points capacity limits the result	Follow Entity Points Issues before changing the action or source scope.
Failed or Skipped records explain the incomplete result	Correct the responsible source data, access, platform constraint, configuration, or capacity issue before deciding whether the fresh result can be retained.

Replacement and clearing are different controls

Control	What to verify
Perform a New Migration	The approved earlier migrated result and affected scope that should be replaced by a fresh configured result.
Clear data on Target Store before Migration	The selected target data types that can be deleted, including records not created by Next-Cart.
Source Platform Options	Whether interrupted, newly added, or normal configured source records were read.
Target recovery plan	Which backup, export, snapshot, or other recovery method protects records that must remain.

A fresh result does not reset Entity Points history

New eligible records consume Entity Points when they migrate successfully for the first time. Records already counted under the same purchased service and migration path do not consume points again merely because a new migration replaces their earlier target result.

Verify the correction

The issue is resolved when:

• History records the intended action;
• the complete configuration matches the approved fresh-result plan;
• Source Platform Options match the intended source-data window;
• replacement remains within the approved earlier migrated scope;
• any target-data clearing matches the separately approved data types;
• protected manual and application-created records remain or have been restored;
• every selected data type has reviewed Success, Failed, and Skipped results;
• representative records and relationships are correct;
• duplicate, missing, cached, or indexed results are classified and resolved;
• Entity Points usage is explainable;
• recovery evidence remains available until validation and sign-off are complete.

Complete Validate Results After a Migration Action and then perform complete target-store validation.

Evidence to collect

Provide:

• purchased service and migration path;
• exact History entry and activity time;
• earlier completed activity and result intended for replacement;
• complete fresh configuration;
• state of Continue the previous migration and Migrate only newly added entities;
• state and selected data types for Clear data on Target Store before Migration;
• 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;
• classification of earlier migrated, manual, test, imported, and application-created target records;
• expected replacement and actual target impact;
• available backup, export, snapshot, or recovery reference;
• 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 immediately when

Open a ticket before further activity when:

• target deletion or replacement exceeds the approved scope;
• Customers, Orders, identifiers, financial history, or other protected records are affected;
• the current result cannot be retained or recovered safely;
• replacement behavior differs from the approved product model;
• broad duplication or relationship conflicts prevent safe cleanup;
• a supported correction repeatedly fails;
• a purchased Add-on or approved Customization produces unexplained target impact;
• internal intervention or platform-specific recovery is required;
• a security incident is suspected.

Prevent the issue next time

Before performing a new migration:

1. confirm that the earlier result should be replaced rather than continued;
2. classify earlier migrated, manual, test, and application-created target records;
3. define replacement scope separately from target-data clearing;
4. prepare and verify recovery evidence;
5. complete and compare the full fresh configuration;
6. choose Source Platform Options independently;
7. pause conflicting target automation;
8. prepare full-result validation samples and pass conditions.

Next step

Use Perform a New Migration to review the action’s intended behavior. Use Compare Migration Action Options when replacement is no longer the correct outcome.