VMware Customers Have More Options Than They Think

Over the past year, I’ve had a lot of conversations with VMware customers trying to figure out what comes next. It’s a challenge Gartner has described as “the new state of VMware,” reflecting the significant changes to licensing, pricing, products, and the partner ecosystem that have reshaped the virtualization landscape since Broadcom’s acquisition.

Some organizations are evaluating alternatives for the first time, while others have already started planning their migrations. Plenty of folks are simply trying to understand their options and determine whether the path they’ve been on for years is still the right one.

What strikes me most about these conversations isn’t the technology itself. It’s the sense of urgency that often accompanies them.

When licensing models change, costs increase, or uncertainty enters the equation, the natural reaction is to start looking for the fastest path forward to stay ahead of the chaos. Organizations want answers. They want clarity. They want to know which platform they should move to and how quickly they can get there.

That’s perfectly understandable.

At the same time, I think there’s a risk in treating the situation as a simple replacement exercise.

The most successful organizations I’ve worked with aren’t necessarily the ones that moved first. They’re the ones that took a step back, evaluated their priorities, and made decisions based on long-term business outcomes rather than immediate pressure.

The good news is that VMware customers today have more options than they’ve ever had before. The challenge isn’t finding alternatives. The challenge is determining which path forward is actually right for your business.

Before You Replace VMware, Understand What You’re Really Replacing

One of the first questions I ask when speaking with customers is surprisingly simple:

What are you actually trying to accomplish?

It’s a simple question for sure, but it’s one that often gets overlooked because the conversation begins with technology and not outcomes. Organizations start comparing hypervisors, reviewing feature sets, evaluating pricing models, and trying to determine which platform can replicate what they have today.

And those are important discussions, for sure, and they have a place in the process, but I don’t think they’re the most important place to start.

Before evaluating products, organizations should spend time understanding their objectives. Are they trying to reduce infrastructure costs (or at least insulate themselves from volatility)? Improve operational efficiency? Increase flexibility? Modernize aging environments? Strengthen disaster recovery capabilities? Address concerns about long-term vendor alignment?

The answer matters because different goals often lead to different solutions.

I’ve seen organizations with remarkably similar VMware environments arrive at completely different conclusions because the business challenges they were trying to solve were different.

In some cases, remaining on their VMware was still the right decision. In others, other private cloud solutions made sense. Some organizations found value in public cloud platforms, while others still adopted hybrid approaches that allowed them to place workloads where they made the most sense.

The technology was only part of the decision.

The business outcome was what ultimately guided the strategy.

There’s another reason I encourage organizations to take a broader view: VMware rarely exists in isolation.

Over the years, most organizations have built an ecosystem around it. Backup platforms, disaster recovery processes, vendor tooling, monitoring tools, security controls, automation workflows, operational procedures, and internal skill sets are often tied to the virtualization layer in ways that aren’t immediately obvious.

Replacing VMware is more than just choosing a new platform: It’s about understanding how that decision impacts the larger environment.

How will backups work?

What changes are required for disaster recovery?

How will monitoring and security tools be affected?

What operational processes need to be updated?

How much retraining will be necessary?

These questions often have a greater impact on the success of a migration than the choice of hypervisor.

I generally advise organizations to focus less on finding a replacement product and more on understanding the broader operational picture and letting that guide them to features, that have advantages that will be beneficial to them and aid them in achieving their goals.

Why Many Organizations Are Re-Evaluating Workload Placement

One of the more interesting outcomes of the VMware conversation is that it’s forcing organizations to revisit infrastructure decisions they may not have questioned in years.

When technology is working, there’s rarely a reason to stop and reconsider where workloads live. Systems remain in place because they continue to support the business. Over time, those decisions become part of the environment’s foundation.

Today, many organizations are taking a fresh look at those assumptions.

As they evaluate their options, they’re asking questions that extend well beyond virtualization:

Does this application still belong where it is today?

Would this workload benefit from a different operating model?

Are there opportunities to improve cost predictability?

Could operational complexity be reduced?

Would a different platform provide better alignment with business goals?

I think these are healthy conversations to have, and don’t need to bog down decision making.

One of the themes I see repeatedly is a shift away from platform-first thinking and toward workload-first thinking. Rather than trying to standardize every application on a single infrastructure model, organizations are becoming more deliberate about workload placement.

Some workloads may benefit from the flexibility of a public cloud platform.

Others may require the predictable performance and cost structure of a private cloud environment.

Some may remain on-premises.

Many organizations ultimately land somewhere in between.

The point isn’t that one approach is universally better than another. The point is that organizations are becoming more intentional about matching workloads to the environments that best support them and partnering with providers who can cover that broad approach with a comprehensive set of services and platforms.

In many cases, the VMware conversation becomes less about virtualization and more about infrastructure strategy as a whole.

And I find that’s often where the most valuable insights emerge.

The Best VMware Strategy May Not Be the Fastest One

When uncertainty enters the market, there’s a tendency to rush toward an answer.

And it makes sense, I think that pressure raises an ostensibly reasonable reaction:

Leadership teams want direction. IT teams want a plan. Budgets need to be built. Roadmaps need to be established.

But major infrastructure decisions tend to stay with organizations for years. The impact extends beyond technology and affects operations, staffing, budgeting, resiliency, and long-term flexibility. The ship of enterprise IT turns slowly!

That’s why I believe the best VMware strategy is rarely the fastest one.

The best strategy is usually the one that begins with understanding business priorities, evaluating dependencies, assessing workloads, and identifying the outcomes the organization is trying to achieve.

It’s only when we start to get a clearer picture of our broader circumstances that it makes sense to evaluate platforms.

Fortunately, organizations evaluating VMware today have more viable options than ever before. Public cloud platforms, private cloud environments, managed infrastructure services, alternative virtualization technologies, and hybrid approaches all offer potential paths forward.

The challenge isn’t finding a solution, it’s finding the solution that aligns with your organization’s goals.

And that takes time, thoughtful evaluation, and a willingness to look beyond the immediate technology decision. Slow is smooth, smooth is fast.

In my experience, organizations that approach the process with this in mind tend to make better decisions—not just for the next year, but for the next five years.

Exploring Your Options

If your organization is evaluating alternatives to VMware, start by looking beyond the virtualization platform itself. Consider the applications, operational processes, recovery requirements, support expectations, and business objectives that make your environment unique. Link up with application owners and heads of potentially impacted business units to find out what’s working, and what’s not working.

The right answer isn’t necessarily the newest platform or the quickest migration path. It’s the solution that best supports your long-term goals.

US Signal helps organizations assess infrastructure options, evaluate workload placement strategies, and build a roadmap that balances performance, cost predictability, resiliency, and operational simplicity. Connect with our team to explore the options available to your environment.