Migrating WebSphere to Cloud Pak for Applications.

What the trade-up actually does.

Cloud Pak for Applications bundles WebSphere along with a runtime and tooling stack under the Virtual Processor Core metric. The migration converts an existing WebSphere PVU entitlement into a VPC entitlement at a defined ratio, so the question that decides the economics is how many PVU collapse into how many VPC. The ratio, and what is included in the bundle, are the levers. Treat the conversion as a contract negotiation, not an administrative swap.

Where double counting hides.

The most common post-migration finding is paying twice. The classic pattern: the Cloud Pak entitlement is purchased and deployed, but the original standalone WebSphere installs are never decommissioned, and the old PVU entitlement is never formally retired. At audit, IBM sees both footprints and counts both. The migration was supposed to replace the old license, but on paper the customer is now carrying two overlapping entitlements and is exposed on whichever one is under-licensed.

• Confirm the trade-up ratio and exactly which programs the VPC bundle includes
• Decommission the standalone WebSphere installs the Cloud Pak replaces
• Retire the superseded PVU entitlement in writing, not just in intent
• Bring the container VPC footprint under ILMT or an approved tool within 90 days

The new metric brings new duties.

Once on Cloud Pak, the deployment is governed by VPC and the container rules. Sub-capacity reporting and ILMT now apply to the VPC footprint under Passport Advantage v11, and container non-compliance means IBM charges for all cores in the cluster. A migration that solves an old WebSphere PVU problem can therefore create a new container reporting problem if the discovery tooling does not follow the workload onto the cluster.

What this means under audit.

A migration is the moment to get the entitlement record clean, which is why it belongs in the Contain and Reconcile discipline of Contain, Reconcile, Challenge, Settle. Reconcile both footprints during the move: prove the old WebSphere installs are gone and the old entitlement retired, and confirm the new VPC count is reported correctly. Done that way, the trade-up removes exposure. Done loosely, it doubles it, and the audit finds both halves.