IBM third party support for Db2, WebSphere and MQ. What it saves, and what a return costs.

Moving stable Db2, WebSphere and MQ versions to a third party provider cuts their support cost by roughly half. Even if you stay with IBM, a credible written bid lowers the renewal.

What does IBM third party support cover, and what does it leave out?

Third party support replaces the break fix, how to, and workaround service you buy from IBM as Software Subscription and Support (S&S), typically at roughly half the price. What it cannot deliver is IBM intellectual property. New versions, fixpacks and vendor security patches stay with IBM.

Licenses bought under Passport Advantage are normally perpetual, so they stay valid after S&S ends. What you give up is the S&S bundle: new versions and releases from Passport Advantage Online, fixes from Fix Central, and IBM help with routine installation, usage and code related questions. S&S runs 12 months at a time, so every anniversary is a decision point.

What good providers put in place of IBM fixes

Good providers make up for the missing IBM code with senior engineers, custom workarounds and security guidance written for the exact versions you run. You reach an engineer who knows your configuration instead of opening a ticket and waiting for triage. That difference in service model is what buyers notice day to day.

Coverage varies by provider and product. Origina specializes in IBM software, and Rimini Street supports Db2 among other IBM products. Get each bidder's supported programs and versions in writing before you compare prices. Our current IBM third party support guide and third party support report compare the options.

Which IBM products are a good fit for third party support?

Stable versions of Db2, WebSphere and MQ that you plan to keep running as they are fit well. A frozen version needs no new IBM intellectual property, so the service you buy is the service you use. Fast moving products, subscription products and anything with a Cloud Pak conversion on its roadmap do not fit.

Expect a mixed answer. A single decision across the whole IBM portfolio, in either direction, gets one half of it wrong. Our guides to Db2 licensing, WebSphere licensing and MQ licensing cover how each product is counted.

How IBM's all or none rule shapes the decision

IBM's International Passport Advantage Agreement says that if you keep S&S for a program at a site, you must keep it for all uses and installations of that program there. So you decide per program and site. You cannot keep IBM support on production Db2 and drop it on test Db2 in the same location.

Why does a third party bid lower the IBM renewal even if you stay?

A bid lowers the renewal because IBM can verify it easily. Buyers who ran the evaluation, obtained a credible bid and then stayed with IBM still cut their renewal by 10 to 20 percent. The option has value even when you never exercise it.

A migration threat at most vendors asks the vendor to believe a cost and a timeline it can dispute. A third party support bid is a priced document from a named provider. It covers products IBM knows are static, at a price IBM can compare with its own, so there is very little to argue about.

Why we disagree with "only ask for a quote if you mean to switch"

The usual advice says a quote you will not use is a bluff IBM will call, so skip it unless you are ready to leave. We disagree. IBM can check the provider, the price and the product list against its own records, so the bid is not a bluff and does not need to be carried out to work.

The better course is to run a proper evaluation on the products that fit, put the written bid on the table at renewal, and decide on the numbers. Where moving pays, move those products. Where it does not, take the lower IBM price.

What the IBM account team will say, and what to say back

• "Third party support puts you out of compliance." Ask which clause they mean. The licenses are perpetual, and the Passport Advantage Agreement treats S&S as something you elect to continue.
• "You will lose fixes and security patches." Agree. That cost is priced into the decision, and the bid covers only versions that need no new IBM code.
• "Coming back later will be expensive." Also true, which is why you have priced reinstatement already. The comparison on the table is the renewal price IBM offers today.
• "You cannot drop support on part of a product." Correct, and the plan is built per program and per site, which is how the agreement reads.
• "Stay and we will add credit toward a Cloud Pak." That only matters for workloads with a Cloud Pak on the roadmap. Ask for it priced separately from the renewal of the static products.

How much can third party support save on an IBM renewal?

On the products you move, expect to save 40 to 60 percent of their support line, which is what stable middleware and database versions saved in our engagements. On products you keep with IBM, a tabled bid lowers the renewal instead. The worked example below shows both routes on the same hypothetical bill.

Say your annual IBM S&S renewal is $1,000,000. Frozen Db2 versions account for $350,000, frozen WebSphere versions for $250,000, and MQ, which you plan to upgrade, for $150,000. The remaining $250,000 covers products with a Cloud Pak conversion planned.

Moving saves more each year but carries the return risk. Bidding saves less and keeps every IBM right in place. The $400,000 left with IBM in the third option is still a renewal you can negotiate.

What coming back would cost in this example

Suppose you move the $600,000 of Db2 and WebSphere support and want IBM back after 3 years. If IBM prices back maintenance at the same annual rate, that is $1,800,000 before any penalty. Your saving over those 3 years was $720,000 to $1,080,000, so a return then costs more than you saved.

How do you keep a way back to IBM support?

You keep it by preparing before the switch, because IBM will not simply renew expired S&S. Under the Passport Advantage Agreement you must buy Software Subscription and Support Reinstatement instead, which brings back maintenance plus a penalty that can erase years of savings. Freeze these before the last IBM anniversary you pay for:

• Proof of entitlement for every product. After the switch, the records proving what you hold become considerably harder to obtain.
• Media archives for every version in use. Access to IBM download channels changes, and a reinstall you cannot perform is an outage you cannot fix.
• ILMT records and a clean report. Sub capacity entitlement stays conditional on instrumentation whoever provides support.
• A documented return path. This is what turns a decision you cannot undo into one you can.
• A fit assessment per product. It separates static versions that fit from fast moving and subscription products that do not.
• The Cloud Pak roadmap check. The conversion route is shut while you are off IBM S&S, and reopening it is part of the return cost.

How to check your own position before you switch

1. Passport Advantage Online. Export your entitlement and proof of entitlement records while your S&S is still active, and download installation media for each version you run.
2. Installed versions. Record exact levels with db2level for Db2, dspmqver for MQ and versionInfo.sh for WebSphere Application Server, so the provider bids on what is deployed.
3. ILMT. Generate and store an audit snapshot, and confirm the reports cover every server running the programs you plan to move.
4. Architecture plans. Ask application owners in writing which workloads are due for an upgrade or a Cloud Pak conversion.

Contract wording to ask for

• From the provider, a named coverage list. Every program and version by name, so scope is never in dispute.
• From the provider, response times by severity. The concierge service should be in the contract.
• From the provider, security guidance per frozen version. It replaces the IBM patches you give up.
• From the provider, a price hold and an exit on notice. Line the notice up with your IBM anniversary so a return is possible without paying twice.
• From IBM, written reinstatement terms before you lapse. Put the return cost in the business case as a number.
• From IBM, a cap on the renewal price for what you keep. Our note on renewal uplift cap wording gives clause language.

Does leaving IBM support increase audit risk?

Not directly, because your license terms and IBM's audit rights stay the same, but it raises the stakes on your entitlement records. Entitlement hygiene decides IBM audits, and a company that has left IBM support still has to evidence what it holds.

Leaving S&S changes who fixes your problems. Sub capacity counting still depends on ILMT, as our ILMT and sub capacity guide explains, and records should be frozen before the switch because rebuilding them later is slow. Our outline of the IBM audit process shows what auditors ask for first.

Common mistakes and what they cost

• Dropping support on part of a program at a site. This breaks the all or none rule and leaves you exposed to a claim for S&S on every installation.
• Applying IBM fixes released after the lapse. Fixes and versions IBM releases after your S&S ends are not covered by your entitlement, even if a download link still works.
• Letting ILMT drift once IBM support is gone. Without current reports, IBM can count full capacity on every server running the program.
• Switching mid term. You have already paid IBM to the anniversary, so an early switch pays for support twice.
• Moving a product with a Cloud Pak conversion planned. You pay reinstatement to reopen a path you needed all along.

What have we seen in IBM third party support decisions in 2024 and 2025?

Across roughly 20 to 30 IBM customers we advised in 2024 to 2025, third party support was evaluated far more often than it was adopted, and both outcomes paid.

• Customers who moved. They moved static Db2, WebSphere and MQ versions that needed no new IBM intellectual property, got the saving shown in the worked example, and saw no measurable service degradation.
• Customers who stayed. They got the bid outcome described earlier, a lower IBM renewal with every IBM right intact.
• Return path. Roughly 18 of 25 engagements kept a documented return path by freezing entitlements, media archives and ILMT records before the switch, at almost no cost when done at that point.
• Service. Service quality was not what made the decision hard. Buyers reported the concierge model as better than the IBM ticket queue. The return path was the hard part.

Freezing entitlements, media and ILMT records costs almost nothing before the switch, and it is what makes the decision reversible.

When should you start the evaluation before an IBM renewal?

Start about a year before the S&S anniversary. A credible bid needs a product inventory, provider due diligence and time for IBM to respond, and none of that fits into the last month.

What to do next

1. Run the evaluation regardless of intent. A credible bid lowers the IBM renewal even if you stay.
2. Assess fit product by product. Separate static Db2, WebSphere and MQ versions from fast moving and subscription products, and respect the all or none rule per site.
3. Check the Cloud Pak roadmap. Keep anything you plan to convert on IBM S&S, because the conversion runs through IBM support.
4. Freeze entitlements, media archives and ILMT records before switching. This is what keeps the way back open.
5. Price the return before you go. Include back maintenance and the reinstatement penalty, so the decision is taken with the exit cost visible.
6. Get help if you want it. The IBM practice runs the assessment with you, our IBM vendor management guide covers the wider relationship, and the IBM knowledge hub holds the rest of our IBM library.

Frequently asked questions