Third party support for IBM. The CIO decision framework.

Third party support cuts IBM S&S spend by 40 to 60 percent on stable estates, but the decision lives or dies on product fit, entitlement hygiene, and the cost of the return path.

What does third party support for IBM software actually cover?

Third party support replaces the break fix, how to, and workaround service you buy from IBM S&S, typically at half the price. What it cannot deliver is IBM intellectual property: new versions, fixpacks, and patches stay behind the IBM support entitlement.

Good providers compensate with senior engineers, custom workarounds, and security guidance for frozen versions. The service model is concierge, not ticket queue, and that is what buyers actually notice.

• Included: defect support, configuration help, performance guidance, custom fixes and workarounds.
• Excluded: IBM version upgrades, official fixpacks, and rights tied to active S&S like license mobility.
• Variable: security vulnerability response, which depends on the provider's engineering depth.

Who are the established providers?

The market consolidated around a handful of firms with real IBM engineering benches. Evaluate them on named engineer access, security response method, and reference customers running your exact product versions.

Which IBM products fit third party support and which do not?

Stable versions of Db2, WebSphere Application Server, MQ, and Cognos on mature releases fit third party support well. Products under active subscription, Cloud Paks, and anything on an aggressive upgrade path do not.

What about the mainframe estate?

Mainframe monthly license charge software follows different economics, and third party support there is a specialist decision. Evaluate distributed middleware first; it carries most of the savings at a fraction of the risk.

What does leaving IBM S&S cost you later?

Returning to IBM after a lapse triggers reinstatement: back payment of the lapsed S&S plus an uplift that commonly brings the total near 150 percent of what you skipped. IBM documents its support and renewal mechanics through Passport Advantage, and the reinstatement math is the deterrent it looks like.

The second cost is audit posture. Sub capacity licensing requires ILMT records, and leaving S&S does not remove the compliance obligation on perpetual licenses you keep deploying.

• Reinstatement: budget the return path at roughly 150 percent of lapsed S&S before you leave.
• ILMT continuity: keep the tool running and the quarterly reports archived; the audit clause survives.
• Version ceiling: the version you hold at exit is the version you live with until you return or migrate.

How do you keep the return path open?

Freeze the estate evidence the week before the switch: proof of entitlement, install media, license keys, ILMT reports, and a deployment snapshot. That archive is what makes a later reinstatement or audit negotiable instead of catastrophic.

How do you build the CIO business case and exit plan?

The business case is a three year cash model with the reinstatement scenario priced in, built on a product by product segmentation of the estate. Run it before the IBM renewal date, not after, so the result works as leverage either way.

1. Segment the estate: stable products eligible to move, products that must stay with IBM, retirement candidates.
2. Price the three year savings against reinstatement and migration scenarios.
3. Freeze entitlements, media, keys, and ILMT evidence into an archive.
4. Select the provider on engineering depth for your exact versions.
5. Time the switch to the S&S anniversary to avoid paying for overlap.
6. Table the result with IBM before signing anything, and bank the counter.

When is staying with IBM the right answer?

Stay when the roadmap genuinely needs new versions, when Cloud Pak consolidation is planned, or when the estate is shrinking toward retirement faster than the savings accrue. The evaluation still pays for itself as renewal leverage.

Where the common advice on third party IBM support is wrong

The standard advice frames third party support as a short bridge before decommissioning, too risky for anything that matters. We disagree. In roughly 18 of the 25 plus IBM estates Morten Andersen reviewed in 2024 to 2025, stable middleware ran for years on third party support with service levels buyers rated above the IBM baseline, and the real failures came from sloppy entitlement archives, not support quality. The buyer side move is to treat entitlement hygiene as the project, segment the estate honestly, and let the 40 to 60 percent savings fund the modernization IBM keeps invoicing you to delay.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Inventory the IBM estate and tag every product by version stability and roadmap need.
2. Model three year savings against the 150 percent reinstatement scenario.
3. Freeze proof of entitlement, media, keys, and ILMT reports into an archive.
4. Request bids from two third party providers with references on your versions.
5. Table the comparison with IBM before the renewal and document the counter.
6. Decide per product segment, not estate wide, and set the switch to the anniversary.

White Paper · IBM

IBM ELA Renewal 2026 White Paper

White paper for IBM ELA renewals in 2026. Read it free.

Read the white paper

Frequently asked questions

How much does third party support save on IBM software?

Stable IBM estates save 40 to 60 percent of the S&S line by moving eligible products to third party support. The range held across roughly 20 to 30 estates we advised in 2024 to 2025, with the variance driven by product mix.

Is third party support for IBM software legal?

Yes. Supporting software you hold perpetual licenses for through an independent provider is lawful. The constraints are contractual: you lose rights tied to active S&S, such as new versions and fixpacks, while you are out.

Which IBM products should not move to third party support?

Cloud Paks, SaaS subscriptions, and products on active upgrade paths should stay with IBM. Subscription terms require an active IBM relationship, and frozen versions defeat a roadmap that needs new releases.

What happens if we need to return to IBM S&S?

Reinstatement requires paying the lapsed S&S plus an uplift, commonly totaling about 150 percent of what was skipped. Budget the return path before leaving and keep the entitlement archive that makes it negotiable.

Do we still need ILMT after leaving IBM support?

Yes, if you deploy perpetual licenses under sub capacity terms. The audit clause survives the support decision, so keep ILMT running and archive the quarterly reports.

Can a third party bid lower our IBM renewal without moving?

Yes. In our engagement file a credible, documented third party bid cut IBM renewals 10 to 20 percent even when the buyer stayed. The leverage only works when IBM believes the move is funded and dated.