Contents
Key takeawaysIs Hyper-V cheaper?How each platform licenses a hostFeature parity in 2026Migration cost and paybackWhen each platform winsWhat we have seen since BroadcomUsing the evaluation at renewalWhat to do nextFAQBefore Software Assurance, Hyper-V plus System Center undercuts VMware Cloud Foundation on licenses, and vSphere Foundation undercuts both. Once conversion, storage, network and retraining costs are added, most organizations save more by renegotiating the VMware renewal than by switching.
- License lines favor Hyper-V against VCF. On 1,000 cores over three years, negotiated Hyper-V plus System Center comes to about $490,000 before Software Assurance, against $630,000 for VCF.
- VVF costs less than both. If your clusters need vSphere without the full private cloud stack, VVF comes to $240,000 negotiated over the same three years.
- The migration is the largest line. Six project components, led by storage and program management, outweigh any three year license saving in the 1,000 core model.
- Renewal pressure is real. VMware subscription costs rose 2 to 3 times at renewal under VCF only packaging, which is what starts most Hyper-V evaluations.
- Renegotiation beat switching. Across 35 to 50 VMware environments we benchmarked in 2024 and 2025, most cut more by renegotiating the renewal than by changing hypervisor.
- Split by tier. Windows dense clusters can move to Datacenter licensing you already own, while mixed workloads stay on a smaller, renegotiated VMware footprint.
Is Hyper-V cheaper than VMware once the migration is priced?
On license lines alone, Hyper-V usually costs less than VMware Cloud Foundation (VCF), and VMware vSphere Foundation (VVF) often costs less than both. Once you add the migration, the answer reverses for most organizations, because the project costs more than the license saving and never appears in a sticker comparison.
The table below prices 1,000 cores over three years. VCF lists around $350 per core per year and VVF around $135, with enterprise discounts landing 20 to 45 percent off list.
| Scenario | VMware VCF | VMware VVF | Hyper-V plus System Center |
|---|---|---|---|
| List price, three years | $1.05 million | $405,000 | $610,000 |
| Negotiated, three years | $630,000 | $240,000 | $490,000 |
| Migration cost | $0 | $0 | $800,000 to $2.5 million |
| Operational shift | Steady state | Steady state | Retraining, plus 15 to 25 percent operating uplift in year one |
What the Hyper-V column actually buys
The $610,000 figure is the perpetual license price for 1,000 cores of Windows Server Datacenter and System Center Datacenter at the 2022 list prices. That is 62.5 sixteen core packs at $6,155 plus $3,607 each, or $610,125. The 2025 editions list at $6,771 and $3,968 per 16 cores, which lifts the same purchase to about $671,000.
- Software Assurance. Windows Server Datacenter SA runs about $1,540 a year per 16 cores, 25 percent of the license price. At that same rate on both products, three years of SA on 1,000 cores adds roughly $458,000 at list, which takes the Hyper-V list total to about $1.07 million, level with VCF at list.
- Licenses you already pay for. Windows guests on vSphere hosts already need Windows Server licensing on those hosts. For a Windows dense cluster, the Datacenter cost exists on both sides of the comparison.
The VMware VCF Renewal: How to Prepare Before Broadcom Names the Price
How do VMware and Hyper-V license a host differently?
VMware now sells per core subscriptions only, in two main bundles, VCF and VVF, with a minimum of 16 cores per CPU. Hyper-V is a role inside Windows Server, so you license the host's cores through Windows Server and buy System Center separately for management. Hyper-V alone is therefore never the right comparison.
| Item | VMware under Broadcom | Hyper-V |
|---|---|---|
| Metric | Physical cores, annual subscription | Physical cores, perpetual licenses sold in 2 and 16 core packs, SA optional |
| Minimum | 16 cores per CPU | 8 cores per processor and 16 per server |
| Guest rights | None; Windows guests still need Windows Server licensing | Datacenter covers unlimited Windows VMs; Standard covers 2 per fully licensed host |
| Management | Aria management tools included in VCF | System Center Datacenter at about $3,607 per 16 cores (2022 list), licensed on the same core rules |
| List price | VCF about $350 and VVF about $135 per core per year | Windows Server Datacenter about $6,155 per 16 cores (2022 list) |
Windows Server client access licenses apply whichever hypervisor runs underneath, so they cancel out of the comparison. VMware subscription costs rose 2 to 3 times at renewal under the VCF only packaging, and individual renewals ran 50 to 200 percent higher. That increase is what starts nearly every Hyper-V evaluation we see.
Why the 16 core minimum rarely decides the comparison
Both vendors charge a 16 core floor, so a single socket server with 8 cores bills as 16 cores under VMware and under Windows Server. The rules part only on older dual socket hosts, where two 8 core CPUs bill as 32 cores under VMware's per CPU minimum and 16 under Microsoft's 8 per processor rule.
On hosts with 16 or more cores per socket the two rules produce the same count, so the minimum rarely changes which platform is cheaper. For the counting rules in detail, see our guide to VMware core licensing.
Should you price VVF before any migration case?
Yes. VVF lists at well under half the VCF price per core, a saving most organizations skip. Clusters that need vSphere but not the full private cloud stack have a cheaper VMware answer before any migration is discussed. Our VCF and VVF comparison lists what each bundle includes, and the VCF components guide breaks down the larger bundle.
Broadcom VMware negotiation guide
How to prepare the renewal, price a credible walkaway and split workloads across platforms.
Get the white paper →Does Hyper-V have feature parity with VMware in 2026?
For most enterprise workloads, yes. After the 2020 to 2024 release cycle, both platforms offer the capabilities a production cluster needs, and neither has a feature gap large enough to settle the decision in 2026. The choice therefore rests on cost, skills and what your workloads look like.
- On both platforms. Live migration, clustering with automatic failover, replication, storage virtualization, network virtualization and Kubernetes integration.
- Where VMware leads. Support for mixed guest operating systems, GPU passthrough at scale, and the depth of partner integrations for backup, security and monitoring.
- Where Hyper-V leads. Windows guest density under Datacenter licensing, and the hybrid bridge into Azure.
What changes for the operations team
Most of the change for operations is in tools and skills. vCenter gives way to System Center Virtual Machine Manager, vSphere skills give way to PowerShell and Windows Admin Center, and Broadcom support becomes Microsoft support. Microsoft's VM Conversion extension for Windows Admin Center, still in preview, replicates running VMs from vCenter to Hyper-V at no extra cost.
Two licensing checks belong in the evaluation as well. If Oracle Database runs in the cluster, read how Oracle treats Hyper-V before you move it. If Azure Local is on the table, Azure Hybrid Benefit waives its host fee core for core against Windows Server Datacenter licenses with active SA, which changes the value of the SA line above.
What does a VMware to Hyper-V migration cost?
A full migration costs $800,000 to $2.5 million on a typical environment and runs over six to eighteen months of project work. The right column below prices a hypothetical company with 1,000 cores, 700 VMs, vSAN storage and NSX used mainly for segmentation.
| Component | The work | Typical cost band | Example, 700 VMs |
|---|---|---|---|
| VM conversion | Assessment, conversion and validation per workload | $200 to $800 per VM | 700 at $400 = $280,000 |
| Storage refresh | vSAN to Storage Spaces Direct or a new SAN | $200,000 to $1.5 million | $600,000 |
| Network rework | NSX to Microsoft SDN or a third party product | $100,000 to $600,000 | $150,000 |
| Backup retooling | Update or replace the backup platform | $150,000 to $500,000 | $200,000 |
| Team retraining | vSphere administrators to Hyper-V and System Center | $50,000 to $200,000 | $100,000 |
| Program management | A six to eighteen month program | $300,000 to $1.5 million | $450,000 |
| Total | Depends on scope | $1,780,000 |
The year one operating uplift
Budget 15 to 25 percent more operating effort in the first year, on top of the project. Backup windows stretch, monitoring has blind spots, and runbooks written for vCenter stop matching reality. Most of it surfaces in the first six months after cutover.
How long does the saving take to cover the project?
In this 1,000 core model, the three year license saving never covers even the $800,000 low end of the migration band. The size of the saving depends on which VMware price you compare against, and the Hyper-V figures below exclude Software Assurance, so they flatter the switch.
| Compared against | VMware, three years | Hyper-V, three years | Saving from switching |
|---|---|---|---|
| VCF at list | $1.05 million | $490,000 negotiated | $560,000 |
| VCF negotiated | $630,000 | $490,000 negotiated | $140,000 |
| VCF negotiated, Windows Datacenter already owned | $630,000 | About $225,400, System Center only at list | About $404,600 |
| VVF negotiated | $240,000 | $490,000 negotiated | Minus $250,000 |
A switch pays only where the VMware quote sits well above these figures and the migration sits at the bottom of its band. Past year three the gap widens in Hyper-V's favor, because VMware bills a new subscription term while only SA recurs on the perpetual Microsoft licenses.
Use our VMware exit TCO calculator to run the same comparison with your own core counts and quotes.
When does VMware win, and when does Hyper-V win?
VMware wins where the workloads are mixed and the VMware stack runs deep. Hyper-V wins where the servers are mostly Windows and the team already runs the Microsoft stack. Most organizations land on a split.
Where staying on VMware makes sense
- Mixed Linux, Windows and legacy guests across the same clusters.
- NSX embedded in the security design, with microsegmentation rules you would have to rebuild.
- Tanzu Kubernetes running in production.
- Any case where the migration costs more than three years of repricing, which is the result most organizations reach late.
Where Hyper-V makes sense
Hyper-V fits Windows dense clusters, organizations with an Azure hybrid strategy, and teams already fluent in PowerShell and System Center. In those clusters, the Windows Server Datacenter licenses are often already owned, so the incremental Microsoft cost is System Center, SA and the project itself.
The split puts the Windows dense tier on the Datacenter licensing you already own and keeps the mixed core on a smaller, renegotiated VMware footprint. For the wider field of alternatives, see the Nutanix cost comparison and Proxmox against VMware. The Hyper-V licensing guide covers the Microsoft rules in detail.
What have we seen in VMware renewals since the Broadcom change?
Across roughly 35 to 50 VMware environments we benchmarked in 2024 and 2025, after Broadcom's move to subscription, a full switch to Hyper-V rarely paid off.
- Timeline. Full migrations ran 12 to 24 months.
- Project cost. Project spend consumed 40 to 60 percent of the first year saving on full migrations.
- Result. Most organizations cut more by renegotiating the VMware renewal than by switching hypervisor.
The reason is that a Hyper-V evaluation priced seriously, with each migration component itemized, changes the Broadcom quote. In most cases it moved the quote further than the migration itself would have saved once project cost and the year one uplift were counted.
The Hyper-V evaluation pays for itself at the negotiating table more often than in the data center.
Why we disagree with treating Hyper-V as free
The common advice says Hyper-V costs nothing because Windows Server Datacenter is already licensed. That holds only for hosts running mostly Windows guests, and it ignores System Center, SA, the storage and network rebuild and the year one uplift. Price the full comparison per cluster, and move only the clusters where it pays.
That is why the evaluation is worth running even when the answer is to stay. Keep it current between renewals, because a walkaway priced against the last renewal will not change the next quote. The split setup, each tier on the platform whose costs fit it, is the one that lasts.
How should you use a Hyper-V evaluation in the Broadcom renewal?
Use it as priced evidence, shared with the account team while it can still change the quote. That means well before the renewal date, while Broadcom still has room to adjust scope and bundle.
What the account team will say, and what to say back
- "VCF is the standard offer for your renewal." Ask for a written VVF quote for the clusters that run vSphere only, and compare the two per cluster.
- "A migration will cost you more than the increase." Agree where it is true, then show which clusters move anyway because their Windows licensing is already paid.
- "The discount is only valid until quarter end." Hold your own timeline, and ask for the quote's expiry to be extended in writing if the evaluation is not finished.
- "You must license every core in the cluster." Accept the counting rule, then reduce the host count and sockets you license before you sign.
- Core reduction rights at each anniversary. The Windows tier will leave during the term, and you should stop paying for it when it does.
- A cap on the renewal price. Without one, the next renewal is priced from whatever Broadcom lists at the time. See our notes on VMware price caps.
- Quotes split by cluster and bundle. VCF where you need it, VVF where you do not, so the saving is visible line by line.
- A core count confirmed in the order. Tie the quantity to your own inventory, not a Broadcom estimate.
How to check your own numbers first
Count physical cores per host and sockets per host from vCenter, using Broadcom's PowerCLI core counting script or an RVTools export, whose vHost tab shows sockets and cores per CPU. On the Microsoft side, list the Windows Server Datacenter and System Center licenses you own and whether SA is active, from your Microsoft volume licensing records.
What to do next
- Count cores per cluster. Pull sockets and cores per host, and apply the 16 core minimum on both sides.
- Price the full comparison. Hyper-V plus System Center plus SA plus migration plus the year one uplift, never the hypervisor alone.
- Get a VVF quote. Test the cheaper VMware bundle cluster by cluster before any migration case.
- Itemize the migration for your environment. Use the six component bands above, with your VM count and storage design.
- Split by tier. Move the Windows dense clusters to the Datacenter licensing you own, and renegotiate VMware for the mixed core.
- Take the evaluation to Broadcom. Share it with the account team months before the renewal date. The Broadcom practice runs the comparison with you.
Deciding what to do about VMware? Our Broadcom VMware negotiation services cover renewal, exit and audit, and work only for buyers.
Frequently asked questions
Is Hyper-V cheaper than VMware?
On licenses, usually yes against VCF and usually no against VVF. Over three years on 1,000 cores, negotiated Hyper-V plus System Center comes to about $490,000 before Software Assurance, while VVF comes to $240,000. The migration project, which runs 12 to 24 months, then decides the real answer, and most comparisons leave it out.
How does Hyper-V licensing work?
Hyper-V is a role inside Windows Server, so there is no separate hypervisor license. You license every physical core in the host, at least 8 per processor and 16 per server, and Datacenter edition then covers unlimited Windows VMs. System Center, which provides Virtual Machine Manager and Operations Manager, is licensed on the same core rules.
Does Hyper-V have feature parity with VMware?
Close enough for most enterprise workloads. The remaining gaps are narrow: VMware handles mixed guest operating systems, GPU passthrough at scale and third party integrations better, while Hyper-V is stronger on Windows guest density and Azure hybrid use. Test your own backup, monitoring and security products on Hyper-V first, since integrations are where VMware's lead is widest.
How much does it cost to migrate from VMware to Hyper-V?
$800,000 to $2.5 million for a typical environment, spread over six to eighteen months of program work. VM count drives conversion cost, but storage and program management are usually the largest lines, each reaching $1.5 million at the top of its band. Organizations without vSAN or NSX can sit toward the low end.
Should we leave VMware for Hyper-V?
Usually not all at once. In most of the environments we benchmarked, renegotiating the VMware renewal saved more than switching did. Move the Windows dense clusters whose Datacenter licensing is already paid, keep mixed workloads on a smaller VMware footprint, and get a VVF quote before accepting a VCF renewal.
When does VMware win the comparison?
When clusters run a mix of Linux, Windows and legacy guests, when NSX is built into the security design, when Tanzu Kubernetes runs in production, or when a migration would cost more than three years of repricing. For clusters that need vSphere without the full private cloud stack, VVF is often the cheapest option available.
Do Windows VMs on VMware need Windows Server licenses?
Yes. Microsoft licenses Windows Server to the physical host whatever the hypervisor, so a vSphere host running many Windows VMs typically needs Datacenter edition on all its cores. That cost sits on both sides of a Hyper-V comparison, which is why Windows dense clusters are the cheapest to move.