The Transaction That Changes the Infrastructure Conversation
Broadcom’s announced acquisition of VMware for approximately $61 billion is not primarily a story about a semiconductor company buying a software business. It is a signal about the structural dynamics of the enterprise infrastructure market, and every CIO and CTO with significant VMware investment should be reading it carefully.
Broadcom has a documented playbook from its acquisitions of CA Technologies and Symantec. It focuses acquired software businesses on their most profitable enterprise customer segments, rationalises the product portfolio to concentrate investment in the highest-margin offerings, and adjusts pricing models to extract more value from the installed base. The pattern is commercially rational and operationally disruptive for the customers in its path.
VMware’s installed base is among the most deeply embedded in enterprise IT. vSphere underpins virtualisation in data centres across European enterprises that have been building on it for fifteen years. NSX handles network virtualisation in organisations where the network team has invested years learning its operational model. vSAN underpins storage in hyperconverged deployments where the alternatives were evaluated and rejected a decade ago. The switching cost is real, which is precisely what makes the installed base valuable to an acquirer applying price and packaging pressure.
This is not speculation about Broadcom’s intentions. It is an extrapolation from observable behaviour across previous acquisitions. Enterprise technology leaders who are surprised by what follows the acquisition close will have chosen to ignore the available evidence.
The Questions CIOs Should Be Asking Now
The acquisition has not yet closed, and the product and licensing changes that typically follow Broadcom acquisitions are not yet confirmed for VMware specifically. But the strategic planning questions that the acquisition raises do not require regulatory approval to begin answering.
The first question is concentration risk. What proportion of the critical infrastructure estate runs on VMware, and what would replacement require in terms of cost, timeline, and operational disruption? Most large enterprises have never quantified this exposure precisely, because until recently there was no strategic reason to do so. The acquisition provides the reason. An honest inventory of VMware dependency is the starting point for any contingency planning.
The second question is contract timing. Existing VMware customer agreements carry specific renewal terms, pricing protections, and support commitments. Understanding when current agreements expire and what renewal conditions look like is urgent. Agreements renewed before the acquisition close, or in the period immediately after when standard terms are still being offered, may provide significantly better long-run commercial conditions than agreements renewed after the acquired business has been restructured.
The third question is strategic optionality. For each major VMware dependency, what are the credible alternatives, at what cost, and over what migration timeline? This is not a recommendation to migrate immediately. It is a recommendation to have an answer to this question before it becomes urgent. The enterprise that does not know what replacing vSphere would require cannot assess whether staying on the platform under new commercial conditions is preferable to migration.
The Competitive Dynamics the Acquisition Creates
VMware’s position in the infrastructure market has been challenged by the hyperscalers for several years, but the combination of migration complexity and operational familiarity has preserved its installed base. The Broadcom acquisition changes the competitive calculus in ways that may accelerate the workload migration the hyperscalers have been unable to drive through feature appeal alone.
If Broadcom moves VMware toward enterprise-focused, premium-priced offerings with reduced investment in mid-market capabilities, the organisations currently running VMware in smaller or less complex deployments face a genuine choice: pay more for capabilities that have been repriced, or migrate to alternatives that were previously considered but rejected.
The alternatives are more credible in 2022 than they were five years ago. Hyperscaler migration has matured. Managed Kubernetes services have reduced the operational complexity of running containerised workloads without a traditional hypervisor layer. HCI alternatives from multiple vendors have improved. The competitive alternatives to VMware are not perfect substitutes, and the migration complexity should not be underestimated, but they are viable options for a broader range of workloads and organisations than was true at the time of the last major VMware contract cycle.
The acquisition also creates commercial leverage that enterprise customers should understand how to use. A supplier that faces genuine competitive alternatives treats contract negotiations differently from one that does not. Whether or not VMware alternatives are the right strategic choice for a given organisation, building credible knowledge of those alternatives strengthens the negotiating position in the VMware conversation.
What Infrastructure Strategy Looks Like After This Transaction
The Broadcom–VMware acquisition is a forcing function for something that good enterprise infrastructure strategy should have been doing anyway: maintaining a clear understanding of vendor dependency, building optionality into architecture decisions, and treating infrastructure platform relationships as strategic vendor relationships that require active management rather than passive renewal.
The enterprises that will navigate the post-acquisition landscape best are those that go into it with current, accurate knowledge of their VMware footprint, realistic options for the most strategically significant workloads, and commercial relationships with their VMware account team that have been actively managed rather than left to auto-renew.
The enterprises that will struggle are those that have allowed VMware dependency to accumulate without assessment, assumed that pricing and packaging would remain stable because they always had, and treated infrastructure vendor relationships as technical decisions rather than strategic ones.
The transaction is still pending regulatory approval as of this writing. The strategic planning it demands does not wait for the close.