VMs moved
Workloads transitioned from hosted infrastructure to Google Cloud VMware Engine.
Telecommunications
~1,000 VMs moved to the cloud in ~90 days.
A telecommunications enterprise exited a hosted infrastructure environment through coordinated application waves.
~1,000VMs in the migration
~90 daysProject delivery
CompletedHosted infrastructure exit
OvernightApplication cutover windows
The challenge
What the organization needed
Aging hosted infrastructure and approaching contract renewals created an aggressive migration deadline. The enterprise needed cloud adoption with minimal application refactoring and controlled downtime.
The approach
How the program delivered
The delivery team analyzed application stacks and target requirements, then coordinated repeatable runbooks and maintenance-window cutovers. RiverMeadow complemented VMware HCX for physical and larger-server use cases within the broader program.
The results
Outcomes delivered
Infrastructure exit
The enterprise exited its hosted infrastructure environment through coordinated application waves.
Delivery window
The migration established the foundation for a cloud-first strategy.
- The hosted infrastructure environment exited.
- Application transformation kept to a minimum.
- A simpler technology estate established in the cloud.
Platform scope
Technology and delivery scope
- Source
- Hosted infrastructure, including physical and virtual workloads
- Targets
- Google Cloud VMware Engine
- Workloads
- Windows Server 2012 R2 and CentOS Linux 7
- Delivery scope
- RiverMeadow and VMware HCX, with coordinated application cutovers
One software platform
Explore the workload lifecycle.
See how RiverMeadow connects workload mobility and modernization with planning, validation and reporting.