FluidCloud Launches vHOP to Help Exit VMware
The new package maps VMware estates and prepares migrations to five public and private cloud platforms without relying on VDDK.
Updated on Nov. 11, 2026 in Software

FluidCloud has launched vHOP, a package designed to map VMware environments and prepare migrations before workload data moves. The package is available through the FluidCloud platform and supports AWS, Microsoft Azure, Google Cloud, Oracle Cloud Infrastructure and Nutanix.
Why it matters
Some companies are reassessing migration plans after changes affecting access to the VMware Virtual Disk Development Kit, which many agentless migration tools have relied on to read virtual disks. Broadcom has said licensed use of VDDK has always been backup and recovery and is not a customer entitlement.
vHOP maps a VMware estate, translates NSX firewall policy and generates Terraform for a target cloud without using VDDK. NSX distributed firewall rules default to allow-all, while AWS security groups support only allow rules, a difference the translation must address.
The players
FluidCloud
FluidCloud is the vendor that markets its migration process as "Cloud Cloning" and offers vHOP through its platform.
Broadcom
Broadcom is the company that owns VMware and has stated that licensed use of VDDK has always been backup and recovery and is not a customer entitlement.
The details
vHOP produces a target architecture, a firewall migration plan and infrastructure code used to build the destination environment. Customers can use a self-service version for a plan in minutes or work with FluidCloud engineers, whose engineer-led version includes read-only discovery through vCentre and NSX Manager application programming interfaces, a review of tools that depend on VDDK, and Terraform modules for the destination cloud.
Timeline
Launch reported on November 11, 2026.
Software Shift
The launch follows Broadcom's statement that VDDK licensing covers backup and recovery only, pushing agentless migration tools that depend on VDDK to re-examine their architecture. vHOP's approach of translating NSX firewall policy into AWS security group rules illustrates the kind of rework such migrations now require.
IT teams planning to leave VMware can use vHOP's plan-first approach to scope migrations before moving data, rather than discovering dependencies mid-project. The engineer-led option's three-day timeline suggests a faster path to a migration plan than manual scoping.
The takeaway
Teams should audit which migration, backup and disaster recovery tools depend on VDDK before committing to an exit plan. Planning dependencies first can prevent costly surprises once data movement begins.
Further reading
For broader coverage of how enterprise software platforms are changing, see the Software section.
Source note: This article includes information reported by IT Brief Australia.



