Key Takeaways
- With vSphere 8 support ending in October 2027, most VMware customers have less time to decide than their contract dates suggest.
- The hardest part isn’t choosing a destination. It’s the migration skills, dependencies, and sunk costs involved in getting there.
- Optimizing first, placing workloads one by one, and separating the licensing decision from the hardware timeline turn a forced decision into a planned one.
What IT leaders actually say is more specific. “Our VMware renewal came in, and we have to deal with it.” “We can’t get the hardware to expand.” “The timeline doesn’t work.”
That was the starting point for our recent webinar, It’s Time to Decide the Future of Your VMware Investment, with Expedient Chief Commercial Officer Alan Skipper and President and Chief Operating Officer John Rosenson. The conversation kept coming back to one idea: for most organizations, the hard part isn’t picking a platform. It’s the clock.
The Clock Is Closer Than It Looks
vSphere 7 support ended in October 2025. vSphere 8 support ends in October 2027, which makes it the last version before VCF to reach end of support.
A year sounds like a lot of runway. Count backward, and it isn’t. Even organizations whose renewals don’t come up until 2028 or 2029 will hit the support cliff inside that contract term.
“We had a long runway a year ago,” Alan said. “Now we’re down to just over a year before there’s a cliff approaching.”
Meanwhile, hardware prices are rising, lead times are stretching, and fewer providers and licensing options are available. Many organizations planned to ride it out in their current environment. They’re discovering that riding it out isn’t a passive choice. The hardware they own has a compatibility ceiling, and replacing it takes longer than it used to.
Why the Decision Feels So Hard
Many IT leaders are on their second or third exit plan. They had a strategy a couple of years ago, revised it last year, and are revising it again because so much around VMware has changed. As John put it, those earlier decisions were probably right at the time. Time has passed, and there’s likely a new decision to make.
What makes that decision hard is rarely the destination. It’s how you get there.
- There’s no perfect option. Every path has real cost, risk, and tradeoffs, often with incomplete information.
- Skills are thin. Stable VMware environments don’t need much upkeep, so many teams haven’t needed deep expertise until now.
- Dependencies run deep. Years of data protection, monitoring, and automation tooling rely on the current stack.
- Sunk cost is real. Years of investment are hard to walk away from, financially and emotionally.
That last point matters more than it gets credit for. When the fear of making the wrong call takes over, the default becomes making no call at all.
You Don’t Have to Make One Decision
Many organizations frame this as a single destination: move everything to VCF 9, to hyperscale, or to an alternate hypervisor by a fixed date. Then they worry about getting 85% to 90% of the way there and finding the last 15% stuck.
Cloud rebalancing changes the question. Instead of one decision for the whole estate, you decide workload by workload, based on cost, compliance, performance, and fit.
Sometimes that means staying put. “I’ve told many, many clients to stay on VMware,” John said. For others, splitting the estate is the right call. And some workloads belong in hyperscale. Alan offered the example of a school district that needs 2,000 hosts during enrollment twice a year and two hosts the rest of the time. That’s a workload built for elasticity.
“Often our recommendations aren’t Expedient solutions,” Alan said. The goal is the right workload in the right place.
Optimize Before You Move
The first step isn’t migrating. It’s finding out whether you’re already in a better position than you think.
Many on-premises environments were sized during the era of enterprise license agreements (ELAs), when core counts and host usage didn’t matter much. A close look at licensing, core counts, and host usage often shows the problem is smaller than expected. And if you do move, you move from a good state to a better one, not from a bad state while trying to fix everything in flight.
In most assessments, a familiar pattern shows up:
- Core workloads are fine where they are once they’re right-sized and properly licensed.
- A smaller set clearly fits better somewhere else.
- A tail of workloads, nine times out of 10, should be retired, not migrated.
Retiring that tail usually produces savings that help fund the rest of the change. It’s like moving to a new house. You don’t pack the garbage.
The Cost Hiding Inside VCF 9
VMware Cloud Foundation brings the full VMware stack together as a private cloud, and VCF 9 adds a dedicated management domain that runs core services in one package. John described the shift from vSphere to VCF as “not really a migration event as much as it is a transformation event,” one that positions organizations for AI, containers, and Kubernetes down the road.
But that management domain requires three hosts. Many organizations run only three hosts in total, which means staying supported could double their hardware at a time when hardware has never been more expensive. Running the domain also requires skills most mid-market teams haven’t needed before.
On Expedient’s platform, the management domain cost is absorbed. It’s the same model Expedient Enterprise Cloud has run for years, with NSX, vCenter, and the rest of the stack managed as part of the service.
Waiting Is a Decision Too
“Waiting sounds prudent,” John said, “but it can often be the most expensive plan.”
Hardware isn’t getting cheaper anytime soon. RAM and storage costs have surged, and every quarter of delay adds to what we call the wait tax. Meanwhile, the subscription meter keeps running.
There’s a timing problem too. The software clock and the hardware clock rarely line up. For many environments, the vSphere 8 support cliff arrives before the hardware is fully depreciated. Waiting doesn’t preserve your options. It shrinks them.
Take the Clock Off the Table
Clients kept telling us they knew they had to decide, but their renewal was forcing them to decide faster than they were ready. A rushed decision is often how they got here in the first place.
The Expedient Bridge Program separates the licensing decision from the destination decision. Clients get one contact, one plan, and one destination for their VMware workloads. In the short term, workloads don’t have to move and hardware stays in place, including for organizations running VMware on their own premises. The licensing and compliance burden moves to Expedient while you plan.
“The pressure they thought was a platform problem was really a deadline problem,” John said. “They just needed more time to think it through.”
That time isn’t time to do nothing. It’s time to make the right financial, infrastructure, and partner decisions. And as our webinar host pointed out, a bridge has a destination. Otherwise, it’s a pier.
Why Expedient
Expedient is one of only 14 Broadcom-authorized VCSPs in the United States, holds Pinnacle status, and has been in the VMware partner program since 2007. We’ve completed hundreds of migrations, and we already run VCF today.
Assessment, discovery, migration planning, and execution are all part of the service. “We’re not consultants,” John said. “We’re your service provider that does it for you.”
Every solution is backed by a 100% SLA with monetary penalties if we miss it, and 99% of clients renew with us at the end of their contracts.
Do You Know What You’re Running?
“Your first move is not choosing the platform,” John said. “Your first move is getting honest about what you’re running and what you need.”
Start with every workload, the real numbers, and your actual timeline. A free VMware Health Check gives you an impartial view of where you’re compliant, where you’re exposed, and what’s coming, so there are no surprises.
FAQs
Is there an on-premises path, or does every option mean moving to the cloud?
There’s an on-premises path. The Expedient Bridge Program was built for organizations running VMware on their own hardware. Workloads and hardware stay where they are in the short term, while the licensing and compliance burden moves to Expedient. You don’t have to make the licensing decision and the destination decision at the same time.
We plan to run our current hardware until it ages out. Does that still make sense?
It might, but check the dates first. For many environments, the vSphere 8 support cliff arrives before the hardware is fully depreciated, and replacement hardware isn’t getting cheaper. Separate the short-term licensing question from the hardware timeline, but know what you’ll do after that and what it will cost.
What actually changes with VMware Cloud Foundation (VCF) 9?
VCF 9 bundles the full VMware stack into a private cloud platform and adds a dedicated management domain that runs core services. It’s less a migration event than a transformation event. The management domain requires three hosts of its own, which can double the hardware footprint for smaller environments. On Expedient’s platform, that cost is absorbed.
We’re already an Expedient VMware customer. What do we need to do?
Very little. Expedient already runs VCF, so moving you is an evolution, not a heavy lift. Renewal timing, upgrades, and the management domain are Expedient’s job, and hardware planning becomes an early conversation, not a fire drill.
