Veeam: Restore/Migrate vSphere VM to Hyper-V

KB ID 0001559


I saw this question asked on EE the other day, and while I’ve done Migrating from vSphere to Microsoft before, I’ve never really tried with Veeam. Migrating and Restoring vSphere Machines to Azure is easy, but what about Hyper-V?


Veeam Backup and Recovery Download

Natively with Veeam Backup and Restore, the only way to do this, is to perform an Agent Based backup of your VMware VM. If you are unfamiliar with doing this,  you create a Protection Group, and add the machines to that protection group. It’s really designed for backing up physical machines, but there’s no reason you can’t backup a VM in the same way.

Just so you know it’s not smoke and mirrors. here’s my VM in vSphere.

Perform an ‘Agent Based‘ backup off this VM.

Veeam Backup via Agent

Restore > Agent Restore > Instant Recovery.

Veeam Instant Recovery

Select the VM > Next > Set the Hyper-V server as the ‘Host’.

Veeam Instant Recovery Select Host

Finish the ‘Wizard’, and perform the restore.

Veeam Instant Recovery Progress

You will need to complete the process by ‘Migrating to production’.

Instant Recovery Migrate to Production

Wait for the process to complete.

Instant Recovery Complete

And now it’s running in Hyper-V. 

VM Running in Hyper-V

I’d run devmgmt.msc and make sure all the drivers are OK. That being said, anything after server 2008 should have the correct drivers for Hyper-V, and Veeam does not support agent-based backups on Server 2008 (or earlier) so all ‘should’ be fine.

Related Articles, References, Credits, or External Links


Author: PeteLong

Share This Post On


  1. Felt the need to say thanks – this was an excellent tutorial. After 10 years of ESXI, and Storage Space Parity finally not sucking (with proper settings via Powershell) I’m moving back home to Hyper-V.

    Post a Reply
  2. Hi , thank you for this. i just did a successful migration from vmware to hyper v following your Guide.


    Post a Reply

Submit a Comment

Your email address will not be published. Required fields are marked *