Migrations

Migrations

Migrations is a collapsible Dashboard group that separates limited Demo activity from purchased migration services. Selecting Migrations only expands or collapses its nested menu; it does not navigate away from the open Dashboard view.

The group contains two destinations:

• Demo Migrations for limited migration tests;
• My Migrations for all purchased migration services.

Choose the migration before configuring it

Demo Migrations and My Migrations are separate execution contexts. Select the Demo or purchased migration first, then open it with Start or Start a New Demo before completing Connect Stores or Configuration. A Demo does not create or replace a purchased migration service.

What a purchased migration includes

Each initial migration service purchase creates one migration that you manage in My Migrations. The purchase includes:

Component	Rule
Migration Path	One fixed Source Platform to Target Platform path. The path cannot be changed after purchase.
Migration Service	Standard, Managed, or Custom. The service can be upgraded from Standard to Managed or Custom, or from Managed to Custom. It cannot be downgraded.
Entity Points Plan	The plan capacity attached to the migration. The plan can be increased after purchase but cannot be downgraded.
Add-ons	Optional capabilities purchased initially or added to the same migration later.
Service Duration	A Paid New migration receives 12 months of access from the successful payment-confirmation timestamp. Upgrades do not extend that period. A Paid Extend order starts a new 12-month period from extension-payment settlement.

Lightspeed edition selection does not change the purchased path

A Lightspeed → Target Platform migration can run from any supported Lightspeed edition. The Edition selection changes the Source connection setup, while the purchased Source Platform remains Lightspeed.

Standard, Managed, and Custom migrations remain visible through My Migrations and use the same Connect Stores, Configuration, and Migration workflow when the project is ready for that work. Customers retain Dashboard visibility and operational access to inspect, manage, and use the available execution controls across all three Services.

For Custom Service, the selected Self-Execute or Expert Handle mode defines who is responsible for execution.

When Expert Handle is selected, Next-Cart is responsible for the agreed migration execution without removing the customer’s operational Dashboard access. Customer-initiated execution should remain aligned with the agreed schedule.

A Paid Custom order can still require approved Customization to be prepared and verified before that custom scope is ready to run. Use the readiness notification rather than the Paid status alone to confirm engineering readiness.

Use the Migrations group

1. Sign in to Next-Cart.
2. Expand Migrations in the Dashboard sidebar. The open Dashboard view remains in place while the nested menu expands.
3. Select Demo Migrations for a limited migration test, or My Migrations for a purchased migration service.
4. Find the intended migration path.
5. Review the available information and actions before continuing.

Demo Migrations

Demo Migrations can show the migration path, start date, last updated date, and available actions for each Demo.

Action	Use it to
Statistics	Review summary and progress information for the Demo Migration.
Start	Open the three-step Demo workflow.
History	Review the activity recorded for Connect Stores, Configuration, and Migration.
Start a New Demo	Create another Demo Migration, subject to the daily Demo limit.

Use Demo Migrations for the Dashboard entry points and available actions. For the complete operating procedure and Demo limits, see Demo Migration walkthrough.

My Migrations

My Migrations lists each purchased service as one migration. Service upgrades, plan capacity, Add-ons, and approved custom work are integrated into that same migration rather than creating a separate migration path.

Information	What it means
Migration Path	The fixed Source Platform → Target Platform path, shown with the two platform identities.
Service	The active Migration Service: Standard, Managed, or Custom.
Entity Points	The used and maximum Entity Points for the active plan.
Created / Expires	Created identifies the project record. Expires shows the end of the active service period: 12 months after a successful New payment, or 12 months after the latest successful Extend payment. Upgrades do not change it.
Status	Whether the purchased migration service is Active, Expired, or Suspended.
Actions	Statistics, History, and Start where the service state allows migration work.

Service status

Status	Meaning	Start availability
Active	The purchased migration service is within its available service period and can be used.	Start is available when no other requirement blocks access.
Expired	The active 12-month service period has ended.	Start is unavailable. Use the available extension path when you want to renew the migration from its latest active package.
Suspended	Access to the purchased migration has been placed on hold, including after an approved full refund where applicable.	Start is unavailable. Review the related order and contact Support when the reason or next action is unclear.

Actions for a purchased migration service

Action	What it contains or does
Statistics	Opens Overview information including Migration Path, Plan & Service, Upgrade Your Migration, Data Migration Progress, Linked Orders, and Delegate Access.
History	Opens the Activity Timeline with detailed records of actions performed for Connect Stores, Configuration, and Migration.
Start	Opens the purchased migration service and its three-step workflow.

Use Delegate Access to grant or revoke access to a purchased migration and to understand how delegated activity appears in History.

Review Linked Orders for this migration

The Linked Orders table inside Statistics is the project-level financial trail. It lists every order associated with the migration, including successful, pending, and failed transactions, without mixing in orders from other projects.

Field	What to use it for
Order Number	Select the hyperlinked Order # to open that transaction’s Order Details page in Orders.
Created	Confirm when the order record was created.
Type	Distinguish New, Upgrade, Extend, or another supported transaction type.
Amount	Review the purchase amount recorded for the transaction.
Status	Distinguish Paid, Pending Approval, Failed, and other recorded order states.

Use the hyperlinked Order # when a linked transaction needs detailed review. After reviewing the order in Orders, return to Statistics when you need to compare that historical transaction with the migration’s active Plan & Service, Entity Points, status, or expiration.

For the complete order-detail fields, Upgrade and Extend behavior, account-wide ledger, and the difference between transaction history and live project state, use Orders.

Upgrade a purchased migration

From the migration Overview, use View Upgrade Option to open the existing project in Checkout. Follow Purchase a Migration Upgrade for the complete Service, Entity Points Plan, Add-on, Payment, and post-purchase verification workflow.

The migration path remains fixed. An Upgrade also does not clear or replace any Source or Target Store URL already locked under Store URL Locking and Store Identity. For upgrade direction, delta billing, the no-downgrade rule, failed Upgrade behavior, and how a successful Upgrade changes the live migration, use Orders.

Extend an expired migration

Use the available extension option for the intended expired migration when the project should continue on the same fixed migration path. Extending the migration does not clear or replace its locked Store URLs. Review the retained package and any concurrent upgrade in the resulting Extend order before payment. After the Extend order becomes Paid, the renewed access period runs for 12 months from the successful extension-payment settlement timestamp.

For the extension billing baseline, which successful changes form the active package, and how an Extend order is synchronized back to the migration, use Orders.

Understand a partial refund

An approved partial refund removes the refunded order value or upgrade components from the recorded migration package. The migration continues from the latest state supported by the remaining purchase and upgrade history.

Refund eligibility is defined elsewhere

The Next-Cart Refund Policy governs whether an order or upgrade is eligible and whether a request is approved. Use Orders and Linked Orders only to verify the resulting transaction and migration state.

Start a purchased migration service

1. In the Dashboard sidebar, expand Migrations, then select My Migrations.
2. Find the migration path you intend to operate.
3. Confirm that Service, Entity Points, Created / Expires, and Status match the purchase you expect.
4. For Custom Service, confirm the approved operation mode and any required readiness notification before executing work that depends on Customization.
5. Select Statistics when you need to review the active plan, progress, linked orders, upgrade options, or Delegate Access before starting.
6. Select History when you need to review previous activity.
7. Select Start for an Active service when the project is ready for execution.
8. Continue through Connect Stores, Configuration, and Migration according to the selected Service and execution responsibility.

The first migration has no last used configuration

When a purchased migration service has not completed a migration before, configure it from the beginning. Next-Cart records the configuration used after migration work is completed. That recorded configuration can support Continue the Migration with the Last Used Configuration later.

Expected result

After using Migrations, you should be able to:

• open the correct category;
• identify the intended migration path;
• confirm whether a purchased service is Active, Expired, or Suspended;
• review Statistics, upgrades, extensions, refund effects, or History;
• open an eligible service with Start;
• continue through Connect Stores, Configuration, and Migration.

Verify before selecting Start

Check	Pass condition
Category	My Migrations is selected for purchased migration work.
Migration Path	The Source Platform and Target Platform match the intended project.
Service	Standard, Managed, or Custom matches the purchase. For Custom Service, the execution responsibility also matches Self-Execute or Expert Handle.
Entity Points	The displayed plan matches the expected coverage.
Created / Expires	Expires reflects the active period: 12 months after the successful New payment or, after renewal, 12 months after the successful Extend payment.
Status	The service is Active.
Migration access	You can open the migration as the owner or through valid Delegate Access.

If the project uses the Migration Project Toolkit, copy the verified migration path, Migration Service, Entity Points Plan, purchased Add-ons, approved Customization, and verified expiry into Project Overview and readiness before planning project work. This keeps the workbook anchored to the live purchased service rather than an earlier estimate.

Failure handling

Issue	What to do
A purchased migration service is missing	Owner: open Orders and confirm that the New order is Paid. Collaborator: confirm that the owner granted Delegate Access to the intended migration. If the paid migration is still unavailable to an authorized user, submit a ticket with the Order #.
Start is unavailable	Check Status and Expires. Use the available extension path for an Expired migration. Review the related order or contact Support for a Suspended migration.
The migration path is wrong	Do not proceed. Review the related order and contact Support if the purchase does not match the intended path.
Entity Points coverage is insufficient	Use Statistics to review Upgrade Your Migration before processing remaining eligible records.
An upgrade is missing	Open Linked Orders or Orders and confirm that the Upgrade order is Paid. Submit a ticket with the order number if the paid upgrade is not integrated into the migration.
An extension is missing	Open Linked Orders or Orders and confirm that the Extend order is Paid. If the package or Expires time is not updated to the new 12-month period, submit a ticket with the Order Number and paid timestamp.
The package does not match a partial refund	Compare the migration with the base order and remaining Linked Orders. Preserve the affected Order # and submit a ticket before using a component that should have been removed or retained.
A Custom order is Paid but approved Customization is not confirmed ready	Do not treat Paid as engineering readiness. Review the agreed timeline and readiness communication, then contact Support with the Order # if the expected notification is overdue.
An activity is unfamiliar	Open History and review the Activity Timeline. If delegated access is involved, follow Delegate Access to review or revoke it.
A delegated user should not have access	Revoke the user through Delegate Access.

Next Steps

For a first purchased migration, select Start and continue through Connect Your Source and Target Platforms, Configure Your Migration, and Run Your Migration.