VMware Renewal Options Compared

This is how the large majority of organisations buy VMware now. The partner takes the expiration date, the core count and the edition, raises the quote in Broadcom's system, and places the order through a distributor. What the partner adds is sizing: checking the licensed cores against the hosts you are actually keeping, saying when a lower tier fits, and pricing the one, three and five-year terms side by side. What it does not add is a separate price list; partners quote against the same programme.

The failure mode is a partner who carries last year's number forward without asking for a host inventory. The fix is to send an RVTools export with the request and to expect the quote to show its working. Where to buy VMware licenses now covers how to tell a good partner from a reseller with a login.

Available only to the accounts Broadcom manages itself. If you are one of them you have an account director's name already, and a partner cannot quote around that relationship; the correct partner behaviour is to refer you back. The products and the list structure are the same as through a partner. What differs is cadence: direct quotes move on Broadcom's quarter rhythm, and a request that lands late in a quarter can wait.

Independent support firms will keep an estate on perpetual vSphere or ESXi running after Broadcom support ends: break-fix, configuration help, and their own mitigations for known vulnerabilities. It is genuinely cheaper per year, and for a frozen estate with no growth and no compliance regime it can be the right answer.

The limits are structural. The provider cannot issue Broadcom patches, cannot add hosts beyond what the perpetual key covers, and cannot move you to a current version. An estate that grows, needs a vendor patch for a CVE, or answers to an auditor has outgrown the option. Treat it as a bridge with a defined end, not a destination.

Proxmox VE, Nutanix AHV, Hyper-V and OpenShift Virtualization all run production workloads, and estates have moved to each since the Broadcom changes. The licence line is usually lower. The costs that decide the answer sit outside it: discovery, dependency mapping, rebuilding automation and monitoring against a different hypervisor, parallel running, and cutover risk. On a mid-size estate that is quarters of senior infrastructure time.

The practical pattern is to renew once, properly sized, while the migration is evaluated for real. Renew or migrate: the cost comparison works the crossover in detail.

1. Are you a Broadcom-managed account? If yes, direct. If unsure, ask a partner; they can find out from your company name and address.
2. Is the estate on perpetual keys, frozen, and outside any compliance regime? If yes, third-party support is worth pricing as a bridge.
3. Do you have spare senior engineering capacity and a multi-year horizon? If yes, migration is a real option; renew once while you scope it.
4. Otherwise, renew through a partner, send the host inventory, and have the lower tier and the longer terms quoted alongside the like-for-like.