We recently hosted a live webinar where we walked through a real VM migration from vCenter to Private Cloud Director using vJailbreak, and the response was overwhelming. Not just in attendance, but in the quality of questions and the post-event survey data. The audience wasn’t just browsing. They were planning.
In this post, I’d like to cover the key themes that came out of both the webinar itself and the attendee feedback, because they paint a clear picture of what organizations are actually worried about when it comes to leaving VMware.
The Migration Isn’t the Hard Part. The Planning Is.
We’ve developed a five-phase sequencing model for a successful VMware exit:
- Assessment
- Parity & Compatibility Mapping
- Provisioning
- Migration
- Maintenance
These phases are detailed in our companion solution brief, “What to Expect When You’re Exiting” and the webinar reinforced exactly why the model matters. What we’ve seen time and again is that teams want to jump straight to phase four (the actual migration) without fully working through the first three.
That’s where projects stall. Discovery is more than pulling a VM inventory list. It’s understanding the connective tissue of your environment: multi-tier application dependencies, backup and DR integrations, storage relationships, security tooling, and observability hooks. If you haven’t mapped those relationships, you’re going to find out about them the hard way – during a change window at 2 AM.
The survey data backs this up. The top migration concerns attendees reported were preserving network identity (IP and MAC addresses), handling complex multi-tier applications, minimizing downtime, ensuring data integrity, and having a reliable rollback path. These aren’t migration problems. They’re planning steps.
“Non-Destructive” Was the Feature That Resonated Most
When we asked attendees which vJailbreak features stood out, the non-destructive migration process was the clear winner. And it makes sense. Your source VM stays exactly where it is, untouched. vJailbreak takes a snapshot, copies the data, converts the disk format, and handles driver changes. If the destination VM doesn’t behave the way you expect, you power it off and power the source back on. Zero damage.
That reversibility is what turns a high-stakes cutover into a low-drama event. During the webinar, Dave Gilinsky, Head of Professional Services and Cloud Support here at Platform9, showed the source VM sitting powered off in vCenter after the migration completed. The VMDK was still there. If we needed to, we could have powered it right back up. That kind of safety net changes the risk calculus for migration planning entirely.
Warm Migration Changes the Scheduling Conversation
Another feature that really resonated with the crowd was warm migration with change block tracking (CBT). This is the capability that lets you start copying data in the background while the source VM is still running. CBT tracks which blocks change on the source disk, so when you’re ready to cut over, vJailbreak only needs to sync the last few minutes of changes.
In practical terms, this means you can schedule data copies to happen during off-peak hours, then schedule the actual cutover for a maintenance window. The final switchover becomes a brief restart rather than a multi-hour data transfer. For organizations running applications across time zones and shifts, this kind of scheduling flexibility is the difference between a migration project that takes months and one that takes weeks.
Your Existing Hardware Still Works
This one consistently surprises people. You don’t need to buy new hyperconverged infrastructure to leave VMware. Private Cloud Director works with your existing x86 servers and SAN/NAS storage. That means no waiting on procurement, no rack-and-stack delays, and no multi-million dollar capital expenditure as a prerequisite for even starting the migration.
vJailbreak can even do in-place host conversions, taking an ESXi host and converting it to a Private Cloud Director hypervisor, then migrating the VMs that used to run on that host. This eliminates one of the biggest logistical bottlenecks we see in large migration projects: waiting for new hardware to arrive before you can begin.
The Audience Is Ready. They Want to Go Deeper.
The post-webinar survey told us something important. The vast majority of attendees rated their interest in Private Cloud Director as a VMware replacement at 4 or 5 out of 5. Most are actively planning a migration or evaluating their options. And the content requests were specific: HA demonstrations, storage configuration walkthroughs, performance comparisons between VMware and PCD workloads, and day-to-day operational workflows.
These are the kinds of topics we’re actively exploring for future sessions — hands-on demonstrations, real-world configuration scenarios, performance validation, and operational workflows that help teams make confident decisions. Expect to see us go deeper in the areas that matter most to practitioners evaluating a VMware alternative.
The conversation has moved past “should we leave VMware?” and into “how do we execute this well?” That’s a healthy place to be, and it’s where we think we can be the most helpful.
What’s Next
If you missed the webinar, we’ve also published a solution brief called “What to Expect When You’re Exiting” that walks through the five-phase migration model in detail, including the risks at each phase and the KPIs you should define before you start. It’s a good read for anyone building a business case or scoping a migration project internally.
If you want to see vJailbreak in action, we’d love to show you. Reach out and we can set up a guided walkthrough tailored to your environment.
