What happens to my mainframe licenses when I outsource?

It depends on the structure. In a common arrangement, your licenses are placed into abeyance or suspension while the outsourcer hosts the environment and provides and pays for the software, often reducing maintenance cost. You typically still own the licenses, so if you change providers or bring the mainframe back in house you reinstate them. In other structures you transfer usage rights to the provider. Either way the move usually requires the publisher's consent and a check against transfer terms, designated or eligible machine clauses, and how capacity based metrics will be measured on shared provider hardware. The licensing mechanics, not the headline hosting rate, decide whether outsourcing actually saves.

Does outsourcing the mainframe always save money on licensing?

No. Outsourcing commonly reduces maintenance cost, with reductions often cited in the 20 to 40% range, because the provider aggregates volume and absorbs some software supply. But those savings can be eroded or reversed by the licensing details: consent fees or transfer charges from the publisher, capacity metrics that measure worse on shared provider hardware, MLC caps and SCRT based billing that do not carry over cleanly, and reversion terms that make it expensive to come back in house. The net result depends entirely on how the contract handles transfer, measurement, and exit, which is why the license terms have to be modeled before the headline rate is trusted.

Can I bring my mainframe back in house after outsourcing?

Usually yes, but the ease depends on how the original deal was structured. If your licenses were held in abeyance and you retained ownership, reinstating them and resuming direct payment to the publisher is relatively clean, often with no back maintenance owed for the abeyance period. If usage rights were transferred to the provider, repatriation can require renegotiating or repurchasing entitlements. The reversion and exit terms are among the most important and most overlooked parts of an outsourcing agreement, because they determine your leverage years later, so they should be negotiated up front, not when you are already trying to leave.

In House vs Outsourced Mainframe Licensing

In house vs outsourced mainframe: the license implications that decide it.

Outsourcing the mainframe commonly cuts maintenance cost, often cited in the 20 to 40% range. But whether it truly saves turns on the licensing mechanics: transfer rights, publisher consent, how capacity is measured on shared provider hardware, and the reversion terms that set your leverage years later. The headline hosting rate is not the answer.

Outsourcing is a sound move when the provider's volume genuinely lowers your software cost and the contract protects transfer, measurement, and reversion. It is a costly one when the headline hosting saving is quietly eroded by consent fees, worse capacity measurement on shared hardware, and exit terms that trap you. Keep the mainframe in house when control, direct publisher relationships, and a clean license position matter more than the maintenance reduction. The decision is a licensing decision wearing an operations costume.

In house vs outsourced, the licensing levers compared
Dimension	In house	Outsourced
Who holds the license	You, directly	Often you, held in abeyance, or transferred to the provider
Who pays the publisher	You	Commonly the provider, bundled into the hosting fee
Transfer and consent	Not required	Usually requires publisher consent and a transfer rights check
Capacity measurement	Your own machines and LPARs	Shared provider hardware; metric can measure worse
Audit responsibility	Yours to manage	Shared or provider led; contract must define it
Typical cost effect	Full direct cost, full control	Maintenance often down 20 to 40%, eroded by terms
Reversion and exit	Not applicable	Critical; abeyance reinstates cleanly, transfers may not

In house vs outsourced, the licensing levers compared

Dimension

In house

Outsourced

Who holds the license

You, directly

Often you, held in abeyance, or transferred to the provider

Who pays the publisher

You

Commonly the provider, bundled into the hosting fee

Transfer and consent

Not required

Usually requires publisher consent and a transfer rights check

Capacity measurement

Your own machines and LPARs

Shared provider hardware; metric can measure worse

Audit responsibility

Yours to manage

Shared or provider led; contract must define it

Typical cost effect

Full direct cost, full control

Maintenance often down 20 to 40%, eroded by terms

Reversion and exit

Not applicable

Critical; abeyance reinstates cleanly, transfers may not

Match the model to where you want control and where the real savings are:

Lean outsourced if

The provider's aggregated volume genuinely lowers your software cost beyond what you can negotiate alone
You can secure publisher consent and favorable transfer terms without punitive fees
You negotiate measurement on the provider's hardware and clean reversion rights up front

Stay in house if

Direct publisher relationships and full control of your license position are strategically important
Your capacity would measure worse on shared provider hardware, eroding the headline saving
You are unwilling to accept reversion or exit terms that weaken your leverage at the next renewal

Whichever way you go, the non negotiable is to model the licensing before the operations. Carry your MLC caps, SCRT based billing, and pooling protections into the agreement explicitly, hold licenses in abeyance rather than transferring them where you can, and negotiate reversion at the start. Those terms decide the economics far more than the hosting rate on the cover page.

What happens to my licenses?Commonly they go into abeyance while the provider hosts and pays for the software, and you retain ownership. The move usually needs publisher consent and a transfer rights check.

Does outsourcing always save?No. Maintenance often falls 20 to 40%, but consent fees, worse capacity measurement, and exit terms can erode or reverse it. The terms decide, not the rate.

Can I come back in house?Usually, but cleanly only if licenses were held in abeyance. If usage rights were transferred, repatriation can mean renegotiating or repurchasing. Settle reversion up front.

What is most overlooked?Carrying MLC caps, SCRT billing, and pooling protections into the new agreement, and negotiating exit terms before you sign rather than when you want to leave.

An operations decision that is really a licensing decision.

Explainers: mainframe outsourcing and license transfer rules and hardware model capacity ratings and software cost. Other comparisons: Tailored Fit Pricing vs sub-capacity and annual vs multi year terms. Hub and commercial: the IBM buyer side guide, mainframe contract review, and mainframe cost optimization.

In house vs outsourced mainframe: the license implications that decide it.

The verdict

Head to head

Who should pick which

Frequently asked

We model the license, not the brochure. That is where it saves or sinks.