Resolve connection blockers before migration configuration so Next-Cart can read and write the supported data required by the selected path.
Connection issues should be resolved before migration configuration. A connection that only partially works can lead to incomplete data-type discovery, missing data, permission errors, or failed validation later.
API setup, KitConnect, and source data file upload are not interchangeable choices. Troubleshoot the setup shown by Next-Cart for the selected Source Platform and Target Platform.
If the connection was verified earlier but fails during existing migration activity, use Connection Issues to preserve activity evidence and diagnose the runtime failure.
Before troubleshooting, confirm that:
Requirement Why it matters You are signed in to the correct Next-Cart account Connection setup belongs to the purchased migration in that account. The migration path is correct Setup values must match the selected Source Platform and Target Platform. You know which side failed Source-side and target-side failures may require different access owners or setup details. You have access to the original credentials or files You may need to re-copy credentials, regenerate tokens, re-export files, or re-upload KitConnect. You can access the source store and target store directly Direct access helps confirm whether the issue is with Next-Cart setup values, platform access, or the store itself. You can contact the store owner, hosting owner, or platform admin Some fixes require permissions you may not have.
Start by identifying the visible symptom.
Symptom Most likely area to check first Credentials are rejected immediately API key, token, secret, username, password, client ID, or authorization value. Credential is accepted but data cannot be read API scopes, permissions, app status, token status, or platform access limits. Store URL is rejected Public store URL, admin URL, API URL, endpoint URL, or domain format. KitConnect URL returns 404 Folder placement, folder name, web root, domain, or HTTPS URL. KitConnect URL returns server error PHP version, file permissions, security rules, hosting restrictions, or incomplete upload. Source files upload but cannot be processed Wrong file format, incomplete export, renamed files, missing data files, or unsupported file structure. File transfer fails SFTP credentials, port, hostname, hosting permissions, file size, or blocked connection. Connection worked before but now fails Expired token, revoked app, changed password, domain change, firewall rule, or hosting change. The data preview or migrated sample comes from the wrong store Wrong environment, staging URL, copied credentials from another store, or incorrect purchased migration.
Open the migration setup in Next-Cart.
Confirm the selected Source Platform and Target Platform.
Identify whether the failed setup belongs to the source store, target store, or uploaded source files.
Confirm that the setup path shown by Next-Cart matches the expected platform setup.
Recheck the required values exactly as entered.
For API or KitConnect setup, select Test Connection for the affected Source Platform or Target Platform.
If the issue continues, use the relevant issue table below.
After applying a fix, test the same side again before changing the connection that already works.
Confirm the other store’s separate Test Connection result when it also uses API or KitConnect. For file-based source setup, confirm that the files are accepted instead.
Issue What to check Fix Invalid token, key, or secret Credential copied with missing characters, extra spaces, wrong account, or expired token. Re-copy the value from the platform admin or create a fresh credential. Missing permission or scope Credential lacks access to Products, Categories, Customers, Orders, Reviews, Coupons, Pages, or other selected data types. Edit the app or token permissions, or create a new credential with the required read access. Wrong URL Next-Cart asks for a public store URL, admin URL, API URL, endpoint URL, or instance URL, but another URL was entered. Use the exact URL type requested by the Next-Cart setup screen. App or integration disabled Private app, custom app, API account, or integration is disabled. Re-enable the app or create a new credential. Token expired or revoked Credential worked before but no longer authenticates. Generate a new token and update the setup values. IP or firewall restriction Platform or security layer blocks requests from external services. Review platform security settings, firewall rules, and IP restrictions. Rate limit or temporary platform block API accepts credentials but fails during data preview or repeated testing. Wait, reduce repeated tests, then try again. Contact support if the issue persists.
Issue What to check Fix KitConnect URL returns 404 Folder was uploaded to the wrong location or the URL uses the wrong folder name. Move the KitConnect folder to the store web root and use the exact folder name in the URL. KitConnect folder was renamed The URL and folder name no longer match. Use the current folder name or upload the original folder again. KitConnect opens from hosting file manager but not from browser Folder is not publicly reachable through the web domain. Confirm the web root, domain, HTTPS access, and hosting path. Permission error Folder or PHP files have restrictive permissions. Use normal hosting-safe permissions such as 755 for folders and 644 for files, unless your host requires otherwise. Server error PHP setting, hosting restriction, incomplete upload, or security rule blocks execution. Re-upload the full folder, check hosting logs if available, and ask the hosting owner to review restrictions. Security system blocks access Web application firewall, CDN, or bot protection blocks the request. Temporarily allow the required access or ask the hosting/security owner to review the block. KitConnect remains after completion Temporary bridge files are still present after migration work is complete. Remove KitConnect after migration work is complete and verified.
KitConnect is used only when Next-Cart requires it for the selected platform setup. Remove it after migration work is complete and verified.
Issue What to check Fix Required file is missing Product, customer, order, category, content, or platform-specific file was not exported. Re-export the missing file from the source platform. File format is wrong File is not in the required CSV, XLSX, XML, TXT, ZIP, SQL, or platform-specific format. Export again using the format required for that platform guide. File was edited manually Column headers, IDs, relationships, or table names were changed. Use a fresh export unless Next-Cart specifically instructed the edit. Export range is incomplete Orders, customers, or products were filtered unintentionally. Re-export all records or the full approved date range. Multiple export batches are incomplete Platform export limit required multiple files, but only one range was uploaded. Export every required range and keep the files organized. File name no longer identifies the data type File was renamed in a way that removed its original meaning. Use clear file names that preserve data type, date range, and platform context. File is unreadable File is corrupted, partially uploaded, compressed incorrectly, or locked. Download or export the file again and upload a fresh copy.
Issue What to check Fix Cannot connect by SFTP Host, username, password, port, or protocol is incorrect. Recheck credentials from the hosting provider and use SFTP when available. Host key warning appears First connection to a server may require host key confirmation. Confirm the host is correct before accepting. Login succeeds but upload fails User lacks write permission in the selected folder. Upload to the correct web root or ask the hosting owner for permission. ZIP upload succeeds but extraction fails Hosting file manager cannot extract the archive or the archive is incomplete. Re-upload the ZIP or extract locally and upload the folder. Uploaded files are in the wrong folder Files were placed outside public_html, www, httpdocs, or the actual store web root. Move files to the correct web root. Transfer stops midway Network interruption, file size limit, or hosting timeout. Retry the upload, use SFTP, or ask the hosting provider to increase upload limits.
Issue What to check Fix Wrong source store Credentials or URL belong to a test, staging, or old production store. Use the source store that contains the data approved for migration. Wrong target store Connection points to a staging store while validation expects production, or the reverse. Confirm the intended target environment before continuing. Domain changed after setup Store URL, admin URL, or API URL changed after the setup was saved. Update the setup values and test again. Store maintenance is active Source store or target store is temporarily unavailable. Wait until maintenance ends and retest. SSL or DNS issue Domain does not resolve consistently or HTTPS certificate fails. Resolve DNS or SSL before testing connection again.
After troubleshooting, you should have one of these outcomes:
the separate source and target Test Connection results identify and verify the affected side;
source data files are uploaded and readable;
KitConnect is reachable at the expected URL;
the issue is clearly identified and assigned to the correct owner;
a support ticket is ready with enough details for investigation.
Check Pass condition Correct account You are working in the account that owns the order and purchased migration. Correct migration path The Source Platform and Target Platform match the purchased service. Correct environment URLs and credentials point to the intended source store and target store. API setup Credentials authenticate and provide access to the required data types. KitConnect setup The KitConnect URL opens and Next-Cart can use it for the required platform connection. Source files Uploaded files are complete, readable, and organized by data type. Source Test Connection The source test passes when the Source Platform uses API or KitConnect. Target Test Connection The target test passes when the Target Platform uses API or KitConnect. Retest result The same side that failed now passes without changing a connection that already worked.
Contact support if:
the connection still fails after you apply the relevant checks;
the platform requires a setup path not shown in your account;
source data files cannot be exported from the platform;
KitConnect is blocked by hosting or security rules you cannot change;
you are unsure whether the setup points to the correct source store or target store;
the issue affects launch timing.
Include:
Order # and migration path;
Source Platform and Target Platform;
source store URL and target store URL;
setup type shown by Next-Cart;
separate Source Platform and Target Platform Test Connection results;
error message or screenshot;
credential type used, without sharing private token values in plain text;
affected data type;
what you expected to happen;
what happened instead;
urgency and launch timeline.
