Skip to content
Back to Site

Install KitConnect

Install KitConnect in the correct store web root, verify access when needed, troubleshoot Not connected, and remove the package after migration work is complete.

Install KitConnect only when the Connect Stores step assigns KitConnect to the Source Store, Target Store, or both. Each store that uses KitConnect requires its own package and installation.

KitConnect is temporary. For architecture, scope, and connection-model background, see Understanding KitConnect.

You need:

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

If you need to identify the directory that serves the store domain, use Locate the Website Web Root Folder. For SFTP, FTP, hosting File Manager, upload, or ZIP-extraction instructions, use Use File Transfer Tools.

The store web root is the directory that directly contains the website source code, or the public directory within the source code when applicable. It is not the server /root directory. Common web-root names include public_html, htdocs, www, wwwroot, public, or pub.

Keep the generated KitConnect folder name unchanged and maintain this structure inside the store web root:

  • 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.

  1. In the Connect Stores step, enter the Store URL for the store assigned KitConnect.
  2. Download kitconnect.zip for that store.
  3. Extract the archive. Keep the generated directory structure, file names, and folder name unchanged so kitconnect.php remains inside kitconnect_xxxxxx.
  4. Upload the complete extracted kitconnect_xxxxxx folder to the store web root through SFTP, FTP, or hosting File Manager. If you upload kitconnect.zip through hosting File Manager instead, extract it in that same web root without renaming or restructuring its contents.
  5. If the other store also uses KitConnect, repeat the Store URL, download, extraction, and upload process for that store.
  6. Use Test Connection when you want to verify access before continuing. If it 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.

For a visual upload walkthrough, see Upload KitConnect via FTP and cPanel.

Use these checks only for the affected store after Not connected appears.

CheckWhat to do
KitConnect folder or file is missingBoth the kitconnect_xxxxxx directory and the kitconnect.php file need to be uploaded. Ensure that the file is located inside the folder. Re-upload the complete extracted folder if the structure is incomplete.
Wrong store web rootStore 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). Use Locate the Website Web Root Folder to identify it, then move or re-upload the complete KitConnect folder there.
KitConnect URL returns 404Confirm that the domain points to the intended store web root and that the URL uses the actual generated KitConnect folder name.
WAF, CDN, Cloudflare, or bot protection blocks the KitConnect URLFollow Cloudflare, WAF, or CDN blocks KitConnect and apply only the access change required for the KitConnect URL.
Web server blocks direct access to the KitConnect URLReview Nginx blocks the KitConnect endpoint when it matches the server setup, or have the hosting administrator allow access to the KitConnect URL without weakening unrelated server protections.
KitConnect URL is reachable but the connection still failsRecheck the Store URL, actual KitConnect folder name, affected Source or Target Store, and values shown in the Connect Stores step, then retry only that store if needed.

For diagnosis after Not connected, use the actual generated folder name in this KitConnect URL pattern:

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

If the connection still fails, use Troubleshoot Connection Setup for the full connection-recovery workflow.

KitConnect is a temporary bridge used during migration. After the migration and required follow-up work are complete and accepted:

  1. Delete the KitConnect folder installed for this migration.
  2. Delete temporary kitconnect.zip copies from the server.
  3. Confirm that the removed KitConnect path is no longer present on the server.

Removing KitConnect does not undo migrated data. If later migration activity requires KitConnect again, download the package supplied for that active migration instead of assuming an earlier package should be reused.

After the required Source and Target setup is complete, continue to the Configuration step.