Skip to content
Back to Site

Validate Full Migration Results

Reconcile processing, scope, configuration, representative records, relationships, and accepted limitations before the Full Migration can enter domain approval and launch preparation.

Verify the completed activity, processed scope, configuration behavior, representative records, relationships, and accepted limitations. Use the evidence to decide whether to proceed to detailed domain validation and launch preparation or correct and revalidate the result.

A completed processing status is an entry condition, not acceptance. Validate the migration as one connected result, then use the detailed checks for Products and Categories, Customers and Orders, Content, URLs and Redirects, sign-off, and launch readiness wherever deeper evidence is required.

Use it after a Full Migration reaches a final state and the immediate execution review is complete. For later continuation or new-migration activity, first complete Validate Results After a Migration Action so the selected action, Additional Options, data scope, and execution state are confirmed.

Do not begin another migration activity while an unexplained result, destructive target impact, or Entity Points discrepancy remains open.

If the project uses the Migration Project Toolkit, record representative checks and findings under Validation evidence. Keep the detailed screenshots, exports, and sensitive evidence in the approved evidence repository and link to them from the workbook.

Collect evidence that identifies exactly what was run and what result should be accepted.

EvidenceRecord
Purchased serviceMigration path, service type, service status, and target store.
Migration activityCompletion time, action, Run Mode, and relevant Activity Timeline entry.
Data scopeOrdinary record-migration scope, any intended additional new records, and selected Data Update fields on eligible existing records when configured.
Execution recoveryRun Mode and, when the activity was paused or stopped, the documented recovery path used for that execution.
ConfigurationSelected data types, Additional Options, Attribute Mapping, purchased Add-ons, and approved Customization.
Processing resultData-type progress, Success, Failed, and Skipped totals, and migration log where available.
Account evidenceRelevant Statistics and Activity Timeline information.
Acceptance baselineApproved scope, sample plan, exact or transformed expectations, severity rules, and sign-off owners.
Record evidenceStable source identifiers, target identifiers or URLs, expected result, and actual result.

Protect credentials and personal data in the validation record. Use only the evidence required to identify the issue and compare the result.

Before sampling records, confirm that the evidence belongs to the intended migration result.

  • Verify the Source Platform and Target Platform in the purchased migration path.
  • Verify the correct purchased service and target environment.
  • Record the migration action and Run Mode.
  • Confirm whether a Continue action was paired with Continue the previous migration in Additional Options.
  • Confirm the approved configuration used for the activity.
  • Record target records that had to remain protected and whether target-data clearing was approved.

Reconcile processing before data acceptance

Section titled “Reconcile processing before data acceptance”

Review every selected data type that appears for the migration path. When all supported types are selected, the normal processing sequence is:

Taxes -> Manufacturers -> Categories -> Products -> Customers -> Orders -> Reviews -> Coupons -> CMS Pages -> Blog Posts

A data type can be absent when it is unsupported for the selected migration path or was not selected. Absence is acceptable only when it matches the approved scope and platform support.

Processing checkPass condition
Final stateEvery selected data type has a completed or reviewed terminal state.
SuccessSuccessful records are available for validation in the target store.
FailedEvery Failed result is classified, and required scope is corrected or formally held.
SkippedEvery Skipped result has an understood reason consistent with filters, dependencies, source quality, platform support, or approved scope.
TotalsSource expectations, Success, Failed, Skipped, unsupported, and intentionally excluded records reconcile plausibly.
Log and Activity TimelineAvailable evidence identifies the activity, result, and affected records.

Do not invent a universal acceptable variance. Exact totals are required when the approved scope and platform behavior make equality an exact requirement. Otherwise, reconcile differences against Failed, Skipped, filtered, unsupported, transformed, or accepted records.

Use risk, business importance, structural complexity, configuration impact, time range, and known exceptions. Increase the sample when the data model is complex, source quality is inconsistent, Failed or Skipped results are material, or Add-ons and Customization affect many records.

Sampling dimensionInclude
Business importanceHigh-revenue Products, priority Customers, operationally important Orders, high-traffic Categories, and important content.
Structural complexityVariants, multiple images, nested Categories, multiple addresses, discounts, tax, shipping, refunds, unusual statuses, and rich content.
Configuration impactPreserved IDs, SEO URLs, redirects, imported images, HTML stripping, mappings, Add-ons, and Customization.
Time and data scopeOlder and recent records, records near the boundaries of the intended scope, additional new Source data included by a Continue action paired with Continue the previous migration, and records around an interruption point when execution recovery must be verified.
Known riskDemo findings, prior source-data issues, previously Failed or Skipped records, unsupported fields, and platform-model transformations.

The sample is sufficient only when it covers the acceptance criteria and the conditions most likely to fail. Do not declare a pass from a fixed sample size that omits material risk.

  1. Identify the accepted migration result

    Confirm the migration path, purchased service, target store, activity, completion time, action, Run Mode, and intended data scope.

  2. Reconcile Success, Failed, and Skipped results

    Review each selected data type. Classify every Failed and unexpected Skipped result before moving to record-level validation.

  3. Confirm the configuration evidence

    Verify that the selected data, Additional Options, mapping, purchased Add-ons, and approved Customization match the configuration approved for this activity.

  4. Reconcile scope and totals

    Compare expected source scope with target presence and processing evidence. Account for unsupported, filtered, failed, skipped, transformed, or intentionally excluded records.

  5. Validate representative records and relationships

    Check presence, identity, required fields, approved transformations, relationships, and operational usability across the applicable data types.

  6. Validate Additional Options

    Test the records affected by a Continue action paired with Continue the previous migration, target-data clearing, description-image import, ID preservation, SEO URL migration, and every other applicable Additional Option that was displayed and selected for the active migration path.

  7. Validate Attribute Mapping

    Test applicable Site, Language, Inventory Location, Attribute Set, Root Category, Customer Group, Order Payment Status, and Order Fulfillment Status mappings. Confirm that each mapped value preserves the approved operational meaning.

  8. Validate purchased Add-ons and approved Customization

    Test normal, boundary and exception records for included processing Add-ons and Customization. Confirm that combined processing preserves required relationships.

    For Data Update, compare selected Source and Target field values on eligible existing records. Verify that non-selected fields and unassociated data remain unchanged and no records were created or recreated by the Add-on.

  9. Confirm target protection and clearing behavior

    Verify that manual, previously accepted, and application-created target records were preserved, replaced, or deleted only as approved. Stop further activity when destructive impact is unexplained.

  10. Reconcile Entity Points

    Compare Entity Points usage with newly eligible records that migrated successfully for the first time. Previously counted records should not consume points again merely because another supported action processed them.

  11. Classify differences and assign severity

    Classify each finding before selecting a corrective path. Assign Blocker, High, Medium, or Low severity based on its effect on required data integrity, operation, or launch preparation.

  12. Record the validation decision and handoff

    Assign Pass, Pass with accepted limitations, or Fail. Record the evidence, accepted limitations, open issues, owners, and the detailed validation pages that must be completed next.

Configuration areaTestable pass condition
Data selectionEach selected supported data type is represented in the result, and exclusions match the approved scope.
Continue action + Continue the previous migrationA Continue action was paired with Continue the previous migration in Additional Options when additional new Source data was intended, and supported relationships to earlier migrated data remain correct.
Execution recoveryA paused or stopped Browser/Background activity followed the documented recovery flow without being confused with Continue the previous migration option.
Clear data on Target Store before MigrationOnly the approved target data types and records were deleted, and required protected records remain.
Strip HTML tagsAffected Category and Product names match the approved plain-text expectation.
Import description imagesRequired supported images are present and associated with the correct target content.
Preserve Customer IDsSupported Customer identifiers match the approved source identifiers without target conflicts.
Preserve Order IDsSupported Order identifiers match the approved source identifiers without target conflicts.
Migrate SEO URLsSupported priority URLs match the approved target behavior.
Create 301 redirectsTested source URLs redirect to the intended target destinations without loops or incorrect chains.
Attribute MappingApplicable source values have the intended target Site, Language, Inventory Location, Attribute Set, Root Category, Customer Group, Payment Status, or Fulfillment Status.
Processing Add-onsFilters, supported field or database destinations, and transformations produce the approved record scope and values.
Data UpdateSelected supported fields on eligible existing records have the intended Source values. Non-selected fields and unassociated data remain unchanged; the required continuation option is enabled and Target clearing is disabled.
CustomizationEach selected item meets its approved acceptance examples without conflicting with standard configuration or Add-ons.

Only test options, mappings, Add-ons, and Customization that were available and included for the purchased migration path. For Data Update, record totals alone do not prove that fields were refreshed.

At this stage, confirm that the complete result is suitable for detailed domain validation. Do not duplicate every field-level check owned by the domain pages.

AreaMinimum coordination check
Taxes and ManufacturersRequired support records exist and link to applicable Products or Orders.
Categories and ProductsRepresentative catalog records exist, retain required relationships, and remain usable for navigation and merchandising review.
Customers and OrdersRepresentative identities, addresses, line items, totals, statuses, and Customer-Order-Product relationships are present for detailed review.
Reviews and CouponsSelected supported records exist and relate to the intended Products, Customers, or discount behavior.
CMS Pages and Blog PostsSelected content exists with required relationships and can advance to content and URL validation.

Use Pass when:

  • the correct activity, configuration, data scope, and execution context are confirmed;
  • selected data types and processing results reconcile;
  • representative records and critical relationships meet approved expectations;
  • Additional Options, mappings, Add-ons, and Customization behave as intended;
  • target protection and Entity Points usage are explainable;
  • no unresolved Blocker or High-severity issue prevents detailed acceptance work;
  • required evidence is recorded.

Use Pass with accepted limitations when:

  • every limitation is known and explained;
  • the platform-model difference or approved exception is permitted by the acceptance criteria;
  • customer impact is understood;
  • an authorized owner accepts the limitation;
  • follow-up work and its owner are recorded;
  • the limitation does not make further validation or launch preparation materially unsafe.

Use Fail when:

  • the wrong activity, path, environment, configuration, data scope, or execution-recovery path was used;
  • required records or relationships are missing or incorrect;
  • Failed or Skipped results affect required scope and remain unresolved;
  • configuration behavior is incorrect;
  • destructive target impact is unexplained;
  • Entity Points usage cannot be reconciled;
  • evidence is insufficient to support acceptance.

Classify failures and select the corrective path

Section titled “Classify failures and select the corrective path”
Failure classCorrective path
Wrong activity or environmentStop validation and identify the correct result before any further action.
Connection or source-access issueRestore and verify the supported connection, then determine the safe continuation path.
Source-data quality issueCorrect the source record or document an approved source limitation.
Selection or additional-data-scope issueCorrect Data selection, the selected Continue action, or applicable Additional Options before another activity.
Additional Option issueCorrect the responsible option and define the records that require revalidation.
Mapping issueCorrect the applicable standard mapping and retest affected values and relationships.
Processing Add-on issueCorrect the filter, mapping, database mapping, or transformation and retest affected records.
Data Update issueCheck eligibility, supported selected fields, required options and any available time restriction in Configure Data Update; retest the same field samples and protected data.
Customization issueCompare the result with the approved Custom Migration requirement and request review when behavior differs.
Processing issuePreserve the log, counts, data type, and record examples before contacting support.
Platform-model limitationDefine the supported target representation and obtain acceptance for the documented difference.
Target-store setup issueCorrect the target configuration without starting another migration activity unnecessarily.
Validation-method or evidence issueExpand the sample, correct the comparison method, or collect missing evidence before deciding.

Record:

  • purchased service, migration path, and target store;
  • migration activity, completion time, action, and Run Mode;
  • intended data scope, migration action, and applicable Additional Options;
  • configuration summary and selected data types;
  • Success, Failed, and Skipped totals by data type;
  • reconciliation of expected scope and target totals;
  • sampled source and target identifiers;
  • Additional Option, mapping, Add-on, and Customization results;
  • target protection and clearing result;
  • Entity Points result;
  • accepted limitations;
  • open issues, severity, owner, due date, and corrective path;
  • final Pass, Pass with accepted limitations, or Fail decision;
  • reviewer and approval date;
  • required domain-validation handoffs.

After Pass or Pass with accepted limitations, continue with the detailed checks that apply to the approved scope:

After Fail, correct the classified cause and repeat only the affected validation after the safe corrective action is complete. Use Support Tickets when the issue requires Next-Cart review.