IBM's default assignment clause does not move your entitlement in a carve-out, it terminates it, and buyers who fix that at signature avoid a second license purchase for the divested entity
Passport Advantage bars client assignment without IBM's consent while reserving IBM's own right to assign in a sale of its business, and a permitted transfer outside the Contract Agreement ends the licensee's authorization under the Proof of Entitlement. That asymmetry means a divestiture triggers a fresh purchase, not a transfer, unless the ELA was pre-loaded with a defined change-of-control and transitional-use clause. The 24-month window IBM itself used in the Kyndryl separation is the precedent to demand at signature, when you still have spend on the table.
Prepared by Redress Compliance · September 6, 2026 · IBM advisory. ELA, Passport Advantage, and Cloud Pak negotiations, 2021 to 2026.
Executive summary
The single most expensive line in an IBM ELA is the one clause most buyers never read: transfer outside the defined Contract Agreement terminates authorization to use under the Proof of Entitlement, so a carve-out extinguishes the license rather than moving it.
The practical consequence is that the divested entity buys the same software a second time, at list, with no accumulated discount history, while the parent keeps paying S&S on entitlement it no longer needs.
Passport Advantage is openly asymmetric: the client cannot assign without IBM's prior written consent and any attempt is void, while IBM's own assignment in connection with the sale of a business unit is unrestricted.
IBM used that reserved right in the Kyndryl separation in 2021, moving roughly 90,000 employees and a Managed Infrastructure Services book of business to a new entity, and the asymmetry is the single most effective argument you have for reciprocity language.
IBM's own separation documents show permitted transitional use generally capped at one to two years, which is the precedent to convert into a contractual 24-month divested-entity window at zero incremental fee.
Ask for what IBM gave itself: continued use of existing entitlement by the separated business for 24 months post-close, with a commercially reasonable efforts obligation to migrate, and no re-price of the parent's remaining estate.
Revision 11 of the Passport Advantage Agreement, announced 1 February 2023 and effective for existing clients from 1 May 2023, added an annual Effective License Position obligation and verification rights across all Sites and all environments where the client uses products for any purpose.
In a separation year, "all environments" reaches into the carved-out estate and into TSA-period usage, which converts a corporate event into an audit exposure unless the ELA scopes verification to entities under your control.
The commercial hosting bar is the clause that breaks the Transitional Services Agreement: Eligible Products may not be used to provide commercial IT services to third parties, and the divested entity is a third party from the moment of close.
Left unfixed, this shows up in the M&A deal itself as a price adjustment, because the buyer prices in the time and cost of standalone licensing, and consent fees flow back through the TSA cost recovery mechanism.
What IBM's paper actually says about assignment, and where the asymmetry sits
Four clauses do the damage, and only one of them lives where most legal teams look.
The Passport Advantage assignment restriction bars you from assigning the agreement in whole or in part without IBM's prior written consent, declares any attempt void, and gives you exactly one crumb of protection: consent will not be unreasonably withheld.
That crumb is unenforceable in practice because IBM does not withhold consent, it conditions it, and price is not a reasonableness test.
Meanwhile IBM's own paper (Z125-5831-10) exempts IBM from the same restriction when it assigns in conjunction with the sale of the portion of its business that includes the product, which is precisely the manoeuvre it executed with Kyndryl.
The third clause is the one that converts a governance nuisance into a second purchase: transfers are permitted only within the defined Contract Agreement.
And a permitted transfer of rights and obligations outside that Contract Agreement terminates the licensee's authorization to use the product under the Proof of Entitlement.
Read that carefully. The entitlement does not travel to the divested entity and sit there unlicensed. It ceases to exist.
Add the commercial hosting bar, which prohibits using Eligible Products to provide commercial IT services to third parties, and your own transition services agreement to the buyer becomes a breach on day one of close.
Finally, affiliate use is not governed by the master at all: the International Client Relationship Agreement pushes Enterprise and third-party End User rights into the applicable Attachment and Transaction Documents. Redline the master, leave the Attachment untouched, and you have bought nothing.
This is the same failure mode we see in IBM ELA clause work generally: the operative language is one document below where counsel is reading.
| Clause | IBM default | Cost in a corporate event | Target redline |
|---|---|---|---|
| Client assignment | Consent required, void if attempted, not unreasonably withheld | Consent priced as a new transaction, not a transfer | Consent deemed given for any affiliate, successor, or divested entity on notice |
| IBM assignment | Unrestricted on sale of the relevant IBM business line | You inherit a new counterparty with no reciprocal right | Reciprocity, or your termination right on IBM assignment |
| Transfer outside Contract Agreement | Terminates authorization under the PoE | Full repurchase at list for the divested estate | Entitlement splits pro rata to the separated entity, PoE reissued |
| Commercial hosting bar | No third-party service provision | TSA to the acquirer is a breach | Named TSA carve-out, 24 months, defined scope |
| Affiliate use | Set by Enterprise definition in the Attachment | Master redlines do not reach it | Enterprise defined to include majority-owned and divested-in-transition entities |
The column that matters is the third one. Three of these five clauses do not create a compliance discussion in a carve-out, they create a purchase order.
Termination of authorization under the Proof of Entitlement is not a technicality you argue about after close: the divested entity is running unlicensed software from the moment the shares transfer.
IBM's revision 11 verification right reaches all environments in which the products are used for any purpose, and the only route back to compliance is buying again at whatever discount a standalone mid-market buyer can command.
Note the timing asymmetry too. Revision 11 landed on 1 February 2023 and applied to existing customers from 1 May, ninety days later, and the standard agreement carries no mid-term renegotiation right for the master terms. You cannot reopen this language when the divestiture is announced.
You pre-load it or you pay for it.
The three corporate events IBM prices differently, and why only one is negotiable after the fact
IBM's sellers do not treat corporate change as one risk category, and neither should you. An inbound acquisition, where you buy a business and want to fold its estate onto your PoEs, is the cheapest thing on this list to fix late.
IBM sees incremental PVUs, incremental Cloud Pak capacity, and a chance to displace whatever the target was running.
In our experience across IBM ELAs, that headroom is worth real discount movement, and it is the one event where you can raise the issue mid-term and get a constructive answer, because the answer is a bigger deal for them.
Change of control, where you are the one acquired, is neutral in theory and a re-price opportunity in practice. IBM's interest is to determine which paper survives, and if the acquirer holds higher-priced agreements, IBM will argue the combined entity migrates to those terms.
That is a negotiation you can still win, but you are negotiating with a gun on the table because your entitlement continuity depends on IBM's consent to an assignment your deal lawyers have already committed to in the SPA.
Divestiture is different in kind. It is a revenue reduction event. IBM loses PVU count, loses subscription and support base, and gains a smaller standalone buyer with no leverage.
There is no upside to trade against, so there is no commercial incentive to help, and the transfer-terminates-authorization language means IBM does not have to help: the default outcome is a full repurchase for the separated entity plus a hosting breach on your TSA.
This is where the Oracle comparison is instructive, because the same structural problem shows up in Oracle assignment and divestiture clauses with different vocabulary and identical economics.
The practical rule: fix acquisition language whenever, fix change of control at renewal, and fix divestiture before you have ever announced one, because the day the deal is public your leverage is gone and the clock is the acquirer's, not yours.
Cut your IBM ELA renewal with 8 buyer side levers
Eight buyer side levers that cut an IBM ELA renewal: the baseline reset, true forward exposure, product rationalization, and the Cloud Pak shift.
Get the white paper →The Kyndryl precedent: IBM wrote for itself the clause it denies you
Every negotiation on this topic stalls at the same point: IBM's account team says a pre-approved assignment right is non-standard, that consent is always granted in practice, and that a transitional-use window for a divested entity is not something IBM does. The answer is not a legal argument.
It is IBM's own separation file. When IBM spun out Kyndryl in 2021, it built the entire transaction on precisely the mechanics it tells you are unavailable, and it documented them in SEC filings that are public, dated, and impossible for your counterparty to characterize as an outlier.
That is the single strongest artifact a buyer brings to this table, because it is not a demand for a concession, it is a request for parity with the seller's own conduct.
Start with scope definition.
The Form of Separation and Distribution Agreement defines the SpinCo Business with surgical precision: the Managed Infrastructure Services unit of the GTS segment, plus named Security, Regulatory and Risk Management and Identity Management offerings from Cloud and Cognitive Software.
Expressly excluding the Public Cloud Platform offering.
That is the drafting model for your carve-out perimeter. Most buyer redlines fail because they say "any divested business unit," which IBM's counsel will reject as unbounded.
IBM's own paper shows the alternative: name the business, name the segment it sits in, name the adjacent offerings that travel with it, and name what does not. A perimeter drafted that way survives legal review because IBM has already accepted the construction for itself.
Then take the change-of-control point, which is where most buyers discover they have no clause at all.
DLA Piper's May 2021 analysis of the spinoff made the observation plainly: whether a separation constitutes a change of control depends on how the client's particular contract defines it, if it is defined at all. In the majority of Passport Advantage estates we review, it is not defined.
That absence is not neutral. It defaults the event down to an assignment, and an assignment requires consent, which puts IBM in the pricing seat at exactly the moment your deal timetable removes your ability to walk.
The second gate is the one buyers miss entirely. DLA Piper flagged that the contract may require customer consent for subcontractors, and that this is likely what Kyndryl would become post-separation.
Translate that into a carve-out: the retained entity continues consuming services from the divested one under a TSA, the divested entity is now a third party.
And the Passport Advantage commercial-hosting bar plus any subcontractor consent requirement produce two separate approval events on the same transaction.
Two gates means two pricing conversations. Buyers who redline only the assignment clause and leave the affiliate and subcontractor language untouched, a pattern covered in the broader IBM ELA clause redline work, have closed one door and left the other open.
Timing is the third lesson, and it is the one nobody prices. DLA Piper recorded that IBM had only very recently begun explaining the contract consequences of the separation to clients, against a timetable that ran formation and asset dropdown over the summer with distribution complete by year end.
Clients had weeks, not quarters, to assess exposure. Whatever the intent, the effect was compressed response time on the party with less information.
That is why notice-timing language deserves the same redline attention as consent language: a 90-day written notice obligation with a defined disclosure of affected entitlements is worth more than a consent right you learn you need thirty days before close.
Which brings the reciprocity argument to its conclusion. The Kyndryl DEF 14A records that permitted transitional uses generally did not exceed one to two years, with a commercially reasonable efforts obligation to cease as soon as practicable.
IBM designed its own separation around a transitional window of up to 24 months and treated that as commercially reasonable. It cannot then tell your board that 24 months of transitional use for your divested entity, at existing metrics, is unreasonable. Put the filing on the table.
The conversation changes from whether the concept is acceptable to what the number is.
What a strong assignment package looks like in numbers
Set the target before the first redline goes back. A strong package is five linked provisions, not one clause, and each has a number attached.
Pre-approved assignment to any entity acquiring a majority of the assets of a defined business unit, with no consent fee and no re-price of the surviving estate. Twenty-four months of transitional use for the divested entity at existing metrics.
A proportional reduction right on S&S when headcount or usage-based metrics fall post-close. An affiliate definition covering majority-owned and majority-managed entities, plus a 12-month tail for entities leaving the Enterprise. Anything less and the divested entity buys again.
| Provision | Default Passport Advantage position | Target outcome | Value at stake |
|---|---|---|---|
| Assignment on divestiture | Consent required, not unreasonably withheld, transfer outside the Contract Agreement terminates PoE authorization | Pre-approved for majority-asset acquirer of a named business unit | Full replacement cost of the divested estate |
| Consent fee | Undefined, priced at the moment of least buyer leverage | Zero, expressly stated | Line item TSAs push back to the buyer |
| Surviving estate re-price | IBM re-tiers the remaining volume | Discount and price hold locked for the term | 5 to 15% of retained spend, market experience |
| Transitional use, divested entity | None, becomes a third party at close | 24 months at existing metrics, Kyndryl precedent | Second license purchase avoided |
| S&S proportional reduction | No mid-term reduction right | Reduce in proportion to divested headcount or usage | Divested share of annual S&S |
| Affiliate definition | Enterprise scope set in the Attachment | Majority-owned and majority-managed, 12-month exit tail | Removes the subcontractor consent gate |
The table has a hierarchy that buyers routinely get backwards. The assignment right prevents the catastrophic outcome, a second purchase for the divested entity, but the proportional reduction right is where the recurring money sits.
On a metered Cloud Pak estate, divesting 30% of the workload without a reduction right means you pay 100% of S&S on 70% of the value for the remainder of the term, and the standard agreement carries no mid-term renegotiation right to fix it.
What IBM will do when you table this redline, and how to answer it
Expect four responses in a predictable order, and expect them from the account team before they ever escalate to IBM legal.
First: "the Passport Advantage agreement is standard corporate paper, we do not amend it." That is true of the base agreement and irrelevant, because you are not amending Z125-5831-10.
You are adding a clause to your Attachment or ELA Transaction Document, which is exactly where IBM already varies affiliate scope and Enterprise definition.
Second: "we handle assignment by amendment at the time of the event." Refuse this one hardest. At the time of the event you have signed the SPA, the close date is public, the TSA clock is running, and IBM knows your alternative to paying is delaying a corporate transaction.
Your leverage at that moment is functionally zero. Third: "the Enterprise definition already covers your affiliates." It covers entities you control, and a divested entity by definition stops being controlled at close, so the definition helps you until the exact day it stops mattering.
Ask them to write "and any entity divested from the Enterprise, for 24 months from close" into the definition and watch how quickly "already covered" becomes a pricing conversation.
Fourth: "any transfer requires a true-up of the divested entity's usage." Concede the audit-adjacent principle and take the counter-position: usage counted once is paid once, and the corollary is a written entitlement reduction on the retained side, sized to the divested footprint.
Effective at close.
IBM will trade this clause, and the trade is nearly always for term or commitment rather than cash.
In our engagements the going rate for a defined change-of-control clause with a 24-month transitional-use window is a 12-month term extension, a modest ramp commitment in year one, or agreement to convert one product family to a Cloud Pak.
All three are acceptable if you are already going that direction. What is not acceptable is paying a line-item premium for the clause.
Anything above roughly 1 to 2 percent of total contract value for corporate-change protection is IBM pricing your M&A pipeline, and it should be met with a straight refusal plus a reminder that the base agreement grants IBM the same right for free.
Sequence matters. Table the assignment redline in the same package as your termination and reduction rights and your uplift cap, not as a standalone ask. Bundled, it reads as one commercial position and IBM prices the package.
Standalone, it reads as a signal that a transaction is coming, and IBM will hold it hostage. If your Cloud Pak conversion is already on the table, spend it here rather than on a discount point.
Evidence base and recurring patterns
Kyndryl's DEF 14A confirms permitted transitional uses generally did not exceed one to two years, which is the precedent you cite when IBM calls 24 months excessive.
Announced 1 February 2023, effective for existing clients 1 May 2023, which is the practical measure of how much warning IBM gives on adverse master-terms changes.
The sourcing here is deliberately public and citable in a negotiation room: Passport Advantage Z125-5831-10 (11/2017) and Revision 11; the International Client Relationship Agreement filed with the Kyndryl separation documents.
The SEC Form of Separation and Distribution Agreement defining the SpinCo Business scope; the Kyndryl Holdings DEF 14A; DLA Piper's May 2021 analysis of contractual consequences for IBM clients; and Morgan Lewis carve-out guidance on pre-negotiated assignment and unbundling rights.
Across engagements three patterns repeat. The clause surfaces during due diligence, not at signature, which means it is found by an M&A workstream with no licensing mandate and no budget line.
Affiliate rights are assumed rather than written, because the Enterprise definition sounds broad enough until a legal entity leaves the Enterprise.
And verification obligations bite in the separation year: Revision 11's clause 4.1 Effective License Position duty plus the right to verify all environments in which products are used for any purpose reaches straight into the separated estate during the TSA period, when nobody owns the data.
Treat corporate-change language as a standing item in your ELA redline set, not an M&A contingency.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
Your first five moves
- Pull the executed master, every Attachment, and every Transaction Document before you touch a redline, because the Enterprise definition that actually governs affiliate use sits in the Attachment, not in the Passport Advantage master, and in our experience most buyers negotiate the wrong document for six weeks before discovering that.
- Confirm in writing whether "change of control" is defined anywhere in your paper at all, since DLA Piper's read of the Kyndryl separation was that the term is frequently absent, and an undefined trigger means every carve-out defaults to the consent gate plus the clause that terminates your Proof of Entitlement authorization on transfer outside the Contract Agreement.
- Map spend to legal entity and business unit now, at PVU and per-user granularity, so you can draw a carve-out perimeter on a slide instead of asking IBM to define it for you; without that map you cannot argue that fees should fall post-separation, which Morgan Lewis identifies as the standard adjustment where pricing was built on headcount or usage that no longer exists.
- Table the assignment package at your next renewal or Cloud Pak expansion, never at the M&A event, because leverage is spend not yet committed, and the same clause costs nothing when there is eight figures on the table and full list price when the deal is announced. Bundle it with the other structural asks in your IBM ELA clause package so it is one of eight redlines, not the only one.
- Price your own fallback before IBM prices it, a standstill plus 24-month transitional-use side letter mirroring the window IBM wrote for Kyndryl, with a pre-agreed transfer fee cap and an audit scope limit that excludes the separated estate.
Frequently asked questions
Can I transfer IBM licenses to a company I am divesting?
Not under default Passport Advantage terms.
The client may not assign the agreement in whole or in part without IBM's prior written consent, and a permitted transfer of license rights outside the defined Contract Agreement terminates the licensee's authorization to use the product under the Proof of Entitlement.
In practice that means the divested entity must acquire new entitlement unless you negotiated assignment rights before the event.
Does an IBM ELA have a change-of-control clause?
Often it does not define change of control at all, which is itself the problem. DLA Piper's analysis of the Kyndryl separation made the point directly: whether a spinoff constitutes a change of control depends on how the client's own contract defines it, if it is defined.
At minimum a separation is an assignment from a contractual perspective, which triggers the consent requirement regardless of what you call it.
Can IBM assign my agreement without asking me?
Yes, in the circumstances IBM reserved for itself. The Passport Advantage terms exclude from the assignment restriction both IBM's assignment of its right to receive payments and IBM's assignment in connection with the sale of the portion of its business that includes the product or service.
That is exactly what happened in the Kyndryl separation, and it is the strongest argument for reciprocal rights on your side of the paper.
How long should a transitional use window be for a divested entity?
Ask for 24 months. IBM's own separation documents show permitted transitional uses generally not exceeding one to two years, paired with a commercially reasonable efforts obligation to cease use as soon as practicable.
Anchoring on IBM's own conduct makes it difficult for the account team to argue that 24 months is unreasonable, and 12 months is a realistic fallback if you are trading elsewhere.
Can our divested business keep using our IBM software under a TSA?
Not without a fix. Eligible Products may not be used to provide commercial hosting or other commercial IT services to third parties, and the divested entity becomes a third party at close.
The parent typically needs a contractual amendment with IBM, usually carrying a fee, and TSAs normally allow the parent to recoup that cost from the divested entity or its new owner, so the exposure lands on someone in the deal regardless.
Do affiliate use rights come from the master agreement or somewhere else?
From the Enterprise definition and the applicable Attachment, not the master assignment clause.
IBM's client relationship framing permits acquisition of products for the client's own Enterprise, with lead companies coordinating activities of their Enterprise companies, and use by third-party end users only as specified in the Attachment and Transaction Documents.
Redlining only the master leaves affiliate exposure untouched.
What did Revision 11 of the Passport Advantage Agreement change for corporate events?
It added compliance obligations that bite hardest in a separation year.
Announced 1 February 2023 and effective for existing clients from 1 May 2023, Revision 11 introduced a contractual obligation to provide an Effective License Position and permits IBM to verify compliance at all Sites and across all environments in which the client uses the products for any purpose.
During a carve-out, that language reaches into the separated estate unless verification scope is limited to entities under your control.
