Broadcom and VMware: your three options now

Broadcom's acquisition of VMware closed in November 2023. Eighteen months later the licensing model, the partner channel, the support framework, and the renewal pricing had all been restructured. If you are a VMware customer in 2026 you have three options now, and the decision is largely a function of whether you can be out of VMware in 24 to 36 months or whether you cannot.

The acquisition changed everything

Pre-acquisition VMware sold roughly 8,000 SKUs across product portfolios that had been built up through fifteen years of acquisitions. Post-acquisition Broadcom consolidated the catalog into a small number of bundled subscriptions: VMware Cloud Foundation (VCF) at the high end, vSphere Foundation in the middle, and a narrow set of point products underneath. The shift was from perpetual plus support to subscription only, from per-CPU to per-core minimum commitments, and from a partner-led channel to a direct-led one for enterprise accounts.

The commercial impact for the average enterprise customer is a 100 to 350 percent increase in run-rate cost on a comparable functional footprint. The variance depends on which legacy SKUs the customer was running, what their core counts look like under the new minimums, and whether they get rolled into VCF or held to a smaller bundle.

Option one: Renew on Broadcom's terms

The first option is to accept the new commercial framework, renew on VCF or vSphere Foundation, and absorb the increase. This is a defensible choice when migration risk is genuinely high (mission-critical workloads with deep VMware integration), when the migration runway is shorter than 18 months, or when the cost increase is contained because the customer's footprint maps cleanly to a smaller bundle.

The negotiation work in this option is about minimising the increase, not avoiding it. The levers are bundle selection (vSphere Foundation versus VCF), term length (longer terms get better unit pricing but reduce flexibility), commitment structure (firm versus ramp), and the ancillary clauses around audit, true-up, and renewal escalation. Done well this can hold the increase to 60 to 100 percent rather than 200 to 300 percent. Done poorly it lands at the upper end of the range.

Option two: Migrate off VMware over 24 to 36 months

The second option is to use the renewal cycle as a migration trigger. Sign a shorter renewal at higher unit cost in exchange for a defined exit window, and use the term to migrate workloads to alternatives. The alternatives in 2026 are credible: Nutanix AHV for the hyperconverged segment, Red Hat OpenShift Virtualization for the container-adjacent segment, hyperscaler-native virtualisation (AWS EC2, Azure, GCP) for cloud-eligible workloads, and Proxmox or Hyper-V for cost-sensitive midsize estates.

The economics work when the run-rate Broadcom increase is large enough that 18 to 24 months of higher subscription costs is repaid by the savings in years 3 onwards. For most enterprise customers the breakeven is between months 18 and 30, with steady-state savings thereafter of 40 to 70 percent on the affected footprint. The risk is execution. Migration projects miss timelines. The renewal needs to be structured to allow for a 6 to 12 month slip without falling off a cost cliff.

Option three: Hybrid, with VMware retained for a tier

The third option is the most common in practice. Retain VMware for the workloads where migration is genuinely difficult or strategically inadvisable, and migrate everything else. The retained tier is typically the production database estate, the legacy application footprint that is not container-ready, and the disaster recovery infrastructure. Everything else (development, test, edge, less-critical production, container-ready workloads) goes to alternatives over an 18 to 30 month window.

The commercial structure that supports this is a smaller-scope VMware renewal with strict footprint definition, combined with a multi-vendor migration to alternatives for the released capacity. The negotiation challenge is preventing Broadcom from minimum-commit-ing the customer back to the larger footprint. The solution is firm scope language tied to specific cluster identifiers, with no ramp commitment beyond the defined scope.

How to decide between the three

The decision tree has three nodes. First node: can you be out of VMware in 24 months on your most critical tier? If yes, option two becomes viable. If no, options one and three are the realistic candidates. Second node: is the run-rate cost increase containable to a smaller bundle? If yes, option one is defensible. If no, option three becomes more attractive. Third node: do you have the operating capacity to run a multi-vendor virtualisation estate? If yes, option three. If no, option one.

Most enterprises end up at option three, and the negotiation work is concentrated on tightly scoping the retained footprint. The customers who end up at option one have either a tight migration timeline that does not work or a workload portfolio that is genuinely VMware-locked. The customers at option two are typically those with strong container adoption, modern application portfolios, or hyperscaler-native strategies that pre-date the Broadcom transaction.

The clauses that matter

Whichever option is chosen, three clauses determine the multi-year exposure. The first is the renewal uplift cap, which limits annual price increase on existing scope. Without it, the customer is exposed to whatever pricing Broadcom announces at renewal. The second is the audit clause, which has tightened significantly under Broadcom's stewardship. The third is the exit clause, which under the new model is materially less generous than under VMware's pre-acquisition contracts and which therefore needs to be negotiated explicitly.

For a complete framework on negotiating with Broadcom in 2026, read The VMware Post-Acquisition Negotiation Playbook. For a worked example, read the UK media customer case study. Or request a confidential renewal review.

What to do this quarter

If your VMware contract renews in 2026 or 2027, this is the quarter to model the three options side by side with real numbers. The decision should be made on the cost-to-migrate analysis, not on a Broadcom proposal that arrives at the eleventh hour. Customers who let Broadcom set the timetable end up with worse outcomes than customers who set their own timetable and present Broadcom with a structured choice.