An acquisition announcement is a free option on your exit plan

The week

On May 26, 2022, Broadcom announced an agreement to acquire VMware in a cash-and-stock deal widely reported at about 61 billion dollars. VMware’s hypervisor and management software ran a large share of on-premises data centers in banks, health systems and public agencies, often underneath core banking, electronic health record and case management systems. Broadcom had earlier bought CA Technologies and Symantec’s enterprise security business, and customers of those products had seen changes in focus, licensing and support afterward. The VMware deal needed regulatory approval in several jurisdictions and did not close until November 2023. In the announcement week itself, nothing changed for customers except the outlook.

Infrastructure teams usually react to a supplier acquisition in one of two ways: alarm that fades, or a decision to wait and see. For a platform as embedded as VMware, both were expensive. The better frame comes from finance. An announcement that precedes closing by many months hands every customer a cheap option. Nothing yet depends on the new owner’s decisions, contracts are still on known terms, and the cost of preparing an alternative is lowest when there is no deadline. Like any option, it has value only if someone pays the small premium to hold it. We break that into three steps: buying the option by pricing a credible exit, keeping it alive with modest ongoing investment, and exercising it, or deciding not to, at the moment terms change.

Buying the option: price the exit

An exit that has not been priced is not an option. It is a hope. The first step is to know what the organization actually owns and what leaving would cost.

Start with entitlements. Many institutions held a mix of perpetual licenses with annual support, enterprise agreements, and products bought through resellers or bundled with hardware, with support renewals scattered across the year. A clean entitlement inventory lists each product, edition, quantity, support end date and the clusters and workloads it supports. That inventory alone often reveals unused licenses and add-ons renewed out of habit.

Then estimate migration cost by workload class. A typical estate splits into three groups. Some workloads are already candidates for public cloud or a managed platform. Some can move to another hypervisor with moderate effort. Some are pinned in place by a software vendor that certifies its product only on one stack, or by disaster recovery designs built on a specific replication product. For each group, a rough cost covers engineering effort, parallel running, retraining and the audit evidence that must be produced again: recovery tests, configuration baselines and access reviews.

The pinned group needs a conversation outside IT. Clinical system vendors, core banking providers and case management suppliers decide which platforms they support. Asking them in 2022 for their certification roadmap, and recording the answer, turned an unknown into a dated dependency.

Keeping the option alive

Options decay if nothing is spent on them. An exit plan written in 2022 and filed away would be stale by the time terms changed. Keeping it alive takes a few deliberate, modest investments.

The most valuable is a small production pilot on an alternative platform. Running a handful of non-critical workloads elsewhere builds skills, runbooks and monitoring, and it tests the assumptions in the cost estimate. Without it, the alternative exists on paper and the team’s estimate of migration effort is a guess. The trade-off is real: a pilot costs licenses, staff time and some operational complexity. It is still far cheaper than discovering at renewal that no one on staff can run anything else.

A second investment is contract hygiene. Aligning support renewal dates, where that can be done on acceptable terms, creates a single decision point instead of a dozen small ones. Some organizations chose to renew early on known terms for workloads they were sure would stay. That is a legitimate use of the window, as long as it is a choice based on the priced exit rather than a reflex.

The third is architecture discipline for new work. Every new system built on hypervisor-specific features deepens the lock-in. Asking design reviews to justify platform-specific dependencies, and to prefer portable tooling for backup, automation and monitoring where the cost is similar, keeps the exit price from rising while the deal is pending.

Exercising the option

An option is exercised when the payoff exceeds the cost. For an infrastructure platform, the trigger is a concrete change in terms: a new price at renewal, a product retired, a support model altered. At that moment the organization compares the new cost of staying with the priced cost of leaving, workload class by workload class.

The answer is rarely all or nothing. A common outcome is a partial exercise: move the workloads that were already easy to move, renegotiate for the pinned ones, and use the credible threat of the first to improve the terms of the second. Suppliers respond to evidence that a customer can leave. A pilot in production and a dated migration plan are that evidence. A slide that says the organization is evaluating alternatives is not.

Public agencies need one more element. Procurement vehicles, competition rules and fiscal-year budgets set their own timelines, often longer than the commercial ones. Starting the procurement groundwork for an alternative, such as market research and draft requirements, during the window kept the option exercisable on the agency’s calendar.

The same discipline applies beyond virtualization. Every regulated organization has a handful of suppliers whose products sit under nearly everything else: identity, productivity, core platforms and databases. Each deserves a standing, priced exit assessment, refreshed every year or two, so that the next ownership change starts from known numbers.

With hindsight

The deal closed in November 2023, and the changes that followed were substantial. Broadcom ended the sale of perpetual licenses in favor of subscriptions, consolidated a long product list into a few bundles, and reworked its partner and reseller programs. Many customers reported much higher costs at renewal. A large U.S. telecom customer sued over support renewals in 2024 before settling, and European cloud providers lodged complaints with regulators. Some organizations accelerated moves to public cloud or other hypervisors, while many stayed and absorbed the increases because their exit had never been priced or tested. By 2026 the episode is a standard case in vendor concentration planning. Customers with a pilot in production and a dated plan generally had more room to negotiate. Those that waited to see had one practical choice.