VMware renewals are the surprise line item on a lot of small-business IT budgets right now. These are the questions owners and office managers bring us when the quote doesn't look like last year's.
The short version:
- Subscriptions replaced perpetual licenses, and the product list collapsed into per-core bundles.
- The 72-core minimum you may have read about is not real. It was withdrawn before it took effect.
- Start pricing alternatives six months before your renewal date, not two weeks before.
Questions owners ask about VMware renewals
What actually changed with VMware licensing?
Broadcom bought VMware and rebuilt how it's sold. Perpetual licenses gave way to subscriptions, the long product list collapsed into a small number of bundles, and licensing moved to a per-core model.
For a small shop running two or three hosts, that turns a one-time purchase plus optional maintenance into a recurring cost sized to every core in the box.
Is the 72-core minimum real?
No. The number still circulates, so here's the record.
In March 2025 The Register reported, citing distributor Arrow, that from April 10 the minimum would rise "from 16 to 72 cores per command line." Broadcom walked it back before it took effect, telling press it had "never announced a price change" and keeping the 16-core minimum set in December 2023.
So why did my quote still go up?
Bundling and the move to subscription. If you ran a stripped-down edition and paid maintenance, the replacement bundle includes components you never asked for, priced across every core in the host.
Watch the renewal date too. The Register reported a 20 percent uplift over the first-year quoted price for customers who don't renew by their anniversary. That term wasn't part of the core-minimum walk-back, but confirm the current one with your reseller before you sign.
Don't let a renewal drift.
Can we keep running our perpetual licenses and not renew?
Technically yes, and plenty of businesses are doing it for a year to buy time.
Understand what you're accepting: no support contract, no guaranteed patch stream, and no supported path to newer hardware or newer guest operating systems. That's a reasonable bridge for twelve months while you plan. It isn't a strategy either. Every cyber insurance renewal questionnaire we've filled out this year asks whether any production infrastructure is unsupported.
What are the real alternatives for a small business?
Three that we actually deploy:
- Hyper-V. Included with Windows Server. The obvious answer if you're already a Microsoft shop.
- Proxmox VE. Open source, capable, free to run, with paid support available if you want a number to call. Strong fit where there's in-house Linux skill, weak fit where there isn't.
- Azure. Retire on-prem virtualization and move the workloads. Best when the hardware is due for replacement anyway.
Which one fits depends on what you're running and who maintains it. We walk through the on-prem-versus-cloud version of this decision in our post on choosing between Azure and AWS.
Should we just move to Azure instead?
Sometimes, but don't assume it's cheaper. Lifting an over-provisioned on-prem server into Azure at the same specs costs more per month than most people expect, and the savings only appear once you right-size and retire what you don't need.
We break the arithmetic down in our post on Azure migration cost for small business.
Why won't anyone quote me a straight per-core price?
Because the public numbers move and the real number depends on your bundle, your core count, your term and your reseller. We won't publish a figure we can't stand behind for your environment.
Get quotes for the same core count across VMware, Hyper-V and Azure on the same day. That comparison is meaningful. A number in a blog post isn't.
How long does a migration off VMware take?
Across the migrations we've run, a small business with two hosts and fifteen to thirty virtual machines takes four to eight weeks end to end.
Most of that is testing and scheduling, not the conversions. The cutover itself happens over a weekend or across two or three evenings, one workload at a time.
What tends to break in a migration?
Three things, and backup is the one people forget:
- Backup jobs. Your backup product has to support the new hypervisor, and job configuration doesn't carry over. Confirm this before you move a single production VM, then verify a restore afterward.
- Hardware-tied licensing. Anything with a dongle or a MAC-address lock needs a re-host request with the vendor, and some take weeks.
- Line-of-business applications. Older ones sometimes need vendor sign-off on the new platform before support continues.
When do we need to decide?
Start six months before your renewal date. That's enough time to price the alternatives properly, pilot one non-critical workload, and negotiate from a position where walking away is credible.
Deciding in the last two weeks means renewing on whatever terms you're handed.
Does this affect us if we're already all-cloud?
Not directly. With no on-premises hypervisor, VMware licensing isn't your problem.
Check anyway. We regularly find one forgotten host in a closet running a legacy application, still licensed, still unpatched, still on the invoice.
Get a straight answer on your renewal
If your VMware renewal is coming up and the quote doesn't make sense, we'll price the alternatives against it and tell you which one fits, including staying put when that's the right call.
The NetSys Group has supported small businesses across New York, New Jersey, Connecticut, Pennsylvania and Southwest Florida since 1998. Contact us for a complimentary consultation, or see how we handle Azure migrations and the rest of our managed IT services.
Turn insight into action.
Take a free cybersecurity or AI readiness assessment, or book a call with a NetSys engineer — no obligation, no runaround.