The VMware and Broadcom Knowledge Hub. Bundles, core math, migration paths.

Broadcom completed the VMware acquisition in November 2023 and collapsed the perpetual portfolio into two subscription bundles. The bundles are VMware Cloud Foundation (VCF) for the full stack and VMware vSphere Foundation (vVF) for the compute only stack.

The shift moved customers off perpetual licenses with annual support onto three year subscriptions priced per core. The 16 core per CPU minimum, the support tier split, and the migration timing now drive the bill.

Read this hub alongside the Broadcom services page, the VMware negotiation playbook, the VCF migration cost estimator, the Oracle on VMware page, and the Vendor Shield subscription.

VCF and vVF bundle structure

The portfolio carries two bundles in 2026. VCF for the full software defined data centre. vVF for the compute only baseline.

Bundle comparison

Component	VCF	vVF
vSphere	Yes	Yes
vSAN	Yes, 100 GB per core	No
NSX Networking	Yes	No
Aria Operations	Yes	No
Aria Automation	Yes	No
HCX migration	Yes	Optional add on
Tanzu Kubernetes	Yes	Optional add on
List price per core per year	350 USD	135 USD

When to pick which

• VCF. Full software defined data centre, vSAN as primary storage, NSX as the network plane, Aria as the operations layer.
• vVF. vSphere compute only on existing SAN storage, third party network, no Aria stack.
• Add ons. HCX, Tanzu, Avi Load Balancer, Site Recovery sit on top of either bundle.

Core counting rules

The core count is the single largest driver on the Broadcom VMware bill. The 16 core per CPU minimum drives the math.

Four counting rules

1. Physical cores only. Hyper threading does not count.
2. 16 core per CPU minimum. A CPU with fewer than 16 cores still licenses at 16.
3. One license per physical core above 16. A 24 core CPU licenses at 24, not at 16.
4. Active cores. Hardware disabled cores do not count. BIOS disable is not sufficient.

Core count examples

CPU choice	Sockets per server	Cores per socket	Licensable cores
Intel Xeon 8 core	2	8	32 (16 minimum each)
Intel Xeon 16 core	2	16	32
Intel Xeon 32 core	2	32	64
AMD EPYC 64 core	2	64	128
AMD EPYC 96 core	2	96	192

Support tier structure

Broadcom carries two named support tiers in 2026. The default is Production. Mission Critical sits above at a 30% premium.

Support tier comparison

Dimension	Production	Mission Critical
Response time, severity 1	30 minutes	15 minutes
Coverage hours	24x7	24x7
Account manager	No	Yes
Technical account manager	No	Yes
Premium uplift	0%	30%

When Mission Critical is worth the uplift

• VCF estates above 500 cores. The TAM relationship moves the renewal posture.
• Regulated environments. Financial services and healthcare with documented response SLAs.
• NSX heavy networks. Complex multi site deployments justify the 15 minute response.

Migration paths in 2026

Four credible exit paths landed inside the 18 month decision window across 2025 and into 2026. Every one carries a cost model, a risk profile, and a timeline.

Four migration paths

1. Azure Local. Microsoft Azure Stack HCI rebranded. Strong fit for Microsoft heavy estates with Azure Arc governance.
2. Red Hat OpenShift Virtualization. KubeVirt based. Strong fit for OpenShift estates already running containers.
3. Nutanix AHV. Hyperconverged platform with native hypervisor. Strong fit for VCF estates running vSAN.
4. Public cloud lift and shift. VMs to AWS, Azure, or Google Cloud native. Strong fit for sub critical workloads on a refresh cycle.

Indicative migration timelines

Path	VM count	Indicative timeline	Indicative cost per VM
Azure Local	1,000	9 to 12 months	1.2K to 2.5K USD
OpenShift Virtualization	1,000	10 to 14 months	1.4K to 2.8K USD
Nutanix AHV	1,000	6 to 10 months	0.9K to 2.0K USD
Public cloud lift	1,000	4 to 8 months	0.6K to 1.5K USD plus run rate

Buyer side negotiation framework

The VMware negotiation is now a Broadcom negotiation. The framework carries seven moves on the table.

Seven negotiation moves

1. Core right size. Document the active core count and rebalance the bundle to vVF where vSAN is not used.
2. Term extension trade. A move from 3 year to 5 year unlocks 8% to 12% on the per core rate.
3. Bundle scope trim. Drop NSX, Aria, or Tanzu where the actual usage is zero.
4. Migration anchor. Present the chosen exit path to anchor the renewal.
5. Support tier hold. Production unless Mission Critical is documented as required.
6. Add on price lock. Lock HCX, Avi, Site Recovery add on prices for the full term.
7. Audit clause cap. Cap the audit notice period and the scope of the audit.

What to do next

The eight step checklist takes a Broadcom VMware position from the default renewal posture to a buyer side position locked at the right bundle.

1. Inventory the estate. Server by server, CPU model, core count, vSAN usage, NSX usage.
2. Score the bundle. VCF or vVF based on actual stack consumption.
3. Compute the core bill. Apply the 16 core per CPU rule across the estate.
4. Quote two migration paths. Cost and timeline for the two best fit exit paths.
5. Draft the seven moves. Procurement memo with the seven moves in the line item math.
6. Run the competitive read. Hyperconverged and cloud alternatives quoted on like for like scope.
7. Time the negotiation. Six months before the subscription anniversary, not three.
8. Lock the term. Three year baseline with the seven moves written into the order form.

Frequently asked questions

How Redress engages on Broadcom VMware

Redress runs Broadcom VMware advisory inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment.

Read the related Broadcom services page, the Broadcom VMware negotiation article, the VMware negotiation playbook, the VCF migration estimator, the Oracle on VMware page, the benchmarking page, the about us page, and the contact page.