License transferability under Passport Advantage.

Buyers tend to treat an IBM entitlement as a thing they own outright, free to deploy anywhere in the group. The Passport Advantage agreement takes a narrower view. The entitlement is a right to use the program within the scope the agreement defines, and that scope is tied to the contracting enterprise. Moving a license to a different legal entity, a newly acquired company, or a business unit being carved out is not automatic, and the rules that govern those moves become very real when an audit examines an estate that has reorganized since the licenses were bought.

This matters because corporate structures change far faster than license records do. Acquisitions fold new entities into the group, divestitures spin business units out, and shared service centers run IBM software on behalf of affiliates that were never part of the original Passport Advantage site. Each of these is a transferability question, and each can turn into a finding if the deployment outran what the agreement actually permits.

What the agreement controls

Passport Advantage defines an enterprise and a site, and entitlements are acquired and counted within that frame. Usage by entities inside the defined enterprise is generally covered, but usage by an entity that sits outside it, or that joined the group after the fact, is not covered simply because it shares a parent. Transfers to a third party are restricted and usually require IBM consent. Crucially, IBM software may continue running on the same servers after a corporate change, which is exactly how a perfectly licensed estate becomes an unlicensed one without anyone deploying anything new.

• Entitlements are scoped to the contracting enterprise, not the brand
• An acquired entity is not automatically inside your Passport Advantage site
• Transfers to a third party are restricted and usually need IBM consent
• A divested unit may lose coverage while the software keeps running

How it surfaces in an audit

The auditor asks for the corporate structure and compares it to the entitlement holder of record. Where a subsidiary is running WebSphere or Db2 under a parent's licenses but sits outside the contracted enterprise, that usage is treated as unlicensed regardless of intent. Mergers create the opposite problem, where the surviving entity assumes it inherited the other side's licenses cleanly when the agreement may require a formal transfer. These are not usage findings in the technical sense. They are entitlement scope findings, and they are won or lost on contract reading, not on core counts.

How we position it

We map the deployment against the precise contracting enterprise and the transfer history, and we read the agreement language that actually applies rather than the assumption that licenses follow the logo. Where a reorganization left coverage ambiguous, we build the argument that the usage sits within the defined enterprise, and where a genuine transfer is needed we make it part of the settlement so the forward position is clean. Entitlement scope is contestable, and a buyer who can document the corporate frame controls the conversation.