VMware Phased Exit Strategy: Migrating Off Broadcom in Waves

Why Phased Exit Is the Right Approach

The instinct when facing a 200 to 500 percent cost increase from Broadcom's post-acquisition VMware pricing is to want to exit quickly and completely. This instinct is understandable but commercially and operationally counter-productive. A rapid, estate-wide migration creates several avoidable problems: it compresses the migration timeline in ways that force higher-risk decision-making, it reduces the commercial leverage the exit plan provides during the Broadcom renewal window, and it increases the likelihood of operational disruption for production workloads that are not ready for migration.

A phased exit, by contrast, delivers cost reduction at each wave while maintaining operational continuity. Wave 1 migrates the 20 to 40 percent of the estate that can move with minimal risk and minimal operational disruption — the evidence from Wave 1 informs the approach for Wave 2, Wave 2 results inform Wave 3, and each completed migration reduces the committed VMware core count and the associated subscription cost. The phased approach also extends the period during which the exit plan provides negotiating leverage with Broadcom, since the plan remains active and credible throughout the migration programme.

Pre-Wave Foundation: Discovery and Classification

Before designing the wave structure, you need a complete and accurate picture of your VMware estate. Discovery and classification is not optional — it is the foundation on which every subsequent wave design decision rests. Organisations that shortcut this phase consistently encounter unplanned workload dependencies, unexpected VMware-specific configurations, and application compatibility issues that delay Wave 2 and Wave 3 migrations.

Discovery Scope

Discovery should cover: every vSphere host and its physical CPU core count (this is your Broadcom billing unit), every VM with its guest OS, vCPU, vRAM, and storage configuration, application-to-VM dependency maps showing which VMs must migrate together, vSphere feature usage — HA policy configurations, DRS rule assignments, vMotion dependencies, vSAN and NSX usage — and any in-guest VMware tooling or applications that depend on VMware-specific APIs or hardware virtualisation features. Automated discovery tools such as VMware vSphere Inventory Explorer, Nutanix Move Discovery, and third-party tools significantly accelerate this work for large estates.

Workload Classification Matrix

Apply a four-attribute classification to each workload cluster: migration complexity (low, medium, high based on dependency count, VMware feature reliance, and application sensitivity), business criticality (tier based on downtime tolerance and revenue or regulatory impact), migration readiness (immediate, planned, deferred based on application team availability and testing requirements), and target platform compatibility (Nutanix AHV compatible, Azure VMware Solution compatible, requires refactoring). This four-attribute matrix generates a priority score for each workload cluster that drives wave assignment.

Wave 1: Foundation Migration (Months 1 to 6)

Wave 1 targets workloads that are low-complexity, medium-to-low criticality, and immediately ready for migration. This typically covers: development and test environments, CI/CD infrastructure, internal tooling (monitoring agents, configuration management, log aggregation), non-production instances of production applications, and cloud-adjacent workloads that already use cloud APIs or services. Wave 1 typically represents 20 to 35 percent of total VMware core count and carries minimal production risk if a rollback is required.

Platform Selection for Wave 1

Nutanix AHV is the preferred Wave 1 platform for on-premises destinations due to its operational maturity, automated migration tooling (Nutanix Move), and direct TCO advantages relative to Broadcom VCF. Nutanix AHV provides a vSphere-equivalent hypervisor with integrated storage management that eliminates vSAN licensing, replacing it with Nutanix AOS storage at a lower per-node cost. Wave 1 on Nutanix also builds the operational familiarity with AHV administration that Wave 2 and Wave 3 migrations will depend on.

Azure VMware Solution is preferred for Wave 1 workloads where cloud proximity and Azure integration are primary requirements — for example, development environments that consume Azure PaaS services or workloads with Azure DR targets. AVS maintains vSphere operational consistency, making it the lowest-friction migration for organisations with limited time to retrain operations teams. The AVS cost model — Azure infrastructure plus Broadcom VCF portable subscription — requires careful modelling to ensure it delivers cost reduction versus on-premises Broadcom pricing for the specific workload profile.

Wave 1 Execution

Wave 1 migration execution uses Nutanix Move (for Nutanix targets) or Azure Migrate (for AVS targets) to automate VM discovery, cutover scheduling, and migration tracking. Each workload migration follows a four-step process: pre-migration validation (confirming target platform compatibility and resource availability), scheduled cutover during a defined maintenance window, post-migration validation (confirming application functionality and performance), and a 48 to 72 hour stabilisation period before decommissioning the source VM. Wave 1 completions reduce the Broadcom licensed core count proportionally and create documented evidence of migration capacity for the Broadcom renewal conversation.

Wave 2: Production Migration (Months 6 to 18)

Wave 2 addresses medium-complexity production workloads: web application tiers, database servers, internal business applications, and infrastructure services such as monitoring, backup, and security tooling. These workloads require longer planning horizons, stakeholder alignment with business application owners, and defined maintenance windows for cutover. Wave 2 typically covers 40 to 50 percent of the total VMware estate by core count and delivers the largest single-step reduction in Broadcom subscription cost.

Wave 2 Planning Requirements

For each Wave 2 workload, the migration plan must address: application dependency isolation (confirming that all dependent workloads have been migrated in Wave 1 or are scheduled for concurrent migration), performance baseline establishment on the target platform before production cutover, rollback procedure with a defined recovery time objective, business stakeholder sign-off on cutover window and acceptance criteria, and post-migration monitoring plan covering the 30-day stabilisation period. The Wave 1 results — performance data, operational observations, team capability assessments — directly inform Wave 2 planning assumptions.

Compressing Wave 2 Cost

Wave 2 is the point at which the Broadcom subscription cost reduction becomes commercially significant. For a 3,000-core estate at VCF pricing of $160 per core per year, completing Wave 1 (900 cores) and Wave 2 (1,500 cores) reduces the committed VMware estate to 600 cores, reducing the annual subscription from approximately $480,000 to $96,000 — a reduction of $384,000 per year independent of any negotiated discount. This arithmetic is the foundation of the bridging agreement negotiation with Broadcom: the annual cost should reduce proportionally with completed migrations.

Wave 3: Complex Workload Migration (Months 18 to 36)

Wave 3 covers the highest-complexity, highest-criticality workloads: ERP systems, core banking and financial applications, healthcare clinical systems, manufacturing execution systems, and any workloads with long-standing VMware-specific configurations or third-party software certifications tied to VMware infrastructure. These workloads require the most extensive planning, the longest test and validation periods, and the most careful stakeholder management.

Wave 3 Migration Approaches

Wave 3 workloads often require a choice between three migration approaches. Lift-and-shift using Nutanix Move or similar tooling is feasible for workloads where the application has no VMware-specific dependencies and the target platform certification requirements can be met. Azure VMware Solution is valuable for Wave 3 workloads where the VMware operational consistency removes certification risk — applications certified for vSphere continue to run on AVS without recertification, as the underlying VMware software stack is unchanged. Re-platforming to cloud-native services is the long-term optimal path for Wave 3 workloads that are candidates for modernisation, but the timeline extends beyond 36 months for most complex enterprise applications.

Commercial Milestones at Each Wave

The phased exit strategy should be synchronised with the Broadcom commercial calendar. Wave 1 completion should precede the first Broadcom renewal negotiation, providing documented evidence of migration capability and reducing the committed core count that drives the renewal quote. Wave 2 completion milestones should be aligned with annual contract review provisions, enabling core count reductions at each review point. Wave 3 planning and partial completion should inform the final-year bridging agreement negotiation, establishing the exit timeline that allows the last VMware subscription to lapse without penalties.

Organisations that negotiate their Broadcom bridging agreement with wave completion milestones written into the contract — providing core count reduction rights at defined intervals — consistently achieve better commercial outcomes over the full migration period than those who sign a static three-year subscription without migration flexibility provisions. The contractual right to reduce core counts is a non-monetary value that can be worth more than the headline price discount, particularly for estates where Wave 2 and Wave 3 completions are within the subscription term.

Governance and Programme Management

A phased VMware exit is a 12 to 36 month infrastructure programme that crosses multiple business units, application teams, and vendor relationships. Effective governance requires: a programme steering committee with CIO-level sponsorship and authority to approve migration decisions and resolve cross-team dependencies, a dedicated migration programme manager with technical infrastructure and vendor management experience, a workload migration status dashboard updated weekly, an escalation procedure for migration blockers that provides a clear path from technical team to steering committee, and a quarterly commercial review with Broadcom covering current core count, completed migrations, and upcoming wave plans. Organisations that establish this governance structure in the pre-Wave 1 planning phase consistently execute phased exits faster and at lower cost than those that attempt to manage the programme through existing operational structures.