Overview

Migration Action Options

Choose the route that matches the next run’s configuration and intended Target Store result. Make the decision in the dropdown at the bottom of Connect Stores. For decision context across the three Migration Actions, see Migration Actions in the Learning Center.

Check which workflow applies

Connect Stores uses shorter UI labels for the three Migration Actions:

Migration Action	Exact UI label in the Connect Stores step
Perform a New Migration	Start a new migration
Continue the Migration with Last Saved Configuration	Continue previous migration
Continue the Migration with a New Configuration	Continue previous + reconfig

• Demo Migration: only the Start a new migration UI label is selectable, corresponding to Perform a New Migration.
• Paid Migration that has not run yet: only Start a new migration is selectable because no earlier paid migration activity or saved configuration exists.
• Paid Migration after it has run at least once: all three UI labels can become available. Choose the underlying Migration Action according to whether the next run should start fresh, reuse the last saved configuration, or reopen the Configuration step.

Use Run a Demo or Full Migration for the Demo and first paid walkthroughs.

Compare later paid actions

Migration Action	Exact UI label	Where it takes you	Configuration handling	Suitable starting point
Continue the Migration with Last Saved Configuration	Continue previous migration	Directly to the Migration step.	Reuses the parameters from the most recent run. Edit Config can open Configuration for inspection or adjustment before starting.	The previous result and settings remain useful.
Continue the Migration with a New Configuration	Continue previous + reconfig	Configuration.	Review and change supported settings, then continue to the Migration step.	Useful earlier work remains, but the next activity needs intentional configuration changes.
Perform a New Migration	Start a new migration	Configuration.	Complete configuration for a fresh migration result.	The earlier migrated outcome should not be continued.

Use Continue actions for later migration activity

After a paid migration has run at least once, use Continue the Migration with Last Saved Configuration or Continue the Migration with a New Configuration for later activity on that same purchased migration. Both actions follow the fixed Source Platform to Target Platform direction of the purchased migration and run only when an activity is started. They do not create an always-on or bidirectional synchronization channel.

Customers can perform these actions manually through the purchased migration. When the project uses Managed Migration or Custom Migration with Expert Handle, Next-Cart technical specialists can perform the applicable Continue action on request within the active service and agreed scope.

Make the decision

1. Inspect the earlier Target Store result.

   Identify records, values, and relationships to retain or correct. Use Activity Timeline for operational history, not configuration values.

2. Choose the configuration route.

   • Reuse the most recent settings with Continue the Migration with Last Saved Configuration by selecting Continue previous migration in the Connect Stores step.
   • Use Edit Config before starting if the loaded settings need inspection or adjustment.
   • Choose Continue the Migration with a New Configuration by selecting Continue previous + reconfig when the earlier result remains useful but the next activity needs a deliberate Configuration review.
   • Choose Perform a New Migration when a fresh result is required; select Start a new migration in the interface after reviewing replacement risk.

3. Check source scope and target impact separately.

   Review source-reading settings, filters, target-data clearing, and protected records. No dropdown action automatically selects newly-added-only processing or authorizes broader deletion.

Migrate different data types at different times

A paid migration can use different supported data-type selections in separate migration activities, but the later activity must still use an action, configuration, and source-data window that are valid for the active migration’s history.

For example, if Products are migrated first and Orders are intended for a later activity:

• confirm that the later configuration includes Orders and every required dependency or relationship for the accepted result;
• verify whether Customers, Products, or other related records already exist in the Target Store and remain compatible with the later Order activity;
• choose the migration action based on whether the earlier result should be reused, reconfigured, or replaced;
• enable Continue the previous migration in Additional Options when the later activity is intended to carry new Source data forward while preserving relationships to earlier migrated data;
• validate representative Order-to-Customer and Order-to-Product relationships after the later activity.

Products can be migrated first and Order history can be migrated later before go-live. Preserve the relationship between the migrated Products and later Orders by keeping the same migration path and validating representative Order-to-Product and Order-to-Customer links after the later activity.

The purchased Migration can be run repeatedly during its 12-month validity period without a separate fixed run-count cap. Every later activity remains subject to the fixed migration path, Store URL locks, supported scope, service terms, and available Entity Points capacity.

Keep these controls separate

• Continue the previous migration is an Additional Option inside Additional Options. It is not the Continue previous migration action label in the Connect Stores dropdown, and it is not Resume Migration for a stopped execution session.
• To import additional new Source data while preserving supported relational links to data migrated earlier, use Continue the Migration with Last Saved Configuration or Continue the Migration with a New Configuration and enable Continue the previous migration in Additional Options. The exact processing behavior still depends on the selected data types, migration path, and supported scope.
• Clear data on your Target Store before the Migration can delete existing target records of selected types, including records not created by Next-Cart. Review it independently of a fresh action.
• Run Mode controls browser-dependent or background execution; it does not select the additional-data scope.
• A migration action does not reset Store URL Locking or Entity Points history.

Before starting

• Confirm the correct Active purchased migration and remaining capacity.
• Verify pre-filled connection details and every established URL lock. Test Connection is optional.
• Record intended configuration changes and their expected target effects.
• Protect target records and prepare recovery before destructive work.
• Resolve an unclear action, unsupported requirement, or unexpected state through Support Tickets before another run.

Next Steps

• Continue the Migration with Last Saved Configuration
• Continue the Migration with a New Configuration
• Perform a New Migration

For detailed control boundaries, use Migration Actions and Additional Options.