3-year cost calculator
Pre-filled for VMware vSphere → XCP-ng. Adjust every figure with your own numbers.
Every figure here is an illustrative estimate, not a vendor quote. Defaults are editable starting points compiled from public information; real, binding pricing comes from the vendor or an authorized distributor. See our methodology.
How this is licensed: vSphere licenses the physical CPU cores of each host (16-core minimum per CPU), not VMs. Count total physical cores across hosts and set $/core to your subscription tier.
All figures are illustrative and fully editable — adjust the cost-per-core and migration inputs with your own numbers. Not guaranteed vendor pricing (defaults reviewed May 2026). For a binding quote, use the request form below to reach an authorized distributor or partner.
Quick comparison: VMware vSphere vs XCP-ng
Common trade-offs teams weigh when staying on VMware vSphere versus moving to XCP-ng. These are general, commonly-reported considerations — not statements of fact about any vendor — so check them against your own contract and the vendors' current terms.
- Already in production — no migration effort or risk
- Mature ecosystem with vendor support and SLAs
- Perpetual licenses eliminated — subscription-only renewals
- 160+ products collapsed into a few costly bundles
- Per-core pricing with 16-core-per-CPU minimums
- Widely reported 3–10× cost increases on renewal
- Ongoing per-core subscription cost to budget for
- Higher vendor lock-in to weigh
- Open source — no license fees
- No vendor lock-in
- Cost model: Optional support / host
- Requires a migration (~18 weeks, high effort)
- Community support by default — paid support optional
- Higher operational learning curve
Why teams evaluate alternatives to VMware vSphere
Reasons commonly cited by users and in public industry coverage for re-evaluating VMware vSphere. These are general, reported considerations — not statements of fact about Broadcom — and may not reflect your situation or the vendor's current terms. Verify against your own contract before deciding.
- Perpetual licenses eliminated — subscription-only renewals
- 160+ products collapsed into a few costly bundles
- Per-core pricing with 16-core-per-CPU minimums
- Widely reported 3–10× cost increases on renewal
The migration plan
Roughly 18 weeks for a mid-size estate, in six phases.
Tooling & automation
Xen Orchestra's VMware import (V2V); install the management agent; map datastores to storage repositories.
OffVendor's wizard pre-fills these scripts with your environment — inventory export, disk/schema conversion, bulk provisioning, and validation.
Frequently asked
Is migrating from VMware vSphere to XCP-ng worth it?
For most teams facing rising VMware vSphere costs, yes — XCP-ng (optional support / host) typically lowers 3-year total cost of ownership, though the right answer depends on workload complexity and in-house skills. Use the calculator to model your own numbers.
How long does a VMware vSphere to XCP-ng migration take?
A typical mid-size estimate is around 18 weeks across six phases — discovery, design, pilot, waved production migration, validation, and decommission. Larger or more complex estates take longer.
What tools are used to migrate from VMware vSphere to XCP-ng?
Xen Orchestra's VMware import (V2V); install the management agent; map datastores to storage repositories.