By Alison / Last Updated May 5, 2022

Why convert VM between Hyper-V and VMware 

While VMware and Microsoft Hyper-V are the most popular virtual products, they are not compatible with each other. VMware products create virtual disks in VMDK format, and Hyper-V creates virtual disks in VHD or VHDX format.

However, sometimes you may need to convert VHDX to VMDK. For example, since VMware supports more operating systems such as Unix or macOS, you may need to convert your Hyper-V VMs to VMware for more application testing. But the cost on VMware can be a really burden for small organizations, so you may need to convert VMware VMs to Hyper-V.

How to Convert between VMware and Hyper-V

How can you convert Hyper-V VM to VMware or vice versa

To convert VHDX to VMDK, there is an official free tool VMware vCenter Converter Standalone for you.

For converting VMware VM to Hyper-V, there was also an official free tool Microsoft Virtual Machine Converter (MVMC). But unfortunately, it was deprecated by Microsoft, and the conversion feature was then provided by Microsoft’s new paid tool System Center Virtual Machine Manager (SCVMM). If you don’t have MVMC, you can choose SCVMM or third-party tools.

In this article I will introduce the detailed steps. You can click the anchor text to jump to the interested part.

Before you begin, please make sure you’ve backed up your VMs to avoid unexpected failures.

Convert Hyper-V VM to VMware using VMware vCenter Converter

1. Launch VMware vCenter Converter Standalone. Click Convert machine on the toolbar to open the wizard.

Convert Machine

2. On Source System page, select source type as Powered off option, and select Hyper-V Server from the below dropping menu.

Specify server connection information, and then click Next.

Select Source System

3. On Source Machine page, select the Hyper-V VM you want to convert. Click Next to continue.

Depending on whether VMware ESXi or Workstation you want to convert the VM to, the following steps are different.

4. If you want to convert to VMware ESXi:

On Destination System page, select VMware Infrastructure virtual machine as the destination type, and provide ESXi or vCenter Server IP Address, User name and Password. Then click Next.

Select Destination System

5. On Destination Virtual Machine page, provide a Name for the new VM, and click Next.

6. On Destination Location page, select the ESXi host, Datastore, and Virtual machine version. Click Next.

Destination Location

If you want to convert to VMware Workstation, Fusion, or Player:
On Destination System page, select VMware Workstation or other VMware virtual machine as the destination type, and select VMware product in the dropping menu.
Provide a Name and select a location for the virtual machine. You can select a local folder or a network share, with User name and Password to be used when connecting to the network share of the destination virtual machine. Then click Next.

7. On Options page, browse the Current settings and optionally Edit the parameters for the conversion task. Then you can click Next to continue.

8. On Summary page, review the information and click Finish to start conversion. You can see the progress in Recent Tasks interface.

Convert VMware ESXi VM to Hyper-V using Microsoft Virtual Machine Converter (MVMC)

Before you begin, please power off the target VM and uninstall the VMware tools.

1. Launch Microsoft Virtual Machine Converter (MVMC). Select the Machine Type as Virtual machine conversion, and click Next to continue.

Select Machine Type

2. On Migration Destination page, select Migrate to Hyper-V, then click Next.

Migrate to Hyper-V

3. On Hyper-V Host page, Enter an IP Address, computer name or fully qualified domain name in Address, to

specify a Hyper-V host as the destination for the new VM.

Check Use my Windows user account option, or provide other User name and password. Click Next to continue.

Hyper-V Host

4. On Disk page:

Click Browse… to specify a path to store the converted virtual disks.

Choose the type of virtual hard disk to use for the converted disk as Fixed size or Dynamically expanding.

Choose the format of virtual hard disk to use for the converted disk as VHD or VHDX. Then click Next.

Select Disk

5. On Source page, specify the Address, Username and password to connect to a vCenter server, ESX server, or ESXi server. Click Next.

Select Source

6. On Virtual Machines page, select the VM you want to convert from the list, and then click Next.

7. On Connection page, select the final state of the source and destination VM as ON or Off.

If the original VM is powered on, have supported versions of Linux installed, and are running the VMware tools, you will need to provide information to connect to the VM, for enabling the VMware tools to be uninstalled. You don’t need to provide it if you uninstalled VMware tools previously.

Connection

Click Next to continue.

8. On Workspace page, click Browse… to specify a folder for storing temporary files in the conversion process. And click Next.

9. On Summary page, review all the configuration information you specified, and then you can click Finish to start conversion.

10. You can see the progress on Completion page. Click Close when it’s done, and remember to reconfigure the new VM on Hyper-V.

Note: If you don't have MVMC, you can choose Microsoft's paid tool System Center Virtual Machine Manager (SCVMM) or third party tools.

Convert exported VMware VMDK to Hyper-V VHDX using PowerShell

1. Export target VM on VMware ESXi or Workstation to OVF template. Generally it will result in 3 files, the manifest file ends with .mf, the OVF file which provides a complete specification of the virtual machine, and the virtual disk file ends with .vmdk. What we need is the exported VMDK file.

2. Launch PowerShell and input the following command to import MVMC module:

Import-Module “filepath\Microsoft Virtual Machine Converter\MvmcCmdlet.psd1”

Note: As for ‘filepath’ you need to type the path where you store the MVMC folder.

Import MVMC module

3. Input the following commands to convert the exported VMDK file into VHDX file:

ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath “filepath\filename.vmdk” -VhdType DynamicHardDisk -VhdFormat vhdx -DestinationLiteralPath “newfilepath\newfilename.vhdx”

Note:
1. As for ‘filepath’ and ‘filename’ you need to type the path where you store the exported VMDK file and its name.
2. As for ‘newfilepath’ and ‘newfilename’ you need to type where you want to store the new VHDX file and its name.
3. -VhdType is used to define the type of the converted disk as Fixed size or Dynamically expanding.
4. -VhdFormat is used to define the format of the converted disk as VHD or VHDX.

Convert VMware VMDK to Hyper-V VHDX

4. Now you can check the converted disk in the specified folder, and use it to create a new Hyper-V VM.

Data Insurance: Backup VMs before performing risky operations

Converting VM is a risky operation, many unexpected problems can occur during the process. A failed conversion can even render your original VM unusable, and result in serious data and financial loss.

So keep taking regular backups is crucial, especially for enterprises. Here I recommend you AOMEI Cyber Backup for it can manage both VMware and Hyper-V VMs on one platform.

✦ Supported Versions: Windows Server 2012 and all later versions, VMware ESXi 6.0 and all later versions.

✦ Multiple VMs Backup: you can even create a backup task that covers all VMs on your host.

✦ Auto Backup Schedule: creating automatic backup schedule to run daily, weekly, or monthly and specify start date and time accordingly.

✦ Auto Cleanup: cleaning old backup files that exceed the specified retention period.

✦ Offsite Restore: capable of restoring backups to new VMs on original or another datastore, host.

✦ Affordable Pricing: reasonable charges only base on the number of bound devices, regardless of how many VMs are on the host.

AOMEI Cyber Backup simplifies a complete backup task into 3 simple steps, and next I will demonstrate how to create one. Here is a free trial for you:

Download FreewareVMware ESXi & Hyper-V
Secure Download

3 quick steps to protect multiple VMs from data loss

1. Bind devices: Access to AOMEI Cyber Backup web client and navigate to Source Devices tab to add and bind your Hyper-V or VMware ESXi host, the VMs on the host will be clearly listed with their backup status for monitoring.

Add VMware ESXi host

2. Create backup tasks: Navigate to Backup Task > + Create New Task and provide Task Name, Backup Type, Device, Target, Schedule, and Backup Cleanup on an intuitive page.

Create backup tasks

you can quickly create a complete backup task that cover multiple VMs within one task. In addition, a task with Schedule and Cleanup will automatically perform backups and delete old backup files that exceed the retention period.

Backup schedule

3. Restore from backup: clicking > Restore on the separately listed backup task, all recovery points related to the task will be listed, you can select from them according to your needs.

Restore to new location

With AOMEI Cyber Backup you can quickly complete backup and restore tasks of multiple VMs. In addition, you can create sub-accounts with limited privileges, to further protect your VMs from accidental mis-operations.

Summary

In this article I introduced how to use the official free tool VMware vCenter Converter Standalone to convert Hyper-V VM to VMware, how to use Microsoft Virtual Machine Converter (MVMC) to convert VMware ESXi VM to Hyper-V, and how to use PowerShell to import MVMC module to covert VMDK file to VHD file. The last way can be used for VMware Workstation VMs.

However, unfortunately, the MVMC was already deprecated by Microsoft. Therefore, if you don’t have MVMC, you can choose Microsoft’s new paid tool System Center Virtual Machine Manager (SCVMM) or other third-party tools to help you convert VMware VMs to Hyper-V.

Conversion is still a risky operation. To avoid disastrous data loss, please remember to back up your VMs with reliable backup tools. Here I recommend you AOMEI Cyber Backup because it can manage VMs on both VMware and Hyper-V with affordable pricing.