What Happens to SaaS Contracts After an Acquisition Closes

An account I watched go through an acquisition mid-term assumed, reasonably but incorrectly, that a change of control might trigger some kind of contract review. It did not: nothing changes on the vendor's side just because a company is acquired. The contract terms, the notice period, the renewal date and the escalator clause all carry forward exactly as written, regardless of who now owns the business.

The original contract had no change-of-control clause, and most SaaS agreements do not. The renewal came due on schedule, under the same terms as before, and the new ownership found out about the upcoming price increase the same way the previous owners would have: from the renewal notice.

Why this catches acquirers off guard

Most post-close integration attention goes toward the systems and contracts that feel most consequential: core infrastructure, major customer agreements, key employee retention. SaaS vendor contracts, individually smaller, tend to sit further down the priority list, discovered gradually as renewal notices arrive rather than reviewed deliberately as part of integration.

What a deliberate post-close review catches

• Which contracts have renewal or notice dates falling before integration attention naturally gets there
• Whether any contracts include change-of-control provisions that create an opportunity or an obligation
• Whether the combined organisation's actual usage still matches what each target-company contract was sized for
• Where vendor overlap exists between the acquirer's and the target's existing stacks

Why earlier is better than later

The same review that would have caught this before close can still be run after. Doing it during diligence means findings can inform deal terms. Doing it after close means you are managing discovered risk rather than negotiated risk. If it is your supplier that has been acquired, the contract and leverage questions are different.