Install KitConnect

Install KitConnect

Install KitConnect only when Next-Cart shows KitConnect setup for the selected Source Platform or Target Platform.

KitConnect is a temporary connection bridge used for supported self-hosted platforms. It is uploaded to the store server so Next-Cart can access the required store data during migration work.

Use KitConnect only when Next-Cart requires it

Do not install KitConnect unless the Next-Cart interface shows KitConnect setup for your selected migration path. Some platforms use API credentials or source data files instead.

Prerequisites

Before installing KitConnect, confirm that:

• Next-Cart shows KitConnect setup for the selected platform;
• you can sign in to the Next-Cart account that owns the order and purchased migration;
• you can download the KitConnect package for the current migration setup;
• you have FTP, SFTP, or hosting File Manager access to the store server;
• you know the web root where the store is installed;
• the person uploading the package is authorized to add and remove temporary files on the server.

What you need

Item	Purpose
KitConnect package	The ZIP package downloaded from the current Next-Cart setup.
FTP, SFTP, or hosting access	Access used to upload the unzipped KitConnect folder to the store server.
Web root path	The public folder where the store is installed. Common names include public_html, www, wwwroot, or httpdocs.
Store domain	Used to form the public KitConnect URL after upload.
Cleanup owner	The person responsible for removing KitConnect after migration work is complete and verified.

Expected folder placement

Upload the unzipped KitConnect folder directly inside the store web root.

• Directorypublic_html/

  • Directorykitconnect_abc123/

    • index.php
    • bridge.php
    • files…

The folder name may differ. Use the folder name generated for your current KitConnect package unless Next-Cart instructs otherwise.

Install and connect KitConnect

1. Sign in to the Next-Cart account that owns the order and purchased migration.
2. Open the migration setup that requires KitConnect.
3. Download the KitConnect package.
4. Unzip the package on your computer.
5. Confirm the unzipped folder name.
6. Connect to the store server through SFTP, FTP, or hosting File Manager.
7. Open the store web root folder.
8. Upload the entire unzipped KitConnect folder into the web root.
9. Do not rename the KitConnect folder unless Next-Cart instructs you to do so.
10. Confirm that the uploaded folder contains the expected KitConnect files.
11. Form the KitConnect URL using the store domain and uploaded folder name.
12. Open the KitConnect URL in a browser to confirm that it is reachable.
13. Enter the KitConnect URL in the Next-Cart setup field shown for the selected platform.
14. Select Test Connection for that platform in Connect Stores.
15. If both the Source Platform and Target Platform use KitConnect, test each side separately.

Form the KitConnect URL

The KitConnect URL normally uses this structure:

https://yourstore.com/kitconnect_folder_name

Replace yourstore.com with the store domain and kitconnect_folder_name with the actual uploaded folder name.

Example value	Meaning
https://example.com/kitconnect_abc123	KitConnect folder uploaded directly under the web root for example.com.
https://store.example.com/kitconnect_abc123	KitConnect folder uploaded under the web root for a subdomain store.

Use the public store domain that reaches the uploaded folder

The URL must open the KitConnect folder from a browser. If the store uses a subdomain, staging domain, or protected environment, use the domain that matches the server location where KitConnect was uploaded.

Expected result

After installation:

• the KitConnect folder is uploaded to the correct web root;
• the KitConnect URL opens from a browser;
• the URL is entered in the Next-Cart setup field;
• Test Connection succeeds for the applicable Source Platform or Target Platform;
• the cleanup owner knows when to remove the folder.

Verify KitConnect

Check	Pass condition
Folder placement	The KitConnect folder is inside the store web root, not inside the wrong domain, backup folder, or private directory.
Folder name	The URL uses the exact uploaded folder name.
Browser access	The KitConnect URL opens from a browser without a 404, redirect loop, login wall, or server error.
HTTPS access	The URL uses HTTPS where the store supports it.
File permissions	Folders and files use normal host-approved permissions.
Security rules	Firewall, CDN, hotlink protection, or server rules do not block access.
Next-Cart setup	The KitConnect URL is entered in the field shown for the selected platform.
Test result	Test Connection succeeds for the source or target store where KitConnect is used.

If KitConnect does not work

Issue	What to check
URL returns 404	Confirm the folder is uploaded to the correct web root and the URL uses the correct domain and folder name.
URL redirects to the storefront or home page	Check server rewrite rules, redirects, and whether the folder was uploaded under the correct site.
URL shows a permission error	Check file and folder permissions, hosting security rules, and whether the server allows public access to the folder.
Connection test fails after the URL opens	Confirm that the selected platform is correct and that KitConnect was downloaded for the current migration setup.
CDN or firewall blocks access	Temporarily allow access for verification or ask the hosting/security owner to review blocking rules.
Uploaded ZIP was not extracted	Extract the ZIP first, then use the unzipped KitConnect folder in the URL.
Wrong environment is connected	Confirm whether KitConnect was uploaded to production, staging, or another environment.

Security cleanup

After migration work is complete and verified, remove KitConnect from the server if it is no longer needed.

Recommended cleanup:

• delete the KitConnect folder from the web root;
• remove any temporary ZIP files uploaded during setup;
• rotate temporary SFTP, FTP, hosting, or admin passwords if they were created for migration work;
• revoke temporary credentials that are no longer needed;
• verify that the old KitConnect URL no longer opens.

Do not remove KitConnect too early

Remove KitConnect only after required migration work is complete and the result has been verified. Removing it too early can block connection verification, support investigation, or follow-up migration actions.

Next step

Situation	Go to
You need help uploading the folder	Use File Transfer Tools
KitConnect is uploaded and reachable	Verify Platform Connections
The URL or connection test fails	Troubleshoot Connection Setup
Platform connections are verified	Configure Your Migration