The situation.
The client is an integrated energy operator with upstream production assets, midstream pipelines, and a refining and marketing business across the United States and western Canada. The VMware estate at the time of the Broadcom renewal proposal was approximately 6,200 vSphere cores running a mixture of vSphere Enterprise Plus, vSAN Advanced on the pipeline SCADA tier, and a small NSX deployment supporting the corporate firewall consolidation. The estate was the product of three discrete IT generations and had never been formally tiered against availability and recovery requirements.
Broadcom's renewal proposal arrived four months before the existing ELA expiration, structured as a full migration to VMware Cloud Foundation on a three-year subscription. The quoted annual subscription was 3.8 times the prior perpetual-plus-support outlay, with all 6,200 cores moved onto the highest VCF tier. The client's CFO had circulated the proposal internally with a single instruction: this number cannot be the answer.
The complication.
Energy sector IT environments are not interchangeable. The pipeline SCADA workloads carry hard real-time availability constraints, are subject to NERC CIP scope, and run on a vSphere build that has been cyber-certified through a multi-quarter process the client did not want to repeat on a different hypervisor. The corporate workloads — file, print, identity, intranet, several hundred internal applications — had no such constraint and were a candidate for almost any modern virtualisation stack.
The refining and marketing business sat in the middle. Some workloads were tied to operational technology and inherited SCADA-adjacent requirements; others were essentially corporate IT with a refinery cost centre. The client had never drawn a formal line between the two, and Broadcom's proposal assumed there was no line to draw.
The response.
The defence and advisory engagement opened with a workload tiering exercise. Over six weeks, every running VM in the estate was classified against four criteria: cyber and regulatory scope, recovery time objective, latency sensitivity, and the cost and risk of re-platforming. The exercise placed approximately 38% of cores in Tier-1 (SCADA, pipeline control, certified safety workloads), 22% in Tier-2 (refining and marketing operational IT), and 40% in Tier-3 (general corporate IT).
The team then constructed a three-track procurement plan. Track one was a renegotiated VCF subscription scoped only to Tier-1 cores, with an aggressive but credible defence of the per-core count and a documented commitment to retire Tier-2/3 cores from the VMware estate over twelve months. Track two was a Nutanix AHV proposal for the Tier-2 operational IT workloads where modern hyperconverged capabilities mapped well to existing storage. Track three was a Proxmox VE deployment for the Tier-3 corporate workloads, supported by an integrator partner experienced in enterprise Proxmox at this scale.
Negotiation with Broadcom proceeded under a credible alternative. Because the Tier-2/3 cores were under active migration planning with named integrators and signed statements of work, Broadcom's account team understood that the alternative was not a slide deck. The renegotiated VCF subscription on the Tier-1 footprint landed at 41% below the line-item-equivalent in the original quote, with a price-lock on subsequent renewals tied to documented core counts.
The migration itself ran for eleven months. The Tier-3 corporate workloads moved first, in parallel waves coordinated against application change windows. The Tier-2 refining and marketing workloads moved in a slower second wave, with the cyber-certification questions resolved through a workload-by-workload assessment. The Tier-1 SCADA estate remained on VMware end-to-end and was the only footprint that Broadcom retained.
The outcome.
Measured against the original Broadcom proposal over the three-year horizon, the documented saving is $11.4 million in subscription cost. Migration tooling, integrator fees, and internal labour are accounted for in that figure and net of the savings shown. The Tier-1 VCF renewal was executed at 41% below the equivalent line items in the original quote and includes a price-lock clause that the client's legal team negotiated as a hard condition of signature.
Beyond the financial outcome, the engagement produced an operational asset that the client did not have before: a documented, signed-off workload tiering against which every future VMware-or-not decision can be made. The corporate workload estate is now running on Proxmox, the refining-and-marketing operational IT is running on Nutanix AHV, and the SCADA estate is running on a VMware footprint that is one third of its prior size and entirely justified.
