What Is a Change of Control Clause in a SaaS Contract?
A change of control clause in a SaaS contract allows either party to terminate, require written consent, or renegotiate pricing when ownership or voting control of the other party changes, typically through a merger, acquisition, majority share purchase, or asset transfer.
Most guides cover the contracts a company sells. This one covers the SaaS agreements a buyer inherits, and what an acquisition can trigger inside them.
Search results for this term mostly describe sell-side risk: customer contracts a target could lose after a deal. For a software buyer the question runs the other way. When your company is acquired, or acquires another, the clause decides whether each vendor agreement carries over untouched, needs consent, or opens the door to new pricing.
What triggers a change of control
- A sale of more than half the voting shares, even though the contracting legal entity stays the same
- A statutory merger in which the customer entity is absorbed or replaced
- A sale of the business or assets that moves the contract to a new entity, which usually engages the assignment clause as well
- A change in the right to appoint the majority of the board, where the definition includes it
Change of control vs assignment clause
| Change of control | Assignment | |
|---|---|---|
| What changes | Who owns or controls the existing customer entity | Which legal entity is party to the contract |
| Typical deal type | Share or stock acquisition | Asset sale or internal restructuring |
| Usual effect | Notice, consent or a termination right, if the clause exists | Consent often required before transfer, unless an affiliate or successor carve-out applies |
| If the contract is silent | Agreement generally continues unchanged | Transfer may still need consent; take legal advice |
Three illustrative clause examples
The wording below is illustrative, written to show the common patterns. It is practical guidance, not legal advice, and real contracts vary.
- Consent required: "Customer shall not undergo a Change of Control without Vendor's prior written consent." Closing without consent can put the customer in breach.
- Vendor termination right: "Vendor may terminate this Agreement on 30 days' notice following a Change of Control of Customer." Common where the acquirer competes with the vendor.
- Affiliate re-pricing: "Fees are calculated on the total employees of Customer and its Affiliates." After close, the fee base can expand to the whole group.
What it means for the software you buy
The renewal date, notice period and escalator clause normally continue through the deal. What changes is the risk around them: consents with deadlines, entities that get merged, duplicate tools that cannot be exited until each term ends, and the "Customer and its Affiliates" headcount trap that re-prices a contract nobody renegotiated. The first year after an acquisition is where these surface.
Pre-close M&A SaaS contract checklist
- List every material SaaS and AI agreement held by the target
- Extract the change of control, assignment and affiliate definitions from each
- Compare consent requirements against the deal structure and close date
- Flag vendor termination rights, especially where the acquirer is a competitor
- Check pricing tied to the headcount or usage of the customer and its affiliates
- Map renewal and notice dates falling inside the integration window
- Assign an owner and deadline for every required notice or consent, and get written confirmation where the effect is unclear
Common questions
Keep reading
Why dozens of SaaS agreements pass through due diligence unreviewed, and the renewal exposure the acquirer inherits the moment the deal closes.
InsightWhat Happens to SaaS Contracts After an Acquisition ClosesNotice periods, renewal dates and escalators carry forward unchanged through an acquisition. What a deliberate post-close contract review catches.