Software vendor acquisitions have become one of the defining commercial risks for enterprise IT buyers. The Broadcom acquisition of VMware — which resulted in forced subscription migration, massive price increases, and the end of perpetual licensing — is only the most visible example of a pattern playing out across the enterprise software market. Change of control provisions in your contracts are your primary protection against an acquirer imposing terms that are materially worse than those you negotiated with the original vendor.
This article is part of our IT Contract Negotiation Strategy guide. Change of control provisions interact with termination for convenience rights (which allow exit when a relationship is no longer commercially viable), software escrow arrangements (which provide operational continuity in the event of vendor failure), IP ownership provisions, and benchmarking clauses. See our contract negotiation checklist for a comprehensive review framework.
Enterprise software contracts are long-term relationships. A five-year enterprise agreement or outsourcing contract concluded with one vendor may, by the time it reaches renewal, be under the ownership of a completely different organisation with different commercial priorities, different support philosophies, and different pricing strategies. Without contractual protections negotiated at the outset, the buyer has no recourse when this happens.
The operational risks of an unprotected change of control are significant. The acquirer may: immediately change pricing terms at the next renewal (often with limited notice); discontinue the product in favour of a competing product in their portfolio; reduce support quality or end-of-life the platform on an accelerated timeline; impose new licensing metrics that create significant additional cost; or require migration to a different platform within a compressed timeframe. Each of these outcomes can impose costs measured in tens of millions of pounds for large enterprise deployments.
Broadcom's 2023 acquisition of VMware is the defining recent example of change-of-control risk in enterprise software. Within 12 months of closing, Broadcom had: eliminated perpetual licensing; forced all customers onto VCF subscription bundles at prices 2–5× the previous per-product cost; discontinued most standalone products; ended channel partner relationships; and significantly reduced support options. Customers with strong change-of-control provisions — consent rights, price protection, and termination rights — were significantly better positioned to negotiate transition arrangements or exercise exit options. Those without such provisions faced the full commercial impact with no contractual leverage.
Defining the change of control trigger is the first critical negotiation. Vendor-standard language typically defines change of control narrowly — often as the acquisition of more than 50% of voting shares — and may exclude internal restructurings, IPOs, and acquisitions of the parent company rather than the contracting entity. Buyer-favourable triggers should be broader.
The trigger definition should include: acquisition of more than 25% (not 50%) of voting power or economic interest by a single acquirer; any transaction resulting in the replacement of a majority of the board; merger with or acquisition by a competitor of the buyer; acquisition by a private equity firm (which significantly changes the vendor's commercial priorities even if the product and team remain the same); and any internal restructuring that transfers the contract to a different entity within the vendor group, particularly one operating in a different jurisdiction.
The 25% threshold (versus the vendor-preferred 50%) is important because PE firms and strategic investors often acquire significant minority stakes that give them effective operational control without triggering a 50% threshold. The Broadcom/VMware deal, and many PE-backed software company acquisitions, would have met a 25% threshold well before the commercial changes took effect.
Once a change of control trigger is defined, the contract must specify what rights the buyer has upon that trigger. There are several distinct rights worth negotiating, which should be clearly distinguishable from each other.
The minimum right is a notification obligation — requiring the vendor to notify the buyer of a change of control within a defined period (typically 30 days of completion or public announcement). This is the easiest to negotiate and the least commercially valuable on its own, but it is a prerequisite for exercising any other rights.
A stronger protection is the right to consent to the assignment of the contract resulting from the change of control. If the buyer does not consent, the contract cannot be assigned to the acquirer. This is a powerful commercial lever — but vendors resist it strongly because it could complicate M&A transactions. In practice, consent rights are most achievable for smaller vendors and for contracts where the buyer has significant leverage (large contract value, strategic reference customer status). For large platform vendors, a watered-down version — the right not to unreasonably withhold consent, with specific listed circumstances in which withholding is reasonable — is more achievable.
A renegotiation right entitles the buyer to renegotiate key commercial terms (pricing, support levels, product roadmap commitments) following a change of control. This is a practical middle ground — it does not give the buyer a veto but does ensure that the buyer cannot simply be presented with a new price list by the acquirer without any contractual recourse. Renegotiation rights should include a specific timeframe (90–180 days) and a fallback (right to terminate without penalty if agreement cannot be reached).
The most powerful protection is the right to terminate the contract — without penalty, early termination charges, or wind-down fees — following a change of control. This is particularly valuable when combined with a transition assistance obligation (requiring the vendor to continue operating and supporting the software for 12–24 months post-notice, to allow the buyer time to migrate). Termination rights following change of control are achievable in many enterprise contracts, particularly where the buyer has meaningful negotiating leverage at the time of initial contract signature.
Even where full consent or termination rights are not achievable, buyers should negotiate specific price and commercial term protections that survive a change of control. These provisions should specify that: the acquirer is bound by the pricing agreed in the original contract for the remaining contract term; any price increases following a change of control are limited to those already contracted (e.g., the agreed annual escalation mechanism); the acquirer cannot alter the licensing metric, support level, or maintenance obligations without the buyer's consent; and the acquirer must honour all commitments in the contract including product roadmap commitments made during the original negotiation.
Price protection after acquisition is typically easier to negotiate than consent or termination rights, because it does not threaten the vendor's ability to complete the transaction — it merely limits the acquirer's ability to immediately extract additional value from the customer base. For buyers who cannot achieve stronger protections, price protection for the remaining contract term (combined with aggressive benchmarking rights) provides a meaningful floor.
| Vendor / Category | Standard CoC Provision | Achievable with Negotiation | Risk Level |
|---|---|---|---|
| Oracle | Notification only; full assignment right to acquirer | Price protection for remaining term; right to renegotiate | Medium (stable but aggressive) |
| Microsoft | Assignment right to acquirer; MCA terms survive | Price protection; product continuity commitment | Low (low acquisition risk) |
| SAP | Notification only; terms transfer to acquirer | Price protection; maintenance commitment; renegotiation right | Medium (S/4HANA transition ongoing) |
| Salesforce | Notification only; full assignment right | Price protection; termination right for PE acquisition | Medium (active acquirer itself) |
| VMware / Broadcom | Acquired — full commercial change imposed | Focus on exit rights and transition support now | High (already changed) |
| Mid-size SaaS vendors | Notification only; assignment to acquirer | Full termination right; escrow trigger; price protection | High (active M&A targets) |
| PE-backed software vendors | Notification only; full assignment right | Termination right; 24-month price freeze; escrow trigger | High (PE exit expected) |
| Managed service providers | Notification + consent right common | Full termination right; transition assistance obligation | Medium (significant consolidation) |
Enterprise software buyers should treat the prospect of a private equity acquisition of their vendors with particular commercial caution. PE-backed software companies operate under financial pressures — return targets, debt service obligations, and exit timelines — that are structurally different from those of strategic or public company owners. These pressures typically manifest as: immediate focus on revenue retention and expansion from the existing customer base; reduction in R&D investment and product innovation; support quality degradation as headcount is reduced; and accelerated price increases at renewal.
Change-of-control provisions for vendors with PE investors (or those likely to be PE targets based on market position and scale) should specifically address: a PE acquisition as a named trigger event; an extended renegotiation window of 180 days rather than 90 days; a right to terminate without penalty triggered by: price increases above the agreed escalation mechanism, material reduction in support levels, or product end-of-life announcement within 36 months of the CoC; and an obligation to continue software escrow with annual verification testing for the remaining contract term.
Is your vendor an acquisition target?
| # | Tactic | Application |
|---|---|---|
| 1 | Assess M&A risk at the time of contracting | Research vendor ownership structure, financial profile, and market position before negotiating — PE-backed vendors require stronger protections from day one |
| 2 | Define the trigger broadly — 25%, not 50% | Most commercially significant acquisitions transfer effective control well below the 50% voting threshold; a narrow definition leaves you exposed |
| 3 | Name specific competitor categories | For sensitive relationships, specify that acquisition by a named competitor or competitor category automatically triggers termination rights without requiring the buyer to demonstrate harm |
| 4 | Negotiate price protection as a floor, not a ceiling | Price protection should specify that the acquirer cannot increase fees above the contracted escalation mechanism — while preserving the buyer's right to negotiate better terms |
| 5 | Link escrow release to change of control | Specify that the buyer's right not to consent to assignment constitutes a release trigger under the escrow agreement — creates operational continuity even if termination is exercised |
| 6 | Require transition assistance as a standard obligation | Regardless of whether the buyer exercises termination rights, require 12–24 months of continued service and migration support following a CoC notification |
| 7 | Address product roadmap commitments explicitly | Require the acquirer to honour specific product roadmap commitments made during the negotiation — or trigger a renegotiation right if they cannot |
| 8 | Use CoC provisions as upfront leverage | The prospect of a CoC termination right affecting deal value can motivate vendors to offer better initial pricing or contract terms in exchange for softer CoC provisions |
| 9 | Review CoC provisions at each renewal | Vendor M&A risk changes over time — a previously stable vendor may become a PE target. Update CoC provisions at each contract renewal to reflect current risk profile |
| 10 | Address the buyer's own CoC symmetrically | Vendor contracts often include CoC provisions that trigger obligations on the buyer (e.g., requiring consent to assignment following the buyer's own merger or acquisition). Negotiate symmetrical treatment |
For related guidance, see our articles on termination for convenience clauses, software escrow agreements, building your BATNA in software negotiations, and software contract red flags. For the complete framework, visit our IT contract negotiation strategy guide.
Change of control protections only have value if they are negotiated before an acquisition occurs. Our advisors identify M&A risk in your vendor portfolio and negotiate the protections you need before they are needed.