IBM third party support in 2026: what it covers and risks.

What IBM third party support covers in 2026, when the economics genuinely work, and why the quote is often worth more as renewal leverage than as a switch.

What does IBM third party support actually cover in 2026?

Third party support replaces IBM Subscription and Support with an independent provider handling break fix, configuration help, and workarounds. It does not include new versions, fixes from IBM, or security patches built by IBM; coverage is whatever the provider can engineer themselves.

That boundary matters by product family. Frozen Db2 or WebSphere estates on stable versions tolerate it well. Products with active security obligations or aggressive version cycles do not, because the IBM software support lifecycle keeps moving without you.

What you give up when you leave

• Version rights: Subscription and Support carries the upgrade entitlement; lapsing it freezes your usable version forever unless you repurchase.
• IBM security patches: third party fixes are workarounds, not vendor patches from IBM Fix Central; regulated estates must assess that gap formally.
• Relationship leverage: the account team buffer that softens compliance posture disappears with the support contract.

What you keep

Perpetual license rights survive. Your entitlements under Passport Advantage remain valid at the last entitled version, and ILMT obligations for sub capacity licensing continue exactly as before.

When do the economics actually work?

The economics work when the workload is frozen, the version is stable, and the exit horizon is defined. Third party support pricing at 45 to 55 percent below IBM only stays a saving if you never need to return.

The return cost nobody models

Reinstating lapsed IBM support means paying the back maintenance for the lapsed period plus an uplift, or repurchasing licenses. In the reversals we advised, return costs erased roughly two years of accumulated savings. Model the return before you leave.

How long the saving needs to hold

As a rule from our engagement file: the move pays if the workload stays frozen for at least three years. Under that horizon, the switching costs and audit friction eat the delta.

Does leaving IBM support increase audit risk?

Yes, in our experience the audit posture hardens after support cancellation. The account team loses revenue and the relationship buffer thins, and ILMT discipline becomes your only defense for sub capacity positions under the License Metric Tool requirements.

Estates that left support with clean ILMT reporting and quarterly snapshots rode out the reviews. Estates with ILMT gaps handed IBM a full capacity claim at exactly the moment they had no commercial relationship to soften it.

Where the common advice on IBM third party support is wrong

The standard advice from third party providers is that any stable IBM estate should move and pocket the 50 percent. We disagree. In roughly 20 of the 25 to 35 IBM estates Fredrik Filipsson advised in 2024 to 2025, the better trade was using a credible third party quote as leverage inside the IBM renewal, capturing 25 to 35 percent through repricing and shelfware removal while keeping version rights and the audit buffer. The buyer side move is to run the third party evaluation honestly, then decide between taking the quote and trading it. Half the value of third party support is never using it.

Half the value of a third party support quote is realized by never using it. The other half requires a frozen workload and a defined exit.

How should a buyer structure the decision?

Structure it as a portfolio decision, not an estate wide switch. Segment by workload stability, patch dependency, and exit horizon, then move only the segment where the three year frozen test holds.

• Segment one, move: frozen workloads with sunset dates and no security patch dependency.
• Segment two, trade: active workloads where the quote becomes renewal leverage with IBM.
• Segment three, keep: Cloud Paks, mainframe MLC, and anything regulated without an accepted patch gap.

What to do next

1. Segment the IBM estate by workload stability and patch dependency.
2. Verify ILMT health and archive quarterly sub capacity snapshots before any change.
3. Collect two third party support quotes for the movable segment.
4. Model the full return cost: back maintenance, uplift, and repurchase scenarios.
5. Take the quotes into the IBM renewal and price the keep scenario first.
6. Move only the segment that passes the three year frozen test.

The IBM practice runs this segmentation as part of renewal preparation, and the IBM knowledge hub holds the related ILMT and Passport Advantage guides. The Renewal Program sequences the whole decision inside your renewal runway.

Frequently asked questions

How much does IBM third party support save?

Forty five to 55 percent against IBM Subscription and Support list on the lines that move, based on our 2024 to 2025 engagement file. Workaround burden on actively patched products claws back up to half of that.

Do we keep our IBM licenses if we leave support?

Yes. Perpetual Passport Advantage entitlements remain valid at the last entitled version. You lose upgrade rights and IBM built fixes, and sub capacity ILMT obligations continue unchanged.

Does leaving IBM support trigger audits?

It raises the likelihood in our experience. Several estates in our file saw compliance reviews within 18 months of cancellation, and clean ILMT reporting was the difference between a non event and a full capacity claim.

Can Cloud Pak workloads move to third party support?

No. Cloud Paks are subscriptions that bundle license and support; cancelling support means losing the license itself. Only perpetual entitlements are candidates.

What does returning to IBM support cost?

Back maintenance for the lapsed period plus an uplift, or full license repurchase. In the reversals we advised, the return bill erased roughly two years of third party savings.