① Explainer · Licensing concept
Moving your mainframe to an outsourcer does not move your licenses with it. Most agreements tie the license to a machine, a customer, or a site, and a transfer needs the vendor's consent. Get the rules wrong and you have created an audit finding. Here is how transfer, abeyance, and reinstatement actually work.
The licenses are yours. The right to run them on someone else's machine is not, unless your contract says so. That gap is where outsourcing deals go wrong.
Mainframe software licenses are commonly tied to a named machine serial, a specific customer entity, or a physical location. When you outsource the mainframe to a managed service provider, the workload moves to the provider's machine, which is a different serial, often a different legal entity, and a different site. Unless your agreement grants a transfer or assignment right, that move can constitute unlicensed use of the software, the precise condition a vendor audit is built to detect.
There are two clean ways through. Under a transfer or assignment, the vendor consents to the license moving to the named outsourcer. Under an abeyance arrangement, you keep ownership of the license but suspend it while the provider supplies and pays the vendor for the software running your workload; when you insource again or switch providers, you reinstate the suspended license, commonly without back maintenance. Both depend on rights written into the contract before the outsourcing deal closes. The decision tree below shows which path applies.
Run each license through these questions before the outsourcing transition. The answers determine whether you can move it, must renegotiate, or are walking into an exposure.
| Question | If yes | If no |
|---|---|---|
| Does the agreement grant transfer or assignment rights? | Confirm the outsourcer is a permitted assignee | Seek vendor consent before any move; treat as a negotiation trigger |
| Is the license tied to a machine serial? | The new serial must be added or substituted | Check whether it is tied to entity or site instead |
| Will the provider supply and pay the vendor (abeyance)? | Suspend your license; document reinstatement terms | You remain the licensee on a machine you no longer run |
| Are reinstatement rights documented for insourcing? | You can bring it back without repurchase or back maintenance | Insourcing later may mean buying the license again |
| Does the estate shrink at the provider? | Exercise true-down so you stop paying for old capacity | You pay the old volume on a smaller footprint |
The single most expensive answer is "no" on transfer rights discovered after the deal is signed. At that point the vendor sets the terms, because the workload is already running where the contract does not permit. Resolve every row before the transition, not during the audit that follows it.
Outsourcing bites when the licensing work is treated as a back office formality after the commercial deal is done. By then the vendor knows the workload is moving and holds the consent you need. The rights below are far cheaper to secure while you still have a credible alternative, namely staying in house or choosing a different provider. Each closes a specific exposure that surfaces in transitions we commonly see.
| Right | What it protects | Exposure if missing |
|---|---|---|
| Assignment to named outsourcer | The legal move of the license to the provider | Unlicensed use on the provider's machine |
| Reinstatement on insourcing | Bringing work back without repurchase | Buying the license a second time |
| Cross machine and cross site usage | Running on the provider's serial and location | License tied to a machine you no longer operate |
| True-down on consolidation | Paying only for the capacity actually used | Paying old volume on a smaller estate |
| No back maintenance on abeyance | Clean reinstatement after suspension | A maintenance bill for the dormant period |
Transfer, abeyance, and reinstatement terms vary by vendor and by contract, and vendors commonly treat an outsourcing transition as a moment to review or renegotiate. The structure described here is the pattern we see; the specific rights in your agreements have to be read individually.
Outsourcing changes the machine your software runs on, so it interacts directly with model capacity ratings and the MSU your provider's box reports. If you are weighing the move at all, read in house versus outsourced mainframe for the full license implications. Because an outsourcing transition is a vendor leverage point, it commonly arrives alongside renewal pressure, which is the work on mainframe license negotiation and, when the vendor turns it into a review, audit defense.
Audit notice or renewal under 18 months out? We mobilize within 48 hours. Moving your mainframe to a provider? Have the transfer rights read before the workload moves, not after.
No. Most mainframe software agreements tie the license to a named machine, customer, or location, and transfer to an outsourcer requires the vendor's consent. Without an explicit transfer right or assignment clause, moving the workload to a provider's machine can constitute unlicensed use, which is exactly the situation an audit is designed to find.
Under an abeyance arrangement, you keep ownership of your license but suspend it while the outsourcing provider supplies and pays the vendor for the software running your workload. If you bring the work back in house or change providers, you reinstate the suspended license. The pattern commonly avoids repurchasing and can reduce maintenance cost during the outsourced period.
Negotiate the right to assign or transfer licenses to a named outsourcer, the right to reinstate on insourcing without back maintenance, the ability to move usage across locations and machines, and true-down rights so a smaller estate at the provider does not still pay for the old capacity. These rights are far cheaper to secure before you sign the outsourcing deal than after.
An outsourcing move changes who runs the software and on what machine, which touches the exact terms vendors use to define a license. It is also a moment of leverage for them: consent can be made conditional, and an estate moving providers without clean transfer rights is exposed. Vendors commonly treat outsourcing transitions as a trigger for review or renegotiation.