The Broadcom acquisition of VMware is disrupting the entire virtualization market. For many organizations the new world order just doesn’t work: licensing costs have ballooned, support models have shifted, and the long-term roadmap feels murkier than ever. The fallout is an urgent wave of VMware displacement that shows no signs of slowing down.
For Managed Service Providers, this may be the biggest opportunity in a decade. Enterprises of all sizes are looking for a trusted partner to guide them through the migration . They need someone who can handle the technical complexity, manage the risk, and get them to the other side without disrupting production workloads.
But here’s the challenge: most MSPs aren’t yet equipped to execute these migrations at scale. Migrating a handful of VMs manually is one thing. Migrating hundreds or thousands of VMs across multiple client environments — without burning through delivery margin — requires a fundamentally different approach.
That’s where vJailbreak comes in. Built by Platform9 and released as a free, open-source tool, vJailbreak is the migration engine that makes enterprise-scale VMware displacement not just possible, but repeatable and predictable. This guide is written for MSP technical leads and practice managers who want to understand how the tool works, how to run it at scale, and how to turn it into a sustainable service offering.
Why Traditional Migration Approaches Break Down at Scale
Many MSPs have run a VMware migration at some point. You inventory the VMs, export them, re-import them on the new platform, validate connectivity, and hand it back to the client. For a small environment with a handful of VMs, this works fine.
But scale that model to hundreds or thousands of VMs across multiple simultaneous client engagements, and the cracks appear fast.
The labor math stops working
Manual migration is fundamentally a labor-intensive process. Each VM requires individual attention: configuration export, storage remapping, network reconfiguration, driver handling, and post-migration validation. At even 10–20 VMs per engineer per day, the staffing costs quickly erode project margins — especially when you’re competing on price.
Downtime tolerance is unforgiving
Enterprise clients have zero patience for unexpected downtime. Traditional migration approaches require maintenance windows that are difficult to schedule and even harder to execute cleanly when dealing with complex workloads, shared storage, or stateful applications. One bad cutover on a high-profile client can define your firm’s reputation.
Knowledge doesn’t scale
Manual migrations accumulate tribal knowledge. The engineer who figured out the quirks of a client’s NetApp configuration or their Windows Server 2016 driver stack becomes a single point of failure. When that person rolls off the engagement, you start from scratch on the next one. There’s no repeatability, no compounding efficiency.
The “shadow work” problem
Without proper tooling, a significant portion of migration project time goes into work that doesn’t directly create value: writing one-off scripts, researching compatibility issues, manually tracking migration status across spreadsheets, and managing client communication about every individual VM. This shadow work kills margin and delays delivery.
The MSPs who will win the VMware displacement wave aren’t the ones who migrate VMs fastest by hand. They’re the ones who build a migration practice around tooling that eliminates the shadow work and makes every engagement run like the last one.
How vJailbreak Works — A Technical Overview for MSPs
vJailbreak is a free, open-source migration tool built specifically to automate the movement of VMware virtual machines to Platform9 Private Cloud Director (which runs on OpenStack). Here’s what MSPs need to understand about how it actually works under the hood.
Architecture: No agents, no drama
vJailbreak runs as a VM inside the target Private Cloud Director environment. From there, it connects remotely to the source VMware vCenter environment using the VMware VDDK (Virtual Disk Development Kit) library. Critically, there are no agents to install on client VMs, and no changes required to the source VMware environment. This dramatically reduces pre-migration prep time and eliminates a whole category of compatibility risk.
Automatic VM discovery
Once connected to vCenter, vJailbreak automatically discovers all VMs in the environment along with their associated metadata, storage configuration, and network setup. For an MSP scoping a migration project, this is enormously valuable — you get a complete inventory of exactly what needs to move before you write a single line of the statement of work.
Change Block Tracking (CBT) for near-zero downtime
vJailbreak uses VMware’s Change Block Tracking technology to keep source and target VM disks continuously synchronized during the migration process. This means the actual “cutover” window — the moment when the client VM goes offline and flips to the new environment — can be measured in seconds or minutes, not hours. For clients with tight downtime tolerance, this is the feature that makes the conversation possible.
Automatic driver and tools conversion
One of the most labor-intensive parts of any VMware migration is handling guest tools and device drivers. vJailbreak handles this automatically on the fly: VMware guest tools are replaced with the appropriate KVM/OpenStack equivalents, and device drivers are converted without manual intervention. This works across most popular Linux and Windows versions.
Seamless cutover and identity preservation
When vJailbreak executes a cutover, it preserves the VM’s system identifiers, network configuration, and external storage connections. From the application’s perspective — and from the perspective of other systems on the network — the VM is the same machine it always was. This “invisible migration” behavior is essential for keeping clients calm and minimizing post-migration validation work.
In-Place Cluster Conversion: The MSP power feature
For MSPs doing full datacenter transitions, vJailbreak’s cluster conversion capability is a game-changer. Rather than requiring new hardware for the target environment, vJailbreak can migrate VMs off an ESXi host, reimage that host as a Private Cloud Director node, and bring it into the new cluster, all without disrupting running workloads. This means clients can exit VMware entirely using their existing hardware, which removes one of the biggest objections to full migration projects.
Parallel scaling
For large environments, vJailbreak can scale horizontally: deploy multiple instances running simultaneously to hit the throughput targets your project timeline requires. The Fortune 500 case study cited above — 200 VMs per day — was achieved through this parallel architecture.
What Makes vJailbreak Different
There are other migration tools on the market. Here’s why vJailbreak stands apart for MSPs specifically.
It’s free — and that changes the economics of migration projects
Most commercial migration tools charge per-VM licensing fees. At scale, those fees become a major line item in your project cost structure — one that either reduces your margin or gets passed to the client, reducing your price competitiveness. vJailbreak has no per-VM licensing cost. The tool is free to download, free to deploy, and free to run as many times as you need across as many client engagements as you have. That’s a structural margin advantage.
Open source means no black-box surprises
vJailbreak’s complete source code is publicly available on GitHub. For MSPs, this matters in two ways. First, you can inspect exactly what the tool does before running it in a client production environment — no surprises, no undisclosed behaviors. Second, if you hit an edge case that the tool doesn’t handle out of the box, you have the option to contribute a fix or work around it at the code level, rather than waiting for a vendor to respond to a support ticket.
The time reduction is real
Platform9 has validated that vJailbreak reduces total migration time, by 70% compared to manual approaches, with half the personnel requirements. In practical terms for an MSP: a project that would have required three engineers over six weeks can be executed by one or two engineers over two weeks. That’s not just a cost saving — it’s a capacity multiplier that lets you take on more concurrent client engagements without growing headcount.
Building a Repeatable Migration Practice
The difference between an MSP that runs a few successful one-off migration projects and an MSP that builds a durable, high-margin migration practice is repeatability. Here’s how to cross that line.
Productize the engagement
Once you’ve run vJailbreak through two or three client engagements, you have enough data to build a fixed-fee pricing model. Price per VM, with tiering based on complexity: Linux VMs with simple storage are cheaper than Windows VMs with RDM disks and complex network configurations. Fixed-fee pricing is easier to sell, easier to budget for clients, and more profitable than time-and-materials once your team is efficient with the tooling.
Standardize your runbook
The seven-step workflow described in this blog is a starting point. After your first few engagements, you’ll have a richer version specific to your team’s tools, your preferred wave sizing, your validation checklist, and the common edge cases you’ve seen. Document it. A shared runbook means every engineer on your team can execute a migration project with the same quality and predictability, regardless of whether they’ve personally done it before.
Use the Platform9 partner program
Platform9 has built a partner program specifically designed to help MSPs build a migration practice. As a Platform9 partner, you get access to NFR licenses for running your own demo and training environment, hands-on lab access, migration services training that covers vJailbreak end-to-end, and co-branded sales collateral. You don’t have to build the go-to-market from scratch — Platform9 has done a significant portion of that work already.
The migration is the door opener, not the destination
This is the strategic point that separates a short-term project revenue stream from a long-term managed services business. Clients who migrate off VMware to Platform9 Private Cloud Director land on a platform that requires ongoing management, day-2 operations support, capacity planning, Kubernetes cluster management, and more. The migration is the door opener. The managed private cloud service is the recurring revenue.
MSPs who position themselves as not just migration executors but as long-term private cloud partners will capture significantly more lifetime value from each client relationship than those who treat the migration as a one-time project.
The Window Is Open — Move Now
The VMware displacement wave is happening right now. Enterprises at every scale are actively looking for migration partners, and the window for MSPs to establish themselves as the go-to provider in this space is wide open — but it won’t stay open forever. The MSPs who move quickly to build the capability will capture disproportionate market share. The ones who wait will find themselves competing on price in a commoditized market.
vJailbreak removes the biggest barriers to building that capability: technical risk, delivery cost, and the dependency on scarce engineering expertise. It’s free, it’s open, and it’s been proven at Fortune 500 scale. The migration economics — $35 per VM, 200 VMs per day, 70% time reduction — make the business case straightforward.
Your VMware clients are facing the Broadcom tax and will be looking for more solutions. With Platform9 and vJailbreak you can be the provider of that solution. Read the vJailbreak documentation and see how you can plan and execute a low-risk migration for your clients.
If you’re still evaluating whether Private Cloud Director is the right platform for your provider environment, our service provider hub walks through the platform comparison, pricing model, and migration path in detail.
Got questions? Reach out and talk to us. We’re happy to help you make your clients’ VMware exits as smooth as possible.
