Skip to content
Back to Site

Continue the Migration with the Last Used Configuration

Continue migration activity without changing the configuration recorded from previous completed activity.

Continue the Migration with the Last Used Configuration

Section titled “Continue the Migration with the Last Used Configuration”

Preserve the earlier accepted target result while processing the next approved source scope with exactly the configuration recorded from previous completed activity. Choose this action only when every recorded setting remains correct.

Use this action when:

  • the purchased service is Active;
  • previous migration activity completed under the same migration path;
  • the earlier result should remain;
  • selected data, Additional Options, Attribute Mapping, Add-ons, and Customization do not need to change;
  • the validation scope is limited to the newly processed activity and continued integrity of the earlier result.

Do not use this action when:

  • this is the first migration under the service;
  • any configuration setting must change;
  • the earlier result should be replaced;
  • target records that must remain have not been classified;
  • the source-reading behavior in the recorded configuration is not appropriate for the next activity.

Use Continue the Migration with a New Configuration when a setting must change. Use Perform a New Migration when the earlier result should be replaced.

Confirm:

  • the correct Active service in Account -> Migrations -> My Migrations;
  • the completed activity and recorded configuration in History;
  • valid source and target store access;
  • the intended source-data window;
  • sufficient Entity Points capacity;
  • no unapproved target-store changes or active automation will conflict;
  • representative records are ready for validation.
  1. Review previous activity

    Open History and identify the completed migration activity that produced the last used configuration.

  2. Confirm the recorded settings remain correct

    Review the data scope, source and target options, mappings, Add-on rules, and Customization used previously.

    If any setting must change, stop and choose the New Configuration action.

  3. Open the migration workflow

    Return to My Migrations, select Start, and choose Continue the Migration with the Last Used Configuration.

  4. Verify Connect Stores

    Confirm that both stores still pass their required connection checks.

  5. Review the loaded configuration

    Confirm that the configuration matches the previous completed activity. Do not alter it under this action.

    Pay particular attention to Continue the previous migration and Migrate only newly added entities. Selecting this migration action does not automatically enable either option.

  6. Open the Migration step

    Review the migration path, Entity Points usage, selected data types, and any deletion warning.

  7. Select a Run Mode

    Choose browser or background processing according to the displayed behavior and operational needs.

  8. Start and monitor processing

    Select Start Migration. Track progress, successful records, failed records, and skipped records for each data type.

  9. Record the final state

    Save the completion time, processed source scope, counts, migration log, and representative target identifiers.

New eligible counted records consume Entity Points when they migrate successfully for the first time. Previously counted records do not consume Entity Points again merely because this action processes them. Taxes, Manufacturers, and Categories do not consume Entity Points.

The activity completes using the recorded configuration without unintended configuration changes. The intended source scope is processed, and the earlier accepted result remains usable.

CheckPass condition
ActionHistory records the Last Used Configuration action.
ConfigurationLoaded settings match the previous completed activity.
Source scopeProcessed records match the intended resume, newly-added-only, or normal source-reading behavior.
ProgressEvery selected data type reaches a reviewed final state.
Earlier resultPreviously accepted records and relationships remain intact.
Entity PointsUsage reflects only newly migrated eligible counted records.
  • If the configuration differs, stop and choose the New Configuration action.
  • If the source scope is wrong, review the two source-reading Additional Options before another activity.
  • If processing is interrupted, capture the final processed counts and determine whether Continue the previous migration is required.
  • If target data changes unexpectedly, stop further activity, preserve evidence, and contact support.
  • using the action before any migration has completed;
  • assuming newly added or interrupted-source behavior is automatic;
  • reusing a configuration without reviewing it;
  • ignoring failed or skipped records;
  • using another action to bypass insufficient Entity Points.

Continue to Validate Results After a Migration Action.