A displayed price for a Next-Cart Migration Service is meaningful only when the capacity and included work behind it are understood. The same Entity Points Plan can carry different Standard and Managed prices because execution responsibility differs. Custom Service can show the same starting amount as Standard Service while producing a different final total because tailored work is quoted separately.
Next-Cart migration pricing therefore has four layers:
- counted capacity through the Entity Points Plan;
- execution responsibility through the Migration Service;
- purchased Add-ons for bounded supported requirements;
- agreed custom work for tailored or non-standard requirements.
Keeping those layers separate prevents a low starting amount from being mistaken for a complete custom quote, and it prevents Store size from being used as a shortcut for service fit.
Establish Capacity Before Comparing Prices
An Entity Points Plan provides counted capacity for Product, Customer, Order, and Blog Posts under the purchased migration path. During purchase, the closest plan that supports the entered Entity Points requirement is selected automatically. A different sufficient plan can be chosen before purchase when more headroom is appropriate.
| Counted data type | Weight |
|---|---|
| Product | 1.0 |
| Order | 0.8 |
| Blog Posts | 0.6 |
| Customer | 0.5 |
The estimate should reflect realistic source quantities and expected growth before migration completion. Entered quantities support pricing and plan selection. They do not limit the migration to that number of records.
For example, a 480-point estimate fits within both Basic and Basic+:
| Plan | Capacity | Headroom after a 480-point estimate |
|---|---|---|
| Basic | 500 | 20 |
| Basic+ | 1,000 | 520 |
Basic is sufficient if the estimate is reliable and little additional Source Store activity is expected. Basic+ provides more room for incomplete inventory or later eligible records. The larger plan does not improve compatibility or remove a custom requirement; it changes counted capacity only.
The full calculation, consumption sequence, and later-record rules are explained in Entity Points.
Read the Pricing Table Through Its Four Layers
The plan table combines capacity with Standard, Managed, and Custom Service pricing:
| Plan | Entity Points | Standard Service | Managed Service | Custom Service |
|---|---|---|---|---|
| Basic | Up to 500 | $39.00 | $89.00 | Start from $39.00 |
| Basic+ | Up to 1,000 | $59.00 | $109.00 | Start from $59.00 |
| Growth | Up to 2,000 | $89.00 | $139.00 | Start from $89.00 |
| Growth+ | Up to 4,000 | $119.00 | $169.00 | Start from $119.00 |
| Pro | Up to 8,000 | $149.00 | $249.00 | Start from $149.00 |
| Pro+ | Up to 16,000 | $199.00 | $299.00 | Start from $199.00 |
| Business | Up to 32,000 | $269.00 | $369.00 | Start from $269.00 |
| Business+ | Up to 64,000 | $349.00 | $449.00 | Start from $349.00 |
| Enterprise | Up to 128,000 | $449.00 | $599.00 | Start from $449.00 |
| Enterprise+ | Up to 256,000 | $569.00 | $719.00 | Start from $569.00 |
| Global | Up to 512,000 | $699.00 | $849.00 | Start from $699.00 |
| Global+ | Up to 1,024,000 | $949.00 | $1,099.00 | Start from $949.00 |
The Standard and Managed columns are fixed prices for the selected capacity and responsibility position. The Custom column is different: it shows the Standard Service price floor for the selected plan, not a fixed final project price.
That distinction is the most important interpretation in the table. The Custom starting amount establishes counted capacity. It does not yet price the tailored requirement.
Some migration paths do not offer a choice among all three Services. When CSV, XLS, or XML is selected as the Source Platform, Custom Service is required. A migration to a Target Platform outside the supported Target Platform list is also handled through Custom Service. Entity Points still determine the required capacity Plan, but only the Custom Service starting price is applicable before the tailored scope is assessed and quoted.
Standard Service Pricing Combines Capacity and Add-ons
Standard Service follows a customer-led execution approach within supported scope.
Standard Service total
= selected Standard Service plan price
+ purchased Add-ons, if applicable
Assume the estimated requirement is 1,700 Entity Points. Growth supports up to 2,000 points and carries a Standard Service price of $89.00.
Growth Standard Service price = $89.00
If no Add-ons are needed, the service price is $89.00. Purchased Add-ons are added separately.
The plan can support small or large projects. Service fit still depends on whether the path and requirements remain supported and whether the customer can coordinate execution and validation.
Managed Service Pricing Includes Expert-Led Execution
Managed Service applies within supported scope when expert-led execution of the agreed migration actions is required.
Managed Service total
= selected Managed Service plan price
+ purchased Add-ons, if applicable
Assume the estimated requirement is 3,500 Entity Points. Growth+ supports up to 4,000 points and carries a Managed Service price of $169.00.
Growth+ Managed Service price = $169.00
Purchased Add-ons are added where applicable.
The price difference from Standard Service reflects execution responsibility. It does not expand supported migration behavior into bespoke transformation, Custom Platform handling, or unsupported application data. Those requirements belong in Custom Service.
Customer validation remains required. Expert-led execution changes who performs the actions, not who can approve the commercial and operational outcome.
Custom Service Pricing Starts With Capacity
Custom Service uses the Standard Service price for the selected Entity Points Plan as its starting floor.
Custom Service final price
= Standard Service price floor for the selected plan
+ agreed customization-work quote
+ purchased Add-ons, if applicable
+ Expert Handle, when included
+ other agreed scope-specific costs, if applicable
Unlike Standard and Managed Service, Custom Service does not turn the starting amount into a final price simply because a capacity plan has been selected. Standard and Managed plan prices are fixed, so the service subtotal can be determined once capacity and applicable Add-ons are known, while Custom Service follows scope definition and an itemized quote before payment. Taxes, discounts, or other order-specific adjustments can still affect the final amount due. Each quoted custom item should correspond to an understood functional requirement, intended target result, and acceptance basis, so the price remains traceable to the work it represents.
Execution responsibility is also explicit. Self-Execute keeps migration execution with the customer after the approved custom work is ready. Expert Handle includes expert-led execution and contributes its agreed engineering cost to the final quote.
Tailored work may involve custom fields, application-owned records, Custom Platform analysis, bespoke transformation, external identifiers, non-standard relationships, Tailored Add-ons, or Custom Add-ons.
Two projects can use the same Entity Points Plan and receive different Custom Service totals because capacity is only one layer. The required analysis, transformation, validation evidence, and execution responsibility may differ substantially.
Custom Service pricing example
Assume a project selects Pro, whose Standard Service price floor is $149.00. The accepted scope includes $300.00 for bespoke Product-data transformation and $50.00 in purchased Add-ons.
$149.00 plan price floor
+ $300.00 customization-work quote
+ $50.00 purchased Add-ons
= $499.00 illustrative final price
The example demonstrates the pricing method. The custom quote and Add-on total depend on the accepted project requirements.
Add-ons Add Focused Capability, Not General Custom Scope
The Standard Add-ons are:
- Data Filter;
- Data Transformation;
- Advanced Data Mapping;
- Advanced Database Mapping.
A Standard Add-on uses its published price and may accompany Standard, Managed, or Custom Service when the available behavior fits the requirement.
If an available Add-on needs modification, it becomes a Tailored Add-on under Custom Service. If a Standard Add-on was already purchased, the accepted Tailored Add-on quote contributes only the additional difference needed for the new migration value. If no Standard Add-on fits, a Custom Add-on may be reviewed and quoted under the same difference-only upgrade principle.
This boundary prevents two pricing errors:
- assuming every Add-on requires a full custom project;
- assuming a fixed Add-on price covers unsupported data or bespoke logic.
Add-ons explains how to classify the requirement before applying its cost.
Capacity Above Global+
Global+ supports up to 1,024,000 Entity Points. Beyond that capacity, each additional 100,000 Entity Points costs $50.00 for Standard Service and Managed Service.
| Service | Additional capacity |
|---|---|
| Standard Service | $50.00 per additional 100,000 Entity Points |
| Managed Service | $50.00 per additional 100,000 Entity Points |
| Custom Service | Start from $50.00 per additional 100,000 Entity Points, plus the agreed custom scope |
Assume the requirement is 1,100,000 Entity Points. The project exceeds Global+ by 76,000 points, so one additional 100,000-point block is required.
| Service | Calculation | Price before Add-ons or custom work |
|---|---|---|
| Standard Service | $949.00 + $50.00 | $999.00 |
| Managed Service | $1,099.00 + $50.00 | $1,149.00 |
| Custom Service | Start from $949.00 + $50.00 | Start from $999.00 |
For Custom Service, the added $50.00 establishes the extra capacity floor. Tailored work remains part of the final quote.
Upgrades Change the Same Purchased Migration
After purchase, an Entity Points Plan can move only to a higher capacity. It cannot be downgraded. A Migration Service follows a similar one-way rule: Standard can move to Managed or Custom, and Managed can move to Custom. Managed cannot move to Standard, and Custom cannot be downgraded.
Add-ons and accepted custom work can also be added later. Once purchased, the added capability becomes part of the same migration rather than a separate migration path.
Upgrade pricing uses a top-up calculation:
Upgrade amount
= total migration value after the upgrade
- amount previously paid toward the migration
The customer therefore pays the difference, not the full package price again. This principle applies to a higher Entity Points Plan, an upward Migration Service change, added Add-ons, and accepted Tailored Add-on, Custom Add-on, or other custom-work quotes.
For a Standard Service upgrade from Basic+ to Growth:
Growth Standard Service price: $89.00
Basic+ Standard Service price: $59.00
Upgrade difference: $30.00
That example changes counted capacity only. Other upgrade combinations use the same difference-only principle against the resulting migration value.
An upgrade does not:
- create a new migration path;
- change the expiration of the active 12-month access period;
- change record selection into a filter;
- include components that were not selected or accepted as part of the upgrade.
The expiration of the active access period remains unchanged even when several upgrades are purchased later. New or changed custom work should be reviewed and accepted separately rather than assumed to be included because an earlier custom quote existed.
Extension Renews the Retained Migration Package
An expired migration can be extended. Extension is not an ordinary component upgrade. Successful payment for an extension starts a new 12-month access period measured from the extension settlement time.
Extension pricing is based on the latest retained migration package. That package includes the base migration and the applicable plan, Migration Service, Add-ons, and accepted custom work integrated during the previous access period. A permitted upward plan, service, Add-on, or custom-scope change may also be included in the resulting extension package.
This distinction protects two decisions:
- an upgrade changes one or more components without changing the current expiration;
- an extension renews the retained migration package and starts a new 12-month access period from successful extension settlement.
Build the Estimate in the Right Order
A reliable pricing estimate follows this order:
- calculate realistic Entity Points;
- choose enough capacity and headroom;
- determine whether scope is supported or custom;
- assign execution responsibility, including Self-Execute or Expert Handle when Custom Service applies;
- identify Standard, Tailored, or Custom Add-ons;
- include any additional capacity;
- confirm the complete accepted custom scope and itemized quote;
- distinguish an active-migration upgrade from an expired-migration extension.
Reversing the order encourages price anchoring. A lower displayed amount can look attractive even when the project still needs different execution responsibility or tailored handling.
The final estimate should make each layer visible. That transparency makes later plan changes easier to understand and prevents the Custom starting floor from being mistaken for the final amount.
Conclusion
Pricing across Next-Cart Migration Services begins with counted capacity, but capacity is only the first layer. Standard Service combines the selected plan price with purchased Add-ons. Managed Service combines the Managed plan price with purchased Add-ons and includes expert-led execution within supported scope. Custom Service starts from the Standard plan price floor and adds the agreed tailored work, Add-ons where applicable, Expert Handle when included, and other accepted scope-specific costs.
Estimate Entity Points first, then decide scope and responsibility. After purchase, allowed upgrades are integrated into the same migration and charged as the difference between the resulting migration value and the amount already paid. They never change the fixed path or the expiration of the active access period. Extension is the separate renewal that carries forward the retained migration package and starts a new 12-month access period from successful extension settlement.
Common Questions
Why is Managed Service priced differently?
Managed Service includes expert-led execution of the agreed migration actions within supported scope.
Why does Custom Service show a starting price?
The amount is the Standard Service capacity floor for the selected plan. The non-standard requirements are assessed and itemized before the final custom price is established. The final total then adds the agreed custom work, Add-ons where applicable, Expert Handle when included, and other accepted scope-specific costs.
What happens above 1,024,000 Entity Points?
Each additional 100,000 points costs $50.00 for Standard and Managed Service. Custom Service starts from the same additional capacity amount and adds the agreed custom scope.
Can an Entity Points Plan be downgraded after purchase?
No. A purchased Entity Points Plan can be upgraded to a higher capacity, but it cannot be downgraded.
Is the full plan price charged again during an upgrade?
No. The applicable charge is the difference between the existing and higher plan for the selected Migration Service.
Which Migration Service changes are allowed?
Standard can be upgraded to Managed or Custom, and Managed can be upgraded to Custom. Migration Services cannot be downgraded.
Does an upgrade extend the access period?
No. An upgrade does not change the current expiration. Extending an expired migration is a separate purchase, and successful extension settlement starts a new 12-month access period.
What does an extension carry forward?
An extension uses the latest retained migration package, including applicable components integrated through earlier upgrades. Permitted upward changes may also be included with the extension. Successful settlement then establishes a new 12-month access period for the resulting package.
Is the website migration service billed as a monthly subscription?
The website migration purchase establishes an active 12-month access period for the retained migration package; it is not described by this pricing model as a month-by-month subscription. Upgrades remain part of the same migration and do not change its expiration. An extension is the separate purchase that renews an expired migration and starts a new 12-month access period from successful extension settlement.
Does the Shopify Migration App use the same pricing as the website migration service?
No. The Shopify Migration App and the website migration service have separate purchase scopes and pricing. Website pricing follows the Entity Points Plan, Migration Service, Add-on, and accepted custom-scope model described here. App pricing should be read from the active Shopify Migration App purchase flow rather than inferred from the website pricing table.
Is there a separate website price for migrating only Products?
The website pricing model is not a separate price list for each selected data type. Capacity is sized through Entity Points, then the applicable Migration Service, Add-ons, and accepted custom work determine the resulting package price. Selecting a narrower scope can change the required capacity or work, but it does not create an independent Product-only pricing table.