24.05.2026
Proxmox VE 9.2 vs VMware: Is It Time for SMEs to Switch?
Proxmox VE 9.2 has been available since May 21, 2026. On paper, it is a minor release. In practice, it matters much more for many...
The free Hyper-V Server is history, Windows Server 2025 is licensed per core. We plan and migrate your Hyper-V environment to Proxmox VE - including Windows guests, VirtIO drivers and activation.
The following are trademarks of their respective owners: Proxmox VE (Proxmox Server Solutions GmbH). WZ-IT is an independent service provider and has no business, partnership, or contractual relationship with these companies. We offer independent migration, installation, hosting, and operations services.
The trigger is rarely the technology - it is the licensing model. Three reasons we see in projects again and again.
The free Microsoft Hyper-V Server last shipped as version 2019 - mainstream support ended on January 9, 2024, extended support runs until January 9, 2029. For Windows Server 2022 and 2025 there is no comparable free product anymore.
Windows Server 2025 is licensed per core - at least 8 core licenses per processor, at least 16 per server. As a hypervisor host, Windows therefore costs money even if only Linux VMs run on it. Proxmox VE runs without host license costs (AGPLv3), a subscription is optional.
Proxmox ships with integrated backups via Proxmox Backup Server, is fully transparent as an open platform and does not tie you to any vendor - your environment stays portable at all times.
To be fair: the Hyper-V role in Windows Server 2022 and 2025 is not discontinued - Microsoft actively develops it further, for example with GPU partitioning and support for up to 4 PB of RAM. The switch is a cost and strategy question: the free path is gone, and whoever keeps using the role licenses the host as Windows Server.
We do not promise blanket percentages - your savings follow from the core count of your hosts. The mechanics behind it are unambiguous though.
The free Microsoft Hyper-V Server last shipped as version 2019. There is no free equivalent for Windows Server 2022 and 2025 anymore - anyone who wants to keep running the hypervisor free of charge has to switch platforms.
Windows Server 2025 is licensed per core - at least 8 core licenses per processor, at least 16 per server. As a hypervisor host, Windows therefore always costs money, even if it exclusively runs Linux VMs.
Proxmox VE is open source under the AGPLv3 and runs without host license costs - a subscription is optional. The per-core math for the hypervisor is eliminated entirely.
To be fair: your Windows guests still need valid Windows Server licenses on Proxmox. What goes away is the license for the hypervisor host - not the guest licenses.
How to license Windows Server on ProxmoxFour steps from the Hyper-V inventory to the cutover - technically clean, with a rollback option and without surprises.
VM list with generation 1/2, dependencies, resource requirements and license check: what runs where, what can move when, and how are Windows guests licensed correctly on Proxmox?
Licensing Windows Server on ProxmoxCluster and storage design based on your baseline (ZFS or Ceph), network and Proxmox Backup Server - including vTPM preparation for Windows 11 guests.
We import VHDX disks directly - QEMU reads the format natively, no separate conversion is needed. Gen 1 VMs get SeaBIOS, Gen 2 VMs get OVMF (UEFI). Windows guests receive VirtIO drivers including switching the boot disk to VirtIO SCSI, BitLocker is suspended beforehand and activation is moved from AVMA to KMS or MAK.
qm disk import <vmid> disk.vhdx <storage>Step-by-step guide: Hyper-V to ProxmoxTest boot per VM, defined rollback window to the Hyper-V estate, onboarding to our monitoring and orderly decommissioning of the old environment.
Ten points we tick off per VM before every cutover - Hyper-V-specific instead of generic. This is exactly where it is decided whether the test boot succeeds on the first try.
The VM generation determines the firmware mapping on Proxmox: generation 1 boots with SeaBIOS, generation 2 with OVMF (UEFI).
Open checkpoints leave AVHDX differencing chains behind. Before the export we merge them fully back into the base VHDX so that a consistent disk moves over.
AVMA only works with a Hyper-V host. These guests need KMS or MAK activation on Proxmox and are flagged in advance.
Back up recovery keys and suspend BitLocker with -RebootCount 0 so the suspension survives reboots until the vTPM is set up on Proxmox.
Which VMs run as cluster roles, which disks live on Cluster Shared Volumes? This determines the target architecture and the migration order.
On Proxmox the virtual NIC gets a new MAC address by default. DHCP reservations, license bindings and firewall rules tied to the MAC are captured beforehand.
Windows 11 strictly requires a TPM, and we plan the vTPM for Windows Server 2025 guests right away as well - including a tpmstate volume per VM.
Reconcile the core count of the target nodes against the existing Windows Server licenses - the guests remain license-liable, only the host license goes away.
Immediately before each move there is a complete, verified backup of the VM - independent of the rollback option to the Hyper-V estate.
The order follows the dependencies. Each window is coordinated with the business units and gets a defined rollback point.
Each point is documented per VM and forms part of our migration log - including a rollback point per wave.
Both hypervisors are technically mature - the differences lie in the licensing model, backup integration and openness.
| Hyper-V (Windows Server) | Proxmox VE | |
|---|---|---|
| Host license costs | Windows Server core licenses for the host (min. 16 cores per server) | No license costs (open source, AGPLv3), subscription optional |
| Backup | Third-party ecosystem required | Proxmox Backup Server integrated - incl. deduplication and verification |
| Managing multiple hosts | SCVMM or Windows Admin Center | Integrated cluster management, plus Proxmox Datacenter Manager |
| Linux workloads | Supported as a guest | Native KVM foundation - Linux runs first class |
| Openness | Proprietary (Microsoft) | Open source (AGPLv3), fully auditable |
As of July 2026. Licensing details are governed by the current Microsoft Product Terms. WZ-IT is an independent service provider.
Three proven target designs we map Hyper-V estates to in projects - from a single host to replacing the failover cluster.
No HA - resilience comes from backup & restore via PBS.
Our recommended standard for production workloads with HA requirements.
The Windows cluster remains as a rollback layer until sign-off.
A Hyper-V migration is above all a Windows migration. The pitfalls are in the details - and that is exactly where we work every day:
Our guide to Windows Server licensing on Proxmox clarifies the host licensing question. And after the migration, we continue to operate your environment on request - as Managed Proxmox from €179.90 per node per month, including monitoring, updates and backup verification.
In-depth knowledge from our Proxmox knowledge base.
24.05.2026
Proxmox VE 9.2 has been available since May 21, 2026. On paper, it is a minor release. In practice, it matters much more for many...
08.05.2026
Three critical Local Privilege Escalation vulnerabilities in the Linux kernel within two weeks — all three sitting in the code for nine to twelve years....
05.05.2026
With Proxmox Backup Server 4.2 (released late April 2026), S3-compatible object storage is officially supported as a backup backend. No more tech preview label, no...
That depends on the number of VMs, data volume and dependencies. Small environments with a handful of VMs are typically migrated within a few days, larger estates in staggered waves over several weeks. After the inventory you receive a concrete schedule per VM - including maintenance windows and rollback points.
A short maintenance window per VM cannot be avoided entirely: the VM is shut down, the VHDX disk is transferred and imported, followed by the test boot on Proxmox. The window is plannable and limited per VM though - we migrate critical systems in stages outside your core hours, and the Hyper-V estate remains as a rollback option until the VM is signed off on Proxmox.
Your Windows and application licenses inside the guests generally remain valid - what changes is the host level: instead of a license-liable Windows Server host, Proxmox VE runs underneath in the future. How Windows Server guests are licensed correctly on Proxmox is explained in our guide "Licensing Windows Server on Proxmox". Important: we cover the technical side - this does not replace legal advice on licensing.
Yes. Windows 11 strictly requires a TPM, and Proxmox provides a virtual TPM (vTPM) via a tpmstate volume. However, the TPM state cannot be taken over from the source hypervisor - which is why we suspend or decrypt BitLocker before the migration and re-enable it on Proxmox afterwards.
AVMA requires a Datacenter host with the Hyper-V role enabled and, according to Microsoft, does not work with other virtualization technologies - so this path is gone on Proxmox. Instead, you activate via KMS (platform-independent, activation threshold of 5 servers, renewal every 180 days) or via MAK or retail keys. We switch the activation over as part of the migration.
Technically both play in the same league - the difference lies in the licensing model and ecosystem. Hyper-V has been discontinued as a free standalone hypervisor and is tied to per-core Windows Server licensing; Proxmox VE is open source and ships clustering, live migration, backup (PBS) and software-defined storage without a license wall. For Windows-heavy environments with a strong Microsoft stack, Hyper-V can still be a fit - if you want to reduce license costs and vendor lock-in, Proxmox is usually the better choice.
No. Proxmox VE is a standalone type 1 hypervisor based on Debian Linux with KVM/QEMU - Hyper-V is neither required nor installed. Hyper-V VMs are converted to the Proxmox format during migration: Proxmox imports the VHDX disks directly, and the VM configuration (generation, firmware, vTPM) is mapped to its Proxmox counterparts.
The Proxmox HA stack takes over the duties of the Windows failover cluster: VMs are defined as HA resources and automatically restart on another node if a node fails. Cluster Shared Volumes (CSV) are replaced by Ceph or other shared storage (NFS/iSCSI). For Ceph we plan at least 3 nodes and a 10GbE network; in a 2-node cluster a QDevice secures the quorum.
Yes, coexistence is actually the normal case: the Proxmox environment is built alongside the Hyper-V estate, both platforms run in the same network, and the VMs move in planned waves. For each wave the Hyper-V estate remains as a rollback option until the VMs are signed off on Proxmox. This spreads the risk and avoids a big-bang cutover.
There is no 1:1 equivalent of SCVMM - we say that honestly. In practice, the integrated Proxmox web interface covers managing a cluster (VMs, storage, network, HA, backups), and the Proxmox Datacenter Manager is added for multiple clusters. Specific SCVMM features such as service templates can be reproduced via the Proxmox API and automation where needed - the inventory clarifies what is actually required.
The maintenance window is essentially determined by the size of the VHDX disks and the transfer path - the copy process dominates. The procedure per VM is always the same: shut down, transfer and import the disk, install VirtIO drivers, test boot. After the inventory you receive a concrete window per VM instead of a blanket estimate.
We price the migration effort individually after the inventory - it depends on the number of VMs, data volume and special cases such as failover clusters or BitLocker. Operations afterwards are predictable: Managed Proxmox starts at €179.90 per node per month, including monitoring, updates and backup verification. At the same time, the Windows Server license for the hypervisor host is eliminated.
Yes. The hypervisor switch does not change your IP design - the VMs keep their addresses. One thing to note: on Proxmox the virtual NIC gets a new MAC address by default, and Windows creates a separate adapter profile for the new VirtIO NIC. We therefore re-bind statically configured IPs to the adapter during the cutover, and adjust DHCP reservations and MAC-bound rules (firewall, license servers) along the way.
Yes. On request, your environment transitions directly into managed operations after the cutover: 24/7 monitoring via our Zabbix cluster, updates in maintenance windows, backup verification with Proxmox Backup Server and fixed response times. That way there is never a moment when nobody feels responsible.
Good choice - we'll help you get started or with operations.
These solutions are often used together with Proxmox
These solutions offer similar functionalities and can be evaluated together
No risk: worst case, you leave with a clearer understanding of your project than before.


“WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.”
Whether a specific IT challenge or just an idea - we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.
Timo Wevelsiep & Robin Zins
Managing Directors of WZ-IT

