The strongest lever is a Nutanix quote you are genuinely prepared to act on
Broadcom's repricing made the exit question unavoidable, and the answer is less automatic than the headline suggests. The licence saving on commodity virtualization is real, but a hypervisor change is a data centre programme rather than a procurement swap, and the engineering line is what decides the payback. In two thirds of the cases we modelled the first year saving shrank once that line was costed honestly, and on small estates the move lost money.
Prepared by Redress Compliance · August 10, 2026 · Broadcom advisory. Based on 30 to 40 Broadcom VMware reviews, 2024 to 2025.
Executive summary
The trigger is structural: post acquisition VCF quotes ran 2x to 3x the prior perpetual plus support annual cost.
Broadcom retired most perpetual licences and standalone products and moved customers onto per core subscription bundles, so cost is now annual and recurring, standalone vSphere buyers are pushed into a larger suite they may not use in full.
And a minimum core charge per processor lifts the floor for smaller hosts.
The median increase in our file was 2.4 times. That is what puts the exit question on the table rather than any dissatisfaction with the platform.
Nutanix removes the standalone hypervisor line, which is the part of the bill that rose most. Nutanix sells a hyperconverged platform with its own hypervisor, AHV, included at no separate licence, and prices per core or per node on its own subscription.
That makes the comparison subscription to subscription rather than subscription against a sunk perpetual cost, which is the framing error that makes the migration look better than it is.
Both vendors now price on cores, so the honest comparison is cost per physical core at identical core counts, with unused suite value stripped out rather than credited.
Migration engineering and tooling rework added 20 to 40 percent on top of the first year licence saving.
The cost lines buyers miss are consistent: virtual machine conversion, testing and cutover windows consuming real engineering time; backup, monitoring, and automation built for vSphere needing reconfiguration or replacement.
And operations teams needing training on a new hypervisor and management plane.
Conversion tooling lowers the conversion effort but does not remove the operational rework, which is the larger of the two.
The exit quote pays for itself even when you stay: estates that produced one cut the VMware renewal 15 to 30 percent. The average in our file was 22 percent, and it applied whether or not the migration happened.
That is the asymmetry worth understanding before committing to a year of disruption: a costed, credible alternative is cheap to produce and moves the incumbent quote, while the migration itself is expensive and only pays back on large commodity estates inside two to three years.
Leaving VMware also removes one lock in and creates another, so the exit only pays if the new commitment is shorter or cheaper on a five year view.
Stay or move, on a five year view
| Cost line | Stay on VMware | Migrate to Nutanix |
|---|---|---|
| Annual licence | High, per core subscription | Lower, per core or per node |
| One time project | None | Significant: migration and rework |
| Operations tooling | Reuse existing | Reconfigure or replace |
| Skills | Existing team | AHV and management plane training |
| Lock in | Broadcom roadmap | Nutanix roadmap |
| Net five year | Predictable, higher run rate | Lower run rate after payback |
The payback point is where the decision actually sits, and it moves with estate size rather than with the size of the increase.
On commodity virtualization at scale the subscription saving usually covers the project inside two to three years, which makes the move defensible on arithmetic rather than on frustration.
On small estates the project cost can outweigh the saving entirely, so the maths favours a negotiated VMware renewal with the exit quote used as leverage.
That is why the headline increase is the wrong input to decide on: a 3x increase on a small estate can still be the cheaper path once the programme is priced. The bundle comparison sits in the VMware licensing comparison and the platform detail in the VCF pillar.
Reading the two quotes side by side
- Normalise the unit. Compare cost per physical core at identical core counts, since both vendors now price on cores and the comparison is cleaner than it looks.
- Strip unused suite value. Do not credit VCF features the estate will never deploy, because a bundle you do not use is not worth what the price list says it is.
- Add the project to the Nutanix side. Amortise the migration across the contract term so the run rate comparison is honest rather than flattering.
- Count the tooling rework separately. Backup, monitoring, and automation built for vSphere carry their own cost, and this is the line buyers underestimate most consistently.
- Price the new lock in. Leaving one roadmap for another only pays if the incoming commitment is shorter or cheaper on a five year view. The alternatives landscape sits in the alternatives comparison and the sequencing in the exit plan.
The VMware alternatives brief 2026
Nutanix, Hyper V, and the rest priced against a repriced VCF renewal, with the migration engineering line costed rather than assumed.
Get the white paper →Holding leverage on either path
Whether you stay or move, the leverage comes from the same two things: a credible, costed alternative and a clear view of what the estate actually uses.
Build the exit quote properly, which means a real Nutanix proposal with migration scope attached rather than a back of envelope figure, because a number the vendor can tell you did not come from a partner does not move anything.
Right size the suite at the same time by dropping VCF capabilities the estate will not deploy, since paying for the full stack and then arguing about the discount is the expensive order to do it in.
Co term and commit selectively, trading a longer term only for a lower per core rate rather than for goodwill. And hold the timeline, because a renewal negotiated under deadline pressure is the weakest position available and it is usually self inflicted.
The sequencing that works is to model the five year run rate for both paths first, then test the VMware renewal against the exit quote, then decide on payback and operational risk rather than on the headline increase alone.
In our file the estates that did this in that order cut the renewal by an average of 22 percent, and a clear majority of them never migrated at all, which is the outcome the arithmetic supported. The comparison against the Microsoft route sits in the Hyper V comparison.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across VMware exit reviews, 2024 to 2025
The common advice is that the Broadcom repricing makes a Nutanix migration an automatic saving. We disagree.
In roughly two thirds of the exit cases we modelled, the first year saving shrank once migration engineering and tooling rework were costed honestly, and on small estates the move lost money outright:
Post acquisition VCF quotes against the prior perpetual plus support annual cost, which is what makes the exit question unavoidable.
What a costed exit quote took off the VMware renewal, applied whether or not the estate went on to migrate.
Three patterns recurred: renewal shock, with VCF quotes at 2x to 3x prior annual cost; underpriced effort, with migration engineering and tooling rework adding 20 to 40 percent on top of the first year licence saving.
And the leverage swing, where estates that produced a costed Nutanix quote cut the VMware renewal by 15 to 30 percent regardless of the eventual decision.
The buyer side move is to build the costed quote first and use it as leverage before committing to a year of disruption, because the credible threat frequently beats the migration itself.
The migration engineering line, not the licence delta, is what decides whether an exit pays back inside three years. The wider library sits in the Broadcom and VMware practice.
Your first five moves
- Pull the current VMware entitlement and the latest VCF renewal quote, then count physical cores and map which suite features the estate actually uses.
- Request a costed Nutanix proposal including migration scope and tooling rework, not a back of envelope figure, because only a real proposal moves an incumbent quote.
- Normalise both quotes to cost per physical core over five years, stripping unused suite value rather than crediting it, and amortise the migration project into the Nutanix run rate.
- Find the payback point before deciding. At scale on commodity workloads it usually lands inside two to three years; on small estates the project can outweigh the saving entirely.
- Use the costed exit quote as leverage on the VMware renewal first, since it cut the quote by an average of 22 percent whether or not the migration happened. The Broadcom practice models both paths with you.
Frequently asked questions
Is migrating from VMware to Nutanix always cheaper?
No. The licence saving is usually real on large commodity estates, but the migration project, tooling rework, and training can outweigh it on smaller ones. In roughly two thirds of the cases we modelled the first year saving shrank once engineering was costed honestly.
Model the full five year run rate including the one time project before treating the move as an automatic saving.
Why did Broadcom VMware pricing rise so much?
Broadcom retired most perpetual licences and standalone products after the acquisition and moved customers onto per core subscription bundles such as VMware Cloud Foundation.
Many estates saw annual cost rise 2x to 3x against the prior perpetual plus support model, with a median of 2.4 times in our review file, driven partly by minimum core charges per processor.
Does Nutanix charge separately for a hypervisor?
No. Nutanix includes its AHV hypervisor at no separate licence inside the Cloud Platform subscription.
Removing the standalone hypervisor charge is the main reason the Nutanix run rate can sit below the repriced VMware subscription, since the hypervisor line is the part of the VMware bill that rose most after the repricing.
How long does a VMware to Nutanix migration take?
It is a data centre programme measured in months rather than a licence swap, and the duration scales with estate size. Conversion, testing, cutover windows, and operational tooling rework all consume engineering time.
Conversion tooling reduces the machine by machine effort but does not remove the operational rework, which is the larger cost.
What costs do buyers most often underestimate?
Tooling rework and skills. Backup, monitoring, and automation built for vSphere need reconfiguration or replacement, and operations teams need training on a new hypervisor and management plane.
Together with conversion effort these added 20 to 40 percent on top of the first year licence saving across the estates we modelled.
How do you compare the two quotes fairly?
Normalise to cost per physical core at identical core counts, since both vendors now price on cores. Strip out VCF suite value the estate will never deploy rather than crediting it.
Then amortise the migration project across the contract term and add it to the Nutanix side, so you are comparing run rates rather than a subscription against a sunk perpetual cost.
Is the exit quote worth building even if we stay?
Yes, and it is the highest return work in the whole exercise. Estates that produced a costed Nutanix proposal cut the VMware renewal by 15 to 30 percent, an average of 22 percent, whether or not they migrated.
The credible, costed alternative frequently beats the migration itself on net cost and carries none of the operational risk.
Does Leaving Actually Save Money
Part 6 of the Negotiating Broadcom series. The honest answer, because a one sided claim gets dismantled in the room. Where switching genuinely saves, where it does not, which products you should never bluff about, and the one precedent that beat the renewal date.
