Purchase a Migration Upgrade

Purchase a Migration Upgrade

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

An Upgrade is an upward change to the active package. It does not create a new migration path, reduce previously purchased capacity or capabilities, or extend the active service period. Upgrade pricing uses the difference between the recalculated project value and the amount already paid for the effective package.

Open the upgrade from the migration you intend to change

Start from My Migrations → Statistics for the existing project. This keeps Checkout tied to the correct migration and preloads the active package before you select any upgrade.

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 → Managed, Standard → Custom, or Managed → Custom. 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 Service Requirements when the project is moving to Custom Service because of bespoke data, logic, platform handling, schema work, or another non-standard requirement.

Open the upgrade in Checkout

1. In the Dashboard sidebar, expand Migrations, then select My Migrations.
2. Find the migration project you want to upgrade.
3. Select Statistics to open the migration Overview.
4. Review the active project information, then select View Upgrade Option.
5. Confirm that Checkout opens with the existing migration’s active specifications already loaded.

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

Configure the upgrade

Use only the controls required by the project. Leaving an area unchanged keeps that part of the active package as the upgrade baseline.

Upgrade the Service tier

Select a higher Service tier when the operating responsibility or technical scope has changed. Supported upward moves are:

• Standard → Managed;
• Standard → Custom;
• Managed → Custom.

A Service downgrade is not supported. Moving to Custom Service is a scope change, not only a label change. When non-standard technical work is required, the approved Custom requirements remain part of the upgrade decision.

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.

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.

Add Add-ons

Enable the Add-ons required by the migration and available for the active Source-to-Target path. Adding an Add-on through an Upgrade makes it part of the same migration after the Upgrade order is successfully paid and applied.

Use Add-ons to understand the fixed processing sequence and open the dedicated configuration guide for each purchased Add-on.

Review the Payment section

Before selecting a payment method, review the complete upgraded package and differential price.

Payment check	What to verify
Migration	The Upgrade still applies to the intended existing migration and fixed migration path.
Service	The selected Service tier is the intended upward change.
Plan	The Entity Points Plan provides the intended capacity. Use Change next to Plan when a higher plan is required even though the entered Data Volume still fits the active plan.
Add-ons	Every newly enabled Add-on is intentional and applicable to the migration.
New Project Value	The recalculated value reflects the resulting package after the selected changes.
Previously Paid	The credited amount reflects the value already paid toward the effective package.
Total	The additional amount due matches the intended Upgrade.

If the displayed package or differential amount is not what you expected, do not complete payment. Recheck the selected changes and the active migration before proceeding.

Complete checkout

1. Confirm the upgraded package and Payment summary.
2. Select the preferred available payment method.
3. Complete the standard payment workflow for that method.
4. Treat the Upgrade as settled only after the resulting order reaches Paid.

Use Payment Methods and Verification for PayPal, card, cryptocurrency, Bank Transfer, and Payoneer payment and verification rules.

Verify the upgrade after purchase

Check both the transaction record and the live migration. They answer different questions.

Verify the Upgrade order

1. Open Orders.
2. Locate the Upgrade transaction for the migration.
3. Confirm the Order type, status, invoice details, upgraded configuration, and differential price.
4. Treat the purchase as effective only when the order is Paid.

Use Orders for Upgrade Order Details, differential billing, failed Upgrade behavior, refunds, and the difference between transaction history and the live migration state.

Verify the active migration package

1. Expand Migrations, then select My Migrations.
2. Open the upgraded migration and select Statistics.
3. Confirm that the active Service, Entity Points Plan or capacity, and purchased Add-ons reflect the successful Upgrade.
4. Confirm that the migration path and service expiration remain correct. An Upgrade does not renew the active service period.

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 start again from Statistics → View Upgrade Option.
Increased Data Volume does not change the Plan	Confirm whether the recalculated Entity Points still fit the active plan. If you intentionally need a higher plan, use Change next to Plan in the Payment section.
A lower Service or Plan is required	Downgrades are not supported through an Upgrade. Review whether a separate New migration is required for the changed purchase structure.
Upgrade Total is unexpected	Do not pay. Compare the selected changes, New Project Value, Previously Paid, and Total.
A Custom upgrade requires work that is not yet defined	Prepare the Custom requirements and use the applicable scope-review process before relying on the proposed package.
The Upgrade order is Paid but the migration still shows the previous package	Verify the Paid transaction in Orders, review Linked Orders in Statistics, preserve the Order # and project evidence, then submit a Support ticket.
The Upgrade order is Failed or unpaid	The proposed changes do not become the active package. Review the recorded order state before creating another payment attempt.

Next Steps

• Use Orders to review the Upgrade transaction, delta billing, and effective migration state.
• Use Payment Methods and Verification for the selected payment workflow and settlement rules.
• Use Entity Points, Plans, and Service Pricing when the upgrade is driven by capacity or Service pricing.
• Use Migrations to continue operating the upgraded project from My Migrations.
• Use Prepare Custom Service Requirements when an upgrade introduces non-standard technical scope.