In this article, we’ll show you how to migrate an existing Oracle VirtualBox virtual machine to Windows 10’s Hyper-V.

Migrate an Oracle VirtualBox Virtual Machine to Windows 10 Hyper-V

To begin, launch the VirtualBox Manager then select the virtual machine from the list pane you would like to export. Make sure the operating system you are exporting is supported by Hyper-V. Click the File menu then click Export Appliance…   Select the virtual machine again, then click Next.   Choose the location where you would like to store the virtual machine file, select the OFV 2.0 format then click Next.   Click Export then wait while the appliance is exported; this can take some time depending on the size of the virtual machine.   Before you can begin the conversion, we will need to use an uncompressing utility such as 7-zip to extract the contents of the OVF file we just exported.   Our next step is to import the VM into Microsoft’s Hyper-V software. Hyper-V does not natively support the Open Virtual Format. Initially, I attempted to convert the VM using Microsoft’s free utility called Virtual Machine Converter and the built-in PowerShell cmdlet. I experienced nothing but frustration getting it to work; see the proof below. I said to myself, “Forget this! There has got to be an easier way than going back to the age of Computer Chronicles.”   After some web searching, I came across a free utility from StarWind called V2V Image Converter designed just for converting different types of virtual hard disk formats. First, you need to sign up for the free download, which will be sent to you in an email link. After receiving your free download, proceed to download and set up StarWind Converter.   Launch the StarWind V2V Image Converter software then click Next.   Choose Local file as your source then click Next.   Choose the format you would like to convert the image to. Hyper-V supports VHD and VHDX formats. VHDX is an improvement over the older virtual hard disk format, supporting up to 64 TBs of storage. Because this is a Windows XP VM, I will stick with a fixed VHD option called VHD Pre-allocated image.

Browse to where on your hard disk you would like to store the converted image.   Select the destination of the VHD file. In my case, this will be used locally, so, I will stick with the default.

Wait while the VMDK file is converted. The larger the VHD, the longer it will take.

Import Virtual Machine into Hyper-V

The next step is to see if it works. Launch Hyper-V in Windows 10, click New > Virtual Machine then click Next. Go through the wizard and configure your virtual machine with the appropriate settings. When you arrive at the Connect Virtual Hard Disk section, choose “Use an existing virtual hard disk,” click Browse…, then open the VHD file we converted earlier then click Next.

Click Finish to confirm your configuration.

Proceed to launch your virtual machine and there you have it. Your Oracle VirtualBox VM is now up and running in Hyper-V.

That wasn’t so bad. Looking for more tutorials on VMs? Check out our post on connecting your virtual machine to the Internet. Also, if you prefer not to use the StarWind software, give the free Microsoft Virtual Machine Converter a try and let us know if you had any luck with it. Simply enter this command in an elevated command prompt: “C:\Program Files\Oracle\Virtualbox\VBoxManage” clonehd –format SourceFileName.vmdk TargetFileName.vhd Downloading and installing any additional converters for this is totally unnecessary. In this case, typing the sample command I forgot a very importand thing: after the –format switch you have to tell the format of new virtual disk, in this case VHD. That’s missing from my original comment. The correct command, this time copy & pasted from my OneNote notebook is: “C:\Program Files\Oracle\Virtualbox\VBoxManage” clonehd –format VHD SourceFileName.vmdk TargetFileName.vhd Once again, my apologies for the typo in my original comment. I noticed that this site transfers two subsequent – (minus) signs to one dash. The format switch in VBoxManage command is preceded by two minus signs, not a dash! Rich R With hyper v I’ve found online that I need to attach external USB disk manually each time I start the virtual machine. Exist a way to avoid this really annoying problem? Thank you. A few notes:

  1. I had to make a “Generation 1” Hyper-V VM for it to be able to boot. 2. The StarWind tool’s UI had changed dramatically in the last year. One thing to keep in mind – VirtualBox is ONLY free for personal use. Commercial use requires you to pay for it. I think it’s $50 USD? Comment Name * Email *

Δ  Save my name and email and send me emails as new comments are made to this post.

How to Migrate VirtualBox VMs to Windows 10 Hyper V - 33How to Migrate VirtualBox VMs to Windows 10 Hyper V - 1How to Migrate VirtualBox VMs to Windows 10 Hyper V - 50How to Migrate VirtualBox VMs to Windows 10 Hyper V - 49How to Migrate VirtualBox VMs to Windows 10 Hyper V - 9How to Migrate VirtualBox VMs to Windows 10 Hyper V - 47How to Migrate VirtualBox VMs to Windows 10 Hyper V - 72How to Migrate VirtualBox VMs to Windows 10 Hyper V - 9How to Migrate VirtualBox VMs to Windows 10 Hyper V - 13How to Migrate VirtualBox VMs to Windows 10 Hyper V - 12How to Migrate VirtualBox VMs to Windows 10 Hyper V - 91How to Migrate VirtualBox VMs to Windows 10 Hyper V - 95How to Migrate VirtualBox VMs to Windows 10 Hyper V - 11How to Migrate VirtualBox VMs to Windows 10 Hyper V - 54How to Migrate VirtualBox VMs to Windows 10 Hyper V - 11How to Migrate VirtualBox VMs to Windows 10 Hyper V - 21How to Migrate VirtualBox VMs to Windows 10 Hyper V - 21How to Migrate VirtualBox VMs to Windows 10 Hyper V - 72How to Migrate VirtualBox VMs to Windows 10 Hyper V - 44