The following migrations are not recommended, but can be performed with some limitations.

• Exchange should be migrated by installing newer versions of Exchange Server in parallel with existing production environments, then move user mailboxes from the old system to the new one.

• Domain controllers should be migrated by preparing a new domain controller, and then migrating the Flexible Single Master Operations (FSMO) roles.

• Move migrates database VMs similar to any other VMs;however, the migration happens at the VM level, not the application level.

• Move will not perform any application-level changes, disk layout updates or best practices on the migrated VM.

• The above approach should be fine for smaller SQL DB servers and for servers without PCI Pass-through, pRDM disks or multi-writer disks (clustered NTFS).

• Also, for larger SQL DB servers, Nutanix recommends you to apply Nutanix best practices to create additional vDisks and rebalance data across those disks to take advantage of the parallel nature of Nutanix distributed storage.

• Time taken for migration depends on the size of the VM, data churn rate within the VM during migration and network bandwidth/connectivity between source and on-prem data center.

• VMs managed by citrix Hypervisor are known to have issues after migration.

Unsupported Features

• IPV6

• VM names with non-English characters.

• VM names with single and double quotes.

• Windows VM installed with running antivirus software. 

• Antivirus software prevents the installation of the VirtIO drivers.

• Guest operating systems with deduplication enabled.

• In case of Hyper-V source VMs, logical 4K aligned VHDX images are not supported.

For more information, please refer: Move Overview