Migrate from DigitalOcean to Hetzner
Droplets to cloud servers.
There's no image transfer between the two: DigitalOcean snapshots can't be exported and Hetzner's docs describe no self-service image import. You rebuild servers on Hetzner and copy the data.
Facts checked against each provider's own pages
The short answer
Rebuild each Droplet as a Hetzner cloud server from a Hetzner image with cloud-init user data[1] (or the hcloud CLI[2]), copy files with rsync or SFTP because DigitalOcean snapshots can't be downloaded[3], move managed databases with pg_dump (Hetzner Cloud lists no managed database service), then shift traffic and update DNS.
What maps to what
| On DigitalOcean | On Hetzner | Notes |
|---|---|---|
| Droplet | Hetzner cloud server | From €5.49/month excl. VAT[4]; not every server type is offered in every location[5]. |
| Droplet snapshot / backup | Rebuild + rsync | DO snapshots can't be downloaded or exported[3]; Hetzner documents snapshots of its own servers only[6]. |
| Volumes Block Storage | Hetzner Cloud Volumes | 10 GB–10 TB, attached to one server at a time[7]; not included in Hetzner backups or snapshots[7]. |
| Managed PostgreSQL / MySQL | Self-managed database on a server | No managed database service is listed for Hetzner Cloud; run the database yourself and restore from pg_dump or mysqldump. |
| doctl / control panel | hcloud CLI / Hetzner Console / API | [8] |
| 500 GiB+ pooled transfer per Droplet | 20 TB per EU server (1 TB US, 0.5 TB Singapore) | [9][4] |
| App Platform apps | Containers on your servers | Hetzner has no PaaS; App Platform specs[10] need re-creating as your own deployment setup. |
The migration, step by step
- 01
Inventory the Droplets
List each Droplet's OS, packages, services, cron jobs, firewall rules and attached volumes, plus any managed databases[11]. This becomes your cloud-init and provisioning checklist.
- 02
- 03
- 04
Copy data
Use rsync or SFTP from the Droplet to the new server. DigitalOcean's docs say the only way to restore files from an image is to recreate a Droplet or volume from it and copy files from there[3].
- 05
Move databases
Dump managed databases with pg_dump or mysqldump and restore into the database you run on Hetzner. Take a final dump during a short write freeze before cutover.
- 06
Update DNS
Lower DNS TTLs ahead of time, then point records at the Hetzner servers once traffic has shifted.
Things the docs warn about
- Hetzner's docs describe no self-service import of external disk images; the only custom-OS route documented is a custom ISO requested through a support ticket[1].
- Hetzner bills a server for as long as it exists, even powered off, hourly rounded up to the full hour with a monthly cap[12]. DigitalOcean bills per second[13].
- Primary IPv4 addresses are billed separately from Hetzner servers; IPv6 is free[12].
- Hetzner's traffic notifications at 75% and 100% don't cap usage[12].
- Cloud Volumes aren't covered by Hetzner backups or snapshots[7]; back them up separately.
- Hetzner's prices are in euros excluding VAT[4]; DigitalOcean's are in US dollars.
Run both during cutover, then switch
AW3 Host connects both your DigitalOcean and Hetzner accounts, so the old and new deployments run side by side from one dashboard and API instead of a big-bang switch.
Weighted routing sends a small share of traffic to Hetzner first (for example 5%, then 25%, 50% and 100%) while DigitalOcean serves the rest. Health checks every 60 seconds watch both; if the Hetzner side fails, failover moves traffic back automatically, and rollback to the previous release is one step. Daily cost sync shows what each provider costs during the overlap, and budget policies alert you if the double-running period gets expensive. Secrets for both are stored encrypted per environment.
When Hetzner has carried all traffic cleanly for long enough that you no longer need the fallback, point DNS at it for good and decommission DigitalOcean.
DigitalOcean vs Hetzner at a glance
| DigitalOcean | Hetzner | |
|---|---|---|
| Category | VPS / cloud servers | VPS / cloud servers |
| Pricing model | Droplets: monthly-capped plans billed per second; App Platform: per container instance[13] | Per-server hourly rate with a monthly cap; outgoing traffic over the allowance billed separately[12] |
| Compute billing granularity | Per second with a 60-second minimum (since 2026-01-01), capped at the monthly price[13] | Hourly, rounded up to a full hour, capped monthly; billed while the server exists, even powered off[12] |
| Internet egress (first paid tier) | Droplets $0.01/GiB over the pooled allowance; App Platform $0.02/GiB[9] | €1.00 for each additional TB in EU and US locations; €7.40 per TB in Singapore (excl. VAT)[4] |
| Regions / locations | 20 datacenters in 13 regions; new resources in 16 datacenters[14] | 6 locations in 4 network zones (Falkenstein, Nuremberg, Helsinki, Ashburn, Hillsboro, Singapore)[5] |
| Deploy model | Droplets are Linux VMs; App Platform deploys from GitHub/GitLab or container images[15] | Virtual machines via Console, REST API or hcloud CLI; cloud-init user data[8] |
| Persistent volumes | Droplets: Volumes block storage; App Platform: ephemeral local filesystem only[16] | Yes: Cloud Volumes 10 GB–10 TB, attachable to one server at a time[7] |
| Config file | App Platform app spec (YAML), applied with doctl or the API[10] | — |
Frequently asked questions
- Can I move a DigitalOcean snapshot to Hetzner?
- No. DigitalOcean says snapshots and backups can't be downloaded or exported, and Hetzner's docs describe no self-service image import. Rebuild servers on Hetzner and copy data with rsync or SFTP.
- Does Hetzner have managed databases like DigitalOcean?
- No managed database service is listed on the Hetzner Cloud pages we checked. You run PostgreSQL or MySQL on a cloud server and restore from a dump.
- How much traffic does a Hetzner cloud server include?
- At least 20 TB per month in EU locations, 1 TB in the US and 0.5 TB in Singapore, with €1.00 per additional TB in the EU and US (€7.40 in Singapore), excluding VAT.
Sources
- Hetzner Docs: Servers FAQ. https://docs.hetzner.com/cloud/servers/faq/ (checked 2026-11-16)
- Hetzner Cloud CLI (hcloud) README, official GitHub. https://raw.githubusercontent.com/hetznercloud/cli/main/README.md (checked 2026-11-16)
- DigitalOcean Docs: Can I download a backup or snapshot?. https://docs.digitalocean.com/support/can-i-download-a-backup-or-snapshot/ (checked 2026-11-16)
- Hetzner: Cloud regular performance plans. https://www.hetzner.com/cloud/regular-performance/ (checked 2026-11-16)
- Hetzner Docs: Locations. https://docs.hetzner.com/cloud/general/locations/ (checked 2026-11-16)
- Hetzner Docs: Backups and snapshots. https://docs.hetzner.com/cloud/servers/backups-snapshots/overview/ (checked 2026-11-16)
- Hetzner Docs: Volumes overview. https://docs.hetzner.com/cloud/volumes/overview/ (checked 2026-11-16)
- Hetzner: Cloud. https://www.hetzner.com/cloud/ (checked 2026-11-16)
- DigitalOcean Docs: Bandwidth billing. https://docs.digitalocean.com/platform/billing/bandwidth/ (checked 2026-11-16)
- DigitalOcean Docs: App spec reference. https://docs.digitalocean.com/products/app-platform/reference/app-spec/ (checked 2026-11-16)
- DigitalOcean Docs: llms.txt product index. https://docs.digitalocean.com/llms.txt (checked 2026-11-16)
- Hetzner Docs: Cloud billing FAQ. https://docs.hetzner.com/cloud/billing/faq/ (checked 2026-11-16)
- DigitalOcean: Droplet pricing. https://www.digitalocean.com/pricing/droplets (checked 2026-11-16)
- DigitalOcean Docs: Regional availability. https://docs.digitalocean.com/platform/regional-availability/ (checked 2026-11-16)
- DigitalOcean Docs: Create apps. https://docs.digitalocean.com/products/app-platform/how-to/create-apps/ (checked 2026-11-16)
- DigitalOcean Docs: App Platform limits. https://docs.digitalocean.com/products/app-platform/details/limits/ (checked 2026-11-16)
Your next deploy
goes everywhere.
Connect a provider, point a service at it, and ship. Add the second provider when you're ready.
No card needed · Free tier · Pay as you go after that