This tool covers four domains: VMware Estate Inventory and Core Count, Cost Optimisation and Right-Sizing, Feature and Capability Assessment, and Alternative Readiness. Use it as the foundation for your next Broadcom renewal or alternative evaluation.
Broadcom subscriptions are priced on physical cores with a 16-core minimum per CPU socket. A server with two 12-core CPUs is licensed for 32 cores (2 × 16-core minimum), not 24 physical cores and certainly not the vCPU count. vCenter reports vCPUs; hardware inventory reports physical cores. These are fundamentally different numbers. Organisations that base renewal core count estimates on vCenter data or asset management tools that report logical processors systematically miscalculate their subscription requirement — usually understating it — creating a compliance gap that surfaces in Broadcom's audit or renewal validation process.
Broadcom's subscription pricing applies to all physical hosts where VMware vSphere is installed and running, regardless of the workload type or whether the cluster is classified as production, development, or DR. Organisations that licence only production compute clusters while running VMware in management, test, and DR environments on the same physical hosts are under-licensed. The compliance gap is often discovered only when Broadcom requests a full hardware inventory during renewal validation or audit. A complete host inventory from hardware management tools (iDRAC, iLO, BMC) — not from vCenter — is the correct starting point.
VCF is Broadcom's premium tier, including NSX (software-defined networking), vSAN (hyper-converged storage), and Aria (cloud management). VVF is the vSphere-only tier for organisations that use traditional storage and networking. The price difference is significant. Organisations that deployed VCF broadly because 'it's simpler' often find that 40 to 60 percent of their infrastructure is running vSphere only, with no NSX, vSAN, or Aria deployment. That portion should be VVF-priced. A cluster-by-cluster VCF/VVF audit — mapping installed and configured capabilities against the tier they are licensed under — often surfaces 20 to 40 percent cost reduction opportunity.
vSAN is a VMware hyper-converged storage feature that is only relevant when hosts contribute local storage to a shared vSAN datastore. Hosts using external storage arrays (Pure Storage, NetApp, EMC) do not require vSAN licensing. VCF bundles vSAN by default, which means organisations with a mix of hyper-converged and external storage may be paying for vSAN on hosts where it adds no value. Mapping storage architecture to licensing tier is particularly relevant for organisations that deployed vSAN in some clusters but retained external storage in others.
Every physical core eliminated before a Broadcom renewal reduces the subscription cost by the applicable per-core rate. Infrastructure teams that have deferred server consolidation work for years may find that a consolidation sprint before renewal — migrating VMs from lightly utilised hosts to more consolidated, higher-density hardware — produces a meaningful reduction in licensed core count. A 10% reduction in physical hosts translates directly to a 10% reduction in subscription cost. This should be a standing agenda item in infrastructure planning discussions in the 12 months before any Broadcom renewal.
Broadcom provides a License Calculator for VCF, VVF, and vSAN that allows input of core counts and storage TiB to calculate the theoretical subscription licence quantities. Running this calculation independently and comparing the output to Broadcom's commercial proposal identifies any discrepancies in Broadcom's sizing assumptions. Common discrepancies include Broadcom applying VCF where VVF is appropriate, overstating the minimum core calculation, and including hosts that are no longer in scope. The calculator output does not constitute a binding quote but is a useful benchmark for proposal validation.
The VMware subscription cost is determined by physical hosts, which are driven by aggregate VM resource demand. A culture of VM over-provisioning — allocating 32 vCPUs and 256 GB RAM to VMs that routinely consume 15% of that allocation — creates an inflated physical host footprint that is then subscribed to Broadcom at full core count. VM right-sizing reduces vCPU and RAM demand, allowing VM consolidation onto fewer physical hosts, which directly reduces the Broadcom subscription requirement. This is a multi-quarter programme rather than a one-time action, but it is one of the few organic cost reduction levers available within the Broadcom pricing model.
NSX is one of the primary reasons VCF is priced above VVF. Organisations that purchased VCF for vSphere and included NSX in the bundle but never deployed NSX are paying the VCF premium with no corresponding capability benefit. Similarly, organisations that deployed NSX in two clusters but have NSX-licensed cores across twenty clusters are over-licensed for NSX. An NSX deployment audit — documenting which hosts have NSX actively configured versus licensed — forms the basis for a VCF/VVF tier challenge in the Broadcom renewal.
Aria Suite (Operations, Automation, Log Insight) is included in VCF licensing. In many enterprises, Aria is either not deployed or partially deployed — the product was licensed but never fully implemented. Aria represents significant VCF bundle value if fully utilised; it represents zero-value overhead if undeployed. Where Aria is not deployed and there is no near-term plan to deploy it, the Aria component's value in the VCF pricing conversation is legitimately challengeable. This argument is most powerful if competing third-party operations or automation tools are already deployed.
Broadcom's support tiers range from standard to Premier, with significant cost differences. Organisations that purchased the highest support tier for all infrastructure regardless of workload criticality are overpaying for support on non-critical environments. Conversely, mission-critical VMware workloads running on basic support may face unacceptable incident response times. Map support tier requirements to workload criticality and right-size support purchasing. This is particularly relevant for organisations that have moved lower-priority workloads off VMware as part of alternative migration efforts — the VMware core count reduction should be accompanied by a corresponding support tier review.
Migrating off VMware requires knowing which workloads are portable and which are VMware-specific. Workloads using VMware-specific features — vSphere VADP backup integration, VMware Tools advanced functionality, vSphere-specific networking constructs — require additional migration effort. Workloads running standard guest OS images with no VMware-specific dependencies are straightforward to migrate. A dependency map categorises the VMware estate into three migration tiers: straightforward (no VMware dependencies), moderate (tools/network dependencies requiring configuration changes), and complex (deep VMware feature integration requiring significant rework). This map drives the alternative evaluation and determines the realistic migration timeline.
A documented PoC is the difference between theoretical leverage and credible leverage in a Broadcom renewal. Broadcom's sales team will probe whether your alternative evaluation is real. A PoC completion report — even for a single cluster or a set of representative test workloads — demonstrates organisational commitment to alternatives that changes the commercial dynamic. Nutanix AHV and Microsoft Azure Stack HCI are the most commonly evaluated alternatives for enterprises seeking on-premises VMware replacement. Red Hat OpenShift Virtualisation is relevant for organisations with existing Red Hat footprint.
Alternative platform evaluations often underestimate migration cost. The technical migration of VMs from VMware to an alternative hypervisor is one component. The operational adaptation — rebuilding backup workflows, network policies, monitoring integrations, and runbook procedures on the new platform — is often larger. The skills transition cost — retraining VMware-certified administrators to operate Nutanix, Hyper-V, or OpenShift — is real and takes 6 to 18 months to fully complete. An independent migration cost estimate that includes all these components produces a realistic 3-year TCO comparison between staying on VMware and migrating, which is the only valid basis for a Broadcom renewal negotiating position.
Interpreting Your Assessment Results
Using This Assessment in Renewal Negotiations
The Broadcom VMware assessment tools in this checklist serve two purposes. The first is compliance: ensuring your subscription covers the correct core count, correct tier, and correct support level to avoid Broadcom's compliance and late renewal penalties. The second is optimisation: identifying every legitimate cost reduction lever — tier right-sizing, consolidation, alternative development — before committing to the next subscription term.
The most valuable output of this assessment is a documented VMware estate inventory. That document serves as the foundation for your Broadcom renewal negotiation, your alternative platform evaluation, and your long-term infrastructure strategy. Without it, every decision about VMware spend is based on assumptions rather than evidence.
Stay Current on Broadcom VMware
Subscribe to the Broadcom knowledge hub for quarterly pricing updates, alternative platform analysis, and renewal intelligence.