Moving workloads between regions

Servers cannot be moved live

Servers do not move between facilities. A regional move involves provisioning in the new region, replicating data, switching traffic, and decommissioning the original server. Because each server is dedicated hardware, there is no shared infrastructure to migrate across.

Plan the move as a scheduled switchover with a rollback option, rather than a background migration.

Sequence

1. Provision in the target regionUse the same hardware profile unless there is a specific reason to change it. Changing both profile and region at once makes performance differences difficult to diagnose.
2. Verify the new hostRetrieve and verify the attestation report before replicating any data.
3. ReplicateTransfer data over your private interconnect rather than the public internet. Outbound rules apply in both directions, so the path must be declared on both segments.
4. Cut overSwitch traffic during an agreed window. Keep the original server running until you have confirmed the new server performs correctly under production load.
5. DecommissionRelease the original server through the portal. Secure erasure runs automatically and produces the required disposal evidence.

We recommend not decommissioning on the same day as the switchover. Retaining the original server for a few days uses some capacity but preserves a rollback option that does not depend on backups.

Compliance implications

All regions operate under the same authorized baseline, so a regional move does not change what you inherit and does not require a new assessment of the hosting platform.

If your own authorization specifies particular regions, update that documentation accordingly. The platform does not flag such discrepancies automatically.