Start Here
Identify the exact next task based on your migration state so you avoid skipped prerequisites, duplicated work, and mixed Dashboard or execution workflows.
Start Here
Section titled “Start Here”Choosing the wrong entry point can duplicate work, bypass readiness checks, or send a Dashboard-level problem into the migration workflow. Identify the next operational decision from the state of the migration, then follow the matching path.
Enter where the work actually stands, whether you are purchasing or preparing, establishing access, configuring behavior, running migration activity, validating results, or recovering from a problem.
Choose the right starting point
Section titled “Choose the right starting point”Choose the starting point according to whether you need to:
- understand the recommended documentation path;
- find the right section for setup, configuration, execution, validation, or troubleshooting;
- identify the correct Dashboard area before opening a migration task;
- avoid mixing account settings with migration execution.
Migration workflow at a glance
Section titled “Migration workflow at a glance”An e-commerce platform migration moves the supported business data and relationships required by the project from the Source Platform to the Target Platform. It is not a promise to clone every source theme, extension, integration, URL pattern, payment rule, or storefront behavior.
Use this lifecycle:
- Prepare the migration path, scope, capacity, access, target environment, and acceptance criteria.
- Connect the Source and Target using the verified method for each platform and role.
- Configure Select Data, Additional Options, Attribute Mapping, purchased Add-ons, and approved Custom requirements.
- Use Demo Migration when a representative validation checkpoint is needed before relying on Full Migration.
- Run the paid migration activity that matches the project state and purchased scope.
- Validate records, relationships, media, URLs, statuses, and accepted platform differences.
- Complete target-store operational setup and launch checks that sit outside the data-migration boundary.
Migration is therefore a controlled transfer and validation process, not an automatic duplication of every source-store behavior. For the conceptual reasoning behind this lifecycle, see How the Migration Process Works in the Learning Center.
Choose the service and execution responsibility
Section titled “Choose the service and execution responsibility”A registered Next-Cart account is required to use the customer Dashboard and migration workflows. Choose the service model that matches the execution responsibility:
- Standard Migration for customer-operated migration within supported standard scope.
- Managed Migration when Next-Cart handles execution within supported standard scope.
- Custom Migration for approved non-standard scope. Its Self-Execute or Expert Handle operation mode determines who runs the agreed migration work.
If the Source Platform is not available as a standard supported path, describe the Custom Platform requirement through Custom Migration. CSV, XLS, and XML file Sources are handled through Custom Migration under the file-based Source model. SQL/database-file intake is also a Custom Migration requirement rather than a standard selectable Source Platform.
When technician access is required, preserve the actual access requirement but do not place passwords, 2FA codes, Backup Codes, secret API keys, FTP/SSH passwords, or other sign-in secrets directly in a Support Ticket. Use Delegate Access or the secure transfer method requested by Support.
Prepare the target environment and launch sequence
Section titled “Prepare the target environment and launch sequence”For a self-hosted Target Platform, prepare the new Target Store in a subdomain or subdirectory before migration when that setup matches the project architecture. Cloud-hosted targets such as Shopify or BigCommerce already provide a hosted store URL, so a separate subdomain is not required for that purpose.
Keep these workstreams separate from data migration:
- Move the approved supported data from the Source Store to the Target Store.
- Install/configure the desired target theme and required extensions separately from the data-migration scope.
- After the Target Store is validated and ready for production, change DNS/domain routing where the architecture requires it.
- After go-live, verify customer-facing email/notification settings and payment/checkout behavior.
- Monitor important old-to-new URL redirects and search evidence after launch so old URLs resolve to the intended new destinations.
Source Store means the existing store that supplies migration data. Target Store means the new destination store that receives the migrated data.
Recommended documentation path
Section titled “Recommended documentation path”The migration context is selected before connection setup or configuration. Use the branch that matches the activity you intend to run.
- Define the intended Source Platform to Target Platform path, required data, estimated volumes, Service needs, and any non-standard requirements.
- For a Demo, expand Migrations, select Demo Migrations, then select Start for an existing Demo or Start a New Demo to create another one. A Demo does not require a paid migration first.
- For paid migration work, use Purchase a Migration when needed, confirm the resulting order and service state, then expand Migrations, select My Migrations, and select Start for the intended Active migration.
- After the Demo or paid migration is open, complete Connect Stores using the setup shown for its Source Platform and Target Platform.
- Complete the Configuration step inside that same migration. Demo Migration exposes a reduced configuration set. Paid migration work exposes the configuration stages available for the purchased service, Add-ons, and approved Customization.
- Continue to the Migration step, choose the available Run Mode, and start processing.
- Review and validate the result before treating the activity as accepted.
- A Demo can be repeated within the Demo frequency limit. After a paid Migration has completed, choose the appropriate Migration Action and applicable Additional Options for the next activity when another run is required.
- Use troubleshooting pages when a connection, configuration, migration, validation, or Dashboard task does not work as expected.
If the project needs shared planning, ownership, risk, evidence, redirect, or sign-off tracking, create a working copy of the Migration Project Toolkit before execution and keep it aligned with the selected migration.
Choose the section you need
Section titled “Choose the section you need”What to prepare before opening task pages
Section titled “What to prepare before opening task pages”| Item | Why it matters |
|---|---|
| Next-Cart Account access | You need access to Orders, Migrations, Checkout, and Support. |
| Migration path | Connection setup and supported data behavior depend on the Source Platform and Target Platform. |
| Purchase or quote information | Before purchase, prepare the intended Service, data-volume estimate, Add-ons, and Custom requirements. After purchase, keep the resulting Service, Entity Points Plan, Order status, and Created / Expires information available. |
| Source and target store details | Setup, validation, and support reports require the correct environments. |
| Scope notes | Data selection, Additional Options, Add-ons, Custom Migration, and validation criteria depend on the data you need to migrate. |
| Launch timing | Timing affects validation, continuation actions, and support planning. |
Expected result
Section titled “Expected result”Before continuing, identify the task area that matches the next action and keep the required migration details available.
Verify your next step
Section titled “Verify your next step”| Check | Pass condition |
|---|---|
| Task | You can identify the task you need to complete. |
| Dashboard location | You know whether the task begins in Home, Orders, Checkout, Support, a destination under Migrations, or a destination under My Account. |
| Migration Path | You can identify the Source Platform and Target Platform. |
| Purchase state | If the migration is not yet purchased, you know whether to use direct Standard Migration or Managed Migration checkout or the Custom Migration quote path. For purchased work, expand Migrations, select My Migrations, and confirm the service Status. |
If you are not sure where to go next
Section titled “If you are not sure where to go next”Use the Dashboard when the issue concerns Orders, purchased migration services, Demo Migrations, Checkout, account settings, or Support.
Open Prepare Your Migration when scope, access, ownership, or acceptance criteria are not defined.
Open Troubleshooting when a setup step, configuration, migration run, validation check, or Dashboard action is blocked.
Next Steps
Section titled “Next Steps”If you have not purchased the migration yet, start with Prepare Your Migration and continue to Purchase a Migration when the path, Service, volumes, and requirements are ready. If the migration is already purchased, open Dashboard to confirm the relevant Order or migration. Use Purchase a Migration Upgrade when that existing project needs an eligible upward package change.