Skip to content
Back to Site

Overview

Diagnose connection, migration-result, image, Entity Points, migration-action, Add-on, Customization, and Custom Service issues safely.

Start with the observable problem, preserve the current evidence, and use the issue page that matches the symptom and provides the safest diagnostic path. Confirm the cause before changing configuration, deleting target data, or starting another migration activity.

SymptomStart here
Platform authentication, KitConnect, source-file access, file transfer, firewall, hosting, or connection verification failsConnection Issues
A completed Demo shows no visible target recordsNo Data Appears After Demo
Some expected records, relationships, or values are absentMissing Data
Records appear more than once or the storefront shows repeated resultsDuplicate Data
Images are missing, broken, rejected, associated incorrectly, or hiddenImage Issues
Entity Points usage, remaining capacity, or covered records are unclearEntity Points Issues
A continuation action loads or produces an unexpected resultContinue Migration Issues
A new migration creates replacement, deletion, duplicate, or protected-record concernsPerform New Migration Issues
An Add-on or approved Customization is missing, unavailable, or produces the wrong resultAdd-on and Customization Issues
The requirement needs unsupported data, bespoke logic, a custom destination, or Next-Cart reviewCustom Service Escalation

Before applying a corrective action, identify:

  • the purchased service and fixed migration path;
  • the migration activity and date or History entry;
  • the action and relevant Source Platform Options;
  • the affected data type and source-data window;
  • representative source and target identifiers;
  • expected result versus actual result;
  • Success, Failed, and Skipped evidence;
  • the exact customer-facing error or target-store symptom;
  • recent configuration, access, platform, application, or target-store changes.

Mask personal data and secrets. Do not include passwords, complete secret keys, payment-card data, or unrelated customer records.

Use Tickets when a supported correction does not resolve the problem, internal intervention is required, destructive risk prevents safe testing, repeated failures continue, or a security incident is suspected.

Use Custom Service Escalation when the required migration result is outside standard configuration, purchased Add-ons, or approved Customization. A supported feature that malfunctions remains a support issue rather than automatically becoming Custom Service.