Converting Legacy PVU Entitlements to Cloud Pak VPC
IBM has steered many products into Cloud Paks, where licensing is counted in Virtual Processor Cores rather than legacy PVU. Conversion looks like a simple swap, but the ratios decide how much entitlement you keep. A weak conversion quietly hands IBM a shortfall to find later.
From PVU to VPC
Legacy middleware was typically licensed in Processor Value Units, a core based metric weighted by processor type. Cloud Paks meter in Virtual Processor Cores, where reporting and ILMT now apply to VPC metered products and manual counting is no longer permitted. When you move a product into a Cloud Pak, IBM converts your existing PVU entitlement into a VPC entitlement using a defined ratio for that product. The conversion is not one for one, and the ratio is the whole game.
Why the ratio decides the outcome
Each product carries its own conversion ratio into a given Cloud Pak. A favorable ratio preserves the capacity your PVU entitlement represented; an unfavorable or misapplied ratio leaves you with fewer VPC entitlements than your real deployment needs. Because the Cloud Pak bundles many components, the same VPC entitlement can be consumed by more than one product, which makes it easy to believe you are covered when the underlying math says otherwise.
Where value leaks during conversion
- Misapplied ratios: using a generic ratio instead of the product specific one understates what your PVU entitlement should convert to.
- Unclaimed entitlements: legacy entitlements that are not carried into the conversion simply disappear from the new position.
- Double counting capacity: assuming one VPC pool covers several bundled components at once leaves a real shortfall.
- Container charging rules: Cloud Pak non-compliance means IBM charges for all cores in the cluster, so a soft VPC count becomes a hard one fast.
Protecting your position
Treat the conversion as a reconciliation, not a form. Start from a clean record of the legacy PVU entitlements, apply the correct product specific ratio to each, and compare the resulting VPC entitlement to a measured VPC requirement from the license service. Keep the legacy proofs of entitlement, because once a product is in a Cloud Pak, the prior entitlement is the evidence that the VPC number was earned and not estimated.
A Cloud Pak conversion changes the metric but not the obligation to prove what you own. Under audit, IBM measures VPC consumption and charges all cores in the cluster when the position does not hold. Carry every legacy PVU entitlement across at the correct ratio, measure VPC with the license service, and keep the legacy proofs, so the new number rests on entitlement you can document.