Overview

Connect Your Source and Target Platforms

Reliable connections give Next-Cart the access needed to read supported source data and write the approved result to the target store.

Next-Cart shows the supported setup for each platform in your migration path. One side may require API credentials, while another side may require KitConnect or source data files. Prepare only the setup shown in your Next-Cart interface.

Use the setup shown by Next-Cart

API setup, KitConnect, and source data file upload are not interchangeable options. Use the setup shown for the selected Source Platform and Target Platform.

Start here

How Platform Connection Setup Works Understand how Next-Cart determines the required setup for each platform.

Set Up an API Connection Prepare API credentials when Next-Cart shows API setup for a platform.

Upload Source Data Files Prepare and upload exported source files when file upload is required.

Install KitConnect Upload KitConnect to the correct web root when server-side setup is required.

Use File Transfer Tools Use FileZilla, Cyberduck, WinSCP, or cPanel File Manager to place required files.

Verify Platform Connections Use the separate Test Connection controls for the source and target stores before migration configuration.

Troubleshoot Connection Setup Resolve API, KitConnect, file upload, permission, URL, and environment issues.

Platform-specific guides

API Connection Guides Find platform-specific API credential preparation guides.

Source Data Export Guides Find platform-specific source export guides for file-based setup.

What you need before setup

Requirement	Why it matters
Correct Source Platform and Target Platform	Connection requirements depend on the selected migration path.
Access to the Next-Cart account that owns the purchased migration	You need the correct account to open the migration workflow and enter connection details.
Source store and target store access	You may need admin, owner, API, hosting, or file export permissions.
Approved migration scope	Credentials and exports should cover the data types you plan to migrate.
Secure credential handling	Tokens, passwords, and temporary access should be shared only through approved secure channels.
Cleanup plan	Temporary API credentials, KitConnect files, and SFTP access should be revoked, removed, or rotated after migration work is complete.

For API and KitConnect setup, Connect Stores provides a separate Test Connection control for the Source Platform and Target Platform. Test each side that uses one of these methods independently. A successful result for one store does not verify the other store.

Recommended order

Step	Page
1	How Platform Connection Setup Works
2	Use the setup page shown by Next-Cart: Set Up an API Connection, Upload Source Data Files, or Install KitConnect
3	Use a platform-specific guide if the setup requires platform-specific values or files.
4	Verify Platform Connections
5	Continue to migration configuration after the required connections pass verification.