Leaving VMware: what Alliancy's 2026 guide says, and where Vates fits

Alliancy’s 2026 guide on VMware dependency gives IT leaders a framework to stay, reduce or exit, with real exit costs per VM. Vates is featured in the alternatives comparison, shares what it sees in migration projects, and two customers report on their move. The guide is in French.

Leaving VMware: what Alliancy's 2026 guide says, and where Vates fits

Alliancy, a French media outlet for CIOs and digital leaders, has published a strategic guide on technology dependency, with VMware as its main case study. Its message is simple: the question is no longer whether to act after Broadcom's takeover, but how much dependency you're willing to accept. Vates is featured in the guide with its own entry in the comparison of alternatives, its view on VMware exits, and two customer experience reports. The guide is in French and free to read.

The guide at a glance
Managing technology dependencies. Use case: virtualization & VMware (original French title: Maîtriser ses dépendances technologiques. Cas d'application : virtualisation & VMware), Alliancy, 2026 edition. Free, available in French only. Inside: a dependency scoring grid, a stay-or-exit decision matrix, exit costs per VM, and two "5-minute REX" reports from Vates customers.

Read the guide (French)

What is the Alliancy guide about?

The guide is called Managing technology dependencies. Use case: virtualization & VMware (our translation: it's published in French only). It gives IT leadership a framework to decide between three options: keep VMware, reduce its footprint, or leave it.

It's built around a short survey of decision-makers run by Alliancy in May 2026 (20 respondents, so read the percentages as signals rather than market data):

Finding (Alliancy survey, May 2026, n = 20)Share
Consider themselves dependent or highly dependent on their main IT vendors95%
Expect VMware-related cost increases above 20% within 24 months42%
Aim to diversify or exit within 3 years (open architectures, multi-cloud, European vendors)84%
Describe their contractual room for manoeuvre as very constrained1 in 3

The guide also sums up what changed after Broadcom closed the VMware acquisition in November 2023: the end of perpetual licences, forced bundles (VCF, VVF), per-core billing with a 16-core minimum per CPU, and fewer authorised partners. It reports price increases of 3x to 12x depending on the profile, and up to 1,000% for some customers.

Where does Vates appear in the guide?

In the comparison of alternatives, Vates gets a dedicated row next to commercial platforms (Nutanix AHV, Hyper-V), KVM-based open source (Proxmox VE, oVirt, OpenShift Virtualization), public and sovereign cloud, and containers. Alliancy lists Vates's strengths as a French vendor with a fully open source stack (XCP-ng for the hypervisor, Xen Orchestra for orchestration, XOSTOR for hyperconverged storage), pricing per physical host, a REST API with automation through Terraform, Pulumi and PowerShell, and local support.

The same table lists the limits: a smaller integrator ecosystem in France than for the incumbents, and a skills ramp-up to plan for. That's fair. It's the reason we built the Vates Alliance Network and keep signing integrators and technology partners, and it's the kind of point a decision-maker should check before signing with any vendor.

Introducing the Vates Alliance Network
Organizations moving to Vates VMS are not looking for products, they are building complete solutions. The Vates Alliance Network (VAN) ensures those solutions are tested, documented, and ready to deploy.

In a section titled "Vates's view on leaving VMware", the guide summarises what we've seen across migration projects since the acquisition (more on that below).

In the "5-minute REX" section, two organisations running Vates VMS share an unfiltered experience report, good and bad.

How do you assess your VMware dependency?

The guide's first step is a diagnosis, not a migration plan. It reads dependency along six dimensions: technology, commercial, contractual, data, legal and regulatory, and skills.

Applied to VMware, Alliancy separates three on-premises situations, because they don't carry the same exit cost:

VMware footprintWhat's deployedMigration difficulty according to the guide
VMs onlyESXi on standard storage and networkFeasible, with technical constraints to validate
VMs + hyperconvergenceESXi coupled with vSANHarder: often requires new storage hardware
Full-stack private cloudESXi, vSAN, NSX, Aria, self-service portalVery complex: automation to rewrite, virtual networking expertise to rebuild

A scoring grid (compute, storage, network, automation, third-party tools, skills, each from 1 to 5) then places the organisation in one of three profiles. Agile organisations can exit quickly. Constrained ones should negotiate hard, reduce gradually and add a second platform. Captive ones need a multi-year plan and should freeze VMware's expansion while they transform.

💡
Running vSAN today? Check the XOSTOR documentation and the storage ecosystem supported by Vates VMS before assuming you need new hardware.

Stay, reduce or exit: which strategy fits?

Alliancy doesn't push everyone out. Staying is a legitimate scenario, as long as its cost is calculated over three to five years on the same basis as the alternatives: direct costs, imposed hardware, the IT budget that won't fund anything else, and the growing difficulty of leaving later.

To put the "stay" scenario next to a Vates VMS scenario, use our VMware cost estimator. Vates VMS is billed per host, with no per-core minimum.

Check the calculator

For those who move, the guide describes three strategies, often combined:

  1. Reduction: shrink the VMware footprint (licences, scope, workloads) without leaving entirely.
  2. Hybridisation: run a second platform for new workloads and stop extending the existing one. It also strengthens your hand in negotiations.
  3. Full exit: migrate everything, best suited to Agile profiles or organisations ready for a multi-year programme.

One point in the guide deserves more attention than it usually gets. Large estates with hundreds or thousands of VMs can take 3 to 10 years to exit fully. But thousands of smaller infrastructures, from 3 to 20 machines, carry far fewer dependencies, and their migration often wraps up in a few months.

Why Biocoop chose open-source virtualization
Biocoop chose Vates VMS to regain control over virtualization costs, governance, and long-term infrastructure decisions through open-source technologies.

How much does leaving VMware cost?

The guide is clear that leaving VMware is never free, and it puts numbers on it:

Cost itemRange given in the guide
Migration of a standard VM with an automated V2V tool€50 to €500 per VM
Migration of a critical or complex workload€1,500 to €8,000 per machine
Refactoring (automation scripts, templates, backup, DR) on Captive profiles30% to 50% of the migration budget
Double run (both platforms in parallel) on a mid-sized projectOften 12 to 24 months

Those figures are what makes the "stay" scenario worth calculating honestly. Our V2V tool sits in the first line: it moves VMs from VMware to XCP-ng through Xen Orchestra, which keeps the per-VM cost on the low end when the workload is standard. The steps are in the migration documentation, and for larger estates our team offers a migration package.

Vates Migration Guide : VMware/Hyper‑V to VMS
Moving away from VMware or Hyper-V? Learn how to migrate to Vates VMS smoothly, cut costs, and regain control of your virtualization stack.

What does Vates see in VMware exit projects?

Most projects we've seen since the acquisition aren't deep application transformations. They're a modernisation of the virtualisation layer. They come from SMEs, local authorities, education, healthcare, industry, MSPs and public administrations, and they're driven by cost control, the search for an alternative licensing model, and the wish to stop depending on a single vendor.

The prerequisites are classic: a reliable inventory, a clear view of critical dependencies (backup, DR, network, storage), tested migration procedures, and trained teams. The hard part is usually organisational rather than technical. Duration ranges from a few days or weeks for small infrastructures to several months, sometimes years, for multi-site environments with hundreds of hosts.

We also see more hybrid strategies: bringing in Vates VMS for new workloads while VMware stays in place for a while. It lowers the risk and gives teams a side-by-side comparison. And when choosing a target, features shouldn't be the only filter. Governance, portability, the economic model, skills availability and ecosystem openness need to be on the list from day one. Otherwise you just recreate the same dependency somewhere else, which is the guide's own conclusion.

On-prem and open source: how Vates operates in 2026
Vates runs near 150 people. We are growing internationally, and we do it mostly on open-source, self-hosted tools. Here is what that actually looks like in practice, and why it matters.

What do Vates customers say in the guide?

💡
Alliancy's "5-minute REX" is a short, subjective report written by an organisation that deployed the solution. It's not a technical evaluation, and both customers took part anonymously.

A managed service provider (160+ employees, CSP and MSP activities) describes its experience as "performant, stable, secure." It ran the project directly with Vates, without an integrator, and rebuilt 12 years of existing infrastructure in 12 months. Good surprises: product maturity, how simple Xen Orchestra and XCP-ng are for administrators, support quality, and a well-documented API. Less good: unlearning some VMware habits, and a real configuration effort on operations (maintenance, updates, backup). Network and storage work was underestimated, which created a delay; the budget held. The financial impact is described as positive. What they'd do differently: hire a full-time XCP-ng expert from the start. They also want us to keep building partnerships such as EasyVirt and Veeam. Their closing words: "Long live an independent Vates."

Expanding the Vates ecosystem with Easyvirt
Easyvirt’s DC Scope and DC NetScope are now fully integrated into Vates VMS! Optimize resources, control costs, and track sustainability, all from your existing ecosystem. Try it free for 15 days or get a co-renewal quote today.

A public sector organisation (300 employees) sums up its experience as "complex, resilient, autonomous." It found the solution solid, with a new way of thinking to adopt and some administration difficulties at first. VM-to-VM switchover went smoothly; limiting downtime was the main constraint. No budget overrun, higher costs than before, and better support in return.

We're keeping both reports as they are, including the criticism. Feedback on administration and day-to-day operations feeds directly into Xen Orchestra 6, and the remark about an ecosystem that's still growing is one we share.

Read the guide

The full guide is free and written in French. It includes the scoring grid, the stay-or-exit decision matrix, a four-phase transformation method with durations, and a point of view from Elée on two years of VMware under Broadcom.

Download the guide

If you're already working through your own VMware diagnosis, start with our VMware alternative page, or start a Vates VMS trial on a few hosts and test a V2V migration on non-critical VMs first.

Vates VMS Quick‑Start: Install XCP‑ng, Deploy XO & First VM
New to Vates VMS? Get up and running quickly with this practical guide to deploying and managing your virtualization stack.