Migrating a Hetzner Cloud Stack to AnubizHost

Use the hcloud CLI to dump your topology: hcloud server list -o json > servers.json, hcloud network list -o json > networks.json, hcloud load-balancer list -o json > lbs.json. This gives you a precise inventory to recreate on AnubizHost.

For each server, note the type (CX21, CCX13, etc.), datacenter, image, attached volumes, and any user-data scripts. Volumes need to be unmounted and copied as filesystem trees (not as raw block devices) for cross-provider portability.

For each Hetzner server, order an equivalent AnubizHost VPS. Cloud Networks (private RFC1918 subnets) can be recreated using AnubizHost's private network feature or by setting up a WireGuard mesh between your nodes - WireGuard scales to dozens of nodes with minimal overhead and works across datacenters.

Load Balancers are reproduced with HAProxy or nginx on a small dedicated VPS. Floating IPs are not portable; you adjust DNS to point at the new IPs and update any IP-dependent code.

For each application server, rsync filesystem data as in our Hetzner VPS migration guide. For databases, use pg_dump or mysqldump as appropriate. For object storage (Hetzner Storage Box), use rclone to copy to an AnubizHost storage VPS or to S3-compatible offshore storage.

For Hetzner Volumes, mount them on the source, then rsync the contents to the equivalent location on the target. Most volumes are just ext4/xfs filesystems with no Hetzner-specific format.

Lower TTL 24 hours ahead, flip records at the cutover moment, re-issue Let's Encrypt on each public endpoint. If you use service discovery (Consul, etcd, Kubernetes DNS), update the addresses inside the cluster. WireGuard tunnels established earlier mean internal traffic continues to flow regardless of public DNS state.

Decommission Hetzner Cloud resources gradually: servers first (after 7 days), then volumes (after backups verified), then the cloud project itself. Each resource is billed per hour, so granular cleanup matters.

Partial migration leaves operational dependencies in the country you're trying to leave. Moving the whole stack to AnubizHost gives you uniform offshore jurisdiction, single-vendor billing in crypto, and consistent privacy posture. Related reading: offshore VPS, Hetzner VPS migration, DigitalOcean Droplet migration.