A 48 page buyer side guide to the IBM transition from Processor Value Unit licensing to Virtual Processor Core licensing. Containers, Cloud Paks, sub capacity claims, ILMT cutover, and the negotiation moves that protect entitlement value across the conversion.
IBM has been quietly retiring Processor Value Unit licensing for almost a decade. The Virtual Processor Core metric is now the default across Cloud Paks, the OpenShift container estate, and most new IBM software contracts. The conversion is not a clerical update. It is a commercial event.
The PVU to VPC transition arrives in three forms. The first is a polite letter from the IBM account team proposing to migrate existing Passport Advantage entitlements onto VPC at a stated conversion ratio. The second is a Cloud Pak proposal that bundles VPC entitlements alongside legacy PVU licenses, with the Cloud Pak ratio table buried in the technical appendix. The third is an audit finding that quietly reclassifies existing PVU deployments under VPC bundle rules and produces a settlement number that ignores the customer's contractual right to remain on PVU. The legal mechanics differ. The commercial endgame is identical. The customer pays for the conversion if they let the IBM narrative go unchallenged.
The PVU to VPC migration is governed by IBM's own conversion ratio tables. Those tables are not a matter of opinion. They are documented inside the IBM Container Licensing reference, the Cloud Pak licensing guide, and the supplier specific Passport Advantage agreement amendments that the customer has signed. Most enterprises lose entitlement value on the conversion not because the ratio tables are unfair but because nobody on the buyer side validates the IBM proposed ratios against the published reference. The customer signs a conversion at the IBM account team's preferred ratio rather than the contractually mandated ratio.
This guide documents the buyer side procedure Redress Compliance uses on every PVU to VPC engagement. It covers the conversion ratio reference, the Cloud Pak bundle arithmetic, the OpenShift container licensing model, the ILMT cutover, the sub capacity claim under VPC, and the negotiation moves that protect entitlement value across the conversion. It maps directly onto the source IBM PVU to VPC transition article and the wider IBM Knowledge Hub. Used in sequence it converts what looks like a clerical migration into a defensible commercial outcome.
The opening section sets the licensing context. PVU originated as a per processor measurement that scaled with hardware capacity. VPC originated as a virtualisation aware metric that scaled with the virtual core count of the workload. The conversion is not arithmetic. The two metrics measure different things, and the IBM conversion ratio is a bridging mechanism rather than a like for like swap. The opening chapter walks through the PVU and VPC definitions, the IBM Container Licensing reference, the Cloud Pak ratio table, and the Passport Advantage amendments that anchor the conversion mechanics. Reading the conversion proposal without reading the reference tables is reading a paragraph and missing the chapter.
The second section covers the conversion ratio audit. We document the IBM published ratio tables product by product, the historical PVU position the customer is entitled to assert, and the conversion arithmetic that protects entitlement value. We include the Redress conversion calculator structure, the data sources for the published ratios, and the contractual reference points that prevent the IBM account team from asserting an unpublished ratio. The objective is a conversion arithmetic that the customer controls, with every ratio referenced to a published IBM document.
The third section covers Cloud Paks and the bundle stack. Cloud Paks are container distributions that bundle multiple IBM products under a single VPC envelope. The Cloud Pak ratio table determines how much VPC entitlement each bundled product consumes from the total. The buyer side risk is that the IBM account team will quote a Cloud Pak proposal that is sized on the marketing bundle rather than on the contractual ratios. We document the Cloud Pak entitlement decomposition, the product family conflicts that consume more VPC than the buyer realizes, and the right sizing motion that prevents the customer from buying VPC capacity they will never use. The Cloud Pak section pairs with the broader Cloud Paks reference inside the IBM Knowledge Hub.
The fourth section covers OpenShift and the container licensing model. The Red Hat acquisition pulled OpenShift into the IBM software estate, and OpenShift Container Platform is now the default substrate for Cloud Paks. The licensing model interacts with the VPC metric in ways that surprise most buyers. We document the OpenShift licensing options, the Cloud Pak for Watson AIOps and Cloud Pak for Data integrations, the worker node sizing that determines VPC consumption, and the IBM Cloud and hyperscaler hosted OpenShift options that change the contracting model. The objective is an OpenShift footprint that supports the Cloud Pak strategy without inflating the VPC bill.
The fifth section covers ILMT cutover. ILMT version 9 introduced VPC reporting alongside the historical PVU measurement. The cutover is not automatic. The customer must reconcile the existing PVU footprint, document the conversion baseline, configure the VPC reporting, and maintain a continuous record across both metrics during the transition. We document the ILMT version 9 configuration, the data quality bar IBM cannot legitimately reject, and the cutover sequence that protects the sub capacity claim. The ILMT chapter pairs with the Redress IBM Audit Defense Checklist.
The closing section covers the negotiation. The conversion is a commercial event because IBM has commercial discretion over the conversion price, the migration credit, the term length, and the bundle that surrounds the VPC entitlement. We document the conversion price book, the field discount authority, the migration credits IBM will reliably deploy when the conversion is bundled with a Passport Advantage renewal, and the side letter language that prevents the conversion from triggering an audit reset on legacy PVU deployments. The result is a conversion that protects entitlement value, retires legacy PVU exposure, and leaves the customer with a Cloud Pak footprint sized to actual demand. For broader IBM commercial defense, this guide pairs with the IBM advisory practice.
Email gated. Corporate addresses only. We will send you a direct PDF link and add you to the buyer side intelligence list. Unsubscribe in one click.
Prefer to talk to a human first?
Schedule an IBM Advisory Call →
Talk to a buyer side advisor. No pitch. No sales theatre. Thirty minutes, your conversion proposal, our reference tables.
One letter a month. Negotiation moves, audit signals, and price book shifts.
