Why Shrinking VMware Usage Can Raise Your Unit Price
Forty-eight percent of VMware customers intend a usage reduction by 2028. Virtified surveyed 450 IT professionals in 14 countries between December 2025 and February 2026. The pressure, the firm says, is Broadcom’s licensing changes: a complete private-cloud bundle rather than the SKUs many estates still run. Downsizing does not automatically produce a smaller bill. Confirm 8.x end of general support on Broadcom’s Product Lifecycle Matrix. A public Broadcom listing puts technical guidance for ESXi 8.0, vCenter Server 8.0, and vSAN 8.0 through 11 October 2029. A shrink you cannot price against the current discount, and against that support clock, is not a shrink. It is a hope.
That’s the problem.
The parent pack is the VMware Broadcom stay vs exit page: perpetual versus VCF, the support path, portable VCF on AVS, and third-party cover.
This is not a hypervisor bake-off. It is a commercial-framing problem. A VMware usage reduction by 2028 only pays if you can price stay, shrink, and leave against the estate you already run (this week, with the current commercial terms still attached). If that answer takes three weeks of specialist reading, the vendor has already framed the meeting.
What Virtified actually found
Virtified, an independent analyst firm, published the inaugural Virtified Loop research on 26 March 2026. Michael Warrilow, chief researcher and a former Gartner analyst covering cloud and virtualization, ran a self-funded survey of 450 IT professionals across APJ, Europe, the UK, and the USA, at organizations with more than 500 employees. Roles sat in operations, infrastructure, architecture, and procurement.
Treat that as directional. Four hundred and fifty respondents is a conversation, not a census. It tells you the pattern your next meeting will run on. It does not tell your CFO that “the market is leaving.”
The headline finding is 48 percent intending to reduce the VMware footprint by 2028, “driven primarily by Broadcom’s changes to VMware licensing.” A second number matters as much: 25 percent of organizations cite finding a suitable alternative as their biggest migration challenge. Warrilow’s line is the one to keep. “While VMware remains the technology leader, Broadcom’s licensing changes have triggered a once-in-a-decade disruption to the dynamics of the IT infrastructure market.” He names Microsoft, Nutanix, and Red Hat as the heavyweights closing the gap, with Canonical, Proxmox, and VATES as emerging open-source contenders.
Users are uncomfortable with a complete private-cloud bundle: Cloud Foundation. Some say the cost is beyond their means. Others do not want every tool in the stack, or the complexity of operating them. Those estates will review the virtual-machine fleet and move some of it. Many of those moves are already under way. Not all of them will produce a smaller Broadcom bill.
Shrinking the estate can raise the unit price
A shrink model is not a smaller count times last year’s unit price. Volume bands, minimums, and bundle SKUs do not automatically travel with the leftover estate. When the count moves, the commercial terms often reset. Sometimes the discount thins. Sometimes it disappears.
If your file still says “we will save the licenses we drop,” you are reading a reporting layer. You have a count. You do not have a commercial outcome.
This is not a criticism of the teams building those models. Traditional SAM tools were built to prove completeness, not to tell you, this week, what the bill looks like if the discount moves when the count moves. An analysis that arrives after the vendor has seen the shrink is a document. One that arrives during the meeting is a decision input.
Picture your procurement director, sixty days from a VMware conversation. The CIO wants a smaller footprint by 2028. Finance wants the saving on this year’s forecast. Virtified still rates VMware as the technology leader. If you cannot put a shrink case on the table that survives a worse unit price, you do not have a shrink case. You have a hope.
VCF is a bundle you may buy on the way out
Bills stay high for a second reason. Migrating off VMware while 8.x is still in general support is hard. Broadcom’s product lifecycle page is the portal into the Product Lifecycle Matrix. A public Broadcom end-of-technical-guidance listing puts ESXi 8.0, vCenter Server 8.0, and vSAN 8.0 through 11 October 2029. Confirm the end of general support date on the matrix for your exact build. After general support ends you stop receiving standard patches, security fixes, and hardware enablement. The product keeps running. It stops being a defensible support position.
Many estates will therefore buy Cloud Foundation anyway, so they stay covered through the window they need to finish a move. That is the trap in the bundle. You can decide to leave and still write a Cloud Foundation check. You can decide to shrink and still write a Cloud Foundation check. The product you did not want unified becomes the product that keeps you supported.
People who stay may have a rational reason: no suitable alternative (the 25 percent Virtified recorded) no path to the cloud, or a low appetite for the risk. Density and a more unified product are possible upsides. The stack still includes tools a lot of estates never asked to operate.
Do not let the vendor frame the next meeting as “do you want a modern private cloud.” The question is which SKUs in that bundle you will operate, which you will pay for and park, and what that costs against the estate you already run.
Going past end of general support is not a holding pattern. It is an audit posture. If a later comparison finds a gap, the true-up is priced without the discount you used to treat as normal. A hardware refresh that slips six months is not a slip. It is an unsupported window with a license conversation attached. That is an audit-defense problem before it is a migration problem.
Stay, shrink, or leave: price all three
Do this before the next VMware conversation.
| Path | What the research points at | What you lock before you pick it |
|---|---|---|
| Stay | Alternatives do not fit (25 percent cite that as the biggest challenge), cloud is not an option, or risk appetite is low. | Deployment matched to the VCF SKU list. Name what you will operate and what you will pay for and not use. |
| Shrink | 48 percent of 450 respondents plan to reduce usage by 2028. Unit price often resets when the count moves. | A shrink model priced with the current discount and without it. If the cliff eats the saving, you do not have a shrink case. |
| Leave | Finishing a move before 11 October 2027 is hard. Many will buy VCF to stay supported. Unsupported holdouts should expect a license conversation priced without the old discount. | Named exit date versus the hardware refresh. Written support through that date. An audit-ready position if you run past end of general support. |
If a non-specialist cannot brief the CIO in fifteen minutes from the pack you have today, you do not have a license position. You have a migration rumor.
The decision layer, not another inventory
You already have discovery data, a CMDB full of VMware records, and a renewal date on a spreadsheet. The gap is not another inventory.
Infrastructure Mapper is the topology layer for cores, hosts, and VMs; RVTools and vCenter sit on the data sources page. The perpetual-to-subscription fight is already on the record in the Tesco vs Broadcom / VMware coverage. The gap is turning that estate into a decision: what a shrink does to the unit price, which VCF SKUs you will operate, and whether an unsupported window is a plan or an audit invitation. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next.
If you are heading into a VMware renewal or an 8.x end-of-support conversation and your current tools still need three weeks to turn a shrink plan into a priced position, book an Audit Readiness Review. You can also start on the free plan and run the analysis on your own data.
The question to walk in with
Do not let the vendor frame this as “Cloud Foundation is the private cloud, here is the upgrade.” The right question is: what are we actually running, what does VCF add that we will not use, what happens to the unit price if we shrink, and what does staying supported through the 8.x general-support window cost against this estate rather than a list price. That is a data question, not a sales question.
Forty-eight percent of a 450-person survey planning to shrink is a signal, not a mandate. Some of those estates will still write a VCF check. Some will stay. Some will wait for a hardware refresh and meet a license conversation on the way. The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.
