Multi Entity Consolidation and IBM License Transfer

When companies merge, divest, or reorganize, software moves between legal entities long before anyone checks whether the licenses can follow. Passport Advantage entitlements are held by a specific enrolled party, and they do not flow across a corporate boundary just because the workload did. The workload moved; confirm the entitlement was allowed to.

Why entitlements do not move freely

A Passport Advantage agreement sits with a named enrolled entity, and the entitlements counted under it belong to that party. When an acquisition folds a subsidiary into a parent, or a carve out spins a division into a new company, the deployments often migrate to shared infrastructure overnight. The contractual right to use that software does not migrate on the same schedule. Transfers between entities generally require IBM consent and a formal assignment, and an installation now running under an entity that never held the entitlement is, on paper, unlicensed use. Auditors look closely at reorganizations precisely because the gap between operational reality and contractual record is widest there.

Where the audit risk hides

Three patterns recur. A parent consolidates subsidiaries onto one estate and assumes the largest entity's entitlements cover everything, when each subsidiary's licenses were enrolled separately. A divestiture leaves the buyer running IBM software with no assigned entitlement at all, because the transfer was never completed with IBM. And shared services consolidation runs one deployment for many legal entities, which can exceed the single entity's count or breach the terms on affiliate use. In every case the deployment looks efficient and the paperwork tells a different story.

• Entitlements are entity bound: they belong to the enrolled party, not to the group as a whole
• Transfers need consent: moving licenses across a corporate boundary generally requires a formal IBM assignment
• Divestiture orphans licenses: a carved out unit can end up running software with no entitlement assigned to it
• Shared services strain counts: one deployment serving many entities can exceed the single entity's right or breach affiliate terms

How buyers protect a consolidation

We reconstruct which entity holds which entitlement and map it against where the software actually runs after the reorganization. Where deployments crossed a boundary, we identify the transfers that need IBM consent and frame them before an audit reads the gap as unlicensed use. In a settlement, we treat the consolidation as leverage: the buyer is often willing to standardize and renew, and that future commitment is the counterweight to a transfer finding rather than a penalty paid on top of it.