For a typical mid-sized environment (10 to 50 VMs), the full migration process takes 6 to 10 weeks from assessment to final handover. Smaller environments (under 10 VMs) can complete in 3 to 4 weeks. Larger or more complex environments with legacy applications, databases, and custom networking may require 12 to 16 weeks. The timeline depends primarily on workload complexity, not VM count. We provide a precise timeline during the assessment phase based on your actual environment inventory.

Need a precise timeline for your environment? Book a Virtualization Expert Consultation.

Near-zero downtime is achievable for most workloads. V2V migration converts VMware VMs to XCP-ng format while the source VM continues running. Cutover windows — the brief period when traffic switches from VMware to XCP-ng — are typically planned during low-traffic periods and measured in minutes, not hours. Databases and stateful applications require brief planned maintenance windows for cutover, which we schedule with your team in advance. True zero-downtime migration is possible for web and application tiers using blue-green deployment strategies.

Planning a low-disruption migration? Book a Virtualization Expert Consultation.

V2V (Virtual-to-Virtual) migration converts virtual machines from one hypervisor format to another — in this case, from VMware's VMDK disk format to XCP-ng's VHD format, and from VMware hardware emulation to Xen paravirtualization. The process uses specialized tools to copy the VM disk, convert the format, and inject the appropriate drivers for the target hypervisor. The source VM continues running during the copy phase. Once conversion is complete and validated, a brief cutover switches production traffic to the migrated VM. The original VMware VM is kept as a fallback for a defined period before decommission.

Have specific VMs to assess? Book a Virtualization Expert Consultation.

The most complex workloads are those with tight hardware dependencies, legacy operating systems, or stateful clustering. Specifically: SQL Server and Oracle databases with Always-On or RAC configurations; Microsoft Exchange (all versions — we support them including legacy); Windows Server Failover Clusters; applications with hardware-level licensing tied to VMware host identifiers; and very old operating systems (Windows Server 2003, 2008) that require specific driver handling. None of these are blockers — but they require more planning time and in some cases a specific migration approach. We identify all complex workloads during the assessment phase.

Have legacy or clustered workloads? Book a Virtualization Expert Consultation.

After migration, your VMware subscription simply isn't renewed at the next renewal date. Active licenses run to their expiry date — there is no need to terminate them early. The economic benefit is realized at renewal: instead of renewing VMware at Broadcom's current pricing, you renew XCP-ng support through Vates at a fraction of the cost. If you have questions about early termination clauses or contract obligations, we advise you to review your current Broadcom agreement — we can assist in interpreting the technical implications.

Reviewing renewal economics? Book a Virtualization Expert Consultation.

Yes. XCP-ng is based on XenServer, which shares conceptual similarities with vSphere. Virtualisation concepts — resource pools, live migration, HA clustering, storage policies — are directly transferable. Xen Orchestra, the management interface, is intuitive and web-based. We provide 3 to 5 days of administrator training covering all essential operations. Most VMware administrators are productive on XCP-ng within 2 weeks. Our Level 1 & Level 2 MSP support provides ongoing assistance during the learning curve — you're not left on your own after handover.

Learn more about XCP-ng Enterprise Virtualization →

Want to discuss training scope and timing? Book a Virtualization Expert Consultation.

Yes — hybrid operation during transition is standard practice, not an exception. Both platforms run simultaneously during migration. We design cross-platform networking, storage, and backup strategies so both environments operate without interference. Some organizations also choose to maintain a long-term hybrid setup — keeping mission-critical legacy applications on VMware while running new workloads on XCP-ng. We design and support both approaches.

Learn more about our VMware Optimization services →

Designing a hybrid roadmap? Book a Virtualization Expert Consultation.

Every migration plan includes a predefined rollback strategy before a single VM is touched. If a cutover fails validation, the workload continues running on VMware — no emergency recovery required. Rollback procedures are documented, tested, and known to your team before migration starts. In our experience migrating dozens of organizations, we have not had a production rollback that caused business disruption. The parallel-systems approach ensures that failure during migration is a technical event, not a business incident.

Want to review rollback architecture for your environment? Book a Virtualization Expert Consultation.