Negative sentiment on Broadcom accelerates VMware migrations

Negative perception of Broadcom is pushing many companies to reassess VMware. Here are the operational and strategic levers accelerating moves to alternatives.

Negative sentiment on Broadcom accelerates VMware migrations
IT manager analysing a migration strategy from VMware to a cloud alternative

The virtualisation market is going through a phase of realignment. Many organisations are reassessing their dependence on a long-standing platform, driven by higher costs, stricter commercial terms and a vendor relationship that is perceived as less collaborative.

In this scenario, competitors are trying to win over dissatisfied customers with proposals that promise greater flexibility, a more predictable economic model and a less binding migration path. The issue concerns not only technology, but also trust in the supplier and the ability to sustain operations over the medium term.

Why companies are reconsidering VMware

The first factor is economic: when a platform becomes more expensive to license and expand, every renewal becomes a strategic event. The second is contractual: the move to broader bundles, often oversized relative to actual needs, reduces freedom of choice. The third is organisational: discontinuity in relationships with partners and support channels increases perceived risk.

For decision makers, the problem is not only the final price but the sum of direct and indirect costs. These include the complexity of governance, the need to retrain teams and the impact on roadmap, compliance and infrastructure maintenance.

What makes a mass migration credible

Migrations do not happen only out of dissatisfaction; they occur when a sufficiently mature operational alternative exists. Competing platforms are focusing on architectures that simplify workload management, favour gradual adoption and reduce dependence on proprietary components.

A decisive aspect is the possibility of starting in stages. Larger organisations prefer to move a limited part of the load first, validate performance and security, then extend the change. This approach lowers risk and makes the investment easier to defend to management.

Implications for those leading IT

For those governing infrastructure and applications, the central point is distinguishing between emotional reaction and architectural rationality. Abandoning a platform solely under commercial pressure can create technical debt; staying too long can increase costs and dependence.

The right choice requires a joint reading of licences, workload portability, replatforming effort, compatibility with hybrid environments and the impact on operational continuity. In practice, migration should be treated as a transformation programme, not as a simple software replacement.

How to set up a sustainable exit strategy

An effective plan starts with mapping workloads: criticality, dependencies, latency requirements, downtime windows and regulatory constraints. Then a target model is needed that clarifies which workloads stay, which are moved and which can be modernised in parallel.

Change governance is also essential: executive sponsorship, transparent priority criteria, success metrics and a rollback plan. Without these elements, migration risks becoming a sequence of costly and hard-to-control exceptions.

Operational takeaways

  • Market sentiment can accelerate exits, but the decision must be grounded in real numbers and dependencies.
  • Costs, contractual constraints and the quality of the vendor relationship weigh as much as technical performance.
  • Alternatives win when they allow gradual, non-traumatic and measurable migrations.
  • Every exit strategy requires assessment, workload prioritisation and rigorous governance.
  • The competitive lever is not just replacing a platform, but reducing overall infrastructure risk.