How Platform Connection Setup Works
Understand how Next-Cart shows the supported connection setup for your selected Source Platform and Target Platform.
How Platform Connection Setup Works
Section titled “How Platform Connection Setup Works”Connection setup is determined by the selected Source Platform, Target Platform, and migration path. Review the setup shown by Next-Cart before creating credentials, exporting files, or installing KitConnect.
Connection setup depends on the selected Source Platform, Target Platform, and migration path. Next-Cart shows the setup that applies to the selected platforms. The two sides of the migration path may require different setup details.
Prerequisites
Section titled “Prerequisites”Before you review connection setup, confirm that:
| Requirement | Why it matters |
|---|---|
| You can sign in to the correct Next-Cart account | Setup is tied to the account that owns the order and purchased migration. |
| The purchased migration exists | You need a fixed migration path before setup details are meaningful. |
| The Source Platform and Target Platform are correct | Setup requirements depend on the selected platforms. |
| You can access the source store and target store | Connection setup often requires admin, API, hosting, or file access. |
| You know who owns technical access | Some setup steps require an account owner, store admin, developer, or hosting administrator. |
Connection setup types
Section titled “Connection setup types”Next-Cart may show one or more setup types depending on the selected platforms.
| Setup type | Where it usually applies | What you prepare |
|---|---|---|
| API connection | Common for supported hosted platforms and platforms with API access. | Store URL, admin URL, API URL, API key, token, client ID, client secret, app credentials, or authorization values shown for the platform. |
| KitConnect | Common for supported self-hosted or open-source platforms when server-side access is required. | KitConnect package, hosting access, web root location, uploaded KitConnect folder, and KitConnect URL. |
| Source data file upload | Common when a supported Source Platform provides exported files instead of direct connection access. | Complete source exports in the required file formats and folder structure. |
| File transfer | Used when you need to upload KitConnect or required files to hosting. | SFTP, FTP, hosting File Manager, correct directory, and file upload verification. |
Test API and KitConnect setup
Section titled “Test API and KitConnect setup”When the required setup uses API credentials or KitConnect, Connect Stores provides a separate Test Connection control for the Source Platform and Target Platform. Run each available test after entering the required values. When both sides use one of these methods, test them separately.
| Result | Meaning |
|---|---|
| Source succeeds and Target succeeds | Both tested store connections are established and you can continue to Configuration after any required source files are also accepted. |
| Source fails and Target succeeds | Correct the source-store setup. The successful target result does not verify source access. |
| Source succeeds and Target fails | Correct the target-store setup. The successful source result does not verify target access. |
| Both fail | Review each side separately because the two stores can have different setup methods, credentials, URLs, or access owners. |
Source data file upload does not use Test Connection. Confirm instead that the required files are uploaded, accepted, readable, and complete.
How Next-Cart uses the selected platforms
Section titled “How Next-Cart uses the selected platforms”The Source Platform and Target Platform determine which connection fields appear.
| Platform role | What Next-Cart needs to do | Common setup result |
|---|---|---|
| Source Platform | Read source-store data from the current platform. | API credentials, KitConnect URL, or source data files, depending on platform support. |
| Target Platform | Write migrated data into the target store where supported. | API credentials, authorization details, or platform-specific connection values. |
| Both platforms together | Translate data from the source model into a target-store structure. | Setup must support the selected data types and migration options. |
Decide which guide to use
Section titled “Decide which guide to use”Use the setup shown in the Next-Cart interface to choose the correct guide.
| If Next-Cart asks for | Use this guide |
|---|---|
| Store URL, API key, access token, client ID, client secret, app credential, or authorization value | Set Up an API Connection |
| Exported CSV, XLSX, XML, TXT, ZIP, SQL, or platform-specific source files | Upload Source Data Files |
| KitConnect URL or temporary server-side bridge access | Install KitConnect |
| SFTP, FTP, hosting control panel, or file manager upload | Use File Transfer Tools |
| A failed connection test, authentication error, file error, or access blocker | Troubleshoot Connection Setup |
Prepare for connection setup
Section titled “Prepare for connection setup”- Sign in to the Next-Cart account that owns the order and purchased migration.
- Open Migrations → My Migrations and select the intended migration path.
- Confirm the Source Platform and Target Platform.
- Open the migration interface for the selected path.
- Review the connection fields shown for the source store.
- Review the connection fields shown for the target store.
- Identify the setup type required for each side.
- Open the matching guide before creating credentials, exporting files, or uploading KitConnect.
- For API or KitConnect setup, use Test Connection separately for each side that uses one of these methods.
Expected result
Section titled “Expected result”After reviewing the setup model, you should know:
- which setup path applies to the source store;
- which setup path applies to the target store;
- which credentials, files, or server access you need to prepare;
- which detailed guide to follow next;
- which access owner must provide credentials, exports, or hosting access;
- which setup items must be cleaned up after migration work is complete.
Verify the setup path before continuing
Section titled “Verify the setup path before continuing”| Check | Pass condition |
|---|---|
| Migration path | The Source Platform and Target Platform match the purchased service. |
| Setup fields | The fields shown in Next-Cart match the selected platforms. |
| Access ownership | The correct person can provide API, admin, file, or hosting access. |
| Source-side setup | The source store can provide the setup shown by Next-Cart. |
| Target-side setup | The target store can provide the setup shown by Next-Cart. |
| Connection tests | Each applicable source or target Test Connection result succeeds when API or KitConnect is used. |
| Security cleanup | You know which credentials, files, tokens, or temporary access must be removed after completion. |
If the setup path looks wrong
Section titled “If the setup path looks wrong”| Issue | What to do |
|---|---|
| The Source Platform or Target Platform is wrong | Stop setup and review the order and purchased migration. Contact support before entering credentials. |
| The setup fields do not match the platform you selected | Confirm the migration path and refresh the migration interface. Submit a ticket if the fields still look incorrect. |
| You expected API setup but see file upload | Confirm whether the selected Source Platform uses exported files for migration input. |
| You expected file upload but see API fields | Confirm whether Next-Cart supports direct platform access for the selected platform. |
| You cannot provide hosting access for KitConnect | Ask the hosting owner to complete the upload or provide temporary access through an approved channel. |
| You cannot create required API credentials | Confirm your admin role and API permissions in the platform. Ask the platform owner to create credentials if needed. |
Security notes
Section titled “Security notes”Keep setup access temporary and limited.
- Create dedicated credentials for migration work where possible.
- Use the minimum permissions needed for the selected data types when the platform allows scoped permissions.
- Store tokens and secrets securely.
- Do not paste passwords, private keys, Backup Codes, or unnecessary sensitive data into tickets.
- Revoke API tokens after migration work is complete and verified.
- Remove KitConnect after completion if it was used.
- Rotate temporary hosting, SFTP, FTP, or admin passwords after completion.
After the required access is prepared, complete the setup shown for each platform and continue to Verify Platform Connections.