There used to be a day when VMware’s ESXi was the “go-to” solution general virtualization workloads. Some would argue this is still the case.
However, the major players in the hypervisor space have matured, largely making the hypervisor a commodity for the simplest of scenarios.
Now, if you’re considering moving from VMware to Hyper-V, you need some tools to get your VM’s migrated.
Microsoft Virtual Machine Converter is a tool similar to VMware Standalone Converter; you can convert physical machines or V2V’s with it. Surprisingly, Microsoft has announced it’s retirement.
As of the writing of this post, the tools is still available here, but your guest machines will have to be 2012 R2 or older. I attempted to convert a Server 2016 VM and got an error. After doing some digging, I found that it wasn’t on the approved guests list for MVMC…As Server 2016 has been out nearly a year at this point, I’m inclined to believe there is no intent to add it to MVMC, as it’s dead.
Microsoft’s recommended alternative, is Virtual Machine Manager in System Center. If you don’t already have a need for System Center, it’s a bit impractical to setup to move a handful of VMs- the requirements are significant.
MVMC really filled a gap here.
Now, there are third party tools to get this done. There’s also the backup and restore method, if your backup platform supports it. I suppose these other methods, such as DoubleTake Move, will get more consideration. Or perhaps we’ll stay on VMware- it has been doing the job just fine.
UPDATE: While a bit older, one solution that should also be mentioned is Disk2Vhd which was commonly used prior to MVMC. In testing, it converted a VMWare Server 2016 disk just fine.