VMware renewal 2026: move to Hyper-V or Proxmox, or stay?

Where we would lean, and when we would not

This is our engineering judgement rather than vendor fact, and it assumes a typical UK small or mid-sized estate: a handful of hosts, a mix of Windows and Linux machines and a small IT team. The evidence behind it follows in the later sections.

Nobody should pick a hypervisor from a headline price. The better question is which platform your team can run confidently when something breaks, and which one your backup, monitoring and application vendors will actually support.

• Mostly Windows guests, Windows skills in-house, a few hosts: lean towards Hyper-V. You are probably buying Windows Server licences anyway and your team already knows the surrounding tooling.
• Comfortable with Linux, a modest number of hosts, no heavy dependence on VMware-specific products: Proxmox VE deserves a serious pilot. The licensing is far lighter but you take on more of the integration work.
• Heavy use of VMware-specific features such as vSAN, network virtualisation or disaster-recovery orchestration, or application vendors who only certify VMware: treat this as a project, not a swap. Renew for the shortest sensible term while you plan.
• Nobody in-house who wants to run a hypervisor: the licence price is the smaller part of the decision. Budget for a partner or managed support whichever platform you choose.

What your renewal quote really depends on

For VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF), Broadcom licenses by physical core and sets a minimum of 16 cores per CPU. Its own worked example counts a host with two 8-core CPUs as 32 licensed cores, so small hosts carry licences for cores they do not have. That article does not mention any separate minimum order size.

You will see a 72-core minimum quoted widely. It traces back to a March 2025 report of a distributor email, and in that report Broadcom did not respond to requests for confirmation. We could not find it in Broadcom's own licensing article. Do not budget from it either way: ask your reseller to state the minimum, the bundle, the term and the core count on the quote itself. The same report mentioned a penalty for renewing late. That is also unconfirmed, so check your contract before letting anything lapse.

Broadcom's published upgrade path from vSphere 8.x leads to VVF 9 or VCF 9, and it lists 11 October 2027 as the end of general support for vSphere 8.0, including ESXi and vCenter. That is less than a year away. Renewing for a term that runs well past it means committing to the newer bundles or paying for support options, so ask what extended support exists and what it costs. Bundle availability has reportedly varied by region, and we could not confirm the UK position from Broadcom, so ask your reseller which bundles you can actually order.

Hyper-V: strongest when your estate is mostly Windows

Hyper-V is a role of Windows Server, so the cost is the Windows Server licensing on the hosts. Microsoft requires licences for all physical cores, with a minimum of 8 per processor and 16 per server. A fully licensed Standard host includes rights for two virtual machines, and each further pair means licensing the cores again. Datacenter has unlimited virtual machine rights. Where the crossover falls depends on your host sizes and your actual quote, so compare quotes rather than trusting a rule of thumb. Licensing per virtual machine instead of per host requires a subscription or active Software Assurance.

If your Windows guests are already covered by Datacenter or similar licensing, Hyper-V may add little to the bill. Confirm that with your licensing partner. Microsoft's use rights govern, and a summary like ours is not a substitute.

For the move itself, Microsoft offers the VM Conversion extension for Windows Admin Center, which is free and works from vCenter versions 6.x to 8.x. It copies disks while the source machine keeps running, then powers the source off for a final change sync at cutover. It handles recent Windows Server and client versions plus a short list of Linux distributions, and Linux guests need Hyper-V drivers installed first. The extension is still labelled as a preview, and Microsoft states it has no obligation to support preview software. That is fine for a pilot but worth weighing before you bet a production migration on it.

The bigger shift is day-to-day management. You lose vCenter, so judge whether Windows Admin Center and Windows Server Failover Clustering give your team what it relies on today. Veeam Backup and Replication covers Hyper-V hosts from 2012 through 2025, so mainstream backup is unlikely to be the blocker, but check your own product.

Proxmox VE: light on licensing, heavier on ownership

Proxmox VE is built around the KVM hypervisor and Linux containers, with clustering, high availability and live migration. Proxmox's pricing page lists every feature at every tier, with subscriptions charged per occupied physical CPU socket per year: Community at €120, Basic at €370, Standard at €550 and Premium at €1,100. Community has no ticket support, Basic includes 3 tickets a year and Standard 10. Three dual-socket hosts are six sockets, so Standard would be €3,300 a year before VAT and any reseller margin, and you should confirm the basis of the price when you order.

Proxmox recommends the subscription-only Enterprise repository for production and says the free no-subscription repository is for testing, because its packages are not always as heavily tested. In practice, a production cluster should carry at least a Community subscription. Support begins at Basic, and ticket-based support is a different thing from the application-vendor and partner ecosystem you may be used to.

Proxmox VE 8 and later include an import wizard for VMware ESXi. Proxmox tested ESXi 6.5 to 8.0, and it does not support vSAN-backed or encrypted disks. Machines with snapshots import more slowly, and the source VM has to be powered off for the import. Windows guests often will not boot from VirtIO disks until the drivers are loaded, so they typically start on SATA or IDE and switch afterwards. Proxmox also advises removing VMware guest tools first and notes that virtual TPM state cannot be migrated. Its migration page does not cover Hyper-V as a source.

Check storage before anything else. Shared iSCSI, Fibre Channel or SAS LUNs can be used through LVM, and Ceph is the built-in clustered option, but do not assume a SAN behaves like the datastore you have now. Verify snapshot and thin-provisioning behaviour in your pilot. Finally, confirm that your backup product supports your Proxmox version. Veeam's documentation listed Proxmox VE 8.2 to 9.1 when we checked, so a newer release may not be covered yet.

Staying on VMware for now

Staying is a legitimate answer if you cannot migrate safely before your term ends. The sensible version is a deliberate bridge: the shortest term you can obtain, a quote you have read line by line and a migration decision date set in advance. A renewal quote is not a migration plan, however close the deadline feels. Whether shorter terms are offered, and at what unit price, is for Broadcom and your reseller to say, so ask directly.

The costs that never appear on a licence quote

Licence price is the easy number to compare and rarely the whole story. These are the items that most often change the answer:

• Migration effort and the outage windows each cutover needs.
• Running old and new platforms side by side until the last machine is proven.
• Windows Server licensing, which follows your guest machines whichever hypervisor you choose.
• Backup, monitoring and management tooling, including any licences that change with the platform.
• Hardware that may need replacing if it is not suitable for the new platform.
• Training and support for the people who will run it.

A staged plan that protects your renewal date

Do these in order, because each step feeds the next. The pilot is the part that turns an opinion into evidence.

1. List every host with its CPU count, cores per CPU and storage type, and every virtual machine with its operating system and any VMware-specific features it relies on. Count licensable cores using Broadcom's rule of at least 16 per CPU.
2. Obtain the renewal quote in writing, showing bundle, term, core count, minimums, late-renewal terms and the extended-support position for vSphere 8.
3. Price one alternative for the same hosts: Windows Server cores for Hyper-V, or sockets and a support tier for Proxmox VE. Add backup tooling and any hardware change, and compare totals.
4. Ask your backup vendor, SAN supplier and key application vendors whether they support the target platform and version. A single no here can end the discussion before you spend time on it.
5. Pilot with a few non-critical machines, ideally one Windows and one Linux, on spare hardware or a freed-up host. Keep the originals intact. The Windows Admin Center tool replicates while the source runs and then powers it off at cutover, while the Proxmox wizard needs the source powered off, so tell any users of a pilot machine before you begin. Copy time depends on disk size and network speed, so treat any estimate you are given with scepticism until you have timed your own.
6. In the pilot, confirm that each machine boots, reaches the network, runs its application and is picked up by your backup. Then restore one from backup and confirm it works. That restore is the check that tells you the platform is ready for real workloads.
7. Choose a renewal term that covers migration with margin, then migrate in small groups of related machines. Keep each source machine until its replacement has passed the same checks, and only then retire it and reduce the licence count.