Validate Results After a Migration Action

Validate Results After a Migration Action

Verify that the selected migration action, configuration path, Additional Options, and execution state produced the intended immediate result before another activity changes the same target scope. This check does not replace complete target-store validation or launch sign-off.

When to use this checklist

Use it after one of these actions reaches a final state:

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

Before you start

Collect the relevant Activity Timeline entry, completed time, migration path, purchased service, migration action, applicable Additional Options, Success, Failed, and Skipped results, Entity Points usage, available migration log, and representative source-to-target identifiers. Review exact configuration values separately when they are needed for validation.

Set the validation boundary

Completed action	Immediate validation boundary
Continue the Migration with Last Saved Configuration	Later processed scope plus checks that the earlier accepted result remains intact.
Continue the Migration with a New Configuration	Later processed scope, every changed setting, and earlier records or relationships that the change could affect.
Perform a New Migration	Complete fresh result, replacement scope, target-data clearing, protected records, and all selected data types.

Configured behavior or execution state	What to verify
Continue action + Continue the previous migration used	For ordinary additional-record processing, the intended new Source records and supported relationships were processed. Data Update field refreshes require their own checks.
Continue action + Continue the previous migration not used	The configured selected scope was processed without assuming that the Continue action itself selected an additional-data window.
Activity was paused or stopped	Recovery followed the documented Browser/Background execution-state flow. Do not treat Continue the previous migration in Additional Options as the resume control.
Data Update was configured	Use Configure Data Update to check eligible existing records, selected field values, required options and preservation of non-selected data. Verify any ordinary new-record scope separately.

Verify the action result

1. Confirm the recorded activity

   Verify the migration activity, migration path, purchased service, completed time, and Run Mode in Activity Timeline.

2. Confirm the data scope and Additional Options

   Compare the selected data types and applicable Additional Options with the records actually processed. If the activity was intended to import additional new Source data while preserving supported relationships, confirm both the Continue action and Continue the previous migration in Additional Options. Do not infer additional-data scope from the migration action alone.

3. Reconcile processing evidence

   Review Success, Failed, and Skipped results for every selected data type. Investigate unexplained omissions before approving the target result.

4. Apply the action-specific checks

   Test the records, configuration changes, replacement behavior, and protected target scope defined below. When Data Update is included, compare selected field values and verify preserved non-selected fields and unassociated data; record counts alone are insufficient.

5. Reconcile Entity Points

   Confirm that newly eligible counted records consumed points when first migrated successfully and that previously counted records were not charged again merely because this action processed them.

6. Record the immediate decision

   Mark the result Pass, Pass with accepted limitations, or Fail. Preserve the evidence and route the result to complete target-store validation.

Action-specific checks

Continue the Migration with Last Saved Configuration

• The recorded configuration loaded unchanged.
• The intended source scope was processed.
• Previously accepted records and relationships remain usable.
• No change-dependent behavior was expected.

Continue the Migration with a New Configuration

• Every approved configuration difference is present.
• Representative records demonstrate each changed behavior.
• Relationships affected by the changes remain correct.
• Earlier accepted data was not altered unexpectedly.

Perform a New Migration

• The fresh configuration produced the intended result.
• Replacement stayed within the approved scope.
• Target-data clearing matched its separately approved setting.
• Protected manual and application-created records remain.
• Recovery evidence remains available until sign-off.

Do not start another action to test an unexplained result

Preserve Activity Timeline evidence, migration logs, representative identifiers, and target evidence. Classify the issue before changing connections, configuration, target data, or migration actions.

If the result fails

Finding	Corrective owner
Wrong connection or inaccessible data	Correct the affected setup and rerun Test Connection for that store.
Wrong selected Data, Option, or standard mapping	Correct Configure Your Migration.
Wrong filter, field or database mapping destination, or transformation	Correct the purchased Add-on and revalidate the affected scope.
Expected Data Update fields were not refreshed	Check eligible prior records, surviving Target counterparts, selected supported fields and optional time restrictions in Configure Data Update.
Approved Customization missing or incorrect	Review the agreed Custom Migration requirement and open a ticket with evidence.
Failed or Skipped records explain the result	Correct the responsible source, platform, access, capacity, or configuration condition.
Wrong data scope or the Continue action and Continue the previous migration configuration	Correct the selected data types, Continue action, or applicable Additional Options before another activity.
Unexpected replacement or deletion	Stop further target changes, preserve evidence, and apply the recovery plan.
Entity Points discrepancy	Review Statistics and Entity Points Issues before continuing.

Evidence record

Record the action, applicable Additional Options, completed time, Run Mode, configuration reference and changes, processed scope, Success, Failed, and Skipped results, representative identifiers, replacement and protected-record result, Entity Points result, findings, owners, decision, and approved next action.

Next Steps

Continue to Validate and Launch Your Target Store for complete migration validation, sign-off, and launch readiness.