Perform a New Migration

Perform a New Migration

Replace the earlier migrated result with a fresh configured result when continuation would preserve the wrong basis for the target store. This action applies after previous migration activity has completed and can replace data produced by that activity for the approved scope where supported.

Review target impact before starting

Confirm which earlier migrated records can be replaced, which target records must remain, and whether target-data clearing is enabled. Prepare an available backup, export, snapshot, or other approved recovery method before destructive activity.

When to use it

Use this action when:

• the purchased service is Active;
• previous migration activity completed;
• the earlier migrated result should be replaced rather than extended;
• a complete configuration is ready for the fresh result;
• affected target records are classified;
• the new result will receive full validation.

When not to use it

Do not use this action when:

• this is the first migration under the service;
• the earlier result remains useful;
• only later source data must be processed;
• a supported configuration change can safely continue from the earlier result;
• manual or application-created target records have not been protected;
• replacement behavior is unclear.

Replacement and target-data clearing

Control	Target impact
Perform a New Migration	Can replace earlier data produced by migration activity for the affected scope.
Clear data on Target Store before Migration	Can delete existing target records for selected data types, including records not created by Next-Cart.

Review these controls independently. A fresh migration result does not automatically require broader target-data clearing.

Before you start

Confirm:

• the exact earlier activity and result that will be replaced;
• the selected data types and replacement scope;
• manual, testing, and integration-created target records;
• available recovery evidence;
• stable source and target store connections;
• a complete new configuration;
• sufficient Entity Points capacity;
• full validation samples and pass conditions.

Perform the new migration

1. Review History and Statistics

   Identify the earlier completed activity, current Entity Points capacity, and target-store result that will be replaced.

2. Classify target records

   Separate earlier migrated records from manual, test, and application-created records. Pause systems that can create conflicting data.

3. Prepare recovery evidence

   Create the available backup, export, snapshot, or recovery record. Document the target environment, time, and responsible person.

4. Open the action

   From Account -> Migrations -> My Migrations, select Start and choose Perform a New Migration.

5. Complete Connect Stores

   Verify the source store and target store using the requirements shown for the migration path.

6. Complete the new Configuration

   Configure Data, Options, Mapping, purchased Add-ons, and purchased Customization for the fresh result.

   Review source-reading options separately. A new migration action does not automatically require resume or newly-added-only behavior.

7. Confirm replacement and deletion scope

   Read every displayed warning. Confirm affected data types, earlier migrated records, protected target records, and any separate target-data clearing instruction.

8. Open the Migration step

   Review the migration path, Entity Points usage, selected data types, readiness status, and warnings.

9. Select a Run Mode

   Choose browser or background processing according to the operational plan.

10. Start and monitor processing

    Select Start Migration and follow progress, successful records, failed records, and skipped records by data type.

11. Protect the new result

    Keep overlapping manual changes and automation paused until the initial validation sample is complete.

12. Save evidence

    Record the new configuration, replacement scope, source-reading options, counts, migration log, recovery reference, and sample identifiers.

Entity Points handling

Replacement does not reset Entity Points history. New eligible counted records consume Entity Points when they migrate successfully for the first time. Previously counted records do not consume points again merely because the new migration replaces their earlier target result.

Expected result

A fresh configured result is available for the selected scope. Earlier migrated data is replaced only as approved, protected target records remain, and every selected data type has a reviewed final status.

Verify the result

Check	Pass condition
Action	History records Perform a New Migration.
Configuration	The complete new configuration matches the approved fresh-result plan.
Replacement	Only approved earlier migrated scope was replaced.
Target clearing	Any broader deletion matches the separately approved option.
Protected records	Manual and application-created records that must remain are intact.
Processing	Failed and skipped records are documented.
Entity Points	Usage follows first-successful-migration rules.

If it does not work

Stop further migration activity when replacement or deletion exceeds the approved scope. Preserve the migration log and target evidence, apply the recovery plan where appropriate, and contact support.

Correct configuration failures only after classifying whether the current fresh result can be safely retained or must be recovered.

Common mistakes

• using the action for a first migration;
• confusing replacement with target-data clearing;
• failing to protect manual or application-created records;
• assuming source-reading options are selected automatically;
• validating only a narrow sample after a fresh result.

Next step

Continue to Validate Results After a Migration Action, then complete full target-store validation.