This is an expected news (by me at least), and it is quite cool tbh. Veeam started a closed beta for integration another hypervisor platform – XCP-NG! The news came out from Vates.tech blog (Vates.tech is the XCP-NG creator/editor) by Olivier Lambert. Veeam after recently adding Proxmox hypervisor as supported platform, the next one on the list is XCP-NG that we have already tested in our lab and we liked it.
The fact that Veeam has decided to integrate another platform confirms VMware customers seeking cheaper alternatives and that they do not need all the software bundles from VMware. That's particularly correct for smaller clients/smaller enterprises.
If they already use Veeam and VMware, the switch to the XCP-NG platform will be easier as you would be able to restore your VMs to XCP-NG by using Veeam Backup and Replication. (the same way this is happenning for Proxmox platform atm).
Update: this closed beta should evolve rapidly into a public beta, according this forum thread. Stay Tuned -:).
The trend of erosion of VMware clients will most likely continue during several years as it is very difficult to quit VMware platform without having a solid ecosystem of replacement. Many admins would just go and rip and swap to another hypervisor straight away, but the implications for such a change are difficult. In fact, VMware’s robust ecosystem and your organization’s reliance on it create significant hurdles.
Here are the key reasons why making the switch is so challenging:
Deep Integration with Infrastructure – VMware often becomes the backbone of an organization’s IT environment. Over a decade, your workflows, automation scripts, and management tools—like vSphere, vCenter, or vRealize—have likely been fine-tuned to VMware’s architecture. Migrating to another hypervisor, such as Hyper-V or KVM, requires reconfiguring these integrations, which can disrupt operations and demand significant time and expertise.
Staff Expertise and Training – Your IT team has likely built deep VMware expertise over the years. From certifications to muscle memory with VMware’s tools, switching platforms means retraining staff on a new system. This not only incurs costs but also risks productivity dips during the learning curve, as teams adapt to unfamiliar interfaces and workflows.
Ecosystem Lock-In – VMware’s vast ecosystem of third-party tools, plugins, and integrations—think backup solutions, monitoring tools, or storage systems—creates a sticky environment. Many of these tools are optimized for VMware and may not play as nicely with other hypervisors, forcing you to replace or reconfigure them, adding complexity and cost.
Licensing and Financial Sunk Costs – A decade of investment in VMware licenses, support contracts, and hardware optimized for VMware’s platform represents a significant sunk cost. Transitioning to another hypervisor often means abandoning these investments or running parallel systems during a costly migration period, which many organizations find hard to justify. However, recent price hikes which what we heard are like x3 to x8 compared to previous pricing, might convince more than one!
Migration Risks and Downtime – Moving virtual machines, storage, and networking configurations to a new platform is no small task. Compatibility issues, data migration challenges, and potential downtime can introduce risks that make IT leaders hesitant. The fear of disrupting critical workloads often outweighs the perceived benefits of switching.
Vendor Relationships and Support – Long-term VMware users often have established relationships with VMware’s support teams and account managers. These relationships provide a sense of reliability and quick issue resolution. Switching to a new vendor means building those relationships from scratch, with no guarantee of the same level of support.
Final Words
Switching from VMware after a decade is like trying to rewrite a book you’ve spent years perfecting. The deep integration, expertise, and financial commitments create a web of dependencies that make migration daunting. While alternatives like Hyper-V, KVM, or Proxmox may offer cost savings or new features, the transition requires meticulous planning, resources, and a strong stomach for change. For many organizations, the path of least resistance is to stay with VMware, unless the benefits of switching are truly transformative. There are not only savings (even if this part is signifficative), but there are other aspects as well.
Source: Xeon Orchestra Blog
More posts from ESX Virtualization:
- 5 New VMware Certifications for VVF and VCF
- VMware Alternative – OpenNebula: Powering Edge Clouds and GPU-Based AI Workloads with Firecracker and KVM
- Proxmox 9 (BETA 1) is out – What’s new?
- Another VMware Alternative Called Harvester – How does it compare to VMware?
- VMware vSphere 9 Standard and Enterprise Plus – Not Anymore?
- VMware vSphere Foundation (VVF 9) and VMware Cloud Foundation (VCF 9) Has been Released
- Vulnerability in your VMs – VMware Tools Update
- VMware ESXi FREE is FREE again!
- No more FREE licenses of VMware vSphere for vExperts – What’s your options?
- VMware Workstation 17.6.2 Pro does not require any license anymore (FREE)
- Migration from VMware to another virtualization platform with Veeam Backup and Replication
- Patching ESXi Without Reboot – ESXi Live Patch – Yes, since ESXi 8.0 U3
- Update ESXi Host to the latest ESXi 8.0U3b without vCenter
- Upgrade your VMware VCSA to the latest VCSA 8 U3b – latest security patches and bug fixes
- VMware vSphere 8.0 U2 Released – ESXi 8.0 U2 and VCSA 8.0 U2 How to update
- What’s the purpose of those 17 virtual hard disks within VMware vCenter Server Appliance (VCSA) 8.0?
- VMware vSphere 8 Update 2 New Upgrade Process for vCenter Server details
- What’s New in VMware Virtual Hardware v21 and vSphere 8 Update 2?
- vSphere 8.0 Page
- ESXi 7.x to 8.x upgrade scenarios
- What is The Difference between VMware vSphere, ESXi and vCenter
- How to Configure VMware High Availability (HA) Cluster
Leave a Reply