If you're planning to leave vSphere after the Broadcom licensing changes, this matters. If you were hoping to download the tool this afternoon, it doesn't help yet.
What's GA and what's still preview
Two different release states are in play here:
- vMode is generally available. Microsoft's companion announcement from November 16 says Windows Admin Center: Virtualization Mode (vMode) is now generally available and ready for your production environments! Released as part of Windows Admin Center version 2611, a single vMode instance can manage up to 1,000 Hyper-V hosts and 25,000 VMs. Those numbers cover vMode's management scale. They are not migration limits for VM Conversion.
- VM Conversion is private preview only. The GA post describes it as a feature that is coming to vMode in private preview, bringing VMware ESXi-to-Hyper-V migration into the same experience you use to manage your virtualization environment.
Access goes through the Windows Server Technology Adoption Program (TAP). Microsoft asks interested organizations to fill out the Windows Server TAP interest form with their contact details, organization name and validation interests, and to list "VM Conversion in vMode" as an area they want to evaluate. Microsoft hasn't announced a public download, a GA date or support commitments for this preview.
Section summary: vMode 2611 is production-ready. The migration tool inside it is gated behind TAP.
Why the old extension disappeared
The original tool had a short history. Microsoft introduced it in public preview as an agentless, cost-free tool for converting VMware VMs to Windows Server with Hyper-V, available in the public feed of Windows Admin Center. You can install it directly from the Extensions settings in Windows Admin Center. Its setup requirements included VMware PowerCLI on the gateway and a VDDK package placed in the Windows Admin Center service directory.
That VDDK requirement caused the problem. NTCompatible's coverage of the Windows Admin Center 2610 preview reported that Microsoft pulled the extension from the feed, and that the cause is a Broadcom change jamming up availability of the Virtual Disk Development Kit (VDDK), which the extension depends on. In other words, the tool for leaving VMware depended on a VMware component that Broadcom controls. That was always a weak point.
Microsoft's new announcement doesn't say whether the appliance-based design removes the VDDK dependency. It only says the appliance reads source disks through HotAdd, so don't assume more than that until the documentation is published. The redesign does explain the timing: the old extension has been gone since the 2610 preview, and this is its official replacement.
Section summary: The extension disappeared because of the VDDK availability problem. The appliance model is how Microsoft is bringing migration back.
How the appliance-based workflow works
According to Microsoft's description, the new VM Conversion works like this:
- Deploy an appliance on each source ESXi host. A Windows appliance VM must run on every ESXi host that holds VMs you're migrating. Windows Admin Center walks you through onboarding the appliance and automates its registration and configuration. You can follow each step in the workflow status pane.
- Read disks via HotAdd. The appliance attaches the source VM's disks through HotAdd and uses changed-block tracking (CBT) to synchronize disk data.
- Run prechecks. Microsoft says improved prechecks verify that source and destination environments are ready before synchronization begins. The individual checks aren't listed.
- Sync ahead of cutover. Data can be synchronized before the maintenance window.
- Cut over. During migration, the tool runs a delta sync while the source VM is still running, powers off the source VM, runs a final sync to capture the remaining changes, and then brings the workload online on Hyper-V.
You launch the workflow from a resource group's More options (...) menu in vMode.
The sequence is familiar if you used the old extension, which also did a full copy while the VM ran and then used CBT deltas for a short cutover. What's new is the per-host appliance and HotAdd disk access. Older guidance recommended putting the gateway in the same site as the ESXi and Hyper-V hosts to reduce WAN traffic. The new design moves the disk-reading work onto the ESXi hosts themselves, but Microsoft hasn't published network-path requirements for the new design, so treat this as a likely benefit rather than a confirmed one.
Section summary: You get one appliance per ESXi host, HotAdd plus CBT for data movement, and a delta-then-final-sync cutover designed to keep downtime short. Microsoft hasn't given a downtime figure.
Batching: ten VMs per flow
A single flow lets you select up to 10 VMs and start synchronization or migration as a batch. One sensible pattern is to sync a group during business hours and then trigger the cutover for those VMs during the maintenance window.
Batching doesn't hide individual VMs. The workflow status pane shows each VM's synchronization and migration progress, which operations have finished, and which workloads need attention. Microsoft says you can see completed checks, the step currently running, elapsed time and synchronization percentages, instead of a single "in progress" label.
Some practical points for planning:
- Group by dependency. Ten VMs per flow fits a typical application tier: web front ends, an app server and a database. Moving an app stack together avoids a period where half the application runs on each hypervisor.
- Microsoft hasn't explained dependency ordering. The announcement doesn't say whether the tool sequences VMs within a batch. If your database has to come up before the app tier, plan that order yourself.
- Larger estates will need several flows. Migrating 400 VMs means a long series of batches, so a migration runbook is still essential.
Section summary: Batches of 10 VMs with per-VM visibility suit app-stack migrations. Ordering within a batch is still your job.
Gaps to fill before you build a plan
The announcement leaves out several details enterprise teams will need:
| Question | Status in Microsoft's announcement |
|---|---|
| Supported ESXi versions | Not specified |
| Supported guest operating systems | Not specified |
| Appliance sizing and network requirements | Not specified |
| vCenter-level connectivity | Not mentioned; the post describes ESXi hosts |
| Static IP preservation, Linux driver prerequisites | Not stated for the new implementation |
| Expected cutover downtime | Not quantified |
| Licensing and support terms for the preview | Not stated |
The old extension's documentation listed vCenter 6.x through 8.x support, a guest OS matrix, static IP preservation and a requirement to install Hyper-V drivers in Linux guests beforehand. That documentation describes a different implementation that has now been retired. Don't assume those capabilities carry over until Microsoft publishes vMode-specific documentation. Joining the TAP is the way to get answers.
After migration: managing the VMs in vMode
Microsoft's position is that migration is the transition, not the endpoint. Once a VM runs on Hyper-V, vMode manages it alongside the hosts, clusters, storage and networking it depends on, through Compute, Storage and Network views. Resource groups organize infrastructure by site, environment or workload. According to the GA announcement, they don't nest, and each host belongs to exactly one group.
Role-based access control limits who can view or manage resources within an assigned scope. Existing Windows permissions on the hosts still apply, so vMode roles don't replace local admin rights. The 2611 release also adds Azure Arc onboarding, built-in backup and restore of the vMode management database, and certificate management through Active Directory Certificate Services. That keeps most post-migration management in vMode.
Analysis: a credible approach that's still behind a gate
This announcement makes Microsoft's Hyper-V pitch more complete. Migration is now built into the free management plane where the migrated VMs will be managed afterwards. The appliance design also looks like a direct response to the VDDK problem that removed the last tool.
There are reasons for caution. Microsoft's roadmaps for this tool have shifted before: the original extension went from public preview to removal, and the replacement starts in a narrower private preview. Administrators with VMware renewal deadlines approaching should keep proven alternatives in their plans for now. They should also treat vMode-native conversion as something to validate in TAP, not as the tool to build a 2027 cutover schedule around today.
What to do now:
- Deploy or upgrade to Windows Admin Center 2611 in vMode and onboard your target Hyper-V hosts and clusters.
- Group your VMware inventory into dependency-based batches of 10 or fewer.
- Plan capacity for a Windows appliance VM on every source ESXi host.
- Apply to the Windows Server TAP and list VM Conversion in vMode as your evaluation area.
- Press Microsoft for the compatibility matrix before you commit to any production cutover dates.
The tool now runs inside vMode, but access is limited to Microsoft's TAP for the time being.
References
- VM Conversion is now in Windows Admin Center: Virtualization Mode Windows Admin Center Blog · 2026-11-17T15:00:00+00:00
- Windows Admin Center 2610 Preview Merges Two Installers into One ntcompatible.com
- VM Conversion Extension in Windows Admin Center (Preview) | Microsoft Learn learn.microsoft.com