SCVMM VMware to Hyper-V Migration

Microsoft Platform Guide

Audience
Public
Source Type
Documentation

ESXi hosts must be in an OK, and not an ‘OK (limited)’ state in order to migrate a VM out of a particular ESXi cluster through SCVMM.

Note: If there is a problem during migration, such as the destination Hyper-V host does not have enough memory to power on a VM that has begun a migration, it may not complete the VM configuration and error after copying the disks. This can require extensive manual intervention. Check to ensure that the destination Hyper-V host has enough resources to power on the VM (CPU/Memory) before initiating the migration.

VMware Snapshots, IDE controllers, physical disks, and more are not supported for VM migration. Some configurations that may flag an ESXi host as “limited”, which will prevent migration are as follows:

  • If the vCenter Server has “Communicate with VMware ESX hosts in secure mode” enabled. Either uncheck this box, or a certificate and public key is required.

  • ESXi requires different credentials than vCenter. The vCenter credential will be applied to all hosts by default. Change the credential under the Management tab of the Host Properties.

  • A certificate has not been imported for this host. Import the certificate under the Management tab of the Host Properties.