Skip to content
Back to Site

Overview

Trace migration problems to the correct layer, contain further impact, apply the safest correction, and collect evidence before retrying or escalating.

Start with the observable problem, preserve the evidence before making changes, 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.

Use this recovery sequence:

  1. Stop the migration activity when an error appears so the failed state can be investigated before additional processing continues. Use the available Stop Migration control for the running activity.
  2. Sign in to the Dashboard and open Support.
  3. Create a Support Ticket for the failed migration and include the error, migration/activity identifiers, affected data type, and representative evidence.
  4. Keep follow-up information in the same ticket while the issue is investigated.

Use the Dashboard Support route and keep follow-up information in the same ticket. Response timing is governed by the applicable support policy.

Classify the problem before starting another migration activity. Migration-related questions and supported defects can be raised through AI Help, Support Agent Chat, or Support Tickets within the purchased Service and accepted scope.

When the correction requires another migration activity, choose the applicable Migration Action. Depending on the situation, use Continue the Migration with Last Saved Configuration, Continue the Migration with a New Configuration, or Perform a New Migration. When additional new Source data must be transferred on the same purchased migration, pair a Continue action with Continue the previous migration in Additional Options. Keep interruption recovery separate from additional-data processing.

Another activity is not an automatic entitlement simply because an issue was found. Preserve accepted target data, determine the cause and intended result, then choose the supported action or support path that fits the case.

SymptomStart here
Platform authentication, KitConnect, File Upload 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 concernsTroubleshoot a New Migration
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 Migration Escalation

Before applying a corrective action, identify:

  • the purchased service and fixed migration path;
  • the migration activity and date or History entry;
  • the Connect Stores action, Run Mode, and relevant Additional Options;
  • the affected data type and intended data scope;
  • 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.

If the project uses the Migration Project Toolkit, update the related Risk, Validation evidence, or project task after the issue is classified. Keep troubleshooting evidence in its appropriate secure system and use the Toolkit to preserve ownership, consequence, and decision status rather than duplicating the complete diagnostic record.

Use Support Tickets when a supported correction does not resolve the problem, Next-Cart assistance is required, destructive risk prevents safe testing, repeated failures continue, or a security incident is suspected.

Use Custom Migration 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 Migration.