Plain-English guidance on the VMware shift

What happened to VMware after Broadcom

Broadcom closed its acquisition of VMware in late 2023 — one of the largest tech deals ever. Within roughly 90 days it retired perpetual licenses, ended perpetual support renewals, and pushed customers onto mandatory subscription bundles under VMware Cloud Foundation.

The licensing overhaul

The portfolio collapsed from 50-plus SKUs into a handful of bundles. Most customers now have to buy VMware Cloud Foundation at notably higher per-core pricing, with no way to license individual products like vSphere Standard or vCenter on their own.

What mid-market customers are feeling

• Roughly 3–5× cost increases at the first subscription renewal
• Forced inclusion of products they never licensed or needed
• Perpetual-license support winding down
• Loss of flexible partner licensing programs
• A thinner channel as smaller resellers exit the program

How the change unfolded

VMware licensing changes, explained

Before Broadcom, VMware sold perpetual licenses: buy vSphere once, then pay annual support at roughly 20–25% of license cost. That model is gone. Every new purchase and renewal is now subscription-only, billed per core, per year.

The VCF bundle effect

VMware Cloud Foundation bundles vSphere, vCenter, NSX-T, and vSAN into one subscription. It's a complete stack — but teams that only needed vSphere now pay for NSX and vSAN they don't use. That bundling is the main driver behind the 3–5× increases customers report.

Current subscription tiers

What to do before your renewal

• Audit your VM inventory and core counts before you negotiate
• Get quotes across all three bundle tiers
• Compare against at least two non-VMware alternatives
• Bring in a vendor-neutral advisor before signing anything
• Consider a one-year bridge subscription while you evaluate

VMware end-of-life, and why it compounds the problem

Many mid-market shops still on vSphere 6.7 or 7.0 face two clocks at once: their version is nearing end of general support while Broadcom simultaneously pushes a subscription model they didn't ask for. That's pressure to either upgrade onto a subscription or migrate — now.

End of general support dates

What end of support actually means

• No new security patches or bug fixes
• Known vulnerabilities go unremediated
• No vendor technical support
• Compliance frameworks may flag the infrastructure as a violation
• Cyber insurers may deny claims tied to EOL systems

How much does a VMware migration cost?

It varies by 10–20× depending on VM count, target platform, internal capability, and approach. A 50-VM Proxmox move might run $50k–$150k in labor; a 500-VM cloud-VMware migration can reach $500k–$2M+. The way to plan is by component, then by three-year total cost of ownership — not migration cost alone.

Cost components by path

Hidden costs to budget for

• Application testing and validation (routinely underestimated)
• Network reconfiguration and firewall rule updates
• Storage migration and replication data-transfer fees
• Downtime contingency and rollback planning
• Backup reconfiguration and contractor augmentation

What a migration timeline really looks like

Most mid-market migrations run 3–12 months from decision to full cutover. Cloud-VMware moves tend to be faster (2–4 months); platform migrations like Nutanix or Proxmox run 4–9 months; container-native paths can stretch to 9–18.

On-prem vs. cloud: which is right for you?

On-prem alternatives (Proxmox, Hyper-V, Nutanix) need upfront capital but deliver predictable long-term cost and full data sovereignty. Cloud VMware (AVS, GCVE, VMC) skips the hardware refresh but carries ongoing consumption costs that often exceed on-prem TCO after year two or three.

Illustrative 3-year TCO — 50 VMs

Illustrative ranges for planning only — your actual figures depend on cores, configuration, and contracts. We model real numbers in the assessment.