Back to blog

VMware Perpetual Licenses: What October 2027 Really Means

Support for vSphere 8 perpetual products ends October 11, 2027, and Broadcom's cease-and-desist campaign is already running. Here is what your licenses are still worth and the three exit paths, compared honestly.

VMware Perpetual Licenses: What October 2027 Really Means

For two decades, buying VMware meant owning software: a perpetual license plus an annual support contract. Broadcom ended that model within weeks of closing the acquisition in November 2023: no more perpetual sales, no more support renewals, everything converted to per-core subscriptions. And there is now a fixed deadline for everyone: general support for vSphere 8 perpetual products (ESXi 8.x, vCenter 8.x, vSAN 8.x) ends on October 11, 2027. After that date, no more updates, bug fixes or security patches for perpetual vSphere, from anyone with access to the source code.

What your perpetual license is still worth

Let us be precise, because fear serves nobody. Broadcom's own guidance confirms that the software entitlement is not revoked when support expires: your hosts and vCenter keep running normally. What you lose is everything around the running software: no support requests, no non-critical patches, and no adding hosts or major version upgrades during the gap.

The lights stay on, but you are operating hypervisors that will never be patched again, on an estate that cannot grow. That is not a steady state; it is a countdown.

The cease-and-desist letters

Since 2025, organizations with expired support have been receiving cease-and-desist letters from Broadcom, demanding they stop using and even roll back patches applied after expiration (zero-day fixes excepted), under threat of legal action and audits. The letters appear to be sent largely automatically on expiry: some organizations received them without having downloaded anything, others after having already migrated entirely off VMware.

Three rules if one arrives. Forward it to legal immediately. Sign nothing, especially any "certificate of destruction" style document, without counsel review, as acknowledging the wrong framing can weaken a genuine perpetual entitlement. And keep your engineers out of contract-law debates with a sales organization. None of this is legal advice, which is exactly the point: it is a legal matter now, not an IT one.

Your three options

Convert to a Broadcom subscription. Restores support at the new pricing and bundling. Legitimate for a small island of workloads certified only on ESXi; as a whole strategy, it locks in a permanent cost increase and a repeat of this negotiation at every renewal.

Third-party support. The pitch is polished: you own the licenses, the 2027 date is a vendor deadline not a business mandate, costs drop, and kernel-level security tooling substitutes for patches. Some of that is fair, and it can decompress a rushed renewal. But no third party can write code for a closed-source product: real patches end with the vendor, runtime protection is mitigation rather than maintenance, and your estate stays frozen. Even its advocates frame it as buying time to evaluate alternatives, which raises the question of what you do with the time.

Migrate to an open platform. The path most of the market has chosen, with Proxmox VE as the leading destination: mature KVM hypervisor, integrated Ceph storage, no per-core arithmetic, and no acquirer who can ever revoke the model, because the platform is open source. The tooling has matured to match: ProxCenter's integrated migration pipeline moves VMs straight out of vCenter or ESXi (vSAN included), with warm migration based on changed-block tracking so large busy VMs cut over in minutes, MAC addresses preserved, in tracked bulk waves. Our step-by-step migration guide walks the journey; our TCO analysis runs the numbers.

The plan if your support has expired or soon will

  1. Document your entitlement: keys, contracts, exact support end dates. Your first defense if a letter arrives.
  2. Freeze and harden: no new hosts, no upgrades, tightened isolation of the management plane. Treat the estate as legacy from today.
  3. Route any Broadcom legal mail through counsel, without exception.
  4. Start the exit in parallel: pilot cluster with ProxCenter connected to both sides, first wave through its pipeline, VMware footprint shrinking toward zero or a small certified island.
  5. Use the countdown as leverage: a visibly progressing migration is the only negotiating position this model respects.

The end of perpetual licensing taught enterprise infrastructure that ownership can be redefined retroactively by an acquisition. The durable answer is not a better contract; it is a platform where the question cannot arise.

Ready to see what the exit looks like on your own hardware? Start a ProxCenter trial: the only thing we need is your node count.