VMware Licensing in Private Equity Portfolios

Private equity is now Broadcom's single most aggressive customer segment for VMware licensing intervention. There are concrete reasons for this. A PE-owned company is often levered, almost always reorganising, frequently carving in or out subsidiaries, and almost certain to have a transaction in the next three to five years. Each of those events is a contractual trigger that Broadcom can use to surface a re-licensing or audit conversation. And the deal calendar — the part operating partners care about — gives Broadcom leverage that other vendors lack.

This article is written for three audiences. First, operating partners and portfolio CIOs who are inheriting VMware estates inside their portfolio companies. Second, deal teams running diligence on a target that is a heavy VMware shop. Third, founder-CEOs who have just sold to a PE buyer and are about to discover that their VMware contract reads differently to a sponsor-owned business than it did to an independent one.

Why PE portfolios are exposed

The exposure is structural, not behavioural. Even a PE-owned business with disciplined IT governance and a clean VMware estate runs into Broadcom friction because of how the contracts are written.

Change-of-control clauses. Almost every VMware master agreement signed in the past decade contains a change-of-control provision. Pre-Broadcom, these clauses were interpreted permissively — VMware would consent to assignment in the ordinary course, often without commercial demand. Post-acquisition, Broadcom has narrowed its interpretation. Sponsor acquisitions, secondary sales, recapitalisations, and even some minority investments now routinely trigger formal consent requests, and consent is increasingly conditioned on a re-licensing event.

Transferability of perpetual entitlement. Perpetual VMware licences are nominally transferable subject to "reasonable consent". Broadcom's working definition of reasonable now includes upgrading the buyer's environment to VCF, paying a transfer fee, or signing a multi-year subscription commitment. For a sponsor that has just paid 12x EBITDA for a software-heavy carve-out, an unexpected mid-seven-figure VMware bill at close is not a welcome surprise.

The Limited Purpose Use clause. Most VMware EULAs restrict use to the named licensee and its "affiliates" — typically defined as entities under more than 50% common ownership. PE-owned platform companies frequently fail this test on day one of a closing, because the platform now sits under a new fund vehicle. Subsidiaries that were previously affiliates may no longer be, and vice versa.

Audit cadence is correlated to transactions. We track audit letter dates against PitchBook deal data and the correlation is no longer subtle. The probability that a PE-owned VMware customer receives a Broadcom compliance contact within twelve months of a closing or refinancing is roughly three times the probability for a non-PE owned customer of comparable size.

Change-of-control: what actually triggers it

Operating partners assume change-of-control is binary — either it triggered or it did not. The reality is more granular, and the granularity matters because Broadcom will assert a trigger in situations where the contract language is genuinely ambiguous.

Transactions that almost always trigger

A full sale of the platform company to a different sponsor triggers nearly every change-of-control clause we have seen. So does a take-private or a take-public transaction (going either direction). A sale of a subsidiary that is itself a VMware contracting party — for example, a divisional carve-out where the divested entity holds the master agreement — triggers a transfer event for that contract.

Transactions where it depends on drafting

A secondary sale between two funds of the same sponsor sometimes triggers, sometimes does not — depending on whether the contract defines control by ultimate beneficial ownership, by direct ownership, or by general partner identity. Recapitalisations where the GP rolls the asset into a continuation vehicle are similarly drafting-dependent.

Minority investments are typically safe unless the investor acquires governance rights that meet the contract's definition of control. A board seat plus consent rights over major decisions can, in some VMware contracts, qualify as control.

Transactions that should not trigger but sometimes do

Internal reorganisations — moving the contracting entity within a corporate group, redomiciling, or merging two sister entities — should not trigger change-of-control on most drafting. Broadcom has nonetheless asserted triggers in some of these scenarios. The defence is contractual rather than commercial: read the clause, identify the parties, and confirm that no party listed in the agreement has actually changed.

The diligence question that gets skipped

VMware estates are rarely flagged as material during deal diligence. They show up as a line item in the IT operating expense schedule and a question about hypervisor in the technology assessment. Neither captures the embedded contractual exposure.

The diligence questions that should be asked, and rarely are, include the following. What is the current support and subscription expiry date on each VMware contract? Are any perpetual entitlements present, and if so, what is the SnS continuation status? Has the target received any Broadcom compliance or licensing review communication in the past 18 months? Are any contracts under "soft audit" or self-assessment? What is the contractual transferability language for each agreement? Have any deployments expanded since the last entitlement true-up?

The diligence answer that should be received, and rarely is, includes a documented entitlement-versus-deployment reconciliation, a list of any open compliance threads with Broadcom, and a written assessment of change-of-control risk on close.

How Broadcom approaches a transaction it has detected

Broadcom is now systematically monitoring deal announcements that involve VMware customers. The outreach pattern is consistent enough that we treat it as a known sequence.

The first communication is usually informal — an account executive emails the named contact at the target asking for "a quick alignment call to discuss the transaction." This conversation is the most expensive call the new owner will ever take if it is handled without preparation. The account executive will reference the change-of-control clause, suggest that consent is required, and propose a meeting with Broadcom's compliance team.

The second communication, if the first does not produce a commercial response, is a formal letter from Broadcom requesting consent to assignment, citing the contractual basis, and proposing terms. The terms are usually a commitment to migrate to VCF, a multi-year subscription, and a discount-to-list that looks attractive but is anchored to a list price that has tripled.

The third communication is an audit notice. By the time the audit letter arrives, the customer has typically been asked twice and refused twice. The audit is the enforcement mechanism for the consent demand.

The defence playbook for sponsor-owned businesses

Defence in a PE context is different from defence in an enterprise context. The differences are not legal — they are temporal. PE-owned businesses live on a deal calendar. The single most important defensive move is to align the VMware position with the deal calendar.

Before the transaction closes

Treat VMware as a diligence item. Read the change-of-control clauses on every VMware contract held by the target. Identify the perpetual entitlements (which transfer subject to consent) and the subscription entitlements (which often do not transfer at all without a re-papering event). Run an entitlement-versus-deployment reconciliation. If a true-up is needed, include it in the working capital adjustment rather than discovering it in year one.

At close

Notify Broadcom on a schedule of the buyer's choosing, not Broadcom's. Most contracts require notice within 30 days of close. The notice should be brief, written, and limited to the facts the contract requires — the identity of the assignee, the date of closing, and the request for consent. Do not volunteer detail about the transaction structure, the buyer's strategy, or the platform's expansion plans.

In the first 90 days

Expect outreach. Do not accept a self-assessment or licensing review request without legal review. Reaffirm the contractual notice obligations and request that any data exchange occur under the audit clause, not informally. Engage independent counsel and an independent licensing advisor on day one — not after the second letter.

Through the hold period

Treat the VMware contract as a managed risk, not a fixed cost. Renewals should be timed to avoid coincidence with refinancings or major strategic events. SnS continuity decisions should be made deliberately, with the exit timing in mind — letting SnS lapse 18 months before a sale is rarely the right move because the buyer will inherit the lapse risk.

Approaching exit

Clean up the VMware position 12-18 months before sale. Ensure that all entitlements are documented, all deployments are within entitlement, all renewals are current, and all open Broadcom threads are closed. A clean position is worth real EBITDA multiple at exit because the buyer's diligence will surface what yours did not, and the price chip will exceed the cost of remediation.

Carve-outs: a special case worth detailing

Carve-outs are the highest-friction VMware transactions in a PE context. A divisional carve-out from a corporate parent creates a NewCo that needs entitlement on day one, usually under a transition services agreement (TSA) with the parent that is intended to expire within 12-24 months.

The fundamental problem is that VMware entitlements typically do not split cleanly. A parent that licenced VMware enterprise-wide cannot, without Broadcom's consent, hand the NewCo a proportional slice of that entitlement. The TSA period is therefore expensive — the NewCo is using software that it is not, in Broadcom's view, licensed for.

The carve-out defence has three legs. First, structure the TSA so that the parent remains the licensed user of any shared infrastructure for the full TSA duration, with the NewCo as a permitted user under the parent's agreement. Second, plan and budget for a NewCo licence purchase well before TSA expiry — list price will be the opening Broadcom position, and a 12-month negotiating window is the minimum required to move that meaningfully. Third, evaluate alternatives early. A carve-out is the rare moment when a hypervisor migration may be commercially preferable to a VMware re-licensing.

Add-ons and roll-ups: the entitlement merge problem

Add-on acquisitions create the inverse problem. A platform company with a clean VMware position acquires a smaller target. The target has its own VMware entitlements, possibly with different SKU mix, different SnS dates, and a different reseller of record. Broadcom's preferred outcome is to merge the entitlements onto a new VCF subscription sized for the combined entity. This is rarely the most economical outcome.

The defence is to maintain the legacy contracts intact for as long as practical, run them in parallel through their natural renewal cycles, and only consolidate when the consolidation produces a commercial benefit to the customer (better discount, longer term, lower aggregate price). Broadcom will resist the parallel-run approach. Persistence and contractual literalism produce results.

Continuation vehicles and secondary transactions

Continuation vehicles have become a meaningful share of PE exits. From a VMware contract standpoint, they are usually — but not always — a change-of-control event. The drafting matters: if the contract defines control by reference to the GP, and the GP is the same in the continuation vehicle, the trigger may not fire. If control is defined by reference to the holding entity, the trigger fires even though commercially nothing has changed.

The right approach is to read the clauses before announcing the continuation vehicle, not after. Where the trigger is ambiguous, Broadcom will assert it; where the trigger is clearly absent, Broadcom will usually concede if pressed.

The four numbers every portfolio CIO should know

If you run IT inside a sponsor-owned business and you are unsure where your VMware risk sits, four numbers tell most of the story.

SnS expiry on each contract. This determines your renewal cycle, your audit risk window, and your migration runway.

Total core count under VMware management. This is the unit of pricing under post-acquisition Broadcom. Every reasonable defence starts from a verified core count, not an SKU count.

Percentage of estate that is perpetual versus subscription. Perpetual entitlement is more defensible in an audit but more vulnerable in a transaction. Subscription is the reverse.

Days since last entitlement-vs-deployment reconciliation. If this number is greater than 365, you do not currently know your position. Most PE-owned IT functions are above 365.

What sponsors actually save by getting this right

Across our PE-portfolio engagements, the typical avoided cost on a Broadcom intervention triggered by a transaction is between $1.2M and $6M, depending on portfolio size. The largest single avoided cost we have documented was $11.4M on a take-private of a mid-cap software business with a heavy VMware footprint. The smallest meaningful intervention saved a $400M revenue add-on $640K on what would otherwise have been a forced VCF migration at close.

These are not theoretical numbers. They are the difference between a transaction that performs to model and one that loses three to six months of management attention to a vendor dispute the deal team did not see coming.

The bottom line

Broadcom has built a commercial machine that treats PE-owned VMware customers as a high-yield segment. The contractual and operational realities of sponsor ownership — change-of-control, frequent transactions, affiliate definitions, TSAs, continuation vehicles — give Broadcom more triggers than it has with any other customer cohort.

The defence is not a single tactic. It is a programme: diligence before close, careful notice management at close, disciplined contract administration through hold, and clean-up before exit. Portfolio companies that run this programme rarely pay material unplanned costs to Broadcom. Portfolio companies that do not are paying for the lesson.

For a confidential portfolio-level assessment of your Broadcom exposure across one or many holdings, Contact us →. We provide written diligence opinions, response playbooks for active audits, and pre-exit clean-up programmes scoped to the deal calendar.