Wrocław + London | VMware exit programs
We design and execute transitions from vSphere/ESXi to Proxmox VE, Microsoft Hyper-V, Nutanix AHV, KVM and Red Hat OpenShift Virtualization. For SAP HANA DB systems, we run a dedicated path only on certified KVM configurations.
Target platforms
The right platform depends on licensing, operating model, HA/DR needs, backup integration, application criticality and the readiness of the operations team.
A platform with KVM, LXC, web UI, HA, SDN, ZFS/Ceph and built-in backup/DR tooling. A strong fit for companies seeking predictable costs and flexible administration.
A type-1 hypervisor in Windows Server and a natural choice for Microsoft, Active Directory, Windows Admin Center, System Center and Azure Local environments.
An integrated hypervisor in Nutanix Cloud Infrastructure managed through Prism, with automation, HA, DR and Nutanix Move for VM migrations.
KVM as the hypervisor layer and OpenShift Virtualization for organizations that want to operate VMs alongside containers, GitOps, CI/CD and Ansible automation.
Process
Every project starts with facts: inventory, application dependencies, maintenance windows and data risk. Only then do we select migration tools.
Inventory of VMs, datastores, networks, snapshots, backups, OS versions, VMware Tools, RTO/RPO, application owners and business criticality.
Compute, storage, networking, HA cluster, backup, monitoring, IAM, segmentation and rollback procedures. SAP HANA DB gets separate sizing and certification checks.
Migration of 3-10 representative VMs, validation of performance, driver conversion, IP addressing, DNS, backup and monitoring.
Grouping systems by dependencies, data replication, cutover rehearsal, production cutover, application testing and go/no-go decision.
Post-migration monitoring, resource optimization, documentation updates, operating procedures and a plan to decommission legacy hosts and licenses.
Estimates
Assumptions: the target platform is prepared, backup works, application administrators are available and migrations are executed in waves outside peak hours. SAP HANA DB requires a separate window and performance tests.
| Scope | Standard VMs | With SAP systems | When SAP HANA DB is present |
|---|---|---|---|
| 10 VM | 1-2 weeks | 2-3 weeks | 3-4 weeks, KVM only |
| 50 VM | 3-5 weeks | 5-7 weeks | 7-9 weeks, KVM only |
| 100 VM | 6-9 weeks | 9-12 weeks | 12-16 weeks, KVM only |
| 200 VM | 10-14 weeks | 14-20 weeks | 20-28 weeks, KVM only |
Timelines are service estimates. The final schedule depends on network/storage throughput, disk sizes, the number of production environments, maintenance windows, compliance requirements and pilot results.
SAP workload
For standard SAP application servers, several target platforms can be assessed. For SAP HANA DB, we run a separate track: certified hardware, supported operating system, TDI requirements, benchmarks and migration only to certified KVM solutions.
About us
AGG Systems helps corporations worldwide design, operate and evolve business-critical infrastructure and ERP landscapes, with a strong focus on SAP environments and certified competence across multiple SAP domains.
We combine infrastructure engineering, virtualization, operating systems, databases, high availability, backup and SAP Basis experience. That makes our VMware migration programs practical: we do not only move virtual machines, we protect application continuity, performance and operational accountability.
Locations
Technical workshops, discovery, platform design, migration waves, post-implementation support and operating documentation for IT teams in Central Europe.
wroclaw@vmware-migrations.euVMware exit programs for international organizations, maintenance window planning, governance, risk audits and migration coordination across regions.
london@vmware-migrations.euPlatform information is based on public vendor materials: Proxmox VE, Microsoft Hyper-V, Nutanix AHV, Red Hat OpenShift Virtualization and the public certification catalog SAP HANA Hardware Directory.