VMware to Hyper-V migration on temp server

You would either need Veeam on the temp host to be able to read the restore points to recover them into Hyper-V, or you would need to use Veeam to convert them to Hyper-V VMs on storage that you could use on the temp server to bring them up or copy them to local storage to run them.

​@tibarra - question is where is your current Veeam server? Do you currently have/own Veeam to make the backups? If you currently have Veeam, simply perform an Instant Recovery of a current backup of your VMs from VMW to Hyper-V. The User Guide covers this:

https://helpcenter.veeam.com/docs/vbr/userguide/instant_recovery_to_hv.html?ver=13

If you don’t currently use Veeam (VBR), you will need to spin a VM up on the Hyper-V server and assign storage to it either directly and use the Veeam “Default Repository” (it creates during install), or add a “Managed Server” with storage on it to your VBR server, and assign the Repository role to this server. Personally, since you only have 10 VMs though, I’d just add storage for your VBR server. Then, create a backup job, add all your VMs to this Job, and back them up to this Repository. When you’re ready to migrate your VMs to this new Host, run this Backup Job then power off your VMs (if you’re able) so they’re current. Get your new Host up & going with Hyper-V, then perform an Instant Recovery of those backups to your new Hyper-V server.

Hope that helps.

The only thing I’ll add to Shane’s advice is to remove VM Tools prior to the migration. If you remove them after it will complain about not being able to reach a vSphere host once on Hyper-V. We scripted removal after migrations but it far easier just to remove them beforehand. 

Agreed Eric; and that goes with migration to any hypervisor. If you don’t remove Tools initially, you tend to run into issues (mainly Windows VMs).

Since you're planning a transition from VMware to Hyper-V, the most critical part of your plan is ensuring that your backup repository or target storage for the migration/recovery/conversion/Instant Recovery_ is accessible to the Hyper-V host or a new Veeam instance.

If you've got an ability to run a Veeam Backup & Replication (VBR) server, I'd suggest setting up a VBR instance on that temp server as well. This allows you to use Instant Recovery to Hyper-/Hyper-V directly from your existing backups.

One thing to check: are you planning to using an existing backup repository that is already accessible via the network or shared storage? If so, you enough information to perform the Instant Recovery.