No Data Appears After Demo

No Data Appears After Demo

Determine whether the Demo produced no records, produced records in a different target store, or produced records that are present but not visible in the expected target-store view. Classify that difference before changing configuration or starting another Demo Migration.

Use this page when the intended Demo reaches a completed or actionable final state but you cannot find any of the expected Products, Customers, Orders, or Pages in the target store. When some expected records are present and others are absent, use the later Missing Data troubleshooting task instead.

Do not start another Demo before identifying the cause

Another Demo can add confusing evidence or repeat the same failure. First confirm the activity, target store, selected data, processing results, and target-store visibility.

Identify what “no data” means

Observable result	What it usually means
The Demo has not reached a final state	Processing may still be active, interrupted, or waiting on an actionable failure. This is not yet proof that no data was produced.
All selected counted data types show no successful records	The source sample may contain no eligible selected records, the selected scope may be wrong, or processing may have failed before records were created.
Failed results appear for the selected data types	A connection, permission, source-data, target-store, or processing issue prevented the expected records from completing.
Skipped results appear without successful counted records	The displayed skip reason must be reviewed. Do not assume skipped records were migrated or that every skip has the same cause.
Taxes, Manufacturers, or Categories appear but no Products, Customers, Orders, or Pages appear	Support data may have been processed while the intended counted sample was not selected, eligible, or successfully completed.
Records exist in the target admin but not on the storefront	Target status, visibility, sales channel, theme, cache, indexing, permissions, or another target-side display condition may be hiding them.
Records appear in another store or environment	The Demo used a different target URL, credential, environment, or migration activity than the one being reviewed.
Processing shows success but no records can be found anywhere in the intended target store	The result requires evidence-based escalation after activity, store, identifiers, and visibility have been verified.

Prepare the evidence

Before making changes, collect:

• the intended Demo activity and completion time;
• Source Platform and Target Platform;
• the exact target store URL and environment;
• the selected Demo data types;
• Success, Failed, and Skipped results where available;
• the source records expected to appear, using stable identifiers;
• access to the target-store admin and storefront where applicable;
• any customer-facing error, warning, or skip reason;
• recent manual changes in the target store that could hide, move, or remove records.

The Demo can select Taxes, Manufacturers, Categories, Products, Customers, Orders, and Pages. Its counted sample is limited to up to 10 Products, 10 Customers, 10 Orders, and 10 Pages. Related Taxes, Manufacturers, and Categories can accompany the selected sample as support data.

Diagnose the empty Demo result

1. Confirm the intended Demo activity

   Verify the completion time, migration path, selected data types, and activity being reviewed. Do not use evidence from an earlier Demo or another migration path.

2. Confirm the intended target store

   Open the target URL and admin area directly. Check the store name, domain, environment, and account so staging, development, or an old target is not mistaken for the intended store.

3. Review the final processing evidence

   Record the Success, Failed, and Skipped result for each selected data type. If the activity is still active or interrupted, resolve that state before classifying the result as empty.

4. Confirm that eligible source records were selected

   Check the source store for the specific Products, Customers, Orders, or Pages expected in the Demo. Confirm that the required data type was selected and that the records belong to the source environment used by the Demo.

5. Search the target admin before relying on storefront display

   Search by stable identifiers such as SKU, customer email, Order number, or Page title. Record counts and storefront navigation alone are insufficient because target filters or visibility settings can hide records.

6. Check target-side visibility

   When records exist in the admin, review the applicable status, publication, sales channel, store view, permissions, cache, indexing, or theme behavior. Do not alter migrated values until you know whether the issue is data absence or presentation.

7. Verify both platform connections

   Confirm that the source connection can still read the selected data and that the target connection points to the intended store. Use the same supported setup shown by Next-Cart.

8. Classify the cause and corrective path

   Classify the result as wrong activity or store, incomplete activity, source-sample issue, selection issue, connection issue, target-visibility issue, expected Demo limitation, or processing issue. Apply only the correction owned by that cause.

Apply the safest corrective path

Confirmed cause	Corrective action
Wrong Demo activity or target store	Stop the review and identify the correct activity and target environment. Preserve both sets of evidence so they are not mixed.
Activity is not complete	Return to the Migration step and determine whether processing is active, interrupted, Failed, or awaiting action. Do not classify an unfinished result as empty.
No eligible source sample exists	Identify representative source records and confirm that they are available in the connected source store before changing Demo selection.
Required data type was not selected	Return to Demo configuration and select the applicable available data type. Keep the Demo limits and unavailable features separate from defects.
Source or target connection is invalid	Resolve Connection Issues and verify the same supported connection before further migration activity.
Failed or Skipped results explain the absence	Preserve the displayed result, reason, affected data type, and sample identifiers. Correct the classified cause or escalate when the behavior requires Next-Cart review.
Records exist in admin but not storefront	Correct the applicable target-store status, visibility, channel, theme, cache, indexing, or permission condition, then check the same records again.
The expected feature is unavailable in Demo	Record it for validation through the purchased service, purchased Add-on, approved Customization, or target-store setup. Do not treat the Demo limitation as failed migration data.
Success is reported but the intended target contains no records	Confirm the target environment and search by stable identifiers. If the discrepancy remains, preserve the activity evidence and contact support.

Verify the correction

Use the same source examples and target environment that exposed the problem.

Check	Pass condition
Activity	The result belongs to the intended Demo Migration and migration path.
Target store	The reviewed admin and storefront belong to the target connection used by that Demo.
Processing evidence	Success, Failed, and Skipped results are understood for every selected data type.
Source sample	The intended source records exist and are eligible for the selected Demo scope.
Record presence	The expected representative records can be found in the target admin by stable identifier.
Visibility	Records that should be customer-visible appear in the applicable storefront, store view, or channel.
Cause resolution	The original reason for the empty result is corrected or documented for support or later purchased-service validation.

Do not mark the issue resolved merely because unrelated target records are visible. Verify the specific records and data types expected from the intended Demo.

Evidence to collect for support

Provide:

• the Demo activity date and completion time;
• the purchased or Demo migration path;
• source and target store URLs;
• selected Demo data types;
• Success, Failed, and Skipped results;
• at least one expected source identifier for each affected counted data type;
• the target searches performed and their results;
• screenshots of the visible status or error with secrets and unnecessary personal data masked;
• whether records appear in the target admin, storefront, another environment, or nowhere;
• every corrective check already completed.

When to escalate

Use Tickets when:

• the intended activity reports success but no corresponding records exist in the confirmed target store;
• all required connections and selected source examples are valid but no counted Demo data is produced;
• Failed or Skipped results do not provide an actionable customer correction;
• the issue repeats after the confirmed cause has been corrected;
• the displayed behavior conflicts with the supported Demo model;
• further testing would risk duplicate or conflicting target data.

Prevent an empty or unreviewable Demo

• Confirm the source and target environments before starting the Demo.
• Identify representative source records before selecting Demo data.
• Include related data types when they are required to evaluate important relationships.
• Keep production and staging target URLs clearly labeled.
• Record the Demo completion time, selected data, results, and target identifiers immediately after processing.
• Preserve the original activity evidence until Demo validation is complete.

Next step

When representative records are visible, continue to Review Demo Results and then Validate Demo Results.

When the Demo still cannot produce reviewable evidence after the cause is classified, submit a focused ticket with the activity, selected data types, processing results, and sample identifiers.