Most managed service providers didn’t see it coming, not because they weren’t paying attention, but because the nature of the risk had been hiding in plain sight. VMware’s pricing overhaul wasn’t just a contract renegotiation. It was a structural revelation: what the industry had long treated as enterprise-standard infrastructure was, in reality, a dependency with a renewal date attached.
MSPs built service portfolios on that foundation. Customers trusted it. Margins were modeled around it. And then, almost overnight, the terms changed. MSPs never owned the platforms they offered; they just thought they did.
The real lesson here isn’t about VMware specifically. It’s about the nature of the relationship every MSP has with the platforms they deliver. The question the market is asking, “what replaces VMware?”, is misplaced. The right question is harder and more important:
Do you want to own your platform, or do you want to rent it from someone else… again?
The Easy Answer — And Why It’s Wrong
When market disruption hits, the instinct is to minimize friction. Find the closest equivalent, execute the fastest migration, and move on. That instinct is understandable. It is also how organizations end up in the same position five years from now.
The responses taking shape across the MSP community are predictable: find the nearest replacement, negotiate the least disruptive path forward, and get back to operations as quickly as possible. These are reasonable short-term reactions. They are not strategies.
Like-for-like thinking produces like-for-like outcomes. If the problem was structural dependency, a faster path to a new dependency doesn’t solve it — it reschedules it.
The Illusion of Choice: Still Renting, Just Somewhere New
Nutanix: A Familiar Structure with Familiar Constraints
Nutanix has earned its reputation as a credible enterprise platform, and for many organizations it represents a genuine improvement over what came before. But the architectural model , tightly coupled compute and storage, means that scaling your footprint means scaling your costs in lockstep. The economics are predictable, and predictable is not always the same as favorable.
More importantly, it remains a single-vendor ecosystem. The dependency doesn’t disappear. It just wears a different logo. The leverage your vendor holds over your roadmap and pricing doesn’t go away; it just wears a different logo.
Hyperscalers: Convenient Entry, Costly Exit
The appeal of hyperscaler migration is real. The onboarding friction is low, the tooling is mature, and the sales cycle is fast. For MSPs under pressure to demonstrate forward motion, it can feel like the decisive choice. But the economics shift over time in ways that are difficult to reverse.
Consumption pricing becomes harder to forecast as utilization grows. Egress costs, integrated services, and the gravitational pull of proprietary tooling create structural lock-in that accumulates gradually until unwinding it becomes a project in its own right. Hyperscalers give you convenience upfront and constraint over time. You still don’t own your stack.
Hyperscalers give you convenience upfront and then constraint over time.
Authorized VCSP Resale: A Bridge, Not a Destination
For some MSPs, the authorized VCSP model has been positioned as a transitional path. But the structural restrictions tell a different story: no new direct customer contracts, no renewals under your own VCSP status, no white-labeling, limited ability to layer differentiated services on top. These aren’t minor inconveniences — they are the business model constraints that define what kind of MSP you can be.
A bridge is only useful if it leads somewhere. A transitional solution without a clear destination is just a slower version of the same problem. These aren’t exits, they’re lateral moves. You’re just writing a check to a new landlord.
What “Owning” Your Platform Actually Means
Ownership, in this context, is not a nostalgic argument for building everything in-house. It is not a case for complexity or a rejection of managed tooling. The distinction matters, because the reflexive objection — “we don’t want to manage all of that ourselves” — is based on a false premise.
Ownership means control and optionality. It means:
- You determine where and how workloads run, without being forced into bundled architectural decisions.
- You integrate with the infrastructure you’ve already built and paid for.
- You can evolve your platform without renegotiating your future every renewal cycle.
- Your roadmap is yours, not a function of what a vendor decides to bundle, deprecate, or reprice.
That is a fundamentally different operating position. It is also an increasingly achievable one.
Why This Matters Now
The VMware episode made pricing risk and vendor control concrete in a way that abstract strategy conversations rarely do. MSPs who had built their margins around stable, predictable licensing costs were suddenly facing structural compression with little runway to respond.
This is not a cost discussion anymore. The numbers matter, but the underlying issue is one of control and risk. Organizations that evaluate their next platform solely on current pricing are solving the wrong equation. The more durable question is: what happens to your business if this new vendor changes the terms in three years?
If the honest answer is “we’d have to move again” the current choice isn’t solving the problem. It’s kicking the can down the road, hoping the unthinkable doesn’t happen twice.
What Good Ownership Looks Like in Practice
The transition away from VMware dependency doesn’t require dismantling existing operations. The organizations navigating this well are doing so by preserving operational continuity for their teams while deliberately expanding the ground they stand on.
In practical terms, this means:
- Your migration timeline is yours — run both environments in parallel and decommission VMware when your team is confident, not when a deadline forces your hand.
- Your hardware stays. Your storage stays. The platform runs on what you already own, not on what a new vendor requires you to buy.
- Multi-tenancy and automation are built in from day one, not layered on after you’ve outgrown the initial deployment.
- Your workloads stay portable. If the landscape shifts again, you move — without re-architecting, re-licensing, or starting over.
The goal is not a perfect platform on day one. The goal is a platform that gets more valuable as you build on it and doesn’t hold you hostage when the market moves. Good ownership means you modernize on your schedule – not because a vendor forced your hand.
A Simple Test: Are You Owning or Renting?
Before committing to any path forward, it’s worth asking a few direct questions about the proposed solution:
- Can your vendor change pricing in a way that forces your hand?
- Are you locked into a specific hardware or cloud architecture by the platform’s design?
- Would moving your workloads require re-architecting, re-licensing, or renegotiating?
- Are you accumulating new forms of dependency?
If the answers to most of these is “yes” then you aren’t in control; you’re still renting. The logo on the invoice has changed, but the relationship hasn’t. Owning isn’t about having the deed. It’s about having the flexibility to scale without asking permission and modernize without paying a premium for the privilege.
Don’t Solve the Wrong Problem
The pressure to exit VMware quickly is real. Customers are asking questions. Finance teams are doing the math. The instinct to demonstrate decisive action is understandable, and in many cases entirely appropriate. But speed without strategy has a cost that rarely shows up in the original business case.
The organizations that will be in the strongest position in five years are the ones that treated this moment as an invitation to reconsider the underlying relationship, not just the vendor name on the contract.
Exiting VMware is not the point. Exiting the pattern of building your business on infrastructure you don’t control, that’s the goal. This is your chance to stop renting your infrastructure. Don’t trade one dependency for another. Learn how Platform9 can help you exit VMware and provide the base for a modern, scalable virtualization stack that you control.
