Migration Actions and Source Platform Options

Migration Actions and Source Platform Options

Choose a migration action and source-reading behavior as two separate decisions. The migration action determines whether Next-Cart reuses, changes, or replaces the configuration path and earlier result. A Source Platform Option changes how eligible source records are read when that option is available.

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

Migration action	Use it when	Configuration consequence	Earlier target result
Continue the Migration with the Last Used Configuration	Previous completed migration activity recorded a configuration, the earlier result remains useful, and every recorded setting is still correct.	Reuses the recorded Data, Options, Mapping, Add-ons, and approved Customization unchanged.	Remains the basis for the next activity.
Continue the Migration with a New Configuration	Previous work remains useful, but one or more supported configuration settings must change.	Opens a configuration path for intentional changes before migration.	Remains useful, but changed behavior and affected records require expanded validation.
Perform 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 be replaced or conflict with existing target records; protected target data must be classified first.

A first migration has no configuration recorded from previous completed activity. Use the Full Migration workflow and configure it from the beginning. Do not describe first-run settings as last used or saved from prior migration activity.

Source Platform Options

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, or create a fresh result.
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 Target Store before 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.

Target clearing is not a generic correction method

Do not use Clear data on Target Store before 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 recorded configuration is still correct, the intended source window was used, and the earlier accepted result remains intact.
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.

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 Compare Migration Action Options to make the action decision before execution.
• Use Configure Additional Options to review Source Platform and Target Platform Options.
• Use Continue the Migration with the Last Used Configuration for the unchanged-configuration procedure.
• 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 Perform New Migration Issues when the result or available controls are unexpected.