What Broadcom’s VMware overhaul means for your server strategy
Broadcom’s VMware licensing changes have hit IT teams hard, but the alternatives may finally be catching up.
Published on 19th May 2026
If you’ve been running VMware for the better part of a decade, you probably didn’t expect to be rethinking that choice any time soon. Broadcom completed its $69 billion VMware acquisition in late 2023, and the licensing changes that followed have put a lot of IT shops in a difficult position.
As someone has previously put it, “There is no longer any such thing as a reasonably priced support option for VMWare. Broadcom has taken over and has basically told everyone except enterprise customers that they do not want our business.”
A January 2026, CloudBolt survey found that 86% of companies are now reducing their VMware footprint, though only 4% have fully migrated. Most are somewhere in between, working through their options at a pace that fits their environment.
What the licensing overhaul actually costs
Moving to subscription licensing wasn’t entirely unexpected given broader industry trends, but the bundling, core-count minimums, and partner program cuts that came with it caught a lot of IT teams off guard.
Subscriptions, bundles, and the end of Essentials Plus
Broadcom replaced perpetual licenses with mandatory subscriptions. If you budgeted VMware as a predictable line item for years, that change alone upends your planning. VMware also consolidated more than 160 products into a handful of bundles and phased out the Essentials Plus kit that a lot of IT departments relied on for their three-host clusters. The new pricing steers those customers toward vSphere Foundation (VVF), bundling Aria and vRealize alongside the hypervisor at three to five times the old price. One IT pro reported costs jumping from roughly $1,100 per socket per year to an estimated $20,000 per year under the new model. Most modest deployments never touch those extras.
Per-core pricing and how the maths works
The updated pricing model charges per core, with a 16-core minimum per CPU. If your server has 8 cores, you still pay for 16. Broadcom briefly tried imposing a 72-core minimum order before reversing it after backlash, but the per-core maths still hits smaller environments the hardest. Renewals have jumped 2x to 12x across the board, and you’ll generally see the steepest hikes if you’re running a modest cluster. Miss your renewal anniversary date and you could face a 20% retroactive penalty with no grace period.
Your existing perpetual licenses don’t just vanish, mind you. You can keep running them, but without patches, support, or access to new versions. For an IT team trying to buy time, that runway exists, though it gets riskier the longer you stay on it. One received a cease-and-desist letter from Broadcom after migrating away, so you may want to loop in legal resources (if you have them) before assuming your legacy licenses are a settled matter.
A shrinking partner ecosystem
In the U.S., only 19 providers remain from what used to be thousands of authorised VMware resellers. In January 2026, the company terminated its Cloud Service Provider (VCSP) program in Europe, a move that prompted an antitrust complaint with the European Commission two months later. If your reseller was among those cut, you likely found out with weeks of notice, not months. With limited buying paths, you have less leverage and fewer people to call when something goes sideways.
Deciding whether to stay, negotiate, or migrate
Your move depends on what you’re actually running, how deeply VMware is embedded in your operations, and whether the new pricing still works out. If you defer this decision, you’re still making one, just on Broadcom’s terms instead of yours.
When staying still makes sense
If your environment leans heavily on VMware-specific capabilities like vSAN for hyper-converged storage or NSX for micro-segmentation, you’ll spend well beyond licensing costs to migrate. That’s real money and real disruption—retraining staff, rebuilding automation, and re-qualifying your disaster recovery plan.
Some compliance frameworks depend on VMware’s formal certifications like FIPS 140-2 and Common Criteria, and not all alternatives have caught up yet. Staying doesn’t mean accepting the sticker price, though. If you’re going to negotiate, go in with a full audit of your actual core Civilization and a credible alternative you can point to.
The signals that it’s time to go
If your VMware deployment is primarily a hypervisor, meaning you’re running vSphere to consolidate servers and that’s about it, you’re paying bundle prices for a capability available elsewhere for a fraction of the cost or for free. You know it’s worth exploring alternatives when your renewal quote has doubled or tripled, or when the per-core minimums are pricing you well above what you were paying under the old per-socket model. The same applies if an Essentials Plus dependency no longer exists or your reseller vanished because Broadcom culled the partner program. If you’re checking several of those boxes, the question shifts from whether to move to how fast you can get there.
The gradual unwind
In CloudBolt’s survey, 56% of respondents said they’re staying on VMware while optimising their footprint, and 63% have changed their strategy at least twice since the acquisition. Gartner predicted that 35% of VMware workloads will migrate to alternative platforms by 2028. One CloudBolt respondent called the unwind an 18-to-24-month project, far more complex than a standard cloud lift-and-shift (and if you’ve done one of those, you know that bar is already high). Those timelines reflect larger environments, though. A leaner deployment with a few dozen VMs and no deep platform dependencies can realistically move much faster.
If you’re running a straightforward deployment, this typically means migrating movable workloads first while keeping the core environment on VMware until you’ve validated a replacement. This phased approach also gives you negotiating leverage—a vendor who knows you’re running Proxmox in your lab will approach that renewal conversation differently.
Where to find a realistic migration path
Three alternatives are central to the conversation right now. Each one fits a different kind of environment, and the migration tooling for all three has considerably improved since the acquisition.
Proxmox VE
Proxmox VE runs on the Kernel-based Virtual Machine (KVM) hypervisor, charges no per-core licensing fees, and has absorbed the most VMware refugees since the acquisition. Backup support used to be the main hesitation, but Veeam now supports Proxmox with app-aware backup processing, and Proxmox’s own backup server handles incremental backups at no cost.
The ESXi import wizard covers most migration scenarios without command-line conversion, and a streamlined environment might be able to move over in a matter of weeks instead of months. You do give up enterprise vendor support unless you pay for a Proxmox subscription, and the platform lacks formal security certifications that some regulated industries require, but for most lean IT teams, the savings justify the tradeoffs.
Microsoft Hyper-V
If you’re already a Windows Server Datacenter shop, the hypervisor comes included at no additional cost, and the deeper your investment in Active Directory and Azure hybrid services, the more natural the fit. You might want to be cautious about Storage Spaces Direct, though. S2D handles the same role as vSAN, but it has a reputation for fragility that you’d want to carefully investigate before committing to it for production workloads.
Nutanix
Nutanix offers an enterprise hyper-converged infrastructure (HCI) platform with more flexible licensing than VMware’s current model. If you need integrated management, vendor support, and a certified stack that open-source alternatives can’t yet match, it’s a strong commercial option. You’re trading one licensing relationship for another, but on more favourable terms.
Build your exit ramp before you need it
Nobody wants to re-litigate a technology choice they made a decade ago and haven’t thought about since. VMware ran, it was stable, and you budgeted for it without much drama. That simplicity was worth something, and its loss is genuinely frustrating.
You’re better positioned than you might think, though. The alternatives are more mature than they were two years ago, the migration tooling has caught up, and the community has already mapped most of the pitfalls. Whether you stay, migrate, or do both in phases, the goal is to have real options when that next renewal arrives. That’s worth starting on now, even if the full transition takes time.
Source
Image Credit
Thanakorn Lappattaranan via Vecteezy