Migration Actions and Source Platform Options

Migration Actions and Source Platform Options

Select the migration action in Connect Stores. Demo and a paid migration that has never run have only Start a new migration available. Later paid activity can reuse the most recent parameters, open Configuration for changes, or create a fresh result. Source Platform Options separately control source reading.

Do not use the action name to infer the source-data window

A continuation action does not automatically resume interrupted processing or limit the activity to newly added records. Confirm the applicable Source Platform Options in the configuration used for that activity.

Migration actions

Choose the action in the dropdown at the bottom of Connect Stores. The descriptive article names explain the intent; the bold text below is the exact option selected in the interface.

Action	Use it when	Configuration consequence	Earlier target result
Continue the Migration with the Last Used Configuration: select Continue previous migration	Previous migration activity exists and its result and settings are a useful starting point.	Opens Migration directly with all parameters from the most recent run. Edit Config opens Configuration for inspection or adjustment before starting.	Remains the basis for the next activity, subject to the configuration actually used.
Continue the Migration with a New Configuration: select Continue previous + reconfigure	Previous work remains useful and configuration needs review or changes.	Opens Configuration. Review the stages and click Go to Migration.	Remains useful, but changed behavior and affected records require expanded validation.
Perform a New Migration: select Start a new migration	The customer needs a fresh migration result instead of continuing the earlier result.	Starts a fresh configuration and migration flow for the selected scope.	May replace or conflict with existing target records; protected target data must be classified first.

• For a first paid run, use Start a new migration, then Continue to Configuration. Follow the Full Migration walkthrough.
• Demo uses only Start a new migration and browser execution. Follow the Demo walkthrough.
• Existing paid activity does not permit changing settings during live processing. Inspect the actual migration state before starting another activity.
• Activity Timeline records operational activity, not saved configuration parameters. Verify previous outcomes in the Target Store; inspect exact loaded settings through Edit Config when needed.

Source Platform Options

Continue previous migration in the migration dropdown is not the Continue the previous migration Source Platform Option. The first selects an action; the second controls interrupted source processing.

Source Platform Option	What it controls	What it does not control
Continue the previous migration	Resumes interrupted source processing from the point where it stopped, when supported and applicable.	It does not select a continuation migration action, approve configuration changes, create a fresh result, or move the resumed execution session to another Target Store.
Migrate only newly added entities	Reads records added to the source store since the last successful migration run, when supported and applicable.	It does not include existing source records merely because they were updated after that run.

A migration action and a Source Platform Option can apply to the same activity. Select the action based on the intended configuration and target result, then confirm the source-reading option based on the required source-data window.

Choose the correct control combination

Intended outcome	Migration action	Source-reading check
Continue from accepted earlier work without changing any configuration	Continue the Migration with the Last Used Configuration	Confirm whether the recorded source-reading options still match the intended window.
Continue from useful earlier work after changing selected data, Options, Mapping, Add-ons, or approved Customization	Continue the Migration with a New Configuration	Select the supported source-reading behavior intentionally in the new configuration.
Build a fresh result instead of continuing the earlier result	Perform a New Migration	Confirm the required source scope separately and assess target replacement or conflict risk.
Resume processing that stopped before completion	Choose the action that matches the intended configuration and earlier-result decision.	Use Continue the previous migration when it is available and appropriate.
Process only records added after the last successful migration run	Choose the action that matches the intended configuration and earlier-result decision.	Use Migrate only newly added entities when it is available and appropriate.
Process existing records whose source values changed after the last successful run	Choose the action and configuration needed for the correction.	Do not rely on Migrate only newly added entities for those existing records.

Controls that remain separate

Control	Separate purpose
Clear data on your Target Store before the Migration	Deletes applicable target records before processing when available and selected. It is a destructive Target Platform Option, not a migration action or Source Platform Option.
Run Mode	Determines whether processing runs in the browser or continues in the background. It does not change configuration or source scope.
Entity Points Plan	Provides counted-record capacity. It does not select an action or filter the source-data window.
Data Filter	Applies purchased field-level conditions per data type to determine which records migrate. It is not a replacement for a Source Platform Option.
Store URL identity	Keeps the paid migration bound to every Source or Target Store URL already locked under the store-identity rules. Migration actions and Source Platform Options do not reset those locks.

Target clearing is not a generic correction method

Do not use Clear data on your Target Store before the Migration to resolve an uncertain action choice, duplicate-data problem, or incomplete validation result. Identify which target records must remain and preserve recovery evidence before any destructive change.

Configuration and validation consequences

Decision	What must be verified
Last Used Configuration	The most recent parameters were used, or intentional Edit Config changes are recorded and validated; the intended source scope and protected earlier result are verified.
New Configuration	Every changed setting produced the intended result, unchanged accepted records remain correct, and interactions between new and earlier behavior are understood.
New Migration	The fresh result is complete, earlier migrated records were replaced only as intended, and manual, imported, application-created, or otherwise protected target records remain safe.
Continue the previous migration	Processing resumed from the correct interruption point without creating an unintended gap or duplicate scope.
Migrate only newly added entities	The last successful migration boundary is correct and existing updated records were not incorrectly expected in the result.

Completion status does not prove data correctness. Review Success, Failed, and Skipped results, then validate representative target records and relationships against the intended action and source-data window.

Entity Points behavior

The selected action does not determine whether a record consumes Entity Points. A new eligible counted record consumes points when it is first migrated successfully. A record already counted under the same purchased service and migration path does not consume points again merely because another supported migration action processes it.

Use Entity Points for the complete counting rules.

Use Store URL Locking and Store Identity before changing Store URLs or interpreting a store-identity mismatch.

Repeat migration activity and service boundaries

Migration actions describe how an existing paid migration can continue, reconfigure, or start a fresh result. They do not define a universal numeric entitlement such as a fixed number of migrations or an unlimited number of reruns.

The service active period, the migration actions available for the project’s history, Entity Points capacity, Store URL locks, and the intended source-data window are separate controls. A 12-month active period is a time boundary for the purchased service; it is not by itself a statement that every migration action can be repeated without limit.

Before planning another activity or a final pre-launch data pass:

1. confirm the paid migration is still active;
2. review the action choices actually available for that migration;
3. decide whether the next activity should reuse the last configuration, use a new configuration, or create a fresh result;
4. use Migrate only newly added entities only when the required source window is limited to records added since the last successful run and the option is available;
5. do not expect that option to include existing records whose values were updated after the previous run;
6. verify Entity Points and Store URL constraints before execution.

If the required activity is not represented by the available controls, use Support Tickets to confirm the applicable service path instead of inferring entitlement from an earlier migration result.

Later migration activity is not continuous synchronization

The ability to run another supported migration activity does not create a continuous one-way or two-way synchronization service. Migration actions process data for the active migration when that action is started; they do not establish an always-on replication channel between Source and Target.

Likewise, a repeated File Upload or an action that processes newly added source records should not be described as recurring synchronization. If a project requires scheduled or continuous sync behavior, treat it as a separate requirement and obtain explicit confirmation of the supported solution.

Do not confuse these decisions

Common confusion	Correct distinction
Continue action and resume option	The action chooses the configuration and result path; Continue the previous migration resumes interrupted source processing.
Continue action and newly-added-only option	The action does not automatically limit records to those added after the last successful run.
New configuration and new migration	New Configuration continues useful earlier work with changed settings; New Migration creates a fresh result.
New migration and target clearing	A fresh migration flow does not by itself mean every existing target record should be deleted.
Updated records and newly added records	An existing record whose value changed is not a newly added record.
Reprocessing and Entity Points recounting	Processing a previously counted record again does not by itself consume its points again under the same service and path.

Related tasks

• Use Migration Action Options to make the action decision before execution.
• Use Additional Options to review Source Platform and Target Platform Options.
• Use Continue the Migration with the Last Used Configuration for direct reuse and the optional Edit Config branch.
• Use Continue the Migration with a New Configuration for the changed-configuration procedure.
• Use Perform a New Migration for the fresh-result procedure.
• Use Continue Migration Issues or Troubleshoot a New Migration when the result or available controls are unexpected.