3-year cost calculator
Pre-filled for XCP-ng → XenServer (Citrix Hypervisor). 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: XCP-ng vs XenServer (Citrix Hypervisor)
Common trade-offs teams weigh when staying on XCP-ng versus moving to XenServer (Citrix Hypervisor). 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
- Established and already integrated in your stack
- Re-evaluating cost, support, or strategic fit
- Commercial option with vendor support and SLAs
- Cost model: Per-socket subscription
- Requires a migration (~12 weeks, low effort)
- Per-socket subscription cost
Why teams evaluate alternatives to XCP-ng
Reasons commonly cited by users and in public industry coverage for re-evaluating XCP-ng. These are general, reported considerations — not statements of fact about Vates — and may not reflect your situation or the vendor's current terms. Verify against your own contract before deciding.
- Re-evaluating cost, support terms, or strategic fit.
The migration plan
Roughly 12 weeks for a mid-size estate, in six phases.
Tooling & automation
Standard V2V conversion plus network and storage re-mapping; validate workloads in a pilot wave.
OffVendor's wizard pre-fills these scripts with your environment — inventory export, disk/schema conversion, bulk provisioning, and validation.
Frequently asked
Is migrating from XCP-ng to XenServer (Citrix Hypervisor) worth it?
For most teams facing rising XCP-ng costs, yes — XenServer (Citrix Hypervisor) (per-socket subscription) 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 XCP-ng to XenServer (Citrix Hypervisor) migration take?
A typical mid-size estimate is around 12 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 XCP-ng to XenServer (Citrix Hypervisor)?
Standard V2V conversion plus network and storage re-mapping; validate workloads in a pilot wave.