Verify Platform Connections

Verify Platform Connections

Verify both store connections before configuration so authentication, permissions, URLs, files, and environments are correct. For API and KitConnect setup, Connect Stores provides a separate Test Connection control for the Source Platform and Target Platform.

Connection verification confirms that Next-Cart can use the setup shown for the selected Source Platform and Target Platform. It helps identify authentication, permission, URL, file, hosting, and environment issues before they affect Demo Migration, Full Migration, or validation.

Verify before configuring migration options

Do not continue to data selection, mappings, Add-ons, or migration execution until required platform connections pass verification or the blocker is understood.

Prerequisites

Before you verify platform connections, confirm that:

Requirement	Why it matters
The migration path is correct	Verification must apply to the intended Source Platform and Target Platform.
The required setup values are entered	Empty or partial setup fields cannot pass verification.
The source store is available	Next-Cart must be able to read source data or source files where supported.
The target store is available	Next-Cart must be able to access the target store where supported.
Credentials are current	Expired, revoked, or regenerated credentials can fail even if they were correct earlier.
Required files are uploaded	File-based source setup cannot pass if required exports are missing or unreadable.
KitConnect is reachable if required	The KitConnect URL must be public, accessible, and placed in the correct web root.

What to verify

Area	Verification goal
Account context	You are using the Next-Cart account that owns the order and purchased migration.
Migration path	The Source Platform and Target Platform are correct.
Source setup	Next-Cart can read the source-store data or source data files required for selected data types.
Target setup	Next-Cart can access the target store and prepare to write supported migrated data.
Permissions	Credentials allow access to the required data types.
Environment	You are connected to the intended production, staging, or test environment.
Security controls	Firewalls, IP restrictions, CAPTCHA, hotlink protection, or hosting rules do not block required access.
Separate test results	The source and target Test Connection results identify which side succeeds or fails.

Verify an API connection

Use this workflow when Next-Cart shows API, token, app, or authorization fields for the selected platform.

1. Confirm that the Store URL, Admin URL, API URL, or endpoint value uses the format requested by Next-Cart.
2. Re-copy API keys, tokens, client IDs, client secrets, or authorization values from the platform if needed.
3. Confirm that the credential is active.
4. Confirm that required scopes or permissions are enabled for the selected data types.
5. Select Test Connection for the Source Platform when the source store uses API setup.
6. Record the source result before changing any target values.
7. Select Test Connection for the Target Platform when the target store uses API setup.
8. Record the target result separately.
9. If either test fails, preserve the affected side and error message before using the failure-handling table below.

Verify a KitConnect connection

Use this workflow when Next-Cart requires KitConnect for the selected platform.

1. Confirm that the KitConnect folder is uploaded to the correct web root.
2. Confirm that the folder was not renamed unless instructed.
3. Open the KitConnect URL in a browser.
4. Confirm that the URL uses HTTPS where available.
5. Confirm that file and folder permissions follow your host’s standard security guidance.
6. Select Test Connection for the Source Platform or Target Platform where KitConnect is used.
7. Test the other side separately when it also uses API or KitConnect setup.
8. If either test fails, check the affected side’s folder placement, URL format, permissions, firewall rules, and hosting restrictions.

Verify source data files

Use this workflow when the selected Source Platform requires exported files.

1. Confirm that each required data type export is present.
2. Confirm that files use the required format, such as CSV, XLSX, XML, TXT, ZIP, SQL, or a platform-specific export format.
3. Confirm that exports cover the required date range or full record set.
4. Confirm that column headers, IDs, file names, and relationship fields were not changed unless instructed.
5. Upload the files through the Next-Cart interface or the required transfer path.
6. Confirm that the uploaded files are visible and readable.
7. Continue only after required files are accepted or the issue is understood.

Verification checklist

Check	Pass condition
Source Platform	The selected Source Platform matches the purchased migration path.
Target Platform	The selected Target Platform matches the purchased migration path.
Source URL	The source URL points to the intended source store or source endpoint.
Target URL	The target URL points to the intended target store or target endpoint.
Source Test Connection	The Source Platform test succeeds when the source store uses API or KitConnect.
Target Test Connection	The Target Platform test succeeds when the target store uses API or KitConnect.
API credentials	Credentials are accepted and have the required permissions.
KitConnect URL	The KitConnect URL is reachable and points to the uploaded folder.
Source files	Required files are uploaded, readable, complete, and in the expected format.
Data access	Next-Cart can access data areas required for the selected scope.
Environment	You are not accidentally connected to the wrong staging, test, or production store.
Security restrictions	Firewall, IP restrictions, CDN settings, and hosting permissions do not block access.

Expected result

After successful verification:

• the source-store setup is accepted;
• the target-store setup is accepted where required;
• each applicable source or target Test Connection result succeeds where API or KitConnect is used;
• required source files are accepted if file upload is used;
• the selected environment is confirmed;
• required data type areas are accessible;
• you can continue to migration configuration.

If verification fails

Classify the failure before changing credentials, files, or migration settings.

Failure area	Immediate check
Source test only	Correct the source URL, credentials, permissions, KitConnect path, hosting access, or environment. Do not replace working target values.
Target test only	Correct the target URL, credentials, permissions, KitConnect path, hosting access, or environment. Do not replace working source values.
Both tests	Diagnose the two sides independently because they can use different setup methods and access owners.
Authentication or authorization	Confirm that the credential belongs to the intended store, remains active, and was copied without spaces or truncation.
Permission or scope	Confirm that the account or credential can access the data required by the approved migration scope.
URL, endpoint, environment, or KitConnect	Confirm the exact value requested by Next-Cart and verify that it points to the intended store and reachable location.
Source data files	Confirm the required files, original headers, readable format, complete export scope, and successful archive extraction.

Do not continue to migration configuration while required access remains unverified. Use Troubleshoot Connection Setup for the complete diagnostic procedure.

Evidence to preserve

Record the migration path, affected side, setup type, separate source and target test results, exact error message, environment URL, and masked screenshot when it materially clarifies the failure. Never include passwords, complete tokens, client secrets, private keys, Backup Codes, or payment details.

Next step

If verification shows	Go to
The connection is successful	Configure Your Migration
API credentials fail	Set Up an API Connection or Troubleshoot Connection Setup
Source files are missing or incomplete	Upload Source Data Files
KitConnect is unreachable	Install KitConnect
File transfer failed	Use File Transfer Tools
You need help from Next-Cart support	Tickets