You Want to Migrate from VMware? Ask Your Architecture Review Board First

Why IT governance—not cost—is the real deciding factor in Broadcom-era VMware strategies.

TL;DR:
Broadcom’s VMware licensing changes are forcing tough conversations—but most enterprises aren’t leaving the platform. Why? Because the real constraint isn’t cost—it’s architecture. Your Architecture Review Board (ARB), not your finance team, should be driving the VMware migration conversation.

The Real Problem Isn’t Price—It’s the Blueprint

Broadcom’s VMware licensing changes have triggered a wave of budget panic. But here’s the uncomfortable truth:
Migrating off VMware has less to do with cost—and everything to do with architectural maturity.

Your Architecture Review Board—not your finance team—should be leading this decision.

What the 70% Migration Stat Actually Means

Based on industry conversations and a Nutanix-cited Gartner prediction, up to 70% of enterprise-scale VMware customers may consider migrating 50% of their workloads by 2028 due to cost pressure.

But “considering” is not “executing.”

In reality, actual migrations remain relatively low—not because organizations don’t care about pricing, but because platform transitions are architectural challenges, not procurement tasks.

The Price Shock Is Real—But It’s Only Half the Story

Yes, some customers are facing licensing increases of up to 8x. Those impacts are often felt by enterprises that previously licensed individual VMware components and are now being funneled into full-stack bundles like VMware Cloud Foundation (VCF).

Others—those already on VCF or long-term enterprise agreements—are seeing little change.

But across the board, most organizations are staying put.
Not because they’re satisfied.
Because migrating off VMware introduces more risk, complexity, and operational debt than it removes.

Operational Resilience Still Wins

Organizations that are leaving VMware weren’t jolted into the decision—they were already preparing for it.

For them, Broadcom’s changes simply accelerated what was already part of the roadmap: adopting container-native platforms, consolidating data centers, or reducing hypervisor reliance.

Everyone else is asking tougher questions:

• How do we preserve operational consistency?
• Will a migration disrupt platform resilience?
• Do we have the right team in place to support a transition?
• Will this derail parallel strategic initiatives—like AI or security modernization?

Replacing your virtualization layer isn’t a procurement decision.
It’s an organizational reckoning.

The Hidden Costs of “Cost Savings”

You may think that reducing your VMware core count will reduce your licensing bill.

But here’s what often happens:

• Renewal pricing doesn’t actually drop.
• Sales teams aren’t incentivized to offer concessions.
• And worst of all? You now need to invest resources in a massive migration.

Here’s what those hidden costs look like:

Common Hidden Costs:

• Rewriting infrastructure-as-code that’s tightly coupled to vSphere APIs
• Retooling backups, DR, and monitoring
• Refactoring networks and storage layers (e.g., replacing NSX constructs)
• Reskilling teams for platforms like Hyper-V, OpenShift, or managed Kubernetes
• Redirecting platform engineering resources from AI, security, or developer experience workstreams

These migrations aren’t 3-month projects.
They’re often 18–36 month journeys—with no shortcuts.

Read Our CTO’s Guide to Migrating from VMware

And the deeper truth?

These aren’t just financial costs.
They’re strategic tradeoffs.

If you’re seriously exploring a VMware migration, now is the time to engage your ARB.
Not to slow you down—but to pressure-test the assumptions that could break your strategy mid-flight.

The Architecture Review Board Isn’t Bureaucracy—It’s Velocity at Scale

So, if the price tag isn’t driving a stampede, what is?
The answer isn’t buried in a budget spreadsheet—it’s in your ability to govern complexity at scale.

And that’s where your Architecture Review Board becomes indispensable.

To some, the ARB looks like a bottleneck.
But in reality? It’s your engine for enterprise velocity.

Think of the ARB like the IEEE. No one likes waiting on a wireless standard. But once it’s in place, vendors and developers can move fast—confident they’re building on a shared, trusted foundation.

Internally, your ARB plays that same role—ensuring speed, scale, and interoperability.

What Happens When You Skip the ARB

I’ve seen organizations go all-in on a cloud-first model and bypass the ARB for the sake of speed.

It works—until it doesn’t.

Once the app is no longer a growth priority, and centralized IT takes over support, problems appear:

• No documentation
• No consistent architecture
• No shared tooling
• No support runway

The result?
A snowflake application.
Expensive. Unsupported. Unscalable.

What Good ARB Looks Like

A modern ARB doesn’t block.
It enables.

“Here’s how to say yes—and still align with enterprise architecture.”

You know your ARB is working when:

• Developers launch new projects with internal architecture templates
• Snowflake apps are the rare exception, not the rule
• Platform standards are embedded into automation, not added as red tape
• Teams build with interoperability as an assumption, not a hope

Shared architectural reality—that’s what enables speed at scale.

Planning a VMware Exit? Ask the ARB First.

If you’re mapping out a VMware migration, don’t start with landing zones.
Start with your Architecture Review Board.

Here’s what they should help you uncover:

• What dependencies are tightly coupled to VMware tooling?
• Are we ready—operationally and technically—to support a new platform?
• What’s the real timeline for migration?
• Will this shift pull resources from higher-priority efforts?
• How will hybrid coexistence with VMware and non-VMware environments be handled?

Your ARB isn’t a committee for checkboxes.
It’s your risk radar, strategy validator, and technical conscience.

Final Thoughts: Maturity Over Movement

Broadcom’s licensing changes are serious.
But that doesn’t mean every organization should panic-migrate.

If you weren’t already heading off VMware, now is the time to evaluate, not react.

A great ARB won’t delay your plans.
They’ll ensure your plan actually holds up—technically, operationally, and financially.

Because migrating for cost and forgetting architecture is like rewiring your house to save on your electric bill—and forgetting the foundation is cracked.

Call to Action:
If your organization is considering a move from VMware, involve your ARB now.
Not because they’ll slow you down.
But because they’ll make sure the platform you’re moving to will still support you three years from now.

⚙️ Need a Peer Gut Check? That’s What Keith on Call Is For.

Not every architecture decision needs a Zoom call.

Sometimes you just need a fast, focused gut check—from someone who’s done this before and won’t sugarcoat the feedback.

That’s Keith on Call.

Keith on Call is my async advisory service for enterprise IT leaders who want:

• A second set of eyes on a platform or migration plan

• No-sell, vendor-neutral technical perspective

• Clear, plainspoken feedback—on your timeline

🧠 Ask a question anytime. I’ll reply with a detailed, written response.
📬 Annual subscription. Async by default. Live sessions included in upper tiers.

👉 Subscribe to Keith on Call