① Guide · outsourcing and license ownership
Outsourcing the mainframe does not outsource the license exposure unless the contract says so, clearly, product by product. Who owns the paper decides who answers the audit, who negotiates the renewal, and who is exposed at the exit. Here are the three models and the clauses to lock before you sign.
48 hour mobilization Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →Mainframe outsourcing deals are negotiated on service levels, transition timelines, and the unit rate. The license question is routinely treated as plumbing, deferred to a schedule nobody reads closely, and that deferral is where the cost hides. Most mainframe software agreements restrict transfer, sublicensing, and third party access, so the moment an outsourcer runs your software, on your hardware or its own, you are commonly in territory that requires the publisher's consent. Publishers know this, and they commonly treat the consent moment as an opening to reprice, to re scope capacity, or to argue the move is a new deployment.
The fix is not complicated, but it has to be deliberate. Decide which products you retain and which the provider holds, write it down product by product, and secure the transfer and outsourcing rights you need from the publisher before the outsourcing clock starts. Silence on this point is not neutral. It surfaces as a surprise at the first vendor audit, or as a trap at the exit when you try to bring the estate back and discover the licenses went with the provider.
Every mainframe outsourcing arrangement is one of three models, or a deliberate mix. The model decides where the risk lands:
| Model | Who holds the license | Where the risk lands |
|---|---|---|
| Customer license | You keep your own agreements; provider operates under them | You hold the audit exposure and negotiate renewals directly. You need rights to the provider's deployment data. |
| Provider license | The outsourcer licenses and bundles cost into the fee | Audit risk sits with the provider. You need the right to verify the passed through cost reflects an efficient estate. |
| Hybrid | Some products with you, some with the provider | Risk is split by product. The schedule must name each product and its owner, with no gaps. |
The clauses to lock before you sign
The leverage on every one of these clauses exists before the outsourcing deal closes and largely evaporates afterward. Once the transition is underway, the publisher knows you have committed to a provider, and the provider knows you are mid migration, and both price accordingly. The work to do up front is to reconcile the estate, decide the model deliberately, and negotiate the license position and the outsourcing agreement as one connected problem rather than two schedules drafted by different teams. This is where our mainframe license negotiation work sits, often alongside audit defense when a provider transition triggers a publisher review. For the related question of separating licenses in a corporate split, see divestiture and mainframe license separation, and for the in house alternative, in house vs outsourced mainframe.
It depends on the model, and it must be written down. Customer license keeps the paper with you, provider license moves it to the outsourcer, hybrid splits it by product. The expensive mistake is a contract silent on which is which.
Commonly, yes, and the vendor will use it as leverage. Most agreements restrict transfer and third party access, so the move often needs publisher consent. Negotiate the rights in before the outsourcing deal. See audit rights clauses to negotiate before you sign.
Whoever holds the license. If you retain it, the audit lands on you even though a provider runs the estate, so you need contractual rights to the provider's deployment data to defend it.
Before the outsourcing deal closes. The leverage exists up front and evaporates mid transition, when both the publisher and the provider know you are committed.
The same consent and transfer problem in a corporate event.
Negotiating the license position and the outsourcing deal as one problem.