Skip to content
Back to Site

Missing Data

Classify the gap as scope, source availability, processing, mapping, target-model, relationship, or visibility failure before choosing a correction that preserves consistency.

Identify whether an expected record is truly absent, outside the compared scope, represented differently by the target platform, or present but hidden by target-store conditions. Start missing-data diagnosis when some migration results are available but particular Products, Categories, Customers, Orders, Reviews, Coupons, CMS Pages, Blog Posts, relationships, or required field values cannot be found.

When a completed Demo Migration produces no visible records at all, use No Data Appears After Demo instead. For partial absence, preserve the evidence before changing configuration and diagnose the smallest affected scope before starting another migration activity.

Observable resultWhat it usually means
The target count is lower than the source count, but sampled records can be foundThe comparison may include different statuses, dates, stores, languages, archived records, deleted records, filters, or target representations.
Particular source records cannot be found in the targetThe records may have been outside the selected scope, ineligible at processing time, filtered out, failed, skipped, or written under a different identifier or target structure.
Parent records exist but related records are absentA required data type or dependency may not have been selected, processed successfully, or matched correctly.
A record exists but an expected field value is empty or in the wrong placeThe field may be unsupported, mapped differently, transformed, redirected through Advanced Data Mapping or Advanced Database Mapping when applicable, or covered by approved Customization.
Records exist in the target admin but not in the expected list or storefrontTarget filters, status, visibility, language, site, sales channel, permissions, cache, indexing, theme, or navigation can hide an otherwise present record.
Products or Categories appear under a different hierarchy or structureThe target data model may represent Categories, collections, variants, options, or attributes differently. Confirm the approved result before classifying it as missing.
Later new Source records are missingVerify the intended ordinary new-record scope, applicable Continue action and Additional Options, data selection, Failed/Skipped results and target visibility.
Data Update did not refresh an existing recordCheck the record was previously migrated by Next-Cart, its Target counterpart still exists, the field was selected and supported, and any available time restriction includes the Source change. Use Configure Data Update.
A File Upload Source is missing a subset that was never included in the uploaded filesThe source export or source file set may have been filtered, incomplete, or missing relationship data before migration began.

Data Update does not create new records or recreate deleted Target records. Its selected-field refresh uses default mappings; changing other Add-ons or Attribute Mapping does not extend that update scope.

Collect enough information to compare the same source and target scope:

  • the purchased service and fixed Source Platform to Target Platform migration path;
  • the exact migration activity and its date or History entry;
  • the source-data window and target environment being reviewed;
  • the affected data type and the approved migration scope;
  • several affected source records with stable identifiers such as SKU, source ID, customer email, Order number, coupon code, Page title, or source URL;
  • corresponding target searches and screenshots using masked personal data where possible;
  • Success, Failed, and Skipped results for the affected data type;
  • relevant Data, Additional Options, Attribute Mapping, Add-on, and Customization choices;
  • the expected result and the actual target result;
  • any source record status, archive state, deletion state, language, site, location, or date condition that could affect eligibility.
  1. Confirm the correct activity and target store

    Verify that you are reviewing the intended migration activity, target URL, store view, site, language, and environment. Do not compare a different Demo, Full Migration, continuation activity, or copied target store.

  2. Compare the same source and target scope

    Align the comparison by data type, store or site, language, date range, status, and approved filters. Exclude source records that were archived, deleted, inactive, outside the selected scope, or created after the activity unless the acceptance criteria require them.

  3. Review processing evidence

    Check Progress, Success, Failed, and Skipped results for the affected data type. Record the displayed reason for every relevant Failed or Skipped sample instead of assuming that all absent records share one cause.

  4. Search the target by stable identifier

    Search the target admin by SKU, source ID, email, Order number, coupon code, title, URL, or another distinguishing value. Clear unintended admin filters and review inactive, draft, hidden, archived, and alternate-language views where applicable.

  5. Confirm source eligibility and selected scope

    Verify that each affected source record existed and was accessible when the activity ran. Review the selected data types and any Data Filter rule. For source files, confirm that the record and required relationship fields were present in the source file set.

  6. Check relationship dependencies

    Confirm that required parent and related records were selected or already existed in the target with reliable matching. Products can depend on Manufacturers, Categories, and Taxes; Orders can depend on Customers, Products, Taxes, Coupons, shipping, and other historical values; Reviews can depend on Products and Customers.

  7. Review mappings, transformations, and target structure

    Check applicable Site, Language, Location, Attribute Set, Root Category, Customer Group, payment-status, and fulfillment-status mappings. Review Data Transformation, Advanced Data Mapping, Advanced Database Mapping, and approved Customization when a record exists but its values, status, destination, or relationship look missing.

  8. Separate target visibility from migration absence

    Confirm whether the target record is hidden by publication status, sales-channel assignment, store view, language, permissions, menu configuration, theme behavior, cache, or indexing. Correct target presentation without starting another migration activity when the migrated data is already present.

  9. Classify the cause and affected scope

    Document whether the issue is caused by the compared scope, source eligibility, selection, filtering, source input, processing, dependency, mapping, target-model transformation, target visibility, manual target changes, or an unexplained service result. Choose a correction only after this classification is complete.

When the migration completes with zero entities imported

Section titled “When the migration completes with zero entities imported”

For Data Update, inspect selected field values rather than expecting newly imported records.

For ordinary record migration, if the activity completes but no expected records were imported, check the Source connection method before changing scope:

  • API-connected Source: confirm that the API credential has permission to read the required data. Depending on the selected Source Platform, that can include Products, Customers, Orders, and other selected data types.
  • File Upload Source: confirm that the required source files were actually uploaded and contain the expected records. Missing or incomplete files can leave the migration with no readable Source records.

Recheck the Source Store setup for the selected platform, correct the missing permissions or files, and verify the Source data is recognized before rerunning or changing migration configuration. If the cause remains unexplained, submit a Support Ticket with the activity, selected scope, source identifiers, and processing evidence.

Confirmed causeSafest corrective action
Wrong activity, target environment, site, or languageStop the comparison and open the correct result. Do not change migration configuration.
Unsupported or unselected data typeConfirm the migration-path capability and approved scope. Select the data type only when supported and required, or document a Custom Migration requirement.
Source record was inactive, archived, deleted, inaccessible, or outside the approved windowCorrect the source state or update the accepted scope before deciding whether another migration activity is required.
Data Filter excluded the recordCorrect the filter rule and test normal, boundary, and exception examples before processing the affected scope.
Source export or source files were incompleteCreate a complete, consistent export and verify required identifiers and relationship fields before replacing the source files.
CSV, XLS, or XML Source shows Product 0/0Treat this as a template-recognition issue first.
Open the exact CSV, XLS, or XML Product template guide and restore the expected filename and structure.
Re-upload the file and confirm Source Product records are recognized before investigating Target visibility.
Failed or Skipped result explains the absenceCorrect the displayed cause, preserve the affected identifiers, and repeat validation only for the corrected scope.
Required dependency or relationship was not availableRestore or include the required parent data and verify relationship matching before processing dependent records.
Attribute Mapping placed the record in an unexpected site, language, group, status, or hierarchyCorrect the responsible mapping and retest the affected records and their operational meaning.
Data Transformation, Advanced Data Mapping, or Advanced Database Mapping used the wrong rule, value, or destinationCorrect the rule or target field and retest representative records, including boundary and exception cases.
Target data model uses an approved different representationRecord the transformation as an accepted result when it meets the acceptance criteria. Do not create a duplicate structure solely to imitate the source.
Target filters, visibility, theme, navigation, cache, or indexing hide the recordCorrect the target-store condition and verify the existing record. Do not process the record again unnecessarily.
Target records were manually deleted or changed after migrationPreserve the target state before further activity, identify who or what changed it, and prepare an approved recovery plan.
Success is reported but required records remain unexplained after all checksSubmit a ticket with activity, scope, identifiers, processing evidence, expected result, and privacy-safe source and target examples.

Repeat the affected checks against the same evidence set:

Verification areaPass condition
Record presenceEvery required sampled record can be found by a stable identifier or approved fallback identifier.
Compared scopeSource and target counts use the same data type, status, date, site, language, and filter scope.
Processing resultRelevant Failed or Skipped results are resolved or documented as accepted limitations.
RelationshipsRequired parent-child, Product-Category, Customer-Order, Order-line, Review-Product, and other supported relationships are intact.
Field destinationRequired values appear in the approved standard or custom target field.
Operational meaningMapped status, group, location, taxonomy, and historical meaning meet the acceptance criteria.
Target visibilityRequired records are available in the approved admin, storefront, site, language, or channel context.
Side effectsThe correction did not create duplicate records, remove protected target data, or change unaffected scope.

Escalate when the cause cannot be corrected safely

Section titled “Escalate when the cause cannot be corrected safely”

Use Support Tickets when:

  • a supported selected record shows Success but cannot be found in the intended target after identifier and visibility checks;
  • repeated Failed or Skipped results remain after the confirmed cause is corrected;
  • the target representation does not preserve a required business relationship or accepted meaning;
  • the correction cannot be completed through the available migration configuration and requires platform-specific technical intervention or Custom Migration;
  • another migration activity could remove, replace, or duplicate protected target records;
  • the issue affects launch readiness and no safe target-side correction is available.

Include the service, migration path, activity date, affected data type, source and target identifiers, relevant configuration, Success/Failed/Skipped evidence, expected result, actual result, and minimal privacy-safe screenshots or files. Never include passwords, full secret keys, payment-card data, or an unnecessary customer export.

  • define the source-data window and acceptance scope before migration;
  • compare source and target using the same statuses, sites, languages, dates, and filters;
  • identify representative records and stable identifiers for every selected data type;
  • keep required dependencies selected unless reliable target matching is confirmed;
  • test filters, field and database mappings, transformations, and Customization with normal and edge-case records;
  • verify source exports before upload;
  • record approved target-model differences before sign-off;
  • restrict manual target changes while validation is in progress.

The following cases are common examples of data that can look missing even when the underlying cause is a target-model, mapping, or visibility difference. Use them after the general diagnostic sequence above so the investigation stays evidence-based.

For this migration behavior, each Shopify Product can have a maximum of 2,048 variants and 3 options. A source structure above either native limit requires an alternative Shopify representation or an approved tailored migration approach.

If a Source Product exceeds those limits, use one of these solutions:

  1. Custom Migration/Customization: have the migration logic exclude selected Product options so only the essential option/variant data is migrated within the accepted Shopify representation.
  2. Shopify Product Option app: install an appropriate Product Option app to extend the Product option model. After the app is set up, Next-Cart can assist, within the applicable Support/Custom scope, with uploading the Product variants by CSV into that app.

Preserve the affected Product IDs, option names, expected variant count, and chosen target representation when requesting assistance.

Square Orders are not visible in the dashboard

Section titled “Square Orders are not visible in the dashboard”

Migrated Square Orders use three states: Completed, Open (New), and Canceled. Orders migrated with the Canceled state do not appear on the Square dashboard in this migration behavior.

If migrated Orders appear to be missing:

  1. check the affected Orders and confirm whether they were migrated with the Canceled state;
  2. review the Order-status mapping in Configuration > Attribute Mapping;
  3. correct the mapping when the Source status was mapped to the wrong Square state;
  4. revalidate representative Orders after the correction.

Incorrect characters or encoding after migration

Section titled “Incorrect characters or encoding after migration”

If error characters appear in a migrated Product description, the diagnosis is that the Source Store description contains specially encoded characters and that character encoding is not supported by the Target Store.

Correct the problem by converting the Product description from the old character encoding to an encoding that is compatible with the Target Store. Verify the corrected text with representative Product descriptions before applying the same conversion more broadly.

If assistance is required, submit a Support Ticket from the Dashboard with affected Product identifiers and examples of the source text and migrated result. Do not rely on an unverified response-time promise.

Magento Products exist in Admin but are missing from the storefront

Section titled “Magento Products exist in Admin but are missing from the storefront”

After migration, Magento can require a manual reindex so Categories and Products appear on the storefront and Product attributes appear correctly in the backend.

  1. Log in to the Magento web server through SSH. PuTTY or another SSH client can be used.

  2. Navigate to the Magento website folder.

  3. Run:

    Terminal window
    bin/magento indexer:reindex
    bin/magento cache:clean
  4. Wait for both commands to complete successfully.

  5. Recheck the Magento storefront for Categories and Products and the backend for Product attributes.

If the commands fail, preserve the command output and server context before making unrelated migration changes. For additional Magento indexer reference, see Manage the indexers on Magento.

Square catalog items exist but are missing from Square Online

Section titled “Square catalog items exist but are missing from Square Online”

After Categories and Products are migrated, the items are stored in the Square Item Library. The Square dashboard can be used to view items, Customers, and Orders.

To make the migrated items visible on Square Online:

  1. Open the Square Online overview page.
  2. Go to Items > Item Sync.
  3. Choose whether to sync all items or only part of the items.
  4. Complete the sync.
  5. Verify that the synced items are visible on the Square Online store.

After the correction, repeat the applicable validation page for the affected data type:

When the same source record appears more than once in the target, continue with Duplicate Data before making cleanup changes.