Review Demo Results

Review Demo Results

Review the completed Demo sample to decide whether the migration path is suitable, what must change before purchase or Full Migration, and whether any requirement needs an Add-on, Custom Service, or target-store preparation. Use Validate Demo Results when you need the full representative validation checklist rather than the immediate post-Demo decision.

When to review

Complete this review immediately after Demo Migration reaches a final state and before relying on the sample for a purchase, scope, or configuration decision.

Before you start

Prepare:

• the completed Demo activity and migration path;
• Success, Failed, and Skipped results;
• source identifiers for the sampled records;
• access to the target-store admin and storefront where applicable;
• the expected source values and relationships;
• a findings log for Pass, Pass with accepted limitations, and Fail decisions.

Make the Demo decision

1. Confirm the completed Demo activity

   Verify the migration path, completion time, selected data, and any Failed or Skipped results.

2. Apply the detailed validation checklist

   Use Validate Demo Results to sample representative Products, Customers, Orders, Pages, supporting relationships, and important platform-model differences.

3. Separate Demo limitations from defects

   Confirm that the finding is not caused by the limited Demo scope or unavailable purchased-service features.

4. Classify every actionable difference

   Assign the finding to connection setup, source data, standard configuration, an Add-on, Custom Service, target-store preparation, or a platform-model limitation.

5. Choose the next decision

   Proceed when the representative result is usable and all required changes are understood. Revise and repeat the Demo when a supported correction needs new evidence. Stop and reassess when an essential requirement remains unsupported or unsafe.

Expected Demo limitations

Do not classify behavior that falls within the documented Demo scope as a defect. The complete sample limits and unavailable features are defined in Run a Demo Migration. Compare the result against those limits before opening a migration issue.

A successful Demo is not final migration approval

Demo provides representative evidence. Complete record coverage, purchased features, target-store readiness, and launch-critical behavior still require Full Migration and complete validation.

A supported discount value within a migrated historical Order is not a standalone Coupon record. Compare the supported Order values separately from the unavailable Coupon data type.

Classify findings

Finding	Next action
Connection or access issue	Correct and verify the platform connection.
Source record is incomplete or inconsistent	Correct or document the source data before purchased migration work.
Data selection, Additional Option, or standard mapping must change	Revise the available Demo setting and repeat the relevant check, or record a purchased-migration change when the setting is unavailable in Demo.
Supported filtering, field or database mapping, or target-value transformation is required	Confirm Add-on compatibility, define the rule for the purchased migration, and plan paid validation. Add-ons cannot be applied or retested within Demo.
Non-standard data, relationship, destination, or logic is required	Prepare a Custom Service requirement.
Target Platform cannot represent the source behavior directly	Approve a supported fallback or required target-side configuration.
Difference is caused by a Demo limit	Validate it later through the purchased service.

Decision output

Record:

• migration path and Demo completion time;
• detailed validation result;
• accepted Demo limitations;
• configuration changes;
• Add-on or Custom Service requirements;
• target-store preparation tasks;
• unresolved blockers;
• decision to proceed, revise, or stop.

If the issue cannot be classified or reproduced, open a ticket with the Demo activity, affected data type, representative identifiers, expected result, and masked evidence.

If the project uses the Migration Project Toolkit, update the Demo-validation gate in Project Plan and record each representative result under Validation evidence. Reassess any triggered Risks and create a Decision only when authorization or an accepted limitation is required.

The end-to-end worked example shows how those records stay connected without duplicating the same finding across sheets.

Next Steps

When the result is acceptable, continue to Configure Your Migration or Review Migration Configuration.