Run the methodology with a senior advisor.
A senior Admodum advisor will walk the methodology through with your CIO, CFO, infrastructure or sourcing team on a private call. Engagements run as fixed fee, contingency or annual retainer.
Thirty pages on the VCF and VVF subscription accounting, the perpetual licence sunset, the renewal envelope under the Broadcom commercial model, the exit architecture, the BATNA-driven renegotiation and the audit posture across the transition.
The Broadcom acquisition of VMware closed in late 2023 and was followed within months by the most consequential commercial-model change inside the enterprise virtualisation market in twenty years. The mandate the buyer faces is therefore not a renewal in the historical sense. It is a transition between two materially different commercial constructs, executed inside a compressed window the buyer did not choose.
The old VMware commercial model rested on perpetual licences with separately purchased Support and Subscription (SnS). The buyer owned the licence in perpetuity and paid the SnS to receive maintenance, updates and support. The model favoured the buyer with a large estate and stable architecture; it favoured the publisher with a steady annuity inside an installed base that could not easily exit.
The new Broadcom commercial model rests on subscription bundles (VMware Cloud Foundation, VMware vSphere Foundation, and the surrounding subscription SKUs), with perpetual licences phased out for new sales and the existing perpetual base offered a documented transition path to subscription. The model favours the publisher with predictable annuity revenue and the buyer with a programme that aligns to the bundle definition; it disadvantages the buyer with an estate that does not align to the bundle definition and the buyer that holds perpetual licences without an active SnS.
The buyer’s posture across the transition is therefore not negotiation in the historical sense; it is a strategic decision about whether to align to the new model, whether to extract a transition concession before alignment, or whether to use the transition window to architect a partial or full exit. Each of the three postures is defensible. Each carries a different commercial profile, a different operational risk and a different long-run cost envelope. The buyer who walks into the transition without selecting the posture in advance lets the seller select it on the buyer’s behalf.
VMware Cloud Foundation and VMware vSphere Foundation are the two subscription bundles inside which the new commercial model expresses most of the existing VMware estate. The bundles are priced per core, with a documented minimum-core quantum and a defined contents list that the buyer must read line by line.
VCF is the premium bundle. It includes vSphere, vSAN, NSX, Aria (the former vRealize suite) and the supporting infrastructure components, with the entitlement scoped per core across the bundle. The bundle definition allocates a per-core entitlement of each component; where the buyer’s actual deployment of a component (typically vSAN capacity or NSX feature set) exceeds the bundled per-core entitlement, an overage charge accrues. The buyer’s consumption profile must therefore be modelled against the bundle definition, not the headline price.
VVF is the entry bundle. It includes vSphere, a defined vSAN allocation and a defined Aria allocation, again scoped per core. VVF is the bundle the buyer with a modest VMware estate, no NSX deployment and no significant Aria deployment most commonly maps onto. The buyer should not assume VVF on the basis of headline price; the bundle’s minimum-core quantum, the limited Aria allocation and the absence of NSX make VVF the wrong destination for many estates that look like they belong there at first read.
The reconciliation runs estate-by-estate, component-by-component. The buyer’s current vSphere licence count, vSAN capacity, NSX deployment, Aria use, supporting Site Recovery Manager (now part of VCF) and historical use of Tanzu (now part of VCF) is mapped onto the VCF or VVF entitlement and reconciled at per-core level. The mapping defines the buyer’s position at renewal.
The perpetual licence base is the buyer’s residual right. Broadcom has phased out new perpetual sales but has not (under the publicly documented commercial position) retroactively voided existing perpetual rights. The buyer’s perpetual licences therefore continue to confer deployment rights in perpetuity, subject to the SnS status.
The SnS expiry is the operational pressure point. A perpetual licence without active SnS continues to confer deployment rights but does not entitle the buyer to security updates, version upgrades, support or remediation. Where Broadcom does not offer SnS renewal on existing perpetual licences (or offers it only at terms the buyer rejects), the buyer faces an architectural decision: deploy and operate on unsupported software, transition to subscription, or transition to an alternative platform.
The buyer’s residual-rights position is consequential at the renewal table. The buyer who holds 4,000 perpetual cores with current SnS walks into the transition with an asset that has commercial value: the buyer can credibly elect to run the perpetual estate on residual rights for a defined window while the alternative platform is assessed. The buyer who holds 4,000 perpetual cores with lapsed SnS walks in without that optionality and must concede the transition terms or accept the operational risk.
Broadcom’s commercial pitch frames the perpetual base as legacy. The buyer’s commercial pitch frames the perpetual base as the asset that gives the buyer time to architect alternatives. Both framings are accurate. The difference is whose narrative anchors the renewal conversation.
The renewal envelope under Broadcom is materially different from the renewal envelope under historical VMware. The buyer’s envelope must therefore be reconstructed under the new model, not extrapolated from the old.
The new envelope is priced per core, with a minimum-core commitment per CPU socket and a multi-year term that runs typically three years. The price per core has, across the engagements Admodum has run since the acquisition closed, moved by a factor of two to five against the equivalent SnS line on the historical perpetual licence. The total renewal envelope under the new model has therefore moved by a comparable multiple against the historical SnS-based renewal envelope.
The buyer’s response to the new envelope sits inside three options. The first is alignment: accept the new envelope, sign the multi-year subscription, optimise inside the bundle. The second is renegotiation: contest the per-core rate, the minimum-core quantum, the bundle fit and the multi-year term, with the BATNA of the alternative platform held against the renewal table. The third is exit: design an alternative-platform programme, run the perpetual base on residual rights inside the migration window, transition out of the VMware estate inside a defined timeline.
The renewal envelope at the transition cycle is therefore not a price. It is the input to a decision the buyer must make about which of the three options is the operating posture for the next three to five years.
The exit architecture is the deployment posture under which the buyer credibly migrates a defined portion of the VMware estate off the VMware platform. The architecture is not a discrete project; it is a position the buyer carries inside the renewal negotiation and operationalises after the renewal is concluded.
The exit options across the VMware estate are limited but real. Nutanix AHV, Microsoft Hyper-V, Red Hat OpenShift Virtualization, Proxmox and the major hyperscaler-native virtualisation platforms all offer a documented migration path from vSphere. None of the alternatives is a one-to-one functional replacement. Each requires a workload-by-workload migration assessment, an operational-tooling change, a skills-set change and a defined cutover window.
The architectural cost frame is the work the buyer must do to make the exit credible. The cost frame must include not only the destination-platform licence but the migration services, the operational tooling retraining, the supporting backup and disaster-recovery integration, the network and storage architecture change, the application-compatibility validation and the operational-risk overlay. A cost frame built only on the destination licence is the cost frame the seller will dismantle inside the renewal meeting.
The exit architecture, properly built, gives the buyer the option to run a partial exit (a meaningful percentage of the estate moved over twenty-four to thirty-six months) without disrupting the production posture. The credible threat of a partial exit is, in many engagements Admodum has run since the acquisition closed, the single most material lever on the renewal envelope.
The BATNA is the alternative platform the buyer has costed, the perpetual-rights position the buyer can operate inside the migration window, and the documented exit timeline the buyer is prepared to execute. The BATNA is not a tactic deployed at the renewal table; it is a programme of work that has been conducted before the renewal table is set.
The renegotiation runs against four levers. The first is the per-core rate; the second is the minimum-core quantum (where the buyer’s actual estate runs below the publisher’s default minimum); the third is the term length (where the buyer prefers shorter term to retain optionality); the fourth is the bundle fit (where VCF or VVF includes components the buyer does not need, or excludes components the buyer does need).
Where the BATNA is credible, all four levers are negotiable. Where the BATNA is not credible, none of the four levers is materially negotiable. The transition envelope under the Broadcom commercial model is not a price the publisher offers; it is a price that reflects the publisher’s read of the buyer’s alternative options.
The buyer who walks into the transition with a documented alternative-platform programme, a costed exit timeline and a perpetual-rights residual position holds the position the publisher prices against. The buyer who walks in without these holds no position the publisher meaningfully prices against.
Cost containment, where alignment is the chosen posture, runs inside the bundle definition. Where the buyer is committing to VCF or VVF for the next three years, the work is to ensure the bundle is not over-scoped against the estate, that the per-core count is correctly minimised, that the bundle’s included components are operationally used, and that the overage exposures are contained.
The per-core count optimisation runs against three architectural levers. The first is CPU consolidation: workloads dispersed across a high core count can in many cases be consolidated onto a smaller core count with adequate headroom, reducing the per-core commitment. The second is socket optimisation: the minimum-core-per-CPU quantum makes high-core-count CPUs more efficient than low-core-count CPUs. The third is workload off-loading: workloads that can be migrated off VMware (to containers, to bare metal, to alternative virtualisation) reduce the per-core commitment.
The bundle-fit optimisation runs against the included-component list. Where the buyer is committing to VCF but does not operationally use NSX, the buyer should challenge whether VVF (or a hybrid of VVF and a smaller VCF carve-out) is the more efficient bundle. Where the buyer is committing to VVF but does operationally use vRealize beyond the bundled allocation, the buyer must size the Aria overage exposure inside the renewal envelope rather than discover it inside the consumption record.
The audit posture under Broadcom has hardened against the historical VMware audit posture. The buyer should expect that the new commercial owner will exercise audit rights more aggressively, that ambiguous deployment positions will be read against the buyer, and that the previously informal commercial tone around VMware true-up will be replaced by a more formal audit-defence framework.
The buyer’s audit-defence preparation rests on the documented entitlement position (the per-core count by SKU, the SnS status by line, the bundle entitlement allocations), the deployment evidence (vCenter inventory, host-level core count, per-component usage), the documented exclusions (workloads on retired hosts, workloads on perpetual licences with current SnS, workloads inside the documented entitlement scope) and the reproducible reconciliation between entitlement and deployment.
The audit defence sits inside the same evidentiary framework Admodum runs for every publisher audit: scope contestation in writing, evidence held under attorney-client privilege where the jurisdiction permits, settlement negotiation against documented compliance positions rather than against the publisher’s asserted exposure. The Broadcom audit context is new; the audit-defence methodology is not.
The Broadcom VMware paper sits inside a broader infrastructure and platform reading list. The companion papers extend the methodology to adjacent commercial mechanics:
The methodology in this paper is the methodology Admodum has applied across thirty-three Broadcom VMware transition engagements since the acquisition closed. Each engagement is structured as fixed fee, contingency / gainshare or annual retainer, depending on the buyer’s posture at the transition window.
A senior Admodum advisor will walk the methodology through with your CIO, CFO, infrastructure or sourcing team on a private call. Engagements run as fixed fee, contingency or annual retainer.