How Virtual Computing migrated 550 VMs to Vates VMS

For many IT teams, VMware licensing changes have triggered more than a pricing discussion. They have led to a broader reassessment of infrastructure strategy, including questions around cost, control, and long-term flexibility.

This was the case for Virtual Computing, where Mohammad Moghtader, CTO and Co-Owner, began evaluating alternatives. The goal was not simply to replace VMware, but to adopt a platform that could deliver strong performance, remain cost-effective, fit existing hardware, and support a more open approach.

When licensing changes become the turning point

The initial reason for considering a move was simple enough: VMware’s licensing changes. But like many infrastructure decisions, the real story went deeper than that.

For Virtual Computing, cost was clearly part of the picture, but so was vendor direction. The team wanted more control over its future and a platform that felt sustainable in the long run.

From there, the discussion quickly moved beyond cost. The team saw an opportunity to reduce dependency on a single vendor and regain control over their infrastructure, while building on something more sustainable over time.

Finding the right balance

Virtual Computing did not jump to a conclusion. The team evaluated several alternatives, including Proxmox, Hyper-V, and Nutanix. What mattered was finding the right balance between technical capabilities and strategic fit.

Performance and stability were essential. So were support, compatibility with current hardware, and overall cost. But another factor also carried weight: working with a company based in Europe.

That is where Vates VMS stood out. The combination of a European vendor and a practical migration path away from VMware made the choice clearer. In particular, the built-in VMware migration capabilities available through Xen Orchestra gave the team confidence that this would not become an unnecessarily painful project.

For organizations starting the same journey, this broader transition logic is also covered in our article on migrating from VMware or Hyper-V to Vates VMS.

Read the guide

A migration planned to stay under control

The project involved migrating around 20 hosts and 550 virtual machines, which required careful planning. Instead of a one-time cutover, the team adopted an incremental approach over several months.

New hosts were deployed with XCP-ng and Xen Orchestra appliance, and virtual machines were migrated in small batches each day. Once a VMware host was emptied, it was reinstalled with XCP-ng and reintegrated into the new environment.

An important aspect of this approach is that both platforms can run in parallel during the transition. This removes the pressure of a fixed migration deadline and allows teams to move at their own pace, validating each step as they go.

This iterative method reduced risk and ensured that operations remained stable throughout the transition!

Dealing with technical edge cases

Some adjustments were needed along the way. Legacy VMware drivers had to be removed for certain virtual machines, and a few required changes such as switching from BIOS to UEFI.

These issues were handled upstream, directly on the VMware side before migration, which helped keep the process efficient and predictable.

The XCP-ng documentation also supported the team during these steps.

Immediate impact

Once the migration was complete, the benefits were visible quickly.

Lower costs were one of the first outcomes, but what matters is what those savings enabled. In this case, reduced costs helped create room for additional infrastructure investment.

The team also reported faster support, better performance, and greater flexibility after the move. That combination is what makes a platform change feel worthwhile. It is not just about escaping a licensing model, but also about ending up with something that works better on a daily basis.

A platform that is easier to work with every day

One of the most interesting points in Virtual Computing’s feedback was not about raw infrastructure metrics, but about the human side of operations.

According to Mohammad, the simplicity of the platform had a direct impact on onboarding and internal training.

A different kind of vendor relationship

As an early adopter, Virtual Computing has seen Vates grow while maintaining its original approach.

This balance between professional support and open-source culture remains a key differentiator.

More than a migration

What began as a response to licensing changes became a broader shift. By moving 550 virtual machines to Vates VMS, Virtual Computing reduced costs, improved performance, simplified operations, and regained control over its infrastructure.

More than a technical transition, this project reflects a move toward a more open and flexible virtualization model, aligned with long-term needs.