Mergers, acquisitions, and divestitures can dramatically impact IBM software licensing. IBM licences are non-transferable by default — CIOs must navigate strict transfer policies, ILMT compliance, ELA renegotiation, Passport Advantage restructuring, and heightened audit risk. This playbook provides the strategic framework to protect your organisation through every stage of corporate transition.
IBM's licensing agreements include clauses that restrict the transfer of licences between organisations. Understanding these policies is essential before any M&A transaction closes.
IBM software licences cannot be freely transferred to another company without IBM's explicit approval. If Company A acquires Company B, B's IBM licences do not automatically belong to A. Passport Advantage defines a customer's "Enterprise" (typically entities with >50% ownership). Any change in corporate structure can alter which entities are entitled to use the software.
Written consent from IBM is mandatory for any licence transfer. This involves notifying IBM of the transaction, providing documentation of the business change, and waiting for IBM to review contract terms. Without approval, continued use by a new entity may be considered unlicensed usage — exposing both parties to audit risk.
Changes in infrastructure or data centre consolidation can affect sub-capacity entitlements. New VM placements might increase PVU counts. ILMT must be deployed and updated across the new environment within 90 days. Failure to update ILMT can result in forfeiture of sub-capacity rights, forcing full-capacity licensing — a potentially enormous cost increase.
If two companies with separate ELAs merge, the combined usage may exceed current terms. If a company under an ELA divests a division, that division loses ELA coverage. Non-renewal or significant changes to an ELA often trigger audits, as IBM checks for compliance gaps once blanket coverage is altered.
Passport Advantage agreements frequently require notifying IBM of a change in control or ownership within a specified timeframe. These clauses dictate rights to continue using software and may require reaffirming that all entities are correctly licensed.
The new owner may need to re-establish support contracts in their name after the transfer. IBM typically does not allow splitting support without a formal transfer. Lapsed support can incur hefty back-maintenance fees if not addressed quickly.
Scenario: Companies A and B, both IBM customers, merge to form a single organisation. Each has IBM software deployed under separate Passport Advantage agreements or ELAs.
Inventory all IBM licences from both entities. Engage IBM early to merge Passport Advantage agreements or consolidate entitlements under a single master account. Two separate licence estates must become one.
Run ILMT across the combined infrastructure immediately. Recalculate PVU usage when combining server farms. New VM placements from data centre consolidation can inadvertently exceed licensed capacity.
Review ELA terms for change-of-control provisions. Renegotiate a new ELA covering the merged entity's full portfolio. Use increased scale as leverage for better pricing or broader product coverage.
Systems from both companies will run in parallel during integration. Request IBM's approval for temporary transitional arrangements — IBM often permits time-bound cross-usage (6–12 months) via a written rider or interim licence.
Mergers are a known audit trigger. Proactively document all steps — inventory lists, IBM communications, transfer approvals, ILMT reports. Conduct a self-audit with a third-party expert immediately after completion.
Scenario: Company A acquires Company C, a smaller firm that heavily uses IBM middleware (WebSphere, Db2) and perhaps IBM Cloud Pak solutions. Company C's software was licensed under its own contracts.
Immediately review C's IBM contracts. Submit a formal request to IBM to transfer C's licences to A. Both parties must co-sign. If IBM approves, C's Proofs of Entitlement (PoEs) and support can be reissued under A's account.
If C was out of compliance (e.g., missing ILMT or over-deployed), A inherits the risk. During due diligence, audit C's IBM deployments. If shortfalls are found, negotiate with IBM before finalising the acquisition if possible.
Cloud Paks use container-based VPC metrics and include Red Hat OpenShift rights. Ensure existing Cloud Pak licences are transferred or plan a "trade-up" where A replaces C's deployment with its own entitlements. Verify version alignment.
After acquisition, identify duplicate IBM capabilities. Engage IBM or an independent advisor to consolidate licences and reduce costs. Use the acquisition as an opportunity to rationalise the IBM software footprint.
Work with IBM to co-term maintenance renewals. Align support renewal dates and terms so acquired software is on the same schedule as A's environment — simplifying budgeting and future ELA negotiations.
Navigating an IBM licensing transition during M&A? Get expert guidance.
IBM Advisory Services →Scenario: Company A is divesting Division X, which relies on various IBM software products. Following divestiture, Division X will become a new independent company or be acquired by another firm.
Option 1 — Transfer: Seek IBM's approval to transfer licences to the new owner. IBM will evaluate if transfers meet policy. Option 2 — New Licences: If transfer is not feasible, the new entity must purchase new IBM licences. Plan for this cost in deal negotiations.
Division X may have used shared IBM instances or shared infrastructure. Establish clear boundaries. For shared systems, decide if X will run its own environment (requiring new licences) or if A will provide services under a Transition Services Agreement (TSA) — which requires IBM approval.
If Division X was not a separate PA site, its entitlements are intermixed with A's. Work with IBM to identify which entitlements are allocated to X's usage and transfer them into a new account for the buyer.
Conduct an internal compliance check on Division X's IBM usage before the divestiture closes. Resolve any over-deployment to give the new owner a clean slate. IBM holds the original company responsible for shortfalls up to separation.
After spin-off, NewCo must quickly establish its own Passport Advantage agreement and, if necessary, negotiate an ELA. NewCo should build its direct relationship with IBM from Day 1 rather than relying on transferred licences indefinitely.
IBM generally prohibits the use of licences for the benefit of third parties without permission. If A will temporarily host services for X after the sale, IBM must explicitly approve this TSA arrangement. Failing to secure approval can expose both companies to audit penalties.
| Aspect | Merger (Two Companies Combine) | Acquisition (A Buys B) | Divestiture (Spinning Off Division) |
|---|---|---|---|
| Licence Ownership | Two sets of licences must be consolidated under one surviving entity. | Acquirer seeks ownership of target's licences. Transfer requires IBM approval; otherwise buy new licences. | Original company retains licences unless transferred. New entity/buyer must receive transferred entitlements or purchase new. |
| Passport Advantage | Two PA agreements/sites to merge into one. Requires IBM coordination to move entitlements. | Target's PA site moved under acquirer's PA agreement (with IBM approval). If target isn't in PA, acquirer may need to enrol. | If divested unit had separate PA site, it transfers to buyer. If not, entitlements must be split out — a complex task needing IBM's help. |
| Sub-Capacity & ILMT | Unify sub-capacity reporting. Deploy ILMT across merged infrastructure. Recalculate PVU counts. | Extend ILMT to acquired servers. Ensure acquired environment was compliant. Integrate different data centres for sub-capacity tracking. | Divesting unit needs its own ILMT post-separation. During transition, track usage separately. Both parties must maintain compliance through handover. |
| ELA / Enterprise Agreement | Renegotiate new ELA for merged entity. Use combined spend for better terms. Existing ELAs may be terminated or merged. | Fold target's products into acquirer's ELA. Increased footprint could justify new ELA. Target's pre-existing ELA may need novation or cancellation. | Amend original ELA to remove divested usage (possibly reduce costs). Divested entity may need its own ELA or alternate licensing. |
| Transition Period | High risk if each uses other's licences without permission. Seek IBM approval for interim use (typically 6–12 months). | Acquired software must be licensed immediately under new owner. Keep using seller's support via TSA or fast-track transfer. | Seller often provides IT services to NewCo via TSA. IBM must authorise seller's licences for NewCo use during this period. |
| Audit Risk | Elevated. IBM audits merged entities frequently, knowing integration complexity causes compliance slip-ups. | Elevated. IBM may audit post-acquisition, especially if target had compliance issues or large licence movement. | Elevated. Both seller and buyer face audit risk. Seller audited for improper licence sharing; buyer for purchasing necessary licences. |
Before the deal (merger, acquisition, or divestiture) is finalised, CIOs and IT leaders should complete every item on this checklist.
Assemble IT asset managers, legal counsel, procurement, and third-party IBM licensing specialists. Make this team responsible for all software licensing aspects of the deal.
Catalogue every IBM deployment in scope — product names, versions, quantities (PVUs, users), licence types (perpetual vs. subscription), and current support status. Do this for both your organisation and the other party.
Gather Passport Advantage agreements, MLAs, ELAs, and Proofs of Entitlement. Pay special attention to clauses about mergers, acquisitions, and change of control. Note which licences are perpetual (owned) vs. term (rented).
For each IBM product, determine if transfer is allowed. Identify geographic or entity restrictions. Most products can transfer with IBM approval, but some older or special licences may not.
Conduct a compliance health check. Are all deployments within entitled limits? Has ILMT been running properly for all sub-capacity products? Identify compliance gaps now — they must be addressed before or immediately after closing.
Inform your IBM account manager (under NDA if needed) that a corporate event is planned. Early dialogue opens options — IBM may share its M&A licensing guide and assign specialists to assist.
Outline how IT systems will be combined, separated, or cooperated during transition. If the plan involves a TSA, document licensing needs to discuss with IBM. TSAs require explicit IBM approval.
Include a line in the deal budget for potential licence purchases. M&A often reveals the need for additional licences. Use worst-case compliance gap estimates to inform this number.
Have an independent IBM licensing advisor review your plans to ensure compliance. They can validate the approach, identify hidden risks, and suggest negotiation points with IBM.
Need an independent IBM licensing assessment before your deal closes?
IBM Licensing Assessment →Once the transaction is completed and Day 1 of the new organisation arrives, the CIO's team should execute the following immediately.
Work with IBM to complete agreed-upon transfers. Ensure written confirmation of entitlement transfers in Passport Advantage or via updated entitlement documents. Save all records.
If a new entity was created, register for Passport Advantage and set up its account. If a combined entity was formed, rationalise old PA accounts. Sign and activate any negotiated ELAs.
Unify ILMT into a single reporting system for merged environments. For spin-offs, set up ILMT separately. Run a fresh baseline report to confirm deployment vs. entitlement in the new structure.
In the chaotic early months, systems change constantly. Keep tight watch on IBM software usage. Have the licensing team review any IBM installation requests during the transition period.
After merging, identify redundant IBM software and plan to decommission. Coordinate with IBM — dropping licences may affect ELA commitments. Schedule for next renewal cycle if possible.
Double-check that all IBM products are covered under current support contracts. If any support was dropped due to the organisational change, contact IBM to reinstate immediately. Lapsed support incurs hefty back-maintenance fees.
Maintain an updated licence position document reflecting the post-deal state. Include licence counts, agreements, usage assignments, and new purchases. This document is critical for any future audit.
After the merger or acquisition, the combined organisation may benefit from a different licensing model. Engage IBM to renegotiate terms. Many CIOs plan ELA renegotiation a few months after the M&A, once they have clarity on needs.
By then, systems will have settled. This audit catches compliance drift — overlooked servers, admin-created IBM instances outside ILMT tracking. Early detection allows remediation before IBM's official auditors arrive.
If new teams are now responsible for IBM licensing, train them on IBM compliance basics — ILMT usage, counting PVUs, IBM's definition of "enterprise." Share internal software asset management policies.
IBM is more likely to cooperate — and perhaps be lenient or creative in solutions — if you bring them into the loop before they discover a change through press releases or audit. Early engagement can lead to IBM providing written guidance, bridge licences or temporary waivers during transition, and better positioning in subsequent negotiations.
Ensure the definition of your "enterprise" in the ELA covers newly acquired entities. If Company B was acquired, are they explicitly named or covered by the >50% ownership rule? Update the contract to list new subsidiaries or exclude spun-off ones.
M&A can alter software allocation. You might be under-utilising some licences and over-utilising others. IBM may allow a one-time rebalancing — swapping surplus Product X licences for needed Product Y to align with new usage patterns.
ELAs often involve committed spend or prepaid amounts. A merger could increase usage (requiring an upsell), while a divestiture might leave you paying for more than you need. Negotiate with IBM to adjust financial terms via amendment.
Sometimes companies use M&A to exit an ELA (e.g., the acquired company's ELA is terminated in favour of the parent's agreements) or to sign a new one to cover a broader licence set enterprise-wide. Early termination may incur penalties unless negotiated.
When negotiating new or updated contracts, try to include flexible provisions for future changes. For example, a clause allowing some licence transfer rights in case of future divestiture. While not always granted, it cushions future M&A events.
Use the M&A moment to optimise IBM licensing — eliminate waste, consolidate duplicate capabilities, and secure better terms through combined negotiating power. The combined entity's increased IBM spend can be leveraged for deeper discounts, broader product coverage, or more favourable ELA terms.
Facing an IBM ELA renewal or renegotiation during an M&A event?
IBM ELA Renewal Service →IBM actively enforces licence compliance. M&A events raise several audit red flags that CIOs must understand and mitigate.
If IBM isn't formally notified, they may become aware through press releases, industry news, or purchasing pattern changes. Unreported changes are viewed negatively. IBM could suspect unlicensed usage and initiate an audit.
Overlooked licence transfers or a divested unit continuing to use software without valid licences. IBM auditors will review current enterprise usage and historical usage around the transaction time.
Not renewing an ELA — a common M&A decision — can trigger an audit within a year. IBM checks if you are over-deployed beyond what you retained in perpetual licences after the ELA coverage ends.
Merging two companies' IT could double capacity without equivalent licence growth — a major red flag for IBM. Significant IT infrastructure changes coinciding with M&A are closely watched.
If a divested unit used the parent's software illegally after separation, both companies face penalties — the parent for sharing licences and the divested company for using unauthorised software. Proper separation with IBM's approval protects both parties.
Non-compliance found in an audit can lead to hefty back-maintenance fees, required purchase of licences at list price (no discount), and in severe cases, legal action. The financial impact can be in the tens of millions — as demonstrated by audit claims exceeding $35 million for a single government entity.
Make software asset evaluation a standard part of due diligence. Just as you review financials and HR liabilities, review software licence liabilities and assets. Licence compliance gaps can represent multi-million-dollar exposure.
Independent advisors provide unbiased compliance assessment and cost-effective strategy. They know IBM's playbook, can foresee issues, and negotiate on your behalf. Engaging experts at the planning stage typically pays for itself by identifying savings or avoiding audit penalties.
Organisational change brings new teams and staff. Instil the importance of software compliance from the start of the new organisation. Conduct quick training sessions on IBM rules in the new context for all IT staff.
Budget as if you might need to purchase substantial additional licences or settle an unexpected compliance bill. Work diligently to avoid needing to spend it by achieving compliance and negotiating well.
Maintain a comprehensive paper trail of all IBM communications, licence transfers, approvals, and internal analyses. This helps with audits and facilitates knowledge transfer during personnel changes.
When negotiating new or updated contracts, include flexible provisions for future changes — clauses allowing licence transfer rights in case of future divestiture or clauses that cushion future M&A events.
Facing an IBM audit post-M&A? Our former IBM auditors defend your position.
IBM Audit Defence Service →Whether you're planning a merger, completing an acquisition, or executing a divestiture — Redress Compliance provides expert, independent IBM advisory from former IBM auditors and licensing specialists.
Download our complete IBM licensing knowledge hub — playbooks, guides, and case studies.
IBM Knowledge Hub →