Few events move an IBM account onto the audit list faster than a merger, an acquisition or a divestiture. The deployment changes hands overnight, but the entitlements that authorize it almost never move as cleanly. That gap between who is running the software and who actually holds the license is exactly what an audit is built to find.
Why corporate change draws an audit.
IBM software entitlements are issued to a named legal entity under Passport Advantage. They are generally not transferable to another entity without IBM's written consent. When two companies combine, when a business unit is carved out, or when a subsidiary is sold, the entity on the license and the entity now operating the software can quietly drift apart. IBM monitors corporate filings, support contact changes and renewal anomalies, and a transaction is a strong signal that the deployed footprint no longer matches the paper.
The non transfer problem.
The buyer of a business often assumes the IBM licenses come with it. In practice, the transfer requires IBM approval, and IBM may treat the moment as an opportunity to true up, reprice or convert the metrics. Common exposures include:
- Entitlements stranded in a seller entity that no longer uses the software, while the acquired operation runs on licenses it does not formally hold.
- Sub-capacity rights that do not survive the move because ILMT was never deployed in the acquired estate within the required window.
- Duplicate or overlapping deployments after integration, where the combined company runs more instances than the merged entitlement pool covers.
What changes in your estate.
Integration work reshapes the very things IBM measures. Servers are consolidated, virtual clusters are merged, and high-risk products such as WebSphere, Db2 and Cognos are migrated onto shared hosts. If the receiving estate counts cores differently, or if a Power LPAR now allocates more cores than before, your processor value unit position can climb without anyone provisioning a single new user. A merger is a capacity event as much as a legal one.
Treat any merger, acquisition or divestiture as a license event from day one. Inventory the IBM entitlements held by every entity involved, confirm in writing what IBM will consent to transfer, and freeze the deployed footprint against the combined entitlement pool before integration scrambles the evidence. The buyer side move is to reconcile the position yourself, on your timeline, rather than discovering the gap in an IBM data request.
How buyers stay ahead of the transfer audit.
The defensible path is to build the merged compliance position before IBM asks for it. That means mapping every product to the entity that holds its entitlement, documenting sub-capacity eligibility across the combined estate, and negotiating any required transfer and metric conversion as part of the deal rather than under audit pressure later. Done early, the transfer is an administrative step. Done late, it is leverage IBM holds over you.