The News
Nutanix has released Move version 6.3.3, introducing a new migration method called DirectPath that transfers VM disk data directly from VMware ESXi hosts to Nutanix AHV without requiring VMware’s Virtual Disk Development Kit (VDDK). The release is a direct response to Broadcom’s decision to remove public VDDK downloads following its acquisition of VMware. Move 6.3.3 supports ESXi versions 6.5 through 8.0 U3, multiple vCenter releases including 9.0, and current Nutanix AOS and Prism Central versions, though it requires a fresh deployment and does not support upgrades to or from this specific version.
Analyst Take
The Broadcom effect is accelerating VMware exits
Broadcom’s acquisition of VMware has been a slow-moving earthquake for enterprise infrastructure. Nutanix Move 6.3.3 is a pointed, tactical response to one of the most immediate technical blockers customers face when they decide to act. The message to the market is straightforward: Nutanix is actively engineering around Broadcom’s decisions so its customers don’t have to.
For ITDMs, the business case here is about removing the last excuse not to migrate. Before DirectPath, a customer who had decided to exit VMware still faced a concrete technical hurdle: sourcing and manually uploading VDDK libraries into the Move appliance. That kind of friction, while seemingly minor, is exactly the kind of procedural obstacle that kills migration momentum inside large organizations. DirectPath aims to eliminate it. The migration workflow itself remains unchanged, which means existing runbooks, training, and muscle memory carry forward.
What DirectPath actually changes for practitioners
For engineers and architects, the architectural shift in this release deserves attention. DirectPath repositions the Nutanix Move appliance inside the source VMware ESXi environment rather than operating as an external observer. Move now requires direct access to the shared datastore containing source VM disks, which changes network topology requirements and potentially affects how migrations are sequenced in environments with strict segmentation policies. The efficiency gain, fewer intermediary data-path operations, is real, but teams should validate datastore access permissions and shared storage configurations before assuming a drop-in deployment.
The compatibility matrix is broad and practically covers the VMware estate that most enterprise customers are actually running. ESXi 6.5 through 8.0 U3 and vCenter up to 9.0 means very few production environments are excluded. The absence of upgrade support from this version is a constraint worth planning around, particularly for shops that rely on in-place appliance updates as part of their change management processes.
The procurement and integration context
Migrations of this kind don’t happen in isolation, and the organizational dynamics surrounding them matter as much as the tooling. According to ECI Research’s Google GovTech Survey, 40.8% of respondents said interoperability with other legacy downstream systems is the biggest bottleneck when modernizing, which reflects exactly the kind of environment where a VM migration tool is necessary but not sufficient. Moving a workload from ESXi to AHV is step one; integrating that workload with surrounding systems, many of which may still carry VMware-specific dependencies, is the harder problem.
At the same time, ECI Research’s Google GovTech Survey found that 55.4% of respondents said 26% to 50% of their current application development budget is consumed by simply maintaining legacy technical debt. That figure reframes the economics of migration. The cost of staying on VMware under Broadcom’s new pricing and licensing model is not just a line item on an infrastructure invoice; it compounds into reduced capacity for new development. Organizations absorbing that budget pressure have a stronger financial argument for migration than they did two years ago. DirectPath makes the technical path shorter. The financial pressure is already there.
Looking Ahead
Nutanix has signaled that Move will continue to evolve with additional migration paths, and that trajectory matters. The VMware-to-AHV path is the most commercially urgent right now, but the longer-term value of Move as a platform depends on how broadly Nutanix extends its source compatibility. Migrations from Hyper-V, KVM, and cloud-based VMs are natural adjacencies, and any expansion there would position Move as a general-purpose migration fabric rather than a point solution for VMware exits.
For vendors competing in this space, Nutanix’s willingness to engineer around Broadcom’s partner restrictions sets a competitive standard. Customers evaluating migration tooling will increasingly expect vendors to absorb that kind of ecosystem friction rather than pass it back to the buyer. Nutanix has made a credible move in that direction with 6.3.3. Whether it sustains that engineering investment as the VMware migration wave matures will determine how durable the competitive advantage is.
Stay Ahead of Application Development Trends
Get weekly analyst insights, research notes, event coverage, and AppDevANGLE updates delivered directly to your inbox.
Subscribe for Weekly Insights
Join technology leaders, practitioners, and GTM teams following the trends shaping modern software delivery.
Looking for deeper research access?
Explore ECI Research reports, survey insights, and market analysis through the ECI Research Portal.
