Test Platform Connections

Test Platform Connections

Test Connection is an optional access check in the Connect Stores step. A Source test checks the Source connection; a Target test checks the Target connection.

Connected verifies access only

A successful Test Connection verifies access to that store side. It does not determine migration scope and does not create the project Store URL lock. After the required Source and Target setups are successfully connected, the applicable URL lock becomes official when Continue to Configuration opens the Configuration step. See Store URL Locking and Store Identity.

Each test checks one connection

Connected on one side does not validate the other side. Required connection details must still be completed on both sides, even when you skip manual testing.

Run the tests

1. Complete the required connection details in the Connect Stores step.
2. To check Source access, click Test Connection in the Source Store section.
3. To check Target access, click Test Connection in the Target Store section.
4. Review the result for the connection you tested. Correct any reported access issue before continuing.

Once the required setup is complete and connected, use Continue to Configuration to advance. For a paid Migration, that Phase 1 to Phase 2 transition commits the applicable Store URL lock. For File Upload, provide the required Source files and complete the Target setup.

Connection feedback

A failed connection automatically displays a pop-up notification and Not connected beside the affected platform. Test Connection provides feedback for the side you test.

Status	Action
Connected	No additional manual connection check is required. Continue with the other side or proceed to the Configuration step.
Not connected	Use the returned error details to correct the affected URL, credential, permission, KitConnect setup, or access restriction, then retest only that side when you need to confirm access before continuing.

If a test fails

Do not change a working connection while troubleshooting the other side.

Keep the original KitConnect folder name

kitconnect_xxxxxx is a placeholder for the folder extracted from kitconnect.zip. Keep the actual extracted folder name unchanged when uploading it. Do not rename it to kitconnect or literally kitconnect_xxxxxx; use the extracted name wherever an example path or URL shows the placeholder.

Connection type	Check only after Not connected
API	Requested URL when the selected setup provides one, valid credential values, required scopes or permissions, token state, and platform access restrictions.
KitConnect	Store web-root placement, complete kitconnect_xxxxxx/kitconnect.php folder/file structure using the actual generated folder name, Store URL, and firewall/WAF/CDN/security blocking.
File-based source input	Export completeness, required format, file integrity, and upload acceptance.

If the same side still fails, use Troubleshoot Connection Setup or open a Support Ticket with the affected side and the exact error message. Do not include passwords, full tokens, client secrets, private keys, or Backup Codes.

Next Steps

Once the required connection details and files are ready, continue to Configure Your Migration.