Organizations reassessing VMware after changes to its licensing and packaging should look beyond the next bill or hypervisor replacement, argues Andre Wu, CEO of IT infrastructure and application hosting provider Summit. In a Nov. 16, 2026, industry-perspectives article, Wu says the central question for CIOs is which infrastructure strategy will preserve useful options over the next three to five years.
Wu frames the decision as a broader platform and operating-model choice. VMware was long considered a low-risk market leader, but after Broadcom’s acquisition, rising costs, licensing shifts and service issues have prompted some organizations to reconsider. A lower-priced alternative may appear attractive, he says, but its license cost alone does not reveal the total expense or risk of switching.
That assessment should include migration effort, existing management tools, staff skills, retraining, and the availability of vendor and partner expertise. Wu cautions that the cheapest hypervisor may not produce the cheapest operating model. A transition that requires extensive operational changes or creates new dependencies can offset apparent savings.
Test flexibility in practice
Wu distinguishes between technical portability and practical portability. Technical portability asks whether a workload can move. Practical portability asks whether the organization can move it without unacceptable cost, disruption, skills gaps or operational complexity. A platform may offer a theoretical exit while leaving a company poorly prepared to use it.
He recommends evaluating whether workloads can move among on-premises infrastructure, private cloud and public cloud; whether management, automation and reporting tools can move with them; and how dependent the organization is on one ecosystem. Leaders should also estimate the time and money required to change platforms and consider what a future pricing or licensing shift might mean.
Alternatives Wu identifies include Nutanix, Hyper-V, OpenShift, Kubernetes and Proxmox. He says the market has matured and that migration has become more feasible than it was five or six years ago, when leaving VMware could represent a major technical undertaking. The article does not claim that any one option is suitable for every organization; the choice depends on workloads, operational requirements and the skills available to run the environment.
Plan for changing workload needs
The range of infrastructure choices has expanded alongside changing enterprise requirements. Wu describes a progression from traditional infrastructure, often built around overprovisioning, to public cloud’s elastic consumption model and then to hybrid infrastructure, reflecting the fact that not every workload belongs in public cloud.
He points to AI workloads, data center capacity pressures, supply-chain constraints, infrastructure costs, workload repatriation, modern application stacks and containers as factors that complicate placement decisions. Some workloads may fit on-premises systems, others private or public cloud, and some may require bare metal. Workload requirements can also change over time.
For that reason, Wu recommends considering more than the immediate renewal or migration deadline. CIOs should ask whether they can relocate workloads as economics or requirements shift, whether their platform supports containers and AI, and whether their teams and partners can operate it effectively. They should also examine whether a decision opens future options or makes a later change harder.
These questions apply beyond VMware. Wu argues that any major provider, including a hyperscaler or strategic platform vendor, could make changes that affect customers. Optionality, in his view, is therefore a general infrastructure principle: understand the dependencies a platform creates and the practical cost of leaving before committing to it.
A deliberate choice, not a default
Wu does not argue that every VMware customer should migrate. For some organizations and workloads, staying may remain the sound choice after evaluating alternatives. But he says that retaining VMware simply because it has historically been the default is no longer a sufficient strategy. The same scrutiny should apply to replacement platforms.
Optionality does not mean operating dozens of environments or avoiding commitment. It means making deliberate choices about dependencies, workload placement and the effort required to change direction. The relevant planning horizon, Wu says, is three to five years—not only the current contract or migration cycle. His central point is that infrastructure decisions should preserve viable future choices, rather than solve an immediate cost problem at the expense of the organization’s ability to adapt.