Migrating VMware virtual machines with SCVMM.

SCVMM 2022 SQL Express support is not documented in the provided context. The context only covers V2V conversion enhancements, VMware-to-Hyper-V conversion steps, and related prerequisites, but does not specify supported SQL Server editions for the VMM database.

For migrating VMware workloads (including domain controllers or Exchange VMs) to Hyper-V using SCVMM, the documented guidance is to use the built-in V2V conversion capabilities:

1. Bring the vCenter server and ESXi hosts under SCVMM management.
   • In the VMM console, under Fabric > Servers, add the VMware vCenter Server using a Run As account with vSphere administrator rights.
   • After adding vCenter, ESXi hosts and their VMs are discovered and managed by VMM.
   • Ensure host status is OK or OK (limited); if limited, import the ESXi certificates or adjust the secure communication setting.
2. Use SCVMM’s V2V conversion to migrate VMware VMs to Hyper-V.
   • SCVMM provides a wizard-based experience to convert VMware VMs in the VMM fabric to Hyper-V.
   • Review prerequisites and limitations before converting:
     • Only supported vCenter/ESXi versions can be converted.
     • VMware Workstation VMs can’t be converted.
     • VMs with virtual hard disks on an IDE bus can’t be converted.
     • VMware Tools must be uninstalled from the guest OS before conversion.
     • VMs on vSAN storage can’t be converted.
     • Online conversions aren’t supported; conversions are offline.
   • For performance and scale, VMM 2025 is recommended for up to four times faster conversion and improved experience.
3. Use SCVMM 2022 V2V performance enhancements where applicable.
   • With System Center Virtual Machine Manager 2022 UR1 and hotfix KB5030053, V2V conversion from VMware to Hyper-V is 3–4 times faster and supports VMware VMs with disks larger than 2 TB.
   • The hotfix is a manual patch (not via Windows Update) and requires backing up and replacing specific SCVMM binaries on the VMM server and Hyper-V hosts.

The context does not provide SCVMM-specific procedures for migrating Active Directory or Exchange beyond treating them as standard VMware VMs for V2V conversion. It only documents the generic VMware-to-Hyper-V migration path via SCVMM.

References:

• SCVMM V2V Conversion Enhancements
• Convert a VMware VM to Hyper-V in the VMM fabric
• Deploy and manage Azure Local instances in VMM
• Windows 11 VM doesn't start after migration from VMware to Hyper-V