Blog Post

Windows Admin Center Blog
3 MIN READ

VM Conversion is now in Windows Admin Center: Virtualization Mode

Priya_Satheesh's avatar
Nov 17, 2026

VM Conversion is now available in private preview inside the generally available version of Windows Admin Center Virtualization Mode (vMode), helping you move virtual machines from VMware ESXi hosts to Hyper-V hosts. 

The preview brings ESXi-to-Hyper-V migration into vMode, with prechecks, synchronization ahead of cutover, and detailed workflow status, followed by ongoing management of the destination environment. 

Note: The earlier preview VM Conversion extension (Preview) was removed from the extension feed, and this appliance-based implementation in vMode is its replacement. 

How VM Conversion works in vMode 

VM Conversion uses an appliance-based approach to move virtual machines from VMware ESXi hosts to Hyper-V hosts. A Windows appliance VM must reside on each ESXi host that hosts the source VMs being migrated. Windows Admin Center guides you through onboarding the appliance VM and automates its registration and configuration, reducing manual intervention. You can follow each step in the workflow status pane.  

The appliance VM accesses the source disks from the source virtual machine through HotAdd and uses changed-block tracking to synchronize data of the source disks. This reduces the data remaining to transfer during cutover, helping limit the time the source VM needs to be offline. Improved prechecks also help you verify that the source and destination environments are ready before data synchronization begins. 

Access VM Conversion from the resource group's More options (...) menu. 

 

                Image 1: Access VM Conversion from the resource group menu in vMode. 

Workflow orchestration status 

VM Conversion builds on vMode's workflow orchestration visibility to help you follow data synchronization and migration in detail. In thest Workflow status pane, you can see completed checks, the step currently running, and progress through disk synchronization and final cutover. Step-level status, elapsed time, and synchronization percentages give you more context than a single "in progress" indicator, making it easier to track each workload and keep your team informed throughout the move. 

 

                Image 2: VM synchronization workflow steps as seen in Windows Admin Center. 

Move multiple VMs in one flow 

When your migration plan involves several virtual machines, starting each VM operation separately adds repetitive work and increases the risk of error. The flow lets you select up to 10 VMs and initiate synchronization or migration as a batch, so you don't have to repeat the process for every virtual machine. You can synchronize data ahead of cutover, then initiate migration for the selected VMs during the maintenance window. 

Batch operations still give you visibility into each VM. Through workflow orchestration status, you can follow individual synchronization and migration progress, see which operations have completed, and identify workloads that need attention. This helps you coordinate the move across a group of VMs without losing track of each virtual machine. 

Plan synchronization and cutover 

Enterprise VMs are often large, with data that changes daily. Planning their migration involves more than completing the initial transfer: teams also need to account for ongoing changes and schedule cutover within a maintenance window. 

During migration, VM Conversion performs a delta synchronization to transfer incremental changes while the source VM is still running. It then powers off the source VM and performs a final synchronization to capture the remaining changes before bringing the workload online on Hyper-V. Transferring most changes before shutdown helps limit the time the VM needs to be offline and supports business continuity. 

Manage the workloads beyond the move 

Once a VM is running on Hyper-V, day-to-day management extends beyond the VM itself to the hosts, clusters, storage, and networking it depends on. vMode brings these together in one place, with Compute, Storage, and Network views to help your team manage the workload in the context of its supporting infrastructure. 

Resource groups let you organize infrastructure by site, environment, or workload. Role-based access control determines who can view or manage resources within an assigned scope, while existing Windows permissions on the hosts still apply. For supported management operations, workflow status provides visibility into progress, individual steps, and errors that need attention. 

Migration is the transition, not the endpoint. Once the workload is running on Hyper-V, vMode gives your team a consistent place to manage the VM and the infrastructure it depends on 

Get started 

If you would like to try the VM Conversion tool in vMode, express your interest in joining the Windows Server Technology Adoption Program (TAP) by completing the Windows Server TAP interest form. Provide your contact details, organization name, and validation interests, and include VM Conversion in vMode as an area you would like to evaluate. 

Published Nov 17, 2026
Version 1.0
No CommentsBe the first to comment