Skip to content
Back to Site

Checkout

Purchase a migration, pay for an upgrade, extend an expired migration, or complete a pending order with the correct service, plan, Add-ons, and payment details.

Checkout converts approved migration requirements into a new purchase, upgrade, or extension by combining the migration path, Migration Service, Entity Points capacity, Add-ons, customer information, and payment.

An initial purchase creates one migration with a fixed migration path, Standard, Managed, or Custom Service, an Entity Points Plan, optional Add-ons, and a one-year duration from the purchase date.

Prepare:

RequirementWhy it matters
Correct accountThe order and purchased migration service belong to the signed-in account.
Migration pathThe purchase is tied to a fixed Source Platform → Target Platform path.
Service requirementChoose Standard, Managed, or Custom according to the required scope and assistance. Every Migration Service remains accessible through the migration workflow.
Counted data estimatesProduct, Customer, Order, and Blog Post estimates support Entity Points calculation.
Add-on requirementsRequired Add-ons must be included in the purchase where applicable.
Custom Service requirementsProvide clear rules, examples, source locations, expected target results, and pass conditions.
Billing informationCustomer, company, address, VAT or GST, and payment details must be accurate.
  1. Sign in to Next-Cart and open Account → Checkout.
  2. Select the Source Platform and Target Platform.
  3. Confirm the displayed migration path.
  4. Select Standard, Managed, or Custom Service.
  5. Enter realistic estimates for Products, Customers, Orders, and Blog Posts where applicable.
  6. Provide Custom Service requirements and attachments when the purchase requires custom handling.
  7. Enter or confirm customer and billing information.
  8. Review the calculated Entity Points and the closest plan automatically selected to cover that amount.
  9. Keep the selected plan or choose another plan that provides sufficient capacity.
  10. Review Add-ons and other purchase details shown for the order.
  11. Review the order summary, discounts, total amount, and payment method.
  12. For a payment-ready order, complete payment only when the migration path, service, plan, and total are correct.
  13. For a Custom Service request that requires scoping, submit the requirements and follow the Draft order process below.
  14. Wait for the order status to update before starting migration work or approved custom work.

A Custom Service request can create a Draft order while Next-Cart reviews the submitted requirements and files. The draft is not ready for payment until the scope and price are finalized.

  1. Submit the Custom Service requirements, examples, files, and acceptance criteria requested for assessment.
  2. Open the Draft order in Orders → Details.
  3. Respond to questions about the migration path, plan, additional work, expected result, or required access.
  4. Review the finalized service plan, additional work, and price.
  5. Wait for the order to move from Draft to Pending Payment.
  6. Select Pay only after the finalized order matches the agreed scope.
  7. Confirm that the order becomes Paid after payment and order processing are complete.

Open Migrations → My Migrations → Statistics, then select View Upgrade Options when the existing migration needs:

  • an upgrade from Standard to Managed or Custom, or from Managed to Custom;
  • a larger Entity Points Plan;
  • one or more additional Add-ons;
  • quoted tailored work, custom Add-ons, or other approved custom work.

Upgrade choices follow these limits:

ComponentAllowed upgradeNot allowed
Migration ServiceStandard to Managed or Custom; Managed to CustomService downgrade
Entity Points PlanA higher-capacity planPlan downgrade
Add-onsAdd capabilities to the existing migrationRemove a purchased Add-on for a lower value
Migration PathNoneChanging the Source Platform or Target Platform
Service DurationNoneRestarting or extending the one-year period through an upgrade

The upgrade is attached automatically to the existing migration after payment is completed.

Checkout applies the amount already paid for the migration and charges only the difference:

Checkout valueMeaning
New ValueThe total value of the migration after the selected upgrade.
Previously PaidThe amount already paid for the migration.
TotalThe additional upgrade price due for the current order.

The same top-up rule applies when Next-Cart provides an accepted quote for tailored work, a custom Add-on, or other approved custom work. Confirm that Previously Paid is applied and that Total represents only the additional amount before placing the Upgrade order.

An Extend order restores the purchase path for an expired migration while retaining its latest recorded package. Review the complete retained value before payment because the extension includes the base migration and the upgrades that remain attached to it.

An extension can also include eligible upgrades, such as:

  • moving from Standard to Managed or Custom, or from Managed to Custom;
  • selecting a higher Entity Points Plan;
  • purchasing additional Add-ons;
  • adding approved custom work.

Before paying for an extension, confirm:

CheckPass condition
MigrationThe Extend order belongs to the intended expired migration and fixed migration path.
Retained packageThe Service, Entity Points Plan, Add-ons, and approved custom work match the latest recorded migration state.
Extension valueThe total includes the base migration and the upgrades retained for the extended service.
New upgradesAny additional upgrade selected during extension is intentional and priced in the order.
Order TypeExtend appears in Order Details.

After payment and order processing, return to My Migrations and confirm that the same migration reflects the extended service state.

  1. Open Account → Orders and identify the pending order.
  2. Select Pay.
  3. Confirm the migration path, service, Entity Points Plan, Add-ons, and total.
  4. Complete payment.
  5. Return to Orders and review the resulting status.
  6. If Status is Pending Approval, do not pay again. Wait for payment confirmation or contact Support with the payment reference if the status does not resolve.
  7. Confirm that Status becomes Paid when order processing is complete.
  8. Open Migrations → My Migrations and confirm that the new, upgraded, or extended migration state appears.
CheckPass condition
Migration PathSource Platform and Target Platform match the intended project.
ServiceStandard, Managed, or Custom matches the required handling.
Data estimatesEntered counted volumes are realistic for the source store.
Entity Points PlanThe automatically selected or manually chosen plan covers the calculated Entity Points.
Add-onsRequired Add-ons are included.
Custom Service requirementsRules, examples, expected results, and pass conditions are complete where applicable.
Customer informationContact, company, address, and tax details are accurate.
PaymentMethod, discounts, and total amount are correct.

After successful Checkout and order processing:

  • the order appears in Orders;
  • the order has an Order #;
  • the purchased migration path and service are recorded;
  • the selected Entity Points Plan and Add-ons are associated with the purchase;
  • a New purchase appears under Migrations → My Migrations, an Upgrade is integrated into the existing migration, or an Extend order restores the applicable expired migration state;
  • the one-year duration is anchored to the initial purchase and is not changed by later upgrades;
  • the service can be started when its Status is Active.
CheckPass condition
OrderThe purchase appears in Orders with the expected migration path, service, amount, and status.
PaymentStatus is Paid. An Upgrade order charges only the additional amount, and an Extend order includes the intended retained package.
My MigrationsThe purchased migration service appears under Migrations → My Migrations.
Service informationMigration Path, Service, Entity Points, Add-ons, and Created / Expires match the completed purchase, upgrade, or extension.
StatusThe purchased migration service is Active before Start is used.
IssueWhat to do
The migration path is wrongDo not complete payment. Correct the Source Platform or Target Platform.
The plan appears too smallRecheck the counted data estimates and select sufficient Entity Points capacity.
A required Add-on is missingAdd it before the initial purchase or use View Upgrade Options for an existing migration.
Custom Service requirements are incompleteAdd field names, source locations, examples, expected output, and validation criteria.
Payment failsReview the order and payment-provider result. Retry through the available order action only when no charge or transfer was completed. If the account was charged or a transfer was sent, preserve the reference and contact Support before paying again.
Payment remains Pending ApprovalDo not pay again. Preserve the payment reference and contact Support if confirmation does not complete within the expected processing time.
The order appears but My Migrations does notConfirm payment and processing status, then submit a ticket with the Order #.
Previously Paid is missing or incorrectDo not place the Upgrade order. Confirm that you opened View Upgrade Options from the intended migration and submit a ticket if the amount remains incorrect.
A paid upgrade is not integratedOpen the Upgrade order in Orders, preserve the Order # and payment details, then submit a ticket.
An extension total does not include the expected retained packageDo not pay. Compare the Service, Plan, Add-ons, and approved custom work with the latest migration state, then submit a ticket.
A paid extension is not reflected in My MigrationsOpen the Extend order in Orders, preserve the Order # and payment details, then submit a ticket.
The purchased service appears but Start is unavailableCheck Status and Expires. Expired or Suspended services cannot be started.

Open Orders to verify the purchase, then open Migrations and select My Migrations when the purchased migration service is ready.