A decision framework for the VMware question
Published August 6, 2026 · 4 min read
Retain, rehost, replatform, or retire — turning Broadcom's licensing shock into a per-workload plan instead of a panic.
Panic migrations break things
Broadcom's move to subscription-only licensing — perpetual licenses gone, the lineup consolidated around VMware Cloud Foundation and vSphere Foundation — put a clock on every VMware estate, and clocks invite panic. But an estate is not one workload; it is hundreds, each with its own dependencies, performance profile, and tolerance for change. Moving them as one undifferentiated mass is how critical systems end up down on a Tuesday.
The alternative is a disposition per workload, drawn from the migration strategies AWS documents as the 7 Rs — retire, retain, rehost, relocate, repurchase, replatform, refactor. In practice four buckets carry most estates: retain where VMware still earns its cost, rehost where a hypervisor swap or cloud landing is straightforward, replatform where containers or managed services fit better, retire what nobody would rebuild.
Dependencies decide the order
The workload list is easy; the dependency map is the work. Shared databases, licensing servers, latency-sensitive pairs, backup jobs — these decide what can move together and what must not move apart. Storage architecture belongs on the same map: a vSAN Original Storage Architecture cluster built on disk groups and a newer Express Storage Architecture cluster pooling NVMe devices age — and exit — on different schedules, as does the vSAN ReadyNode hardware underneath them.
Prove the path on a pilot wave
Whatever the target — cloud, Red Hat OpenShift Virtualization via the Migration Toolkit for Virtualization, or a leaner vSphere core — a pilot wave of production-shaped workloads validates tooling, runbooks, and rollback criteria while the stakes are small. The mechanics differ by disposition: vSphere vMotion and Storage vMotion inside the estate, VMware HCX for workload mobility across environments, cold migration or rebuild where honesty demands it. The pilot's report becomes the template every later wave follows.
Waves with cutover windows, rollback criteria, and owner sign-off shrink the estate on a schedule everyone can see. That visibility, more than any tool, is what keeps a migration funded and calm.