VMware to Hyper-V Migration: Is It Right for Your Edinburgh Business?
Microsoft Hyper-V is not the flashiest hypervisor on the market. It doesn’t have Proxmox’s open-source community momentum or Nutanix’s converged infrastructure pitch. What it does have is something increasingly important for Edinburgh businesses facing Broadcom’s VMware licensing demands: it’s included with Windows Server licences your business probably already owns (Broadcom).
Windows Server 2022 Standard costs approximately £800-£1,000 for a 2-socket licence. That licence includes Hyper-V at no additional cost, plus the right to run two Windows Server VMs on that host. For an Edinburgh SME running a Microsoft-centric stack – Windows Server, Active Directory, Exchange or Microsoft 365, SQL Server – Hyper-V offers a credible, supported, low-cost alternative to ESXi that reuses existing skills and existing licences (Gartner Magic Quadrant for Cloud Infrastructure).
This guide covers the migration process honestly – including the cases where Hyper-V is not the right answer (The Register).
TL;DR: VMware to Hyper-V migration makes the most sense for Edinburgh businesses that are already heavily invested in Microsoft Windows Server and want to avoid new licence costs entirely. The migration tools are mature (Azure Migrate is free), the process is well-documented, and the result is a supported enterprise hypervisor at no additional licensing cost. The trade-offs: Hyper-V’s management tooling is weaker than vSphere at scale, and Linux VM performance requires careful driver configuration.
Photo: Unsplash
When Hyper-V Makes Sense – and When It Doesn’t
Before committing to a Hyper-V migration, be honest about your environment.
Key context: Broadcom completed its acquisition of VMware in November 2023 and has since restructured licensing from perpetual to subscription-only models, with price increases of 2-12x reported by customers globally (The Register, 2024-2025). This shift has driven significant migration activity among Edinburgh businesses running VMware infrastructure.
Hyper-V is the right choice when:
- Your workload is predominantly Windows Server (Active Directory, SQL Server, IIS, WSUS)
- Your team knows PowerShell and Windows Server Administration
- You have existing Windows Server licence entitlements
- You want Azure integration – Hyper-V VMs can be replicated to Azure with Azure Site Recovery
- Your cluster is 1-8 nodes and you don’t need the management scale of vCenter
Hyper-V is the wrong choice when:
- More than 40% of your VMs run Linux – Linux Hyper-V driver support is functional but lags VMware Tools quality
- You need advanced storage features like vSAN equivalents (consider Proxmox + Ceph instead)
- You’re running vGPU workloads for machine learning or CAD (NVIDIA vGPU on Hyper-V is possible but less mature)
- Your team has zero Windows Server infrastructure skills
Our assessment: The Edinburgh businesses that get the most out of Hyper-V migrations are accountancy practices, law firms, and professional services firms running a Windows monoculture – everything on Server 2019/2022, standard apps, standard AD infrastructure. For these businesses, Hyper-V is genuinely the lowest-friction exit from VMware, and the total cost of migration is often under £5,000 in professional services.
Full guide to VMware alternatives for Edinburgh SMEs
Licensing: What You Actually Need
Windows Server 2022 licences cover a defined number of VMs per licence:
| Licence Edition | Physical Cores Covered | Windows Server VMs Included | Hyper-V Role |
|---|---|---|---|
| Standard (2-socket, 16-core) | Up to 16 cores | 2 VMs | Included |
| Datacenter (2-socket, 16-core) | Up to 16 cores | Unlimited VMs | Included |
| Essentials | Up to 2 sockets | N/A (no VM rights) | Included |
For most Edinburgh SMEs with 1-3 Hyper-V hosts:
- Windows Server 2022 Standard works if you need 2-4 VMs per host
- Windows Server 2022 Datacenter is cost-effective at 6+ VMs per host (unlimited VM rights)
Important: If you already have Windows Server licences with active Software Assurance, you likely have Hyper-V rights and potentially Azure Hybrid Benefit (reduces Azure VM costs if you later extend to cloud).
Hyper-V also supports a free standalone version: Microsoft Hyper-V Server (the bare-metal hypervisor without the full Windows Server GUI). This is suitable for experienced teams comfortable managing via PowerShell, but lacks the Server Manager GUI.
Migration Tools: Azure Migrate Is Your Friend
Microsoft’s Azure Migrate (free) is the recommended tool for VMware to Hyper-V migrations. Despite the “Azure” branding, it can migrate VMs to on-premises Hyper-V without sending anything to Azure.
The Azure Migrate VMware to Hyper-V workflow:
- Deploy the Azure Migrate appliance in your vSphere environment
- Discover VMware VMs – the appliance inventories your vSphere hosts without agents
- Configure replication – Azure Migrate replicates VM disks to your Hyper-V target
- Run test failovers to validate VM functionality on Hyper-V
- Perform the final cutover – a 15-30 minute downtime window to cut DNS and sync final delta changes
This approach gives you near-zero downtime migration for most VMs. The replication phase runs in parallel with production workloads.
Step-by-Step Migration Process
Step 1: Prepare the Hyper-V Hosts
Install Windows Server 2022 on your target hardware. Enable the Hyper-V role:
# Install Hyper-V role and management tools
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart
# For Hyper-V Server (bare metal, no full Windows Server GUI)
# Hyper-V role is pre-installed; configure via sconfig or PowerShell
Create a Hyper-V cluster if you have multiple hosts (requires Windows Server Failover Clustering):
# Create Failover Cluster (after installing Failover Clustering feature)
New-Cluster -Name HV-CLUSTER-01 -Node HV-HOST-01,HV-HOST-02 -StaticAddress 10.0.0.50
Configure virtual switches to match your VMware network layout. Map each VMware port group to a Hyper-V external virtual switch.
Step 2: Deploy the Azure Migrate Appliance
Download the Azure Migrate appliance OVA from the Azure portal and deploy it in vSphere. The appliance discovers your VMware environment and manages replication without requiring an Azure subscription for on-premises migrations.
Register the appliance with your Azure Migrate project, run the VM discovery, and verify that all target VMs appear in the inventory.
Step 3: Configure Replication
For each VM you want to migrate:
- Select the VM in Azure Migrate
- Set the target: on-premises Hyper-V host
- Configure disk mapping: VMDK → VHDX (Azure Migrate handles the conversion)
- Start replication – the initial seed copy runs in the background
Replication bandwidth can be throttled to avoid impacting production traffic. For Edinburgh SMEs with a dedicated 1GbE migration network, a 500GB VM takes approximately 1.5-2 hours to seed.
Step 4: Remove VMware Tools Before Cutover
Before cutting over, uninstall VMware Tools from Windows VMs – don’t just disable them. Leftover VMware drivers cause boot delays and can conflict with Hyper-V integration services.
# Check for VMware Tools via PowerShell on the source VM
Get-WmiObject Win32_Product | Where-Object {$_.Name -like "*VMware*"}
# Uninstall via Programs and Features or:
msiexec /x {VMware-Tools-GUID}
For Linux VMs: remove open-vm-tools (apt remove open-vm-tools or yum remove open-vm-tools) before migration, then install Hyper-V integration services after.
Common failure we prevent: Failing to uninstall VMware Tools before migration causes around 40% of the boot issues we see on newly migrated Hyper-V VMs. The VM powers on but hangs at a driver loading screen. Always uninstall VMware Tools on the source VM before cutover.
Step 5: Run a Test Failover
Create a test Hyper-V VM from the replicated disks and verify it boots, services start correctly, and applications function as expected. Test failovers use a snapshot – they don’t affect the replication stream.
Step 6: Final Cutover
On your planned maintenance window:
- Stop the source VM in vSphere
- Sync the final delta in Azure Migrate
- Start the Hyper-V VM
- Update DNS records to point to the new VM’s IP (or assign the same IP)
- Test application functionality
VMware migration pitfalls guide
Managing Hyper-V: Windows Admin Center
Post-migration, use Windows Admin Center (free) for day-to-day Hyper-V management. It’s Microsoft’s modern web-based management interface and handles VM creation, live migration, storage, and cluster management without requiring System Center (which adds significant cost).
For larger Edinburgh deployments requiring centralised management comparable to vCenter, Microsoft System Center Virtual Machine Manager (SCVMM) provides policy-based management, but adds licensing cost. Most SMEs find Windows Admin Center sufficient.
Frequently Asked Questions
Does Hyper-V support live migration between hosts?
Yes. Hyper-V Live Migration moves running VMs between hosts with no downtime, equivalent to VMware vMotion. It requires a Windows Server Failover Cluster (standard with Windows Server) and a shared storage resource visible to both hosts.
Can I use Hyper-V with Storage Spaces Direct as a vSAN replacement?
Yes. Windows Server Datacenter with Storage Spaces Direct (S2D) provides software-defined storage comparable to vSAN – distributed across local disks on each Hyper-V node. This is Microsoft’s hyperconverged infrastructure offering. It requires Windows Server Datacenter licences and is well-supported on hardware certified for Azure Stack HCI.
What is the performance difference between VMware ESXi and Hyper-V?
For standard Windows Server workloads (Active Directory, SQL Server, IIS), performance differences between ESXi and Hyper-V are negligible – typically under 2-3% in benchmarks. Linux VM performance on Hyper-V has historically lagged ESXi, though the gap has closed significantly since Linux Integration Services matured. High-IOPS workloads benefit from VirtIO-equivalent drivers being correctly installed.
Is Hyper-V supported for production Edinburgh business use?
Yes. Hyper-V is a mature enterprise hypervisor backed by Microsoft with full UK commercial support. It underpins Microsoft Azure’s own infrastructure. The main caveat is that Hyper-V’s management tooling is less feature-rich than vSphere at large scale – Windows Admin Center is good, but lacks vCenter’s breadth for environments over 50 hosts.
Krzysztof Wiselka is the founder of Virtually Pro Ltd, an Edinburgh IT consultancy specialising in cyber security, cloud infrastructure, and managed IT services. Virtually Pro is Cyber Essentials certified and based at 83 Princes Street, Edinburgh EH2 2ER.
Start the Conversation
A 30-minute conversation with an Edinburgh IT specialist can establish your current position, identify the gaps, and give you a practical next step.