You prepare by separating two decisions. The first is where your workloads will run. That one depends on Broadcom, your contracts, and your partners, and it may not be settled for years. The second is whether your team knows, trusts, and controls its own estate. That one depends only on you. The work that answers it is the same whether you renew, migrate, or run both: identify every system, connect them, clean the data, add application context, and set the guardrails. Those are the first five of our ten steps to autonomous IT operations, and they put you in a position to make the bigger decision on your terms, whenever it comes.
Here's why that matters this week. According to CRN, Broadcom has deauthorized Insight Enterprises, one of its top-tier VMware partners, from reselling VMware licenses and Broadcom-funded VMware Cloud Foundation services in North America. SDxCentral reports that Insight will stop delivering VMware licenses and VCF services to North American customers after October 31, and that Broadcom declined to comment. A year ago, Broadcom pointed customers seeking renewals to Insight as one of three national VMware providers.
If your renewal path ran through Insight, your plan just changed. If it didn't, you are probably asking the question every infrastructure leader we talk to is asking. What changes next, and when does it settle?
Why does the VMware landscape keep shifting under your plans?
Since the acquisition, the changes have come one after another. Licensing moved to subscriptions. Partner programs narrowed. Support timelines firmed up, with vSphere 8 general support ending on October 11, 2027. Access to tools that some migration products depended on changed, as we covered in our post on Broadcom pulling public access to VDDK. Each change landed on teams that had already made a plan.
The market is reacting, though more slowly than the headlines suggest. As The Register reports, Gartner's 2026 Magic Quadrant for Distributed Hybrid Infrastructure assumes that by 2029, 55% of enterprises will start proofs of concept for alternatives to their VMware deployments, up from 25% in 2026. That is a forecast about evaluation. It does not say 55% will leave. Gartner still rates VMware's core virtualization technology as a strength.
So most leaders are living in the middle. Unhappy with the uncertainty, and unconvinced that leaving is safer than staying.
Why do so many IT leaders stay with VMware?
Staying is often the rational call. The Register notes that many customers decide it is safer to stay with Broadcom longer while they build a plan. A platform exit is a large, risky program, and the risk is real.
But here's what we hear when we ask leaders what actually worries them. The concerns are rarely about the hypervisor.
- We don't have one trusted inventory. Several systems of record describe the same estate, and they disagree.
- Dependencies live in people's heads. Nobody can say with confidence what else a move will touch.
- Our team is already running the business. There is no spare capacity for a multi-year program.
- Our partner relationships may change before the program ends.
- If we start and it goes badly, we own the outage and the explanation.
Every one of these is a problem with data, context, or control. None of them is solved by picking a destination. And all of them make every option harder, including staying. A renewal negotiated without a clean picture of what you run is a renewal negotiated blind.
What can you control while the vendor landscape keeps moving?
Most estates are before Foundation today. That's the honest starting point, and it's where the controllable work lives. The first five steps get you there.
- Identify every system: List the systems of record you actually run, including the spreadsheets that fill the gaps.
- Connect them to an orchestration platform: Your systems of record stay where they are. One platform sees across all of them.
- Clean the data: Reconcile records that describe the same asset, and route every gap to someone who can close it.
- Add application context: Attach dependencies, ownership, usage, and lifecycle stage to every asset, so you can see what a change will touch before it runs.
- Set the guardrails: Decide who may do what, who approves, and turn on the audit trail before the first action.
Here's the thing. None of these steps assumes an answer about Broadcom.
|
Foundation step |
If you renew |
If you migrate |
If you run both |
|
Identify every system |
You size the renewal against what you actually run |
You scope the program from a complete list |
You know which estate holds what |
|
Clean the data |
You renew against records you trust |
Waves start from records you trust |
One view stays accurate across platforms |
|
Add application context |
You know what depends on each cluster |
You sequence waves by what each move will touch |
You can move workloads one application at a time |
|
Set the guardrails |
Changes in place are approved and recorded |
Every wave has an approval path and a record |
The same rules apply on both sides |
That is the core of our view. Running a business means constantly changing it, so day-to-day operations and large programs like a platform exit are the same motion. The foundation you build to run VMware well is the same one you need to leave it well.
Why does neutrality matter during a vendor shake-up?
When a vendor reshapes its channel, the knowledge of your estate should not sit with any one vendor or reseller. An Agentic ITOps platform cannot be one of the vendors it manages. ReadyWorks earns nothing from where workloads run, what is bought, or what is decommissioned. Your systems of record stay. Your partner relationships stay too. Work with the partner you know, on the platform you keep.
If you do decide to move, the roles stay clear. On VirtualReady, ReadyAI analyzes the estate, recommends waves, and plans the program. A named delivery team executes it, whether that is a services partner, ReadyWorks when engaged to deliver, or your own engineers, with your sign-off at every phase. AI-planned. Expert-delivered.
Where does agentic AI fit for a team that wants to move carefully?
Caution and AI are compatible. The journey is built for it. ReadyAI today works at the Assisted stage: it recommends, a person approves, and the action runs within the guardrails the organization sets. Every action is logged, explainable, and covered by a tamper-evident audit trail.
ReadyWorks meets you where you are and delivers value at every stage. You set the pace. Every stage runs on the same platform. Hand more of the work to ReadyAI as your confidence grows, and keep as much in your team's hands as you want. For a leader facing a vendor decision with no clear end date, that matters. You can start building capability now without committing to an outcome you aren't ready to choose.
How do you find your starting point?
We built the Map your own module on our journey page for exactly this moment. It asks eight questions about your estate as it is today: how many systems of record you run, how large the estate is, the program in front of you, how changes are approved, how much you trust the data, whether you can see application dependencies, how you bring owners and users along, and where AI sits in your operations.
Pick a VMware exit or virtualization migration as your first program, or pick day-to-day operations if you plan to stay for now. Either way, it lays out the ten steps as they apply to you: your first five steps, your first program, your first governed actions, how long it takes, who does the work, and what you gain. You can save it as a PDF to forward to the people who need to be part of the decision.
Map Your Journey Before the Next Announcement
Nobody outside Broadcom knows what the next change will be. You don't need to. The leaders who come through this period well will be the ones who used it to get their estate known, clean, and governed, so that every option stays open and every decision rests on facts.
Map your journey, or talk to someone who has done this.
Frequently Asked Questions
How do you prepare for Broadcom uncertainty if you aren't ready to leave VMware?
Separate the platform decision from the readiness work. Identify every system, connect them, clean the data, add application context, and set the guardrails. That work helps whether you renew, migrate, or run both, and it leaves you ready to decide on your own timeline.
What happened between Broadcom and Insight?
According to CRN, Broadcom deauthorized Insight Enterprises from reselling VMware licenses and Broadcom-funded VCF services in North America. SDxCentral reports that Insight will stop delivering those licenses and services after October 31, and that Broadcom declined to comment.
Is Gartner predicting that 55% of enterprises will leave VMware?
No. Gartner's assumption, as reported by The Register, is that 55% of enterprises will start proofs of concept for alternatives by 2029, up from 25% in 2026. That is a forecast about evaluation, not completed exits.
Do we have to choose a destination before we start?
No. The first five of the ten steps are the same for every estate and every destination. Most estates are before Foundation today, so that is where most of the useful work begins.
Does ReadyWorks replace our VMware partner or our systems of record?
No. Your systems of record stay where they are, and you can work with the partner you know. ReadyWorks is neutral and earns nothing from where workloads run or what is bought.
What does the Map your own module give us?
Eight questions about your estate produce the ten steps mapped to your situation: your first five steps, your first program, your first governed actions, a timeline, who does the work, and what you gain, with a PDF you can forward.
