Connection Issues

Connection Issues

Restore reliable access to the intended Source Platform and Target Platform before you continue migration work. Use this page when Test Connection fails for either store, a connection that worked earlier stops working, Next-Cart cannot read or write the expected data, or the connection resolves to the wrong store environment.

The safest correction is the narrowest one that addresses the confirmed cause. Preserve the error evidence, identify the affected side, and avoid changing unrelated configuration while the connection problem is unresolved.

Do not replace the displayed connection setup with another method

Next-Cart determines and displays the supported setup for each platform. API access, KitConnect, source data files, and other setup paths are not freely interchangeable. Correct the setup shown for the selected migration path.

Identify the observable problem

Start with what you can confirm rather than assuming that every access failure has the same cause.

Observable problem	What it usually means
A connection value is rejected immediately	A required value is incorrect, expired, revoked, copied from another store, or entered in the wrong field.
The connection passes authentication but source data cannot be read	The credential may lack required read access, the wrong source store may be connected, or the platform may be restricting access.
The target store can be opened directly but Next-Cart cannot write to it	The target credential may lack required access, the store may be read-only or unavailable, or a platform or security rule may block the request.
A connection worked earlier and now fails	A token, app, password, domain, firewall rule, hosting setting, or store status may have changed.
The connection succeeds intermittently	The platform, API, hosting environment, network, rate limit, or security layer may be temporarily interrupting access.
Data is read from or written to the wrong store	The URL or credential belongs to a staging, development, copied, old, or otherwise unintended environment.
Source files or KitConnect cannot be reached	The issue belongs to the supported file, folder, permission, URL, hosting, or transfer setup shown for that platform.
The connection test passes but migration activity still fails at one data type	The basic connection may be valid while a permission, platform limit, data-specific request, or processing issue still requires diagnosis.

Prepare before changing access

Collect the following information first:

• the Next-Cart account and purchased service you are using;
• the fixed Source Platform to Target Platform migration path;
• the exact source store and target store URLs or environment names;
• whether the issue affects the source side, target side, or both;
• the separate Source Platform and Target Platform Test Connection results when API or KitConnect is used;
• the stage where the failure appears: connection test, configuration, Demo Migration, Full Migration, or validation;
• the customer-facing error message and the time it appeared;
• the most recent activity or History entry associated with the issue;
• whether a credential, app, domain, hosting rule, or store status changed recently.

Do not include passwords, full tokens, client secrets, private keys, Backup Codes, payment-card data, or unnecessary personal data in notes or screenshots.

Diagnose the connection safely

1. Confirm the account, service, and migration path

   Verify that you opened the intended purchased service and that the Source Platform and Target Platform match the stores you are trying to connect. Stop if the path or service is wrong.

2. Identify the affected side and stage

   Determine whether Next-Cart cannot read from the source store, cannot write to the target store, cannot use uploaded source files, or loses access only during migration activity.

3. Confirm the intended store environment

   Open both stores directly. Check the domain, admin area, account, store name, and environment so staging or old-store access is not mistaken for production access.

4. Confirm the supported setup shown by Next-Cart

   Compare the displayed fields or instructions with the selected platforms. Do not substitute a different setup path because another method seems easier.

5. Check current availability and recent changes

   Confirm that the store, platform API, domain, hosting environment, and required app or integration are active. Review any recent token rotation, password change, domain change, firewall update, or hosting change.

6. Apply the narrowest corrective action

   Correct only the affected URL, credential, permission, file, KitConnect, hosting, or security setting. Keep a note of what changed and when.

7. Repeat Test Connection for the affected side

   Use the separate Test Connection control for the same source or target connection that failed. Do not change the connection that already works, or alter migration data, mappings, Add-ons, or target records merely to make the test pass.

8. Verify that the original task can continue

   Confirm that the affected test now succeeds, the other store still passes its own test when API or KitConnect is used, and the failure no longer appears at the stage where it was first observed. For file-based source setup, confirm that the required files remain accepted.

Apply the appropriate correction

Issue family	Safest corrective action
Incorrect, expired, or revoked access value	Re-copy or regenerate only the required value from the correct platform account, then update the affected connection.
Missing API or app permission	Review the access requested by the displayed setup and grant the required supported permission. Do not grant unrelated access.
Wrong URL or environment	Replace the value with the exact URL type and store environment requested by the Next-Cart interface.
Disabled app, integration, or store access	Re-enable the required access or create a new supported credential, then document the change.
Temporary platform or rate-limit response	Stop repeated rapid testing, preserve the error and time, and test again after the temporary restriction has cleared.
Firewall, CDN, bot protection, or hosting block	Ask the platform, hosting, or security owner to review the specific blocked request. Avoid broadly disabling security controls.
Source data file, KitConnect, or transfer issue	Use Troubleshoot Connection Setup for the setup-specific file, folder, URL, permission, and hosting checks.
Connection passes but migration activity still fails	Record the affected data type, Success, Failed, or Skipped result, sample identifiers, and error evidence. Escalate when the same supported access cannot complete the expected operation.
Setup fields do not match the selected platform	Stop. Confirm the migration path and refresh the migration interface. Contact support if the displayed setup remains inconsistent.

Verify the correction

A connection issue is resolved only when all applicable checks pass:

Check	Pass condition
Correct service	The connection belongs to the intended purchased service and migration path.
Correct stores	The source and target values point to the intended environments.
Source access	Next-Cart can read the source data or source files required by the supported setup.
Target access	Next-Cart can access the intended target store for the required operation.
Source Test Connection	The source test succeeds when the Source Platform uses API or KitConnect.
Target Test Connection	The target test succeeds when the Target Platform uses API or KitConnect.
Stable result	The same side that failed now passes without an unexplained intermittent error.
Original task	Configuration, Demo Migration, Full Migration, or validation can continue past the point where the connection failed.
Security	No unnecessary credential, permission, or temporary access remains exposed.

A successful connection test does not by itself prove that every data type will process correctly. If a later activity still fails, preserve the data-type result and diagnose that failure separately.

Evidence to collect for support

When the issue remains unresolved, provide:

• the purchased service or order reference;
• Source Platform and Target Platform;
• source and target store URLs with sensitive query values removed;
• the affected side and connection setup shown by Next-Cart;
• the separate source and target Test Connection results;
• the exact error message and timestamp;
• the stage where the error occurs;
• the related activity date or History entry;
• changes already tested and their results;
• masked screenshots where useful;
• affected data type and sample record identifiers when the connection fails during migration activity.

Mask secrets before attaching evidence

Show the field name and visible error, but hide passwords, complete tokens, client secrets, private keys, Backup Codes, and payment details. Preserve non-sensitive evidence before rotating access. If exposure is suspected, secure or revoke the credential immediately and report the incident.

When to escalate

Use Tickets when:

• the setup displayed by Next-Cart does not match the selected platform or migration path;
• the same connection fails after the relevant value, permission, URL, and environment have been verified;
• a connection test passes but Next-Cart still cannot read or write the supported data;
• repeated failures affect the same data type after access has been corrected;
• the correction requires internal intervention or platform-specific analysis;
• destructive changes would be required to test further;
• you suspect that credentials or store access were exposed or misused.

Prevent the issue from returning

• Record who owns each store credential and when it expires.
• Keep production and staging URLs clearly labeled.
• Avoid changing app permissions, domains, security rules, or hosting settings during active migration work without recording the change.
• Preserve original source exports and connection evidence until validation is complete.
• Remove temporary KitConnect or other temporary access only after migration work is complete and verified.

Next step

After the connection is stable, use Verify Platform Connections and return to the task that was blocked.

If a Demo reaches a final state but no migrated records are visible, continue to No Data Appears After Demo.