Buyers who only tabled a third party bid, without moving, still cut the IBM renewal 10 to 20 percent

The evaluation is worth running whether or not you intend to switch, because the two outcomes pay differently and both pay. That is unusual enough to be worth stating plainly before any of the product level detail.

Prepared by Redress Compliance · August 16, 2026 · IBM advisory. 20 to 30 IBM estates advised, 2024 to 2025.

Third party support replaces the break fix, how to, and workaround service you buy from IBM, typically at half the price. What it cannot deliver is IBM intellectual property.

Across the IBM estates advised, third party support was evaluated far more often than it was adopted, and the notable finding is that both outcomes paid. Estates that moved stable middleware and database versions saved 40 to 60 percent of the support line with no measurable service degradation. Buyers who ran the evaluation, obtained a credible bid, and then chose to stay with IBM still cut their renewal by 10 to 20 percent. That asymmetry is unusual and it changes the economics of the exercise: the evaluation is worth running even when the decision is already to stay, because the bid itself is the leverage.

The reason it works is that the alternative is unusually verifiable here. A migration threat at most vendors requires the buyer to assert a cost and a timeline the vendor can dispute. A third party support bid is a document from a named provider with a price on it, covering products the vendor knows are static, at a price the vendor knows is roughly half its own. There is very little to argue about, which is precisely why it moves the number without needing to be acted on.

What makes the decision genuinely hard is not the service quality, which buyers report as better in the concierge model than in a ticket queue, but the return path. Reinstating lapsed IBM support triggers back maintenance plus a penalty that can erase years of savings, which means the exit is asymmetric in the same way the entry is cheap. Roughly eighteen of twenty five engagements kept a documented return path by freezing entitlements, media archives, and ILMT records before the switch. That preparation is what converts an irreversible decision into a reversible one, and it costs almost nothing at the point it is done.

The audit dimension deserves separate attention because it is where an otherwise sound decision goes wrong. Entitlement hygiene decides audits, and an estate that has left IBM support still has to evidence what it holds. Proof of entitlement, media archives, and ILMT records need freezing before the switch, not reconstructing afterwards, because the records that prove your position are the ones that become hardest to obtain once the commercial relationship has changed. The wider IBM posture sits in the vendor management playbook, and the library in the IBM practice.

• Proof of entitlement for every product, because after the switch the records proving what you hold become considerably harder to obtain.
• Media archives for every version in use, since access to IBM download channels changes and a reinstall you cannot perform is an outage you cannot fix.
• ILMT records and a clean report, because sub capacity entitlement remains conditional on instrumentation regardless of who provides support.
• A documented return path, kept by roughly eighteen of twenty five engagements, which is what makes the decision reversible rather than final.
• A product by product fit assessment, separating static versions that fit from fast moving and subscription products that do not.
• The Cloud Pak roadmap check, since that conversion path closes while you are outside IBM support and reopening it is part of the return cost.

Across roughly 20 to 30 IBM estates advised, third party support was evaluated far more often than adopted, and both outcomes paid:

Roughly 18 of 25 engagements kept a documented return path by freezing entitlements, media, and ILMT evidence before the switch. That preparation is what makes the decision reversible, and reinstating lapsed support without it triggers back maintenance plus a penalty that can erase years of savings.

Good providers compensate for the absence of IBM intellectual property with senior engineers, custom workarounds, and security guidance for frozen versions. The service model is concierge rather than ticket queue, and that difference is what buyers actually notice day to day.

What does third party support for IBM actually cover?

Break fix, how to, and workaround service, typically at roughly half the IBM price, with defect support, configuration help, performance guidance, and custom fixes. What it cannot deliver is IBM intellectual property: new versions, fixpacks, and patches.

How much can we save?

Between 40 and 60 percent of the support line for estates that moved stable middleware and database versions, with no measurable service degradation in the engagements advised.

Is it worth evaluating if we intend to stay?

Yes, and that is the unusual finding. Buyers who tabled a credible third party bid without moving still cut the IBM renewal 10 to 20 percent. The option carries value unexercised, so the evaluation pays either way.

Why does a bid move the number so reliably?

Because it is verifiable in a way most alternatives are not. It is a document from a named provider, with a price, covering products the vendor knows are static, at roughly half the vendor price. There is very little available to dispute.

Which products fit?

Static Db2, WebSphere, and MQ versions fit well, because a frozen version needs no new intellectual property. Fast moving and subscription products do not, and neither does anything with a Cloud Pak conversion in its roadmap.

What is the return path problem?

Reinstating lapsed IBM support triggers back maintenance plus a penalty that can erase years of savings. The exit is asymmetric with the entry, which is why the return path has to be preserved deliberately rather than assumed.

How do we preserve the return path?

Freeze proof of entitlement, media archives, and ILMT records before the switch. Roughly 18 of 25 engagements did this, and it is what converts an effectively irreversible decision into a reversible one at almost no cost.

Does leaving IBM support affect audits?

It raises the stakes on entitlement hygiene. You still have to evidence what you hold, and the records proving your position become harder to obtain once the commercial relationship has changed. Freeze them first.

What about security patches?

They are not available from IBM while you are outside support. Good providers compensate with security guidance for frozen versions and custom workarounds, but the absence of vendor patches is a real constraint that belongs in the risk assessment.

Should the decision be estate wide?

No. Fit is product specific, so an estate wide decision in either direction gets one half of the portfolio wrong. Assess product by product and expect a mixed answer.