Der innere Inhalt wird nur auf Englisch bereitgestellt. Navigation und Beschriftungen wurden zu Ihrer Bequemlichkeit übersetzt.

Kontaktieren Sie uns

Free white paper · Enterprise estates

Replace VMware
across your organization

A practical guide to migration, services and subscriptions for organizations that must re-justify VMware at every renewal.

How Vates VMS can replace VMware in your organization

Replacing VMware with Vates VMS

vSphere 7 has been out of support since October 2025 and vSphere 8 follows in October 2027. If you must renegotiate, re-version and re-budget anyway, the cost of seriously evaluating an alternative has never been lower.

What you'll learn:

  • How your VMware concepts map to Vates VMS, one to one
  • The migration method: audit, pilot, waves, rollback at every step
  • Storage strategy: keep your SAN, converge with XOSTOR, or mix
  • Backup, DR, security, compliance and sovereignty
  • How to build a 5-year cost model on your own estate
  • Honest limits, and how to de-risk each one in the pilot
Download the white paper (PDF)

PDF · 31 pages · 2.2 MB · no registration

Benachrichtigung bei Aktualisierung dieses Leitfadens erhalten

Mit dem Absenden dieses Formulars erklären Sie sich damit einverstanden, dass Vates Ihre E-Mail-Adresse in seinem Marketing-Automation-Tool speichert, um Sie zu benachrichtigen, wenn die von Ihnen auf vates.tech heruntergeladenen Leitfäden aktualisiert werden. Dazu erfasst Vates, welche Leitfäden Sie herunterladen. Sie können sich jederzeit über den Link in jeder E-Mail oder in Ihrem Präferenzcenter abmelden. Ihre personenbezogenen Daten werden gemäß der Datenschutzerklärung von Vates verarbeitet.

What's inside the white paper

"How Vates VMS can replace VMware in your organization" (Vates, October 2026) is a practical guide for IT leaders and infrastructure teams who must decide what to do at their next VMware renewal. The white paper covers the platform architecture, the VMware-to-Vates VMS concept mapping, the migration method, storage and backup options, security and sovereignty, the subscription model with a cost method, the known limits of Vates VMS, and a printable evaluation checklist.

Why VMware is back on the table

Since Broadcom completed its acquisition of VMware in late 2023, perpetual licenses have ended, the catalog has been collapsed into a few bundles built around VCF and VVF, and pricing has moved to a per-core model with a 16-core minimum per CPU. The white paper lists the public milestones: a 72-core minimum order announced and then withdrawn in spring 2025, a 20% late-renewal penalty, vSphere 9 sold only inside VVF and VCF, and VVF withdrawn from sale in several European countries in late 2025.

According to the white paper, first subscription quotes after the acquisition commonly landed between 2 and 5 times the previous cost. vSphere 7 reached end of general support in October 2025, and vSphere 8 follows in October 2027, which gives every vSphere 8 customer a hard deadline to either accept the new terms or run an alternative in production.

Vates VMS at a glance

Vates VMS (Virtualization Management Stack) is a 100% open source virtualization platform developed and supported by Vates, a French software vendor founded in 2012. The engineers who write the hypervisor, the management layer and the storage stack also staff Vates support. The stack has three core parts:

  • XCP-ng , a type-1 bare-metal hypervisor built on the Xen Project (hosted by the Linux Foundation). The 8.3 branch is an LTS release with monthly security updates, and it installs and updates in air-gapped environments.
  • Xen Orchestra , an agentless web-based control plane for VM lifecycle, backup, disaster recovery, monitoring, RBAC and audit, driven through the documented XAPI.
  • XO Lite , a management interface embedded in every XCP-ng host.

An XCP-ng resource pool spans up to 64 hosts, and larger estates run as multiple pools under one Xen Orchestra. Since QCOW2 reached general availability in XCP-ng 8.3 (2026), virtual disks scale to 16 TiB instead of the former 2 TiB VHD limit. Vates has been listed in the Gartner Market Guide for Server Virtualization since 2022, and its Windows PV drivers have been signed by Microsoft since 2025.

Translating VMware concepts

The white paper maps VMware components to Vates VMS almost one to one, so a VMware team keeps its mental model:

  • ESXi becomes XCP-ng; vCenter Server becomes Xen Orchestra; the vSphere Host Client becomes XO Lite.
  • VMware Tools become XCP-ng guest tools, with Microsoft-signed Windows PV drivers.
  • vMotion and Storage vMotion become live migration of VMs and storage; HA and DRS become XCP-ng HA plus XO load balancing.
  • vSAN becomes XOSTOR; SRM and replication become continuous replication and DR plans in Xen Orchestra.
  • Aria Operations becomes DC Scope; Aria Operations for Networks becomes DC NetScope.
  • Tanzu becomes Vates Kubernetes Service; PowerCLI becomes a PowerShell module, the REST API, Terraform and Pulumi.

Two differences favor Vates VMS: Xen Orchestra replaces both vCenter and a separate backup product, and XCP-ng is the same software for every customer, with no feature gated behind a higher edition.

The migration method

Xen Orchestra includes a V2V migration wizard that connects to vSphere, imports VMs, converts their disks and reconfigures them as XCP-ng guests, including VMs on vSAN datastores. On NFS and most VMFS 5 datastores, the wizard uses warm migration, so downtime is limited to the final transfer of changed blocks. On VMFS 6 and vSAN, the VM must be powered off during import. Vates VMS migrations follow four phases:

  • Audit: inventory VMs, dependencies, storage, network and backup obligations, with DC Scope profiling the VMware estate.
  • Pilot: migrate a small, non-critical perimeter and validate performance, backups and runbooks.
  • Migration waves: move VMs in coherent batches while both platforms coexist, with no big-bang cutover.
  • Validation and decommissioning: compliance checks, backup chain handover, shutdown of the source.

The source environment stays intact until each wave is validated, which keeps a rollback path open. Perimeters of a few dozen VMs commonly complete in weeks, and multi-site estates in a few months.

Storage, backup and disaster recovery

Vates VMS supports two storage strategies. Existing SAN or NAS arrays (NFS, iSCSI, Fibre Channel, SMB) plug into XCP-ng as storage repositories. Alternatively, XOSTOR pools the local disks of 3 to 7 XCP-ng hosts into a replicated virtual SAN built on DRBD (co-developed with LINBIT), with a replication factor of 1 to 3 and automatic failover. Mixed designs are common.

Xen Orchestra backup includes incremental backups with changed block tracking, continuous replication, testable DR plans, file-level restore, S3-compatible targets and automated restore health checks. XO Proxy runs backup jobs locally at each site while only metadata crosses the WAN. Veeam Data Platform 13 also lists XCP-ng as a supported hypervisor, with official plugin support announced for 2026.

Security, sovereignty and operations

Vates VMS provides vTPM 2.0 and UEFI Secure Boot for guests, TLS 1.3+ on management traffic, CVE-tracked monthly patching, SSO through LDAP, OpenID Connect and SAML, granular RBAC and a full audit trail. The platform runs on your hardware with no telemetry requirement and no activation server. Automation covers Terraform, Pulumi, Ansible, Packer, PowerShell, the REST API, Cloud-init and a Go SDK. DC Scope and DC NetScope (by EasyVirt) add capacity forecasting, rightsizing, energy and carbon monitoring, and network flow mapping.

The same visibility pays off before any hardware purchase. DC Scope gives a single view across mixed VMware and XCP-ng estates, so oversized VMs and idle resources show up before you add servers; CDC Habitat cut its CPU and RAM consumption by about 10% through rightsizing. With RAM prices up more than 400% in a year, older hosts are also worth keeping: XCP-ng runs on hardware beyond its compatibility list, with Vates support. Read: before buying new hardware, make sure you're using the hardware you already own .

The subscription model and a worked cost example

Vates VMS is priced per physical host, regardless of cores, sockets or VMs. Plans differ by support level (up to 24/7 Enterprise support with a one-hour severity-1 response), not by features. Because the stack is open source, VMs keep running and remain manageable if a Vates subscription expires.

The white paper's worked example takes 20 hosts with 2 CPUs of 24 cores each: 960 billable VMware cores versus 20 Vates VMS hosts. At the lowest public reseller list prices for VMware VVF, without negotiated discounts, three years cost €555,120 ($633,312) for VMware versus €54,000 ($54,000) for Vates VMS Pro, a difference of €501,120 ($579,312). The ratio is about 10.3x on this estate and about 6.9x on 5 hosts with 16-core CPUs. The white paper also gives a three-step method to model your own estate over five years.

Honest limits and next steps

The white paper names the gaps of Vates VMS and how to de-risk each one in the pilot: a less dense third-party ecosystem than VMware, Veeam plugin feature coverage to verify, disks above 2 TiB not yet supported on XOSTOR and SMB repositories, network virtualization narrower than NSX's advanced constructs, and a few weeks of team adaptation. It closes with four decision questions (coverage, migration risk, economics, strategic position), three first steps (a lab, an audit, a scoping call with Vates) and a three-phase evaluation checklist.

Download the white paper (PDF)

A managed process, not a leap of faith

Vates has run this process across hundreds of VMware exits.

Migration in waves

Migration in waves

Rollback always available
Audit, pilot, then coherent batches per application, department or site. Both platforms coexist throughout, and the source stays intact until each wave is validated. V2V is built into Xen Orchestra, vSAN included.

Priced per host

Priced per host

Support tiers, not feature tiers
No core count, no socket count, no VM count. Denser CPUs never raise your bill. On 20 hosts with 24-core CPUs, the three-year gap with VMware VVF reaches roughly €501,120 at public reseller list prices.

Compare with VMware

Sovereign and reversible

Sovereign and reversible

Open source, European vendor
Your hardware, your datacenter, no activation server that must phone home. Standard disk formats and open APIs make reversibility structural, and an expired subscription never stops your VMs.

One vendor, hypervisor to control plane

XCP-ng replaces ESXi, Xen Orchestra replaces vCenter and your backup product at once, XOSTOR replaces vSAN, and DC Scope covers capacity planning like Aria Operations. Support is staffed by the engineers who write the code, up to 24/7 with a one-hour response on critical incidents.

Recognized and production-proven

Listed in the Gartner Market Guide for Server Virtualization since 2022, and running in production at KDDI France, Biocoop, Exodata, the Festival de Cannes and many more.

Read our user stories

Want Vates in the room?

Migration packages cover risk assessment, V2V tooling, rollback planning and go-live support, handled end to end by Vates engineers. Training and a Technical Account Manager are available too.

Talk to our team

Migrating from VMware with fewer than 10 hosts

Fewer than 10 hosts?

If your IT team is one or two people running 3 to 10 hosts, our field guide is written for your scale: a two-day audit, a lab on spare hardware, and a realistic three-week calendar.

Get the small IT team field guide

Don't take our words for it - read what our users have to say