Prepare Source and Target Store Access
Confirm the account, admin, hosting, API, file, and approval access needed before Next-Cart can connect your selected Source Platform and Target Platform.
Prepare Source and Target Store Access
Section titled “Prepare Source and Target Store Access”Prepare the access required for the Source Platform and Target Platform before you start connection setup.
Next-Cart shows the supported setup for each platform in your selected migration path. Some platforms require admin access or API credentials. Some self-hosted platforms require hosting or server access for KitConnect. Some source platforms require exported data files.
Prerequisites
Section titled “Prerequisites”Before preparing access, confirm that:
- you can sign in to the Next-Cart account that owns the order and purchased migration;
- the order and Migrations → My Migrations show the correct Source Platform and Target Platform;
- the source store is available and not in the middle of major platform maintenance;
- the target store is created, accessible, and stable enough for validation;
- the person preparing access is authorized to create credentials, export data, or request hosting access;
- you know who can approve access changes, security changes, and migration decisions.
Access you may need
Section titled “Access you may need”| Access area | Prepare this | Why it matters |
|---|---|---|
| Next-Cart account | Email login, social login, or team access for the account that owns the order and purchased migration. | You need the correct account to access Orders, Migrations, Checkout, Tickets, and the migration workflow. |
| Source Platform admin | Admin access to the source store. | You may need to review source data, create credentials, export data, or confirm source records. |
| Target Platform admin | Admin access to the target store. | You need to confirm target readiness, validate migrated results, and adjust target-side settings. |
| API credentials | API keys, access tokens, private app credentials, client IDs, or secrets where requested. | Next-Cart uses the supported platform setup to read or write migration data. |
| Hosting or server access | SFTP, FTP, hosting control panel, or file manager access where KitConnect is required. | KitConnect must be placed in the correct web root for supported self-hosted platforms. |
| Source export files | Complete CSV, XML, XLSX, TXT, ZIP, or platform export files where source file upload is required. | Some source platforms provide migration data through exported files rather than direct platform access. |
| Security approval | Permission to create, share, rotate, or revoke temporary access. | Migration work often requires temporary credentials that should be removed after completion. |
| Decision owner | A named person who can approve scope, mapping, Add-ons, Custom Service requirements, and validation decisions. | Setup delays often happen when no one can approve changes or clarify expected results. |
Prepare access
Section titled “Prepare access”-
Confirm the purchased migration path
Open your Next-Cart account and review the order and purchased migration. Confirm that the Source Platform and Target Platform are correct.
-
Identify the access owner for each environment
Name the person responsible for source store admin access, target store admin access, hosting access, billing access, and technical approvals.
-
Review the setup requested by Next-Cart
In the migration interface, check the setup required for the Source Platform and Target Platform. Prepare only the setup shown for that migration path.
-
Prepare source store access
Confirm that you can open the source store admin, view the data in scope, create credentials if requested, and export source files if your platform requires file upload.
-
Prepare target store access
Confirm that you can open the target store admin, review migrated records, adjust target-side settings, and test storefront or admin behavior after migration.
-
Prepare hosting or server access if KitConnect is required
Confirm that you can access the web root, upload the KitConnect folder, form the KitConnect URL, and remove the folder after completion.
-
Prepare credential cleanup
Record which temporary credentials, API tokens, social connections, passwords, or server access details must be revoked, rotated, or removed after migration work is complete.
-
Document access limits and blockers
Note any restrictions such as missing admin rights, expired credentials, unavailable hosting access, source export limits, blocked IP ranges, or security approval delays.
Expected result
Section titled “Expected result”After completing this task:
- you know which account owns the order and purchased migration;
- the Source Platform and Target Platform are confirmed;
- source store and target store access are ready for setup and validation;
- required credentials, files, or server access can be prepared when requested;
- the correct people can approve access, scope, mapping, and validation decisions;
- temporary access cleanup is planned before migration work begins.
Verify your access readiness
Section titled “Verify your access readiness”| Check | Pass condition |
|---|---|
| Account ownership | You can open the correct order in Orders and the purchased migration in My Migrations. |
| Migration path | The Source Platform and Target Platform match the purchased service. |
| Source admin access | You can view the source records that will be migrated. |
| Target admin access | You can open the target store and inspect migrated results when available. |
| Credential authority | You can create, copy, rotate, or revoke credentials if the platform setup requires it. |
| File export readiness | If source file upload is required, you can export complete files in the required format. |
| Hosting readiness | If KitConnect is required, you can access the web root and remove temporary files after completion. |
| Approval ownership | A named person can approve access, setup changes, scope decisions, and validation results. |
Failure handling
Section titled “Failure handling”| Issue | What to do |
|---|---|
| You cannot access the correct Next-Cart account | Check the login method used for purchase. If needed, use password reset or contact the account owner. |
| The migration path is incorrect | Do not continue setup. Review the order and purchased migration, then contact support before entering credentials. |
| Source store access is incomplete | Ask the store owner to grant the required admin, export, or credential permissions. |
| Target store access is incomplete | Ask the target store owner to grant admin access before validation starts. |
| API credential creation is blocked | Confirm your admin role has permission to create apps, tokens, or integrations. |
| Source export files are incomplete | Re-export the full required range. Do not manually remove columns or rename fields unless instructed. |
| Hosting access is unavailable | Ask the hosting owner to provide temporary SFTP or file manager access, or assign someone who can install KitConnect. |
| Security approval is blocked | Pause setup until the access owner approves credential sharing, temporary access, and cleanup responsibilities. |
What not to do
Section titled “What not to do”Do not:
- enter credentials before confirming the migration path;
- create credentials with broader permissions than needed when a narrower permission set works;
- manually edit source export headers or delete columns unless instructed;
- use a staging target store when you intend to validate a production target store;
- leave temporary credentials, server access, or KitConnect files in place after completion;
- continue setup when you are unsure which account owns the purchased migration.
Next step
Section titled “Next step”| If your access is ready | Go to |
|---|---|
| You need to connect the platforms | Connect Your Source and Target Platforms |
| You need to define exactly what data should migrate | Define Migration Scope |
| You need expert handling for non-standard data | Prepare Custom Service Requirements |
| You need to define pass/fail criteria | Define Acceptance Criteria |
| You need help with access or setup blockers | Tickets |