① Guide · product retirement
A mainframe product can be decommissioned operationally and still cost you, because the contract, not the machine, decides what you pay. Bundles, co-termed renewals, and maintenance back charges turn a clean retirement into a penalty. Here are the six traps, and how buyers sunset a product without paying to leave.
The machine stops running it. The contract keeps charging.
Retiring a mainframe product feels like an operational task: migrate off it, uninstall it, stop using it. But the cost lives in the agreement, and the agreement is usually written to make leaving expensive. A product inside a bundle may have no defined credit when removed. A renewal co-termed across the portfolio may reprice the survivors when one drops out. And maintenance that lapses on a product still installed, or still counted as deployed, can trigger a back charge that dwarfs the saving.
The result is a familiar pattern: a team proudly decommissions a tool, stops the maintenance to capture the saving, and discovers at the next true up or audit that the exit cost more than the license. Sunsetting cleanly is a contract exercise first and a technical one second. The traps below are the ones we see most often, with the move that defuses each.
| Trap | How it bites | The move that defuses it |
|---|---|---|
| Bundle with no part price | Removing one product yields no credit; the bundle prices the whole. | Establish standalone value of what you keep before negotiating removal. |
| Co-termed repricing | Dropping one product re rates the survivors at the next co-term. | Model the survivor price before, not after, the removal. |
| Volume commitment breach | Removal drops you below a minimum that unlocked a discount. | Check the commitment floor before you reduce the portfolio. |
| Maintenance back charge | Lapsed support plus reinstatement costs more than the saving. | Confirm out of scope in writing before maintenance stops. |
| Still installed, still counted | Decommissioned in use but left on the machine, so still deployed. | Verify genuine uninstall and capture evidence of the date. |
| Mid term timing | Removing mid term, when only the vendor benefits from the lock in. | Time the exit to a renewal or term boundary when the deal is open. |
These are patterns we commonly observe across publishers, not provisions of any one contract. Your own agreement language governs; read the termination, co-term, and maintenance clauses before acting.
Confirm out of scope before you stop paying.
A clean sunset runs in a deliberate order. Read the agreement for the termination, co-term, maintenance, and minimum commitment clauses tied to the product. Model what the products you keep will cost once the target is gone, so a hidden repricing does not surprise you. Verify the product is genuinely uninstalled, with a dated record, so it cannot be counted as deployed in a later audit. Then, at a renewal or term boundary, agree in writing that the product is out of scope and that maintenance ends without a back charge or reinstatement exposure.
Sequenced that way, the saving is real and it holds. Reversed, with maintenance stopped before the contract position is confirmed, the exit becomes the penalty. This is closely tied to our cost optimization work and to the leverage we build in every license negotiation, because the best time to remove a product cleanly is the same moment you are renegotiating the rest.
④ What changes with us in the room
The vendor prices the exit to deter it. We price it to take it.
Typical renewal reduction we negotiate
Engagements delivered since 2019
Mainframe spend negotiated on the buyer side
Sometimes, but the contract decides, not the decommission. Bundles, co-terms, and minimum commitments can breach when one product leaves. Time the removal to a renewal or term boundary, confirm in writing the product is out of scope before maintenance stops, and check that dropping it does not re rate the products you keep.
The most common penalty. Let support lapse on a product still installed or later needed, and reinstatement commonly requires back maintenance plus a fee that can exceed the saving. Confirm the product is genuinely uninstalled and formally out of scope before support stops. See the real cost of leaving.
Carefully, since the bundle resists it. Bundled deals often price the whole, not the parts, so there may be no credit for removing one. Establish the standalone value of what you keep, test whether the bundle is genuinely cheaper, and negotiate removal at renewal when the whole agreement is open rather than mid term.
At a renewal or term boundary, when the agreement is open and you are renegotiating the rest. That is when removal carries the least penalty and the most leverage, because the vendor wants the renewal and you can write the exit terms into the same deal. See our vendor consolidation playbook.
Related: cost optimization service · the mainframe exit question · vendor consolidation playbook · all publisher hubs
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →