Start Here

Start Here

Choosing the wrong entry point can duplicate work, bypass readiness checks, or send a Dashboard-level problem into the migration workflow. Use this page to identify the next operational decision based on the state of your migration.

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.

Use the purchased migration service as the working center

Purchased migration work is organized in My Migrations. In the Dashboard sidebar, expand Migrations, then select My Migrations and keep using the same migration when reviewing Statistics, History, connection setup, Configuration, migration activity, and validation evidence. When the existing project needs a higher Service tier, more Entity Points capacity, or another supported Add-on, use Purchase a Migration Upgrade from that migration’s Statistics view.

When to use this section

Use this section 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

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:

1. Prepare the migration path, scope, capacity, access, target environment, and acceptance criteria.
2. Connect the Source and Target using the verified method for each platform and role.
3. Configure Select Data, Additional Options, Attribute Mapping, purchased Add-ons, and approved Custom requirements.
4. Use Demo Migration when a representative validation checkpoint is needed before relying on Full Migration.
5. Run the paid migration activity that matches the project state and purchased scope.
6. Validate records, relationships, media, URLs, statuses, and accepted platform differences.
7. 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.

Recommended documentation path

The migration context is selected before connection setup or configuration. Use the branch that matches the activity you intend to run.

1. Define the intended Source Platform to Target Platform path, required data, estimated volumes, Service needs, and any non-standard requirements.
2. 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.
3. 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.
4. After the Demo or paid migration is open, complete Connect Stores using the setup shown for its Source Platform and Target Platform.
5. Complete Configuration 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.
6. Continue to Migration, choose the available Run Mode, and start processing.
7. Review and validate the result before treating the activity as accepted.
8. A Demo can be repeated within the Demo frequency limit. After a paid migration has completed, use the available Additional Migration Options for the next activity when another run is required.
9. 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

Dashboard Keep migration ownership and service access under control by tracing purchases to active migrations, verifying payments, delegating safely, and securing the account.

Migration Project Toolkit Turn migration governance into a connected evidence system that ties scope, owners, risks, validation, redirects, decisions, and launch readiness to one project baseline.

Prepare Your Migration Lock down scope, access, ownership, Custom requirements, and acceptance evidence before setup so later configuration and validation rest on explicit decisions.

Connect Your Source and Target Platforms Establish verified source and target access using the setup Next-Cart requires for each platform, then resolve connection failures before configuration begins.

Configure Your Migration Translate approved scope into executable Select Data, Additional Options, Attribute Mapping, Add-on, and Custom settings, with a deliberate review before any migration processes records.

Run Your Migration Execute Demo, Full, continuation, or fresh migration activity with the correct action, configuration state, Run Mode, and immediate result checks.

Validate and Launch Your Target Store Turn completed processing into an evidence-backed acceptance and launch decision by validating migrated data, operational readiness, exceptions, and post-launch stability.

Troubleshooting Trace migration problems to the correct layer, contain further impact, apply the safest correction, and collect evidence before retrying or escalating.

Reference Resolve operational decisions with authoritative rules for Entity Points, service boundaries, migration controls, data availability, processing order, and platform-model differences.

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 Service, and validation criteria depend on the data you need to migrate.
Launch timing	Timing affects validation, continuation actions, and support planning.

Expected result

After using this page, you should know which documentation section to open next and which migration details to keep available while you work.

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/Managed checkout or the Custom quote path. For purchased work, expand Migrations, select My Migrations, and confirm the service Status.

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

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.