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.

Check which workflow applies

• Demo Migration: only Start a new migration is available, including a repeated Demo.
• Paid migration that has never run: only Start a new migration is available; there are no earlier paid settings to reuse.
• Paid migration with earlier activity: compare the actions below when the migration is ready for further work. Prior activity does not mean a live run can be reconfigured while processing.

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

Compare later paid actions

Option in Connect Stores	Where it takes you	Configuration handling	Suitable starting point
Continue previous migration	Directly to Migration.	Preloads every parameter from the most recent run. Edit Config opens Configuration for inspection or adjustment before starting.	The previous result and settings remain useful.
Continue previous + reconfigure	Configuration.	Review and change supported settings, then click Go to Migration.	Useful earlier work needs intentional configuration changes.
Start a new migration	Configuration.	Complete the configuration for a fresh result, then click Go to Migration.	The earlier migrated outcome should not be continued.

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 directly with Continue previous migration.
   • Use Edit Config before starting if the loaded settings need inspection or adjustment. You do not have to choose another action solely to use that button.
   • Choose Continue previous + reconfigure when you intend to start with the full Configuration review.
   • Choose Start a new migration when a fresh result is required, 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;
• use Migrate only newly added entities only when the desired source window truly consists of records added since the last successful run;
• validate representative Order-to-Customer and Order-to-Product relationships after the later activity.

Do not treat retired historical action labels as separate entitlements or assume unlimited later runs. Use only the migration actions and Source Platform Options actually available to the active migration.

Keep these controls separate

• Continue the previous migration is a Source Platform Option inside Additional Options. It is not Continue previous migration in the action dropdown.
• Migrate only newly added entities does not include existing records merely because their values were updated.
• 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 source 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 the Last Used Configuration
• Continue the Migration with a New Configuration
• Perform a New Migration

For detailed control boundaries, use Migration Actions and Source Platform Options.