IBM Cloud Pak licensing runs on Virtual Processor Cores, VPCs. The conversion math from older PVU products varies. Some conversions deliver less effective capacity than the original entitlement.
IBM Cloud Pak licensing runs on Virtual Processor Cores, VPCs. The conversion math from older PVU products to Cloud Pak VPCs varies by source product. Some conversions deliver less effective capacity than the original entitlement.
This landing page introduces the IBM Cloud Pak Licensing Negotiation Playbook. The playbook covers the VPC math, the conversion ratios, the seven Cloud Paks, and the eight negotiation tactics that protect customer entitlement during the migration.
Read alongside the IBM services, the IBM hub, the Cloud Pak licensing guide, the IBM audit defense landing, and the Vendor Shield subscription.
The playbook covers six layers of the Cloud Pak negotiation. Each layer builds on the prior.
The playbook is written for the IBM customer migrating from the legacy PVU model to Cloud Pak. The reader profiles below are the primary audience.
The 50 page playbook is structured as twelve chapters plus three appendices.
| Chapter | Topic | Pages |
|---|---|---|
| 1 | The Cloud Pak licensing model | 4 |
| 2 | VPC math fundamentals | 5 |
| 3 | Conversion ratios from PVU products | 6 |
| 4 | Cloud Pak for Integration | 4 |
| 5 | Cloud Pak for Data | 4 |
| 6 | Cloud Pak for Security | 3 |
| 7 | Cloud Pak for AIOps | 3 |
| 8 | Cloud Pak for Network Automation | 3 |
| 9 | Cloud Pak for Watson AIOps and Business Automation | 4 |
| 10 | Eight negotiation tactics | 5 |
| 11 | Audit risk profile | 3 |
| 12 | Renewal posture | 3 |
VPCs replace the PVU model on Cloud Pak. One VPC corresponds to one virtual core. The customer must license the maximum simultaneous VPC consumption across the deployment.
The conversion from PVU products to Cloud Pak VPCs varies by source product. The table below is the standard IBM conversion guide. Customer specific ratios may differ.
| Source product | Destination Cloud Pak | Standard conversion ratio | Buyer side note |
|---|---|---|---|
| WebSphere Application Server ND | Cloud Pak for Integration | 70 PVU = 1 VPC | Approx 1 to 1 net |
| WebSphere Application Server | Cloud Pak for Integration | 50 PVU = 1 VPC | Slight customer benefit |
| MQ Series | Cloud Pak for Integration | 70 PVU = 1 VPC | Net loss on per CPU dense workloads |
| DB2 Enterprise Edition | Cloud Pak for Data | 120 PVU = 1 VPC | Material entitlement loss |
| Cognos Analytics | Cloud Pak for Data | 240 PVU = 1 VPC | Significant entitlement loss |
| QRadar | Cloud Pak for Security | Custom per deal | Always negotiate the ratio |
| Tivoli Storage Manager (Spectrum Protect) | Cloud Pak for AIOps | Custom per deal | Always negotiate |
The DB2 and Cognos conversion ratios in the standard IBM table often deliver less effective capacity than the original entitlement. A 1,200 PVU DB2 estate converts to 10 Cloud Pak for Data VPCs at the standard 120 to 1 ratio.
The same workload may require 14 VPCs in production. The customer is short by 4 VPCs immediately. Always model the actual deployment before agreeing to the standard ratio.
IBM has consolidated the legacy software estate into seven Cloud Paks. Each Cloud Pak is a curated bundle of related products on the OpenShift platform.
| Cloud Pak | Primary use case | Includes |
|---|---|---|
| Cloud Pak for Integration | API, messaging, integration | App Connect, MQ, API Connect, Event Streams, DataPower |
| Cloud Pak for Data | Data warehouse, analytics, AI | DB2, Db2 Warehouse, Cognos, Watson Studio, Watson Knowledge Catalog |
| Cloud Pak for Security | SIEM, threat hunting, SOAR | QRadar, ReaQta, Resilient SOAR, Cloud Pak for Security console |
| Cloud Pak for AIOps | IT operations management | Watson AIOps, NetCool, Tivoli, Instana |
| Cloud Pak for Network Automation | Network ops | Telco network automation suite |
| Cloud Pak for Watson AIOps | AI operations and observability | Watson AIOps, Instana, Turbonomic |
| Cloud Pak for Business Automation | BPM, RPA, content services | BAW, BAI, FileNet, RPA, Operational Decision Manager |
The eight tactics in the playbook protect customer entitlement during the Cloud Pak migration and renewal.
The IBM Cloud Pak migration is a contract opportunity, not a tooling exercise. The buyer side wins the deal in the conversion ratio negotiation, the multi pak bundle, and the renewal cap. Once the customer is on Cloud Pak at standard ratios, leverage drops sharply.
Not immediately. IBM continues to sell legacy PVU licenses on most products. The Cloud Pak migration is positioned as a strategic move, not a forced replacement. The buyer side decision depends on the workload, the architecture, and the contract leverage at the next renewal.
Yes. IBM publishes a standard conversion table but the ratios are negotiable per deal. Customer specific ratios reflect the actual workload, the deployment architecture, and the deal commercials. The playbook covers the conversion negotiation framework in detail.
ILMT and BigFix Inventory continue to track Cloud Pak VPC consumption. The reporting cadence stays at quarterly minimum. The playbook covers the ILMT migration path and the audit safe harbor language to negotiate at signing.
Buying two or more Cloud Paks together drives a cross product discount uplift of 3 to 8 percentage points. The Cloud Paks must be on the same contract and the same renewal date. The playbook covers the bundling tactics and the trap of buying Cloud Paks that are not needed.
Default is 5 to 9 percent on the IBM standard renewal. The cap is only available when negotiated upfront. A 4 percent cap saves 5 to 12 percent on the three year TCO. The playbook covers the cap clause language and the negotiation posture.
Redress runs Cloud Pak negotiation inside the Vendor Shield subscription, the Renewal Program, and standalone advisory. Every engagement is led by a former IBM commercial executive on the buyer side. The playbook is the starting reference for every engagement.
Redress runs IBM Cloud Pak negotiation inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. Every engagement is led by a former IBM commercial executive on the buyer side.
Read the related IBM services, IBM hub, Cloud Pak licensing guide, audit defense landing, IBM assessment tools, benchmarking, about us, locations, and contact pages.
A buyer side reference on IBM audit defense. ILMT compliance, sub capacity rules, Cloud Pak conversion, and the seven step audit response.
Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying Ibm contracts. No vendor influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →The IBM Cloud Pak migration is a contract opportunity, not a tooling exercise. The buyer side wins the deal in the conversion ratio negotiation, the multi pak bundle, and the renewal cap. Once the customer is on Cloud Pak at standard ratios, leverage drops sharply.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
VPC conversion math, multi pak bundle uplift, audit safe harbor language, and the renewal cap on every IBM Cloud Pak engagement we run on the buyer side.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
