Here is the short version. Assignment controls who can transfer the contract; change of control defines what happens when either party is bought. Vendor templates tilt both toward the vendor. The buyer-side move is to make assignment rights mutual, permit your own corporate changes without consent, and remove any language that lets the vendor re-price or terminate when you reorganise. These two clauses live in our wider ITSM contract clause library; this article is the deep read on the pair.
What does an assignment clause actually let the vendor do?
A typical vendor draft says the customer may not assign the agreement without the vendor's prior written consent, while the vendor may assign freely, including to an acquirer or in connection with a sale of the business. Read plainly, that is asymmetric: the vendor keeps full flexibility and hands you a permission slip you have to request. In an industry where vendors are acquired routinely, you can find your contract, your data and your support relationship transferred to a company you never chose, on terms you cannot revisit.
The fix is symmetry. You should be able to assign to an affiliate or to a successor entity in a merger, acquisition or reorganisation without consent. Where the vendor wants a consent right at all, cap it as "not to be unreasonably withheld, conditioned or delayed." And if the vendor assigns, your pricing, terms and service levels should carry over unchanged, so a vendor sale never becomes your re-pricing event.
What does the change-of-control clause cost you in an acquisition?
Change-of-control language defines a trigger event: one party being acquired, merged or majority-sold. The vendor-favorable version treats your acquisition as grounds to re-price, re-scope, suspend or terminate. That is the most expensive moment to be exposed, because during a transaction you need certainty, you may need to move licenses to a new entity, and you have no time to re-shop the vendor. The clause becomes a toll the vendor collects precisely because you cannot walk.
Vendor draft versus buyer-side rewrite
| Issue | Typical vendor draft | Buyer-side rewrite |
|---|---|---|
| Customer assignment | Prohibited without vendor consent | Permitted to affiliate or successor without consent; consent for others not unreasonably withheld |
| Vendor assignment | Free, including on sale of business | Permitted, but your price, terms and SLAs survive unchanged |
| Your change of control | Trigger to re-price, re-scope or terminate | Permitted with notice; no re-pricing or termination right for the vendor |
| Combining estates after a merger | Silent or treated as new purchase | Right to combine entitlements and apply existing volume tier |
| Carve-out or divestiture | No transfer rights | Right to assign a proportionate share to the divested entity |
How do you negotiate the rewrite?
- Raise it early, as a standard term, not a special ask. These are governance points; framing them as routine removes the drama and the vendor's pretext to charge for them.
- Make assignment mutual first. Symmetry is hard to argue against and anchors the rest of the conversation.
- Delete the re-pricing trigger on your change of control. Replace it with notice only. The vendor keeps the relationship; you keep your terms.
- Add merger and carve-out mechanics. Secure the right to combine entitlements after an acquisition and to assign a proportionate share in a divestiture, so corporate change never forces a new purchase.
- Tie it to the usage definitions. An entity change interacts with how "user" is counted, which is why we pair this with usage-definition clauses.
Across ITSM engagements our firm averages a 30% reduction and has negotiated more than $420M in contract value since 2019, and a meaningful share of that value sits in terms like these rather than in the headline discount. A clean assignment clause is worth nothing on the day you sign and a great deal on the day you reorganise.
Our gated ITSM Contract Terms and True Forward Guide includes model assignment and change-of-control language alongside the rest of the protective terms.
Book a negotiation review.
We redline assignment and change-of-control language so a vendor sale or your own acquisition never becomes a re-pricing event. Fixed fee or gainshare.
Book a contract negotiation review →What to do next
Find the assignment and change-of-control sections in your current master agreement and check three things: is assignment mutual, does your acquisition trigger re-pricing, and can you combine or carve out entitlements. If any answer favors the vendor, flag it for the next amendment window. Related protections sit in audit and true-up clauses, and the engagement runs through our contract negotiation service on fixed fee or gainshare. The full set is indexed in the clause library pillar.
Frequently asked questions
- What is an assignment clause in an ITSM contract?
- It governs who may transfer the contract. Most drafts let the vendor assign freely and require your consent; make the right mutual so you can assign to an affiliate or successor without consent.
- What does a change-of-control clause do?
- It sets what happens if either party is acquired. Vendor versions treat your acquisition as a re-pricing or termination trigger; negotiate it down to notice only.
- Why do these clauses matter most during an acquisition?
- Because that is when you need to move or combine licenses and have the least leverage. Fixing the language before signing is far cheaper than negotiating under deal pressure.