Two real VMware quotes for one SMB. The cheaper one is the trap.

Here is one number from a real refresh quote that landed on a Victorian business owner's desk last month: $100,800 (AUD). That is the VMware licence alone, on a five-year term. Not the hardware. Not the Windows licensing. The hypervisor. It is more than a third of the entire bill to replace two servers and keep the lights on. For an eight-VM transport business running two hosts, VMware now costs roughly $20,000 a year, and it is the fastest-rising line on the page. That is the number that starts the conversation about leaving.
We wrote about how Broadcom got here when it restructured VMware's pricing: the bundled subscription, the per-core model, the briefly-floated 72-core order minimum it walked back under pressure but that still colours how the channel quotes. This is what the new model looks like as a number on a page. The business — a transport and logistics operator running about eight virtual machines — had reached an ordinary fork in the road. The hardware was due for refresh. So we priced both ways out: refresh on-premises and stay on VMware, or move the whole environment to a managed private cloud. Both quotes are real. The interesting part is which one is cheaper, and why that turns out to be the wrong question.
The on-prem quote, every line
The refresh path is a one-off capital cost. Two current-generation servers, the storage array to sit behind them, and a backup server come to $161,462. Windows Server licensing across the cores adds $22,284. And VMware vSphere Foundation, on a five-year term, adds $100,800. Over a third of the combined hardware-and-software bill is VMware alone. The total, before anyone has been paid to actually do the migration, is $284,546 ex GST.
Look closely at how that licence is counted. The two servers carry 64 physical cores between them; the quote covers 72. Broadcom walked the 72-core order minimum back under pressure last year, and yet here it sits on a 2026 refresh quote — eight cores of hypervisor billed against silicon that does not exist. The abstract policy from the last piece turns out to be a line item on a real Victorian SMB's quote.
That is a like-for-like build, not a stripped one: dedicated storage, four-hour hardware response, current-generation processors, sized to the resilience the business already runs on. A leaner refresh would bring the sticker down — fewer cores, a slower warranty, storage folded into the hosts — but it changes the hardware, not the single-site position below.
That number has a quiet feature: it buys exactly what the business already has. One site. One server room — in this case a room so tight that the rack has to be wheeled out the door to be worked on, which means the fibre uplinks to the downstream switches get run across the floor during maintenance. One foot on a cable and the whole network is down. A single UPS, no standby generator. No disaster recovery beyond a manual failover to the backup box. Spend the $284,546 and the operating position is unchanged. Newer hardware sits in the same corner, carrying the same single-site risk, on a licence the vendor will reprice at the next renewal.
The private cloud quote
The move costs $6,736 a month ex GST on a 36-month term: $5,526 for the compute across the eight VMs, $1,210 for managed backup. What that monthly includes is the part that matters. Storage replicated three times across independent nodes, with VMs restarting automatically if a host fails. A Melbourne datacentre with power and cooling redundant past 2N. A dual-firewall cluster. Immutable backups held offsite with a long-term retention schedule. ISO 27001 and IRAP-assessed Australian sovereignty. Windows Server licensing bundled in. And, structurally, no hardware to refresh ever again, because there is no hardware to own.
The move does take on one dependency the server room did not have: the internet link becomes the path to production, with staff reaching SQL and remote-desktop sessions over the connection rather than the LAN. It is engineered with redundant carriage — a known trade, not a hidden one.
The number that looks bigger
Run both over five years and be honest about it. The monthly comes to $404,160. The on-prem capital cost is $284,546. On the sticker, staying is roughly $120,000 cheaper. If the comparison stopped there, the refresh wins, and most comparisons do stop there.
It shouldn't, for two reasons. The first is that the on-prem column is incomplete. The quote leaves out the power three boxes draw, the cooling on top, the UPS batteries replaced inside the term, and the maintenance contract that keeps ageing hardware alive. None of those appear on the cloud side. Add them back and the gap narrows.
The second reason is the one that actually decides it. The two quotes do not buy the same thing. The $284,546 buys a single site with no disaster recovery. The $6,736 a month buys redundant power and cooling, replicated storage, automatic failover, an offsite immutable backup, and assessed sovereignty. To make the on-prem option match that, you stop buying hardware and start buying a second platform: a second site to fail over to, storage replicated across nodes instead of riding on one SAN, and the network to tie them together. That is another large slice of capital on top of the $284,546 — the slice most refresh quotes quietly leave out. The moment you compare like for like, the cheaper quote stops being cheaper.
And then, in year five or six, you do the whole thing again. Another refresh, another pile of capital, another VMware renewal priced by a vendor that has shown you precisely where it is heading. The monthly has no capital cliff in year five and no second refresh in year ten. The bill moves with what you consume; it does not reset to zero and ask for six figures back.
A hardware refresh is a sideways move. It changes the hardware, not the posture.
What the cheaper number actually costs
This is the trap in every on-prem-versus-cloud comparison, and it is worth naming plainly, because the numbers are built to mislead. The capital quote looks smaller because it is an incomplete picture of a weaker position. The monthly looks larger because it is a complete picture of a stronger one. We have made the same case about the costs that never reach the invoice and about why owning the hardware stopped adding up. This is what it looks like when a real quote forces the choice.
For a Victorian SMB with a VMware renewal and a refresh both coming due, the right move is not to weigh the cheapest way to stand still against the cost of moving. It is to ask what each number actually buys, over the life of the decision, at equal resilience. On that basis the refresh is the expensive option that happens to carry the smaller price tag.
Communicat runs this private cloud platform out of Melbourne, and we will put the real quote in front of you the same way: every line, both paths, no thumb on the scale. If you are staring at a VMware renewal, the first thing worth doing is the honest five-year comparison, at equal posture — before the renewal decides it for you.
Frequently asked questions
How much does it cost to migrate off VMware?
The migration itself is the smaller number. For a typical SMB of around eight VMs, the consulting to move the environment is a one-off engagement, and the ongoing cost is a fixed monthly platform fee rather than capital. In the real case below, the move landed at $6,736 per month ex GST on a managed private cloud, against a $284,546 one-off to refresh and stay on VMware. The right way to read the cost is over the life of the decision, at equal resilience, not as migration-versus-nothing.
Is private cloud cheaper than refreshing on-prem VMware?
Not on the sticker, and that's the trap. Over five years the on-prem capital cost can look six figures cheaper than the monthly. But the capital quote leaves out power, cooling, UPS and maintenance, and it buys a single-site platform with no disaster recovery. Adding the resilience the cloud includes by default — a second site, replicated storage, automatic failover — is a large additional slice of capital on top of the refresh. At equal posture the refresh is the dearer option, and it repeats at the next refresh.
What is the VMware 72-core minimum and does it still apply?
In April 2025 Broadcom briefly introduced a 72-core minimum per subscription order, which would have forced even small two-host clusters to license 72 cores regardless of actual core count. It walked the rule back under industry pressure, and vSphere Foundation reverted to a 16-core-per-CPU minimum. The episode still matters: it showed Broadcom's direction of travel, and resellers continue to quote VMware defensively. The durable point for an SMB is not the exact floor — it is that the hypervisor licence is now the fastest-rising line on a refresh quote.
Does moving off VMware mean losing high availability?
The opposite, usually. A single-site on-prem VMware setup with one SAN and a backup box has high availability only on paper — a power, cooling, or storage-controller fault takes everything down. A managed private cloud replicates storage across independent nodes, restarts VMs automatically on a host failure, and keeps immutable backups offsite. For most SMBs the move adds resilience that would cost six figures to build on-premises.

Written by
Managing Director
John Zammit is Managing Director at Communicat IT, a Melbourne MSP serving Victorian SMBs since 1987. He writes about cloud economics, infrastructure strategy, and the gap between sales narratives and operational reality.