For many organisations, VMware has long been a backbone of enterprise infrastructure. It’s mature, widely adopted and deeply embedded across core platforms.
While the foundation has not disappeared, the commercial model has changed, forcing leaders to reconsider its place in their organisation’s technology stack.
Following Broadcom’s acquisition, VMware moved towards subscription licensing and discontinued perpetual license sales. While some organisations reported sharp price increases, the impact has not been uniform. For many, the more complex challenge lies in reduced cost certainty and changing commercial structures, which make long-term planning more difficult. Where a critical platform becomes harder to forecast and harder to govern, the implications can extend beyond IT into financial planning, risk management and board oversight.
In regulated environments such as financial institutions, infrastructure decisions sit within board accountability for operational resilience and third-party risk. Leaders must determine whether the new commercial reality aligns with long-term financial, risk and operating objectives.
The strategic response is to favour structure over urgency. Here we explore how to quantify exposure, avoid a reactive exit and take a value-led path that improves cost control without compromising resilience.
From infrastructure cost to strategic exposure
VMware’s licensing shift changes how infrastructure appears in financial models. What was once a predictable capital investment, typically paired with support contracts, becomes a recurring operating expense with new assumptions, new bundling and new renewal dynamics.
For finance leaders, this introduces uncertainty into multi-year planning. For technology leaders, it compresses decision timelines and increases the cost of indecision. At the board level, it raises a more strategic concern: when a platform is both foundational and volatile, commercial dependency becomes a governance issue, not just a procurement one.
The risk of a reactive exit
For many leaders, when costs rise, the instinctive response is urgency. Organisations feel pressure to move away from VMware ahead of renewal windows to avoid being locked into significant price changes.
Speed may be necessary, but it does not guarantee value. Time-pressured lift-and-shift migrations often recreate existing environments elsewhere without reducing complexity, retiring technical debt or improving operating discipline. When the cloud is treated as a direct substitute for an on-premises data centre, run costs can climb quickly, particularly if estates move without rationalisation and consumption replaces licensing without strong controls.
Financial services organisations can end up choosing between paying more to remain or moving quickly but failing to improve cost efficiency and resilience elsewhere. Neither outcome is strategic in today's fast-moving technology landscape.
A value-led approach to VMware migration
The most effective response is to treat VMware cost pressure as a trigger for structured optionality and to take a phased approach that proves value early. That means building a clear view of exposure and constraints, then shaping a portfolio approach rather than a single all-or-nothing decision.
Start by establishing the facts: renewal dates, contractual constraints, how bundles map to the current estate and what operational commitments must be protected. From there, segment workloads by criticality and change suitability. Some will need to remain stable while options are developed. Others can move quickly to reduce near-term exposure. A third set may justify deeper platform changes because the value comes from improving scalability, efficiency or operating model maturity.
From there, leaders typically have three practical pathways:
- Optimise selected VMware workloads in place, while reducing commercial exposure elsewhere
- Move suitable workloads to public cloud or alternative virtualisation platforms where it makes economic and operational sense
- Use the moment to modernise applications so they rely less on the underlying virtualisation layer altogether
The point is not to create a perfect taxonomy but to offer decision clarity, so action is prioritised where it reduces risk and improves cost outcomes.
What this means for financial services leaders
In financial services, optimisation cannot come at the expense of stability. A well-governed roadmap should strengthen operational resilience and security posture alongside cost predictability. Done well, this reduces exposure to licensing volatility while also reducing concentration risk and creating space to modernise, including in areas like data, analytics and artificial intelligence.
VMware licensing change creates an inflection point, but it is not transformational on its own. Transformation comes from the response, and organisations that handle this with structure rather than urgency are more likely to reduce exposure, strengthen resilience and preserve long-term flexibility.
To achieve this, leaders should consider:
- Do we have a clear view of exposure and decision deadlines?
- Which parts of the estate must remain stable, and which can change quickly?
- What governance and resilience guardrails are non-negotiable?
- How will we measure success beyond ‘moving off VMware’?
If you are reassessing your VMware estate in light of cost exposure, resilience obligations and long-term cloud strategy, our experts can help you define a value-led path that reduces licensing pressure while strengthening governance, operational resilience and cost control.
Learn more in our latest e-book, in which our experts share where to start when considering an exit from VMware.