Why does vHOP bypass VDDK, now restricted by Broadcom?

FluidCloud developed vHOP (VM Hopping Engine) in response to the restriction imposed by Broadcom on the use of the VMware Virtual Disk Development Kit (VDDK). Since August 2026, Broadcom has limited licensed access to VDDK to only backup and recovery operations, according to Network World. This decision has complicated VMware migrations, as VDDK was widely used to copy virtual disks before transferring them to other environments.

vHOP avoids this issue by using VMware ESXi standard APIs via the Network File Copy (NFC) protocol, as explained by FluidCloud. Unlike VDDK, this approach does not depend on Broadcom’s licensing restrictions, while offering improved performance: up to 2 times faster for restoration and image creation, according to FluidCloud’s internal tests.

vHOP converts security rules and network dependencies into Terraform code in three days, allowing teams to know exactly what they are moving before even choosing a disk-copy tool.

How does vHOP automate network and security policy translation?

One of the major challenges of VMware migrations lies in translating network configurations and security rules, often complex and poorly documented. vHOP addresses this issue by integrating an agentless discovery of virtual machines, networks, NSX groups, and firewall policies through VMware vCenter and NSX Manager APIs. This data is then translated into Terraform modules for the target cloud, as Yahoo Finance reports.

This feature allows IT teams to generate a target architecture plan, a firewall migration plan, and infrastructure code before transferring data. vHOP also identifies third-party tools dependent on VDDK in the current ecosystem, avoiding incompatibilities. For example, NSX rules are converted into equivalents for AWS, Azure, Google Cloud, or Oracle Cloud Infrastructure (OCI), while flagging potential quota limits.

What performance and scalability does vHOP offer for large-scale migrations?

FluidCloud highlights vHOP’s ability to handle large volumes of virtual machines in a single operation. According to Network World, vHOP can migrate over 1,000 virtual machines in a single batch, a performance enabled by optimized transfers via compressed snapshots. These snapshots reduce transferred data by a factor of 5x by copying only modified disk blocks, thus speeding up the process.

Two versions of vHOP are available: a self-service option that generates a plan in minutes, ideal for simple migrations, and an engineer-led version offering in-depth analysis over three days, including full network dependency mapping and security policy reviews. The latter is particularly suited for critical environments where precision and planning are paramount.

What this means here: opportunities for businesses and governments in West Africa

For West African businesses and governments, many of which still rely on VMware for critical infrastructure, vHOP could provide a viable solution to reduce Broadcom dependency while easing migrations to public clouds or hybrid environments. With VDDK restrictions, local organizations risk being stalled in modernization or multi-cloud diversification efforts, especially if they use third-party tools dependent on this technology.

vHOP would enable Beninese and regional IT departments to plan more secure migrations to platforms like AWS or Azure, often chosen for critical workloads, or to Google Cloud for less sensitive projects. The automated translation of NSX policies into Terraform would reduce human error risks during network reconfiguration, a major concern in environments where IT resources are sometimes limited. Finally, the ability to process hundreds of VMs in a single operation could accelerate infrastructure consolidation projects, a recurring need in African administrations seeking efficiency.

However, vHOP adoption will depend on the maturity of local IT teams to leverage Terraform-based tools and complex APIs. Targeted training or technical partnerships may be required to fully capitalize on this solution.