Perform a New Migration

Perform a New Migration

Use Perform a New Migration when the previous migrated result should no longer be the basis of the next run. In Connect Stores, this Migration Action appears as Start a new migration.

This action creates a fresh configured result on the same purchased Source Platform-to-Target Platform path. It does not reset Store URL locks, the purchased migration identity, or Entity Points history.

Use this action when

Choose a fresh migration result when:

• the earlier migrated result should be replaced rather than continued;
• the next run needs a distinct result that will be validated independently;
• the required change is broader than continuing the earlier result with revised supported configuration.

Use Continue the Migration with a New Configuration when the earlier result remains a useful basis and supported configuration changes can address the requirement.

Keep replacement separate from target clearing

Perform a New Migration and Clear data on your Target Store before the Migration are separate decisions. The clearing option can delete records that were not created by Next-Cart. Confirm the intended replacement scope, protect unrelated target records, and prepare recovery before enabling destructive target clearing.

Before you start

• Open the correct Active purchased migration.
• Review the previous Target Store result and identify what should be retained, replaced, or protected.
• Confirm the intended data scope, validation samples, and recovery plan for any destructive target operation.
• Do not use this action to bypass a Store URL lock or to reset Entity Points usage.

Select Start a new migration

1. In the Next-Cart Dashboard, expand Migrations, open My Migrations, and select the intended purchased migration.
2. In the Connect Stores step, confirm that the stored Source and Target details still identify the intended stores. Use Connect Your Source and Target Platforms or Troubleshoot Connection Setup when a connection needs attention.
3. In the migration-action dropdown, select Start a new migration. Next-Cart opens the Configuration step for the next run.

Test Connection is optional and does not establish or clear a Store URL lock. Follow Store URL Locking and Store Identity when store identity is uncertain.

Review Configuration for the fresh result

A fresh migration action does not mean every configuration value should be accepted without review. In the Configuration step, confirm the complete intended result across:

• Select Data;
• Additional Options;
• Attribute Mapping;
• purchased Add-ons;
• approved Custom requirements, when applicable.

Keep Continue the previous migration separate from the migration action selected in the Connect Stores step. It is an Additional Option with its own new-data-delta and relationship-continuity behavior.

Use the Configuration guides for the exact procedures:

• Select Data
• Additional Options
• Attribute Mapping
• Add-ons
• Custom
• Review Migration Configuration

When configuration is complete, click Go to Migration.

Run and validate the fresh result

Use Start and Monitor a Migration for Run Mode, execution status, interruption behavior, and migration-log handling.

After processing finishes:

• validate every selected data type and required relationship against the fresh-result plan;
• confirm that only the intended earlier migrated scope was replaced;
• verify protected manual, test, and application-created target records;
• investigate failed and skipped records;
• complete Validate Results After a Migration Action.

Completed means processing finished. It does not prove that every record was imported successfully or that the result is acceptable for launch.

Entity Points and continuity boundaries

A fresh action does not reset Entity Points history. Newly eligible counted records consume Entity Points when they are successfully migrated for the first time. Records already recognized under the same purchased migration and fixed migration path do not consume Entity Points again merely because another supported migration action processes them.

Demo Migration and a paid migration that has never run use Start a new migration only. See Run a Demo or Full Migration for first-run procedures.

Resolve a problem

• Replacement scope is unclear: do not start. Classify the affected target records first.
• Configuration is not ready: return to the relevant Configuration page, correct the setting, and review the full configuration again.
• Unexpected deletion or replacement occurred: stop further activity, preserve the migration log and target evidence, apply the recovery plan where appropriate, and contact Support.

Next Steps

Continue with Validate Results After a Migration Action after the migration activity finishes and the log has been preserved.