The tool category for converting a VMware virtual disk to a Hyper-V virtual disk is the virtual to virtual (V2V) tool. Microsoft recommends SCVMM for this. Other tools include Starwind Software’s V2V Converter.
A subset of tools that only focus on converting the virtual disk files and not migrating the VM include: qemu-img on Linux or Windows, disk2vhd from Microsoft Sysinternals, and VMware’s ovftool. Other hypervisors, such as Oracle’s Virtualbox, VMware Workstation, Citrix XenServer, have tools for converting virtual disk types and are out of scope for this article.
The tool category for converting a physical disk to a virtual disk is the physical to virtual (P2V) tool and includes StarWind Software’s P2V Migrator. Either migrate all of the VMs disks to virtual disks on the target Hyper-V host, or disconnect all disks except the boot or system disk and migrate it, and then connect clones of the other physical disks in the destination Hyper-V VM. Everpure’s PowerShell SDK2 can be used to initiate snapshots of production volumes, copy those snapshots to new volumes, and then use PowerShell or Microsoft’s tool of choice to connect these new Pure Volumes to the appropriate VMs.