Install KitConnect

Install KitConnect

Install KitConnect only when Connect Stores assigns the connector setup to the Source Store or Target Store. Place the bridge in the public web root, enter the requested connection values, and optionally use Test Connection to check access.

Keep the original KitConnect folder name

In this guide, kitconnect_xxxxxx is a placeholder for the folder extracted from kitconnect.zip. Its suffix is unique to your Next-Cart account. Keep the actual 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.

Before you start

You need:

• access to the active migration as the owner or through Delegate Access;
• SFTP, FTP, or hosting File Manager access;

If you need help connecting by SFTP or FTP, locating the web root, uploading the extracted folder, or extracting the ZIP through hosting File Manager, use Use File Transfer Tools before continuing.

Required placement

• Directorypublic_html/

  • index.php
  • Directorykitconnect_xxxxxx/

    • kitconnect.php
    • …

In this example, we assume public_html is the website’s root directory. Your root directory name may differ depending on your web server configuration.

Before continuing from Connect Stores to Configuration, confirm the store URL that applies to the paid migration. The applicable Store URL locks at that transition, not when Test Connection succeeds. See Store URL Locking and Store Identity.

Install KitConnect

1. In Connect Stores, download kitconnect.zip for the store that requires KitConnect.
2. Extract the archive and keep the extracted folder name unchanged: kitconnect_xxxxxx/kitconnect.php.
3. Upload that folder to the store web root by SFTP, FTP, or hosting File Manager. If you upload the kitconnect.zip through hosting File Manager instead, extract it in the same web root.
4. Enter the Store URL in Connect Stores.
5. If the other store also uses KitConnect, repeat the installation for that store. Its manual connection test is also optional.

Manual testing is optional. If a test returns Connected, no separate browser or application-level check is required. If access fails, Next-Cart displays a pop-up notification and Not connected beside the affected platform.

If Test Connection returns Not connected

Only then inspect the bridge directly.

Symptom or check	Corrective action
Wrong store web root	Store web root is not the /root directory. It is the directory directly containing your website’s source code, or the public directory within the source code (if applicable).
kitconnect_xxxxxx/kitconnect.php is missing	Both the kitconnect_xxxxxx directory and the kitconnect.php file need to be uploaded. Ensure that the file is located inside the folder.
Handshake URL returns 404	Confirm that the domain points to the correct store web root and that the URL uses the actual extracted KitConnect folder name.
Server or permission error	Confirm that the kitconnect_xxxxxx directory and the kitconnect.php file have correct permissions.
Firewall or security challenge	Allow the KitConnect endpoint through the WAF, CDN, Cloudflare configuration, or security plugin.
Endpoint responds but the test still fails	Recheck the exact KitConnect values and selected store, then retest only that side.

For diagnosis, the example handshake URL is below. Replace kitconnect_xxxxxx with your actual extracted folder name:

https://your-domain.com/kitconnect_xxxxxx/kitconnect.php

If the test still fails, use Troubleshoot Connection Setup.

Remove KitConnect after migration work

After the migration and required follow-up work are complete and accepted, delete the actual KitConnect folder installed for this migration and temporary kitconnect.zip copies from the server. Use the installed folder name, not the placeholder kitconnect_xxxxxx.

Next Steps

Once the required Source and Target setup is complete, continue to Configure Your Migration.