On-premise migration
Successful migrations are almost never a single cutover. The ones that work run hybrid for months: some workloads already in the cloud, some still on your own racks, and both talking over a private network as though they shared a room.
A Real Story
How this runs in production
Trans Andalas ran 60 VMs on its own racks in Bekasi. There was not one night in the year that could be used to move everything at once — their fleet runs around the clock.
The migration took eight months in hybrid mode. A VPN gateway joined the new VPC to the old data center, workloads moved wave by wave, and the core database stayed on bare metal because that is genuinely where it belongs.
- VMs migrated
- 60
- running hybrid
- 8 bln
- maintenance windows
- 0
We were not looking for a way to move overnight. We were looking for a way to run in two places for eight months without anyone noticing.
Reference Architecture
Exactly what they run
The plan names below are the same ones listed on the pricing page.
- VPC NAT GatewayVPC + VPNEncrypted link to the old racks throughout the transition.
- Virtual Machines4.large × 38Application workloads, moved a wave at a time.
- Bare Metal1× EPYC 64-coreThe core database — still physical, now in our region.
What You Get
Built for this workload
VPN gateway
An encrypted link to the data center you run today.
Isolated VPC
Private subnets with route tables entirely under your control.
NAT gateway
Outbound access for private instances with no public IP.
Built From