Skip to content
VMware Exit Strategy | Move Beyond Broadcom Licensing | Intelligent Visibility
Infrastructure / VMware Exit Strategy

You don't have to renew on their terms

A practical guide to evaluating your VMware exit options, planning a controlled migration, and building a modern infrastructure that restores budget predictability and technical sovereignty.
See the AIM Modernization Program Talk to an Architect

The Broadcom effect on enterprise VMware environments

Since the Broadcom acquisition closed, VMware licensing has fundamentally changed. Perpetual licenses are gone. A-la-carte purchasing is gone. What remains is a bundled subscription model that forces organizations to pay for capabilities they may not need, at price points that often represent a 3–6x increase over previous renewal costs.

For many enterprise IT organizations, the VMware renewal conversation has shifted from a routine procurement exercise to a strategic inflection point. The question is no longer "how do we optimize our VMware spend?" It's "do we still want VMware to define our infrastructure roadmap?"

3–6x renewal increases

Core-based pricing and forced bundling are driving dramatic cost increases, particularly for organizations with large on-prem footprints.

Double billing for bundled features

Software-defined networking and storage capabilities bundled into VMware subscriptions that your hardware already delivers natively.

Loss of purchasing flexibility

No more buying only what you need. Bundled SKUs force adoption of features that may not align with your architecture or operational model.

Roadmap uncertainty

Product direction, support quality, and long-term investment in the platform are no longer under the same leadership that built the trust in the first place.

This isn't about whether VMware is good technology. It is. The issue is that the commercial model around it has changed in ways that put enterprise buyers at a disadvantage. A VMware exit strategy isn't anti-VMware — it's pro-sovereignty. You should control your infrastructure roadmap, not your licensing vendor.

Your three options — and when each one makes sense

There is no single right answer. The right exit strategy depends on your workload profile, your timeline, your team's operational maturity, and how much of your environment can move versus how much needs a transitional path. Most enterprises use a combination.

Most common path

Nutanix AHV

Full hypervisor replacement

Replace ESXi with an enterprise hypervisor that's included with the platform. Nutanix Move automates workload migration with minimal disruption. No separate hypervisor license, no forced bundling, no per-socket tax.

  • Zero hypervisor licensing cost
  • Automated migration from ESXi via Nutanix Move
  • HCI or disaggregated deployment models
  • Cloud extension via NC2 on AWS
Best for: workloads that can move to a new hypervisor. Most general-purpose VMs migrate cleanly.

AWS EVS

Cloud runway for VMware workloads

Move VMware workloads to AWS Elastic VMware Service without re-platforming. Keeps VMware compatibility in the cloud while you exit on-prem licensing. A transitional path, not a permanent destination.

  • No application refactoring required
  • Eliminates on-prem VMware licensing
  • Buys time for workloads not yet ready to migrate
  • Full AWS service integration available
Best for: legacy workloads with VMware dependencies, compliance constraints, or applications that need more time before re-platforming.

Hybrid approach

Parallel modernization

Migrate the majority of workloads to Nutanix AHV on-prem while placing VMware-dependent workloads on AWS EVS. No workloads left behind, no big-bang cutover, and every VM has a defined path forward.

  • Every workload gets a path — nothing is stranded
  • Controlled, phased migration reduces risk
  • On-prem savings from AHV + cloud flexibility from EVS
  • Strongest long-term architectural position
Best for: large enterprises with mixed workload portfolios and varying migration readiness across business units.

What a controlled exit actually looks like

The biggest risk in a VMware exit isn't the technology — it's the approach. A "rip-and-replace-everything-at-once" migration is almost never the right move. The organizations that execute this well treat it as a phased modernization program with clear milestones, workload-level decision making, and production protection at every step.

1
Weeks 1–6

Assessment and architecture

Inventory the current VMware estate, evaluate renewal timing and exposure, classify workloads by migration readiness, identify dependencies and blockers, and design the target-state architecture across Nutanix AHV, Pure Storage, Arista networking, and AWS continuity.

2
Weeks 6–18

Pilot migration

Stand up the new fabric, migrate an initial set of workloads using Nutanix Move, validate performance and operational readiness, and establish the operational cadence for the broader rollout. This phase proves the model before scaling.

3
Months 3–12

Broader migration and optimization

Systematically migrate remaining workloads by priority. Workloads that can't move off VMware yet are placed on AWS EVS. Storage is consolidated onto Pure FlashArray. Networking is unified on Arista leaf-spine. Each wave is validated before the next begins.

4
Ongoing

Aegis co-managed operations

Transition into the Aegis operating model for performance monitoring, incident response, configuration management, and lifecycle operations. The infrastructure is modern — the operating model should be too.

How to evaluate whether your environment is ready

Not every VMware environment is ready to exit tomorrow. But every VMware environment should have a plan. Here's how to assess where you stand:

When is your next renewal?

If your VMware renewal is within 12 months, you need to start the assessment now. The architecture and pilot phases take 3–4 months minimum before you have a credible alternative in production.

Under 12 months → start assessment immediately

What's your workload profile?

General-purpose VMs (file servers, app servers, databases, web services) migrate cleanly to AHV. Workloads with deep VMware API dependencies or specific vSphere features may need the EVS transitional path.

Mixed portfolio → hybrid approach with AHV + EVS

How tightly coupled is your storage?

VSAN environments require the most planning since storage and compute are tightly integrated. Environments running external storage (Pure, NetApp, etc.) have a simpler migration path since storage is already independent.

VSAN → more planning needed, but still doable

Do you have internal migration expertise?

Hypervisor migrations are high-stakes infrastructure changes. If your team hasn't done one before, this is where a partner with proven migration experience (and co-managed operations for Day 2) makes the difference.

Limited experience → co-managed approach through AIM
The AIM program was designed specifically for this moment. Aegis Infrastructure Modernization combines the architecture design, migration execution, and co-managed operations into a single program. Cisco UCS for compute, Nutanix AHV for virtualization, Arista for storage networking, Pure Storage for performance, and AWS EVS for workloads that need more time. Every workload gets a path forward.

What happens if you do nothing

Doing nothing is a decision too, and it has costs:

The licensing gap widens. Each renewal cycle under the new model increases your cumulative overspend. Organizations that exit earlier capture more savings over time.

Your negotiating leverage decreases. Broadcom knows which customers have no alternative. The organizations with a credible exit plan — even if they haven't fully executed it yet — negotiate from a stronger position.

Technical debt accumulates. Every year you stay on ESXi without a forward path is another year of investment in a platform you'll eventually need to leave. The migration doesn't get simpler with time — it gets more complex as dependencies grow.

Your team's skills narrow. Engineers running ESXi exclusively for years will need ramp time on any alternative. Starting the transition now means building those skills while you still have time, not under renewal pressure.

The strongest position is a credible plan, even if you haven't finished executing it. Having a validated target-state architecture and a pilot deployment in production gives you real leverage at the negotiating table — whether you choose to leave VMware entirely or use that position to negotiate better terms.

Start with an infrastructure assessment

We'll review your VMware estate, renewal timeline, workload profile, and storage dependencies — then define the most practical exit path for your environment. No obligation, no product pitch.

Explore the AIM Program Talk to an Infrastructure Architect

Guides

8 resources

Guides Resources