IBM software in cloud is not free of compliance risk. Sub capacity in cloud, ILMT in containers, Cloud Pak entitlement bridging, and BYOSL versus dedicated host. The seven traps that catch most migrations and the framework procurement teams use to control IBM cloud spend.
IBM software is portable to AWS, Azure, Google Cloud, and IBM Cloud under the right conditions. The conditions are precise. A cloud migration that does not respect them turns a clean compliance position into an audit exposure inside 90 days.
The seven traps below cover the most common cloud migration failure modes. Each trap maps to a specific buyer side action.
This article gives the buyer side framework. Pair it with the IBM hub, the Cloud Pak strategy, the IBM audit defense, and the ILMT guide.
IBM sub capacity licensing allows PVU consumption to be measured at the VM or container level rather than the physical core level. The right exists only on Eligible Public Clouds and only with ILMT in operation.
| Condition | Required | Common gap |
|---|---|---|
| Cloud on IBM Eligible Public Cloud list | Yes | Niche regional clouds excluded |
| ILMT operational and reporting | Yes | Lapsed installation in cloud |
| ILMT report retained for two years | Yes | Reports not archived in cloud move |
| Quarterly reporting cadence | Yes | Cadence broken during migration |
| Hardware report consistent with ILMT | Yes | Cloud hardware report not generated |
If ILMT lapses for any product, the customer falls back to full capacity licensing for that product. Full capacity in cloud means licensing the full physical core count of the underlying host. The full capacity number is typically 4 to 16 times higher than sub capacity.
ILMT was designed for VM and bare metal environments. The container era requires the BigFix container scanner extension on every Kubernetes node. A traditional ILMT installation does not see container PVU consumption.
Cloud Pak entitlement uses Virtual Processor Cores rather than PVU. The conversion ratio from PVU to VPC depends on the Cloud Pak family. The conversion is one way at the contract level.
| Cloud Pak | Source product | PVU to VPC ratio |
|---|---|---|
| Cloud Pak for Integration | WebSphere, MQ, ACE, API Connect | 70 PVU per VPC typical |
| Cloud Pak for Data | Db2, Watson, Cognos, DataStage | 140 to 280 PVU per VPC |
| Cloud Pak for Watson AIOps | Tivoli, Netcool, IBM Cloud Pak for AIOps | Variable, plan dependent |
| Cloud Pak for Security | QRadar, Resilient, Guardium | Variable, plan dependent |
| Cloud Pak for Business Automation | FileNet, Blueworks, Datacap | 140 to 280 PVU per VPC |
The conversion is calculated at contract execution. PVU entitlement that is partial against a Cloud Pak target leaves a residual gap. The buyer side audit identifies the gap before the conversion is executed and either tops up the PVU or postpones the conversion.
Bring Your Own Software License runs on shared multi tenant cloud infrastructure. Dedicated host runs on a single tenant physical server. The two routes have different licensing rules and different infrastructure costs.
| Dimension | BYOSL on shared | BYOSL on dedicated host |
|---|---|---|
| Sub capacity required | Yes | Optional |
| ILMT operational | Required | Required if sub capacity used |
| Infrastructure cost | Standard cloud rate | 2 to 5 times standard rate |
| License count | Per VM or container | Per physical core |
| Best for | Variable workloads, fast scale | Steady state, large footprint |
The IBM PVU table assigns PVU values per physical core type. A virtual core in cloud is mapped to the underlying physical chip family. The mapping is not always intuitive.
The vCPU shown in the cloud console is typically a hyperthread, not a physical core. The PVU calculation runs on the physical core count. The buyer side ILMT report normalizes the vCPU to physical core using the cloud provider hardware report.
IBM Passport Advantage is contracted at the geography level. A US Passport Advantage contract does not automatically permit deployment into APAC or EMEA cloud regions.
An IBM audit motion in progress does not pause for a cloud migration. The audit period covers the migration window. Compliance gaps during the migration are inside scope.
The eight step checklist below runs the buyer side process. The work fits inside a 60 day cloud migration planning window.
No. Only on Eligible Public Clouds and only with ILMT operational. The current eligible list includes AWS, Microsoft Azure, Google Cloud Platform, IBM Cloud, Alibaba Cloud, and several others. Niche regional clouds are typically not eligible. Check the IBM website for the current list at the time of migration.
Only with the BigFix container scanner extension on every Kubernetes node. A traditional ILMT installation does not see pod PVU consumption. The container scanner reads pod CPU limits and tags. Without it the customer falls back to full capacity for the container workloads.
Roughly 70 PVU per VPC for the WebSphere, MQ, ACE, and API Connect family. The exact ratio depends on the source product mix and the Cloud Pak edition. The conversion is calculated at contract execution and the residual gap must be topped up or postponed.
Dedicated host suits steady state large footprint workloads where sub capacity overhead is not justified. Shared with sub capacity suits variable workloads where the cloud elasticity is the value. The infrastructure cost on dedicated host is typically two to five times the shared rate.
No. The audit period covers the migration window. The buyer side action is to freeze the inventory at audit notice, tag every cloud resource, maintain the ILMT cadence, and document each migration wave. The audit defense and the migration both need independent oversight.
Not without amendment. Passport Advantage is contracted at the geography level. The deployment region must sit in the contracting geography. The remediation is either an amendment to add geographies or a workload relocation to in geography regions.
Redress runs the IBM cloud migration licensing review, the ILMT operational audit, and the Cloud Pak conversion modeling on the buyer side. The deliverable is a defended cloud licensing position, a defended ILMT cadence, and a defended audit window across the migration program.
Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.
A buyer side framework for the next IBM cloud migration or audit motion. Includes the sub capacity matrix, the ILMT container checklist, the Cloud Pak conversion math, and the BYOSL versus dedicated host decision tree.
Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for enterprise customers running IBM at scale against the published commercial models.
Open the white paper in your browser. Corporate email only.
Open the Paper →We froze the IBM inventory at migration day one, deployed the BigFix container scanner across the OpenShift cluster, mapped 480 PVU into Cloud Pak for Integration VPCs, and used the documented sub capacity position to land the migration with zero compliance findings on the IBM audit that opened in month nine.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Sub capacity rule changes, ILMT release notes, Cloud Pak conversion math updates, and IBM commercial behavior across every renewal cycle.
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.
