Purchase a Migration Upgrade

Purchase a Migration Upgrade

Use the existing migration’s Upgrade path when the project needs more capacity, a higher Service tier, or additional supported Add-ons. The Upgrade remains attached to the same migration and fixed Source Platform to Target Platform path.

An Upgrade is upward-only and does not extend the active service period. Checkout calculates the difference between the resulting project value and the amount already paid for the effective package.

Before you start

Confirm the intended migration and the specific change required.

Check	What to confirm
Migration project	The Source Platform, Target Platform, and migration project are the ones you intend to upgrade. The migration path cannot be changed through an Upgrade.
Active package	Review the active Service, Entity Points Plan, Add-ons, and relevant custom scope in Statistics before changing anything.
Upgrade direction	Service upgrades move upward only: Standard Migration → Managed Migration, Standard Migration → Custom Migration, or Managed Migration → Custom Migration. Entity Points Plans can increase but cannot be downgraded.
Add-ons	Identify only the Add-ons required by the project and available for the selected migration path.
Custom requirements	If the upgrade introduces non-standard technical work, define the requirement and obtain the applicable approved scope before treating the Custom upgrade as ready for payment.

Use Prepare Custom Migration Requirements when the project is moving to Custom Migration because of bespoke data, logic, platform handling, schema work, or another non-standard requirement.

Later migration activity after a paid Migration has run is handled through Continue the Migration with Last Saved Configuration or Continue the Migration with a New Configuration on that same purchased Migration. It does not require a separate synchronization subscription. If the active Migration needs a higher Service tier, more Entity Points capacity, or additional Add-ons, use this Upgrade workflow. Service and Entity Points Plan downgrades are not supported through an Upgrade.

Step 1: Open the Upgrade in Checkout

Follow this sequence from the project you intend to change.

1. Expand Migrations, then select My Migrations and locate the project.

   

2. Select Statistics for that migration.

   

3. In the Overview, confirm the migration path and active package, then select View Upgrade Options.

   

4. Confirm that Checkout opens with the existing migration’s specifications already loaded.

   

If the migration path, Service, Plan, or project identity in Checkout does not match the migration you intended to change, stop before payment and reopen the Upgrade from the correct project.

Step 2: Configure only the required changes

Leaving a control unchanged keeps that part of the active package as the Upgrade baseline.

Upgrade the Service tier

Select a higher Service tier only when the required operating responsibility or technical scope has changed. Supported upward moves are Standard Migration → Managed Migration, Standard Migration → Custom Migration, and Managed Migration → Custom Migration. A Service downgrade is not supported.

Moving to Custom Migration is a scope change, not only a label change. When non-standard work is required, keep the approved Custom requirements aligned with the Upgrade.

Upgrade the Entity Points Plan

Increase the estimated Data Volume to reflect the project requirement. Checkout recalculates Entity Points and automatically selects the closest plan whose capacity can accommodate the increased volume.

If the increased volume still fits within the allowance of the active plan, the plan does not change automatically. To reserve a higher plan intentionally, go to the Payment section and select Change next to the Plan line, then choose the higher plan required for the project.

The upgrade uses differential billing. Checkout calculates the resulting project value, credits the amount already paid for the effective package, and charges the remaining Total. Do not manually calculate a price difference and purchase a separate customization product only to raise Entity Points capacity. Start from Statistics → View Upgrade Options so the change remains attached to the correct migration.

Data Volume sizes capacity; it does not filter records

Increasing Products, Customers, Orders, or Blog Posts estimates changes the capacity calculation. It does not select or exclude individual records. Use Select Data for data-type scope and Data Filter for supported record-level conditions.

Confirm the updated Data Volume

When additional capacity is required, verify the Products, Customers, Orders, and Blog Posts estimates used for the Entity Points calculation.

Add Add-ons

Enable only the Add-ons required by the migration and available for the active Source-to-Target path. The Add-on becomes part of this same migration after the Upgrade Order is successfully Paid and applied.

Use Add-ons for processing order and configuration guidance.

Step 3: Review payment and place the Upgrade Order

Review the Payment section before selecting a method. The migration path must still identify the intended project, the Service and Plan must reflect the intended upward change, and every new Add-on must be deliberate.

The billing summary shows New Project Value, Previously Paid, and Total. Total is the additional amount due for the Upgrade.

If you intentionally need a higher Entity Points Plan even though the entered Data Volume still fits the active Plan, use Change next to Plan and select the higher Plan.

1. Confirm the final migration, Service, Plan, Add-ons, New Project Value, Previously Paid, and Total.

   

2. Select an available payment method.

   

3. Select Place Order only after the resulting package and differential Total are correct.

   

4. Complete the selected payment workflow. Use Payment Methods and Verification for method-specific settlement instructions.

5. Treat the Upgrade as effective only after the resulting Order reaches Paid.

Step 4: Verify the Upgrade Order

1. Open Orders and locate the Upgrade transaction for the migration.

   

2. Open the Order Details and confirm the Order type, configuration, payment summary, and status.

3. Confirm that the Upgrade reaches Paid before treating the proposed changes as effective.

   

Use Orders for detailed transaction-state, invoice, refund, failed-Upgrade, and differential-billing guidance.

The Paid Upgrade Order includes a View Migration link to its project.

Step 5: Verify the active migration package

Return to Migrations → My Migrations → Statistics after the Upgrade is Paid. Confirm that the active Service, Entity Points capacity, and purchased Add-ons reflect the successful Upgrade while the migration path and service expiration remain unchanged.

Order Details proves what was purchased. Statistics proves what is active now. If those views disagree after a Paid Upgrade, preserve the Order # and project evidence before contacting Support.

Failure handling

Issue	What to do
Checkout opens the wrong migration or package	Stop before payment. Return to My Migrations, open the intended project, and restart from Statistics → View Upgrade Options.
Increased Data Volume does not change the Plan	Confirm whether the calculated Entity Points still fit the active Plan. If you intentionally need a higher Plan, use Change next to Plan in Payment.
A lower Service or Plan is required	Downgrades are not supported through an Upgrade. Review whether a separate New migration purchase is required.
Upgrade Total is unexpected	Do not pay. Recheck the selected changes, New Project Value, Previously Paid, and Total.
A Custom Upgrade requires undefined work	Prepare the Custom requirements and complete the applicable scope-review process before relying on the package.
The Upgrade is Paid but the migration still shows the previous package	Verify the Paid Order in Orders, compare Linked Orders and Statistics, preserve the Order # and project evidence, then submit a Support Ticket.
The Upgrade is Failed or unpaid	The proposed changes do not become the active package. Review the recorded Order state before another payment attempt.

Next Steps

Use Migrations to continue operating the upgraded project, Orders for transaction evidence, and Payment Methods and Verification for method-specific settlement guidance.