VMware After Broadcom for a Three-Host Shop: Stay, Shrink or Move?

A lot of small and medium businesses run VMware on a handful of hosts: two or three servers and some shared storage, set up years ago and rarely touched since. Since Broadcom bought VMware, perpetual licences have given way to per-core subscriptions, the product line has been folded into a few bundles, and many small customers have seen renewal quotes change sharply. For a three-host shop the question is simple to ask and harder to answer: is VMware still worth it?

There are three realistic answers. Licensing terms change often, so confirm current terms with Broadcom or your reseller before you decide.

First, find out what you actually run

Before comparing anything, write down:

• How many hosts, CPUs and cores you license, and when the current support or subscription ends
• Which VMs exist, what each one does, and which ones the business can't work without
• Which VMs nobody can explain (there are usually a few)
• How backups work, and whether the backup product supports the platforms you might move to
• How old the hardware is. If the servers are due for replacement anyway, moving costs much less than it seems.

Per-core licensing means core counts matter. Broadcom licenses a minimum number of cores per CPU, so a server with fewer cores than that minimum still pays for the minimum. Check the current rule, and count your cores before you get a quote.

Option 1: Stay, and right-size

Staying is the lowest-risk choice. Your backups, monitoring, procedures and skills keep working, and nothing has to be migrated.

• Choose the smallest bundle that covers what you actually use.
• License only the cores you need: fewer, newer hosts can mean fewer licensed cores, and switching off VMs nobody needs may let you drop a host.
• Makes sense when the renewal is affordable, the hardware is fairly new, or you rely on features and integrations the alternatives don't match.

Option 2: Shrink what you run

Many small environments carry servers that no longer need to exist. Before choosing a hypervisor, ask what could leave the cluster altogether:

• File servers whose contents belong in SharePoint, OneDrive or Google Drive
• Old email, print or application servers left over from past projects
• Line-of-business applications whose vendor now offers a hosted version

Shrinking can turn three hosts into one, or into none. It also makes options 1 and 3 cheaper, so it's worth doing whichever way you go.

Option 3: Move to another platform

Microsoft Hyper-V

Often the natural move for a Windows-heavy small business. Hyper-V is part of Windows Server, and Windows Server Datacenter licensing covers unlimited Windows VMs on a licensed host, which you may be paying for already. The day-to-day tools differ from vCenter, and you'll need to check your backup product supports it.

Proxmox VE

Open source, with optional paid support subscriptions. It runs VMs and containers, clusters small numbers of hosts well, and has a low licence cost. The trade-off is fewer third-party integrations and more reliance on whoever supports it, so plan who that will be.

Azure or another cloud

Moving a few servers to the cloud removes the hardware and hypervisor question, but the running cost is monthly and permanent, and a small office's internet connection becomes part of the critical path. Compare three to five years of running cost, not just the first month.

How to decide

Whatever you choose, do the sums over three to five years: licences or subscriptions, hardware, the one-time cost of migrating, and the time someone will spend running it.

If you move, move carefully

• Test the new platform with one non-critical VM first, including a backup and a restore.
• Migrate in small batches, with the original VM kept (switched off) until the new one has proven itself.
• Plan around your renewal date. If time is short, ask about a short bridge renewal rather than rushing a migration.
• Update the documentation as you go: what runs where, how it's backed up, and how to restart it.