Microsoft Virtual Machine Converter 3.0: From VMware to Hyper-V

Microsoft Virtual Machine Converter is the software that allows IT Admins to convert machines to Hyper-V or Microsoft Azure. The new v3 introduce some new features like:


  • Supports conversion and provisioning of Linux-based guest operating systems from VMware hosts to Hyper-V and Azure
  • Supports conversion of offline virtual machines
  • Supports conversion of physical machines
  • Supports the new virtual hard disk format (VHDX) when converting and provisioning in Hyper-V in Windows Server 2012 R2 and Windows Server 2012
  • Supports conversion of virtual machines from VMware vSphere 5.5, VMware vSphere 5.1 and VMware vSphere 4.1 hosts to Hyper-V virtual machines


Supports as guest operating systems that you can select for conversion:


  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2
  • Windows Server 2008
  • Windows 8
  • Windows 7


These are the Operating System supported as Hypervisor:


  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2 SP1


How to Convert VM from VMware to Hyper-V

First of all select what kind of conversion you want (Virtual or Physical) and the destination (Azure or Hyper-V) as showed in figure 1.


Figure 1 – Migration Destination


Insert the credential of destination server and the path where locate the disks of the new VM, figure 2; select if you want generate fixed or dynamic disk and the format (vhd or vhdx).


Figure 2 – Host Path


After insert the vCenter/vSphere source’s credential go ahead to select what is virtual machine to convert, as showed in figure 3.


Figure 3 – Source VM


To convert the source’s disk/s is necessary a repository that could be local or remote; keep in mind that you need the same space requirement of source’s vmdk/s. The summary screen, figure 4, shows all the details of conversion plus warnings/errors about source virtual machine.


Figure 4 – Summary


When all the steps are finished, figure 5, it will be possible open the Hyper-V console to see the new VM. Check the right configuration before start the VM: for example if the vSwitch are different between VMware and Hyper-V you need to change the link manually, as showed in figure 6.


Figure 5 – Wizard Complete


Figure 6 – vSwitch Not Configured


Critical Notes

The virtual machines created with EFI bios are not supported for conversion. In this case you should use another way to convert them to Hyper-V.


As usual, remember to read the documentation before start conversion.


Download MVMC 3.0: