Hetzner does not appear to sell a general done-for-you migration service for its Cloud and Dedicated products. Instead, it publishes migration documentation and tutorials that you or your team carry out, while full-service moves are typically offered by third-party specialists. That distinction is the heart of your decision: you are choosing between a documented self-managed path and paid outside help.
Hetzner's own guides are authoritative and free, but they assume real server skills. A specialist costs money, yet absorbs the scoping, cutover and rollback planning that makes a move risky in the first place.
What "Hetzner Migration Service" Can Mean
The phrase gets used for two different things. The first is Hetzner's library of official guides: migrating data from another provider, cloning an entire partition, transferring a domain, and importing mailboxes. These are instructions, not a service.
The second is a third-party migration engagement. Agencies and freelancers publish their own playbooks, such as a six-phase AWS-to-Hetzner strategy covering scoping, parallel setup, data migration with dual-writing, cutover and post-migration hardening. Nothing in the material reviewed for this article indicates that Hetzner staff perform full website, mail or database migrations for Cloud or Dedicated customers.
Hetzner's support page does advertise an AI chatbot, personal support by phone and email, guides and status updates. It does not define how far migration assistance extends, so treat the published documentation as your primary reference.
What Hetzner's Own Documentation Walks You Through
The guides are specific enough to be useful, and that specificity is also a warning about the skill level involved.
General data migration. Hetzner's guide for moving data from another provider covers bringing your data across, updating DNS records to the new server's IP, and verifying that everything works before you delete the old server.
Whole-partition migration. A separate guide migrates an entire partition from another provider to a Hetzner cloud server using dd over SSH and rescue mode. The documented method means creating the new cloud server, copying system configuration files, starting the new server in rescue mode, and copying partitions with dd. The steps differ depending on whether the old server has separate root and boot partitions or a single partition for both. That guide is dated 2024, so confirm details against your current console and operating system before relying on it.
Domain transfer. Hetzner's provider-change guide describes transferring a domain with an auth code, with an order processing time of one to two business days. If the domain stays with the previous provider, the website remains accessible during the transfer and can be reached via a temporary URL. The guide also recommends lowering the domain TTL to a few minutes, waiting about 24 hours, then pointing DNS at the new server's IP. Once a transfer has started it may take up to five business days, except for .de.at and .eu domains. For many top-level domains, a domain can only move to another registrar 60 days after initial registration.
Mailbox migration. Mailboxes can be migrated from remote IMAP accounts using the mailimport tool, or on a one-time basis through an authorized support request from konsoleH.
What a Paid Migration Engagement Usually Includes
A specialist's playbook typically runs from assessment to hardening. The AWS-to-Hetzner guide reviewed here sets out six phases: pre-migration scoping, auditing and planning; parallel setup; data migration and dual-writing; cutover; post-migration hardening; and known pitfalls.
Cutover practice from independent sources fills in the operational detail. One DNS cutover tutorial recommends lowering A/AAAA and relevant CNAME TTLs to 300 seconds 24 to 48 hours before cutover, and warns that lowering TTL ten minutes before switching will not help most users, because caches keep the old TTL until it expires. It also suggests staging the new server and validating it by hostname using hosts-file overrides or curl --resolve, before any public DNS change.
What a paid engagement does not automatically provide is a better outcome. You are buying process discipline and hands-on capacity, and you should ask any provider to describe their cutover, validation and rollback steps in those terms before you commit.
Decision Criteria: How to Judge the Two Routes
Compare the routes on the same six points. The weights are yours to set.
| Criterion | Official Hetzner documentation (you execute) | Third-party specialist |
|---|---|---|
| Coverage | Data migration, whole-partition migration, domain transfer, website upload, database creation, IMAP mailbox import | Scoping, parallel setup, dual-writing, cutover, hardening |
| Downtime control | Lower TTL to minutes, wait about 24 hours, repoint DNS; domain can stay put during transfer | Staged validation, TTL planning, hosts-file or curl testing, rollback preparation |
| In-house skills | SSH, dd, rescue mode, chroot, grub reinstallation, DNS records, IMAP import |
Handled by the provider per its playbook |
| Cost model | No documented service fee; your cost is staff time and risk | Not documented in the sources reviewed; vendor savings claims are promotional |
| Rollback planning | Verify data and update DNS before deleting the old server | Export the zone, keep old record values, check certificates, keep rollback ready |
| Data sensitivity | You control access and timing throughout | Depends on the provider's process and your contract |
If your stack matches a published guide closely, the documentation route has a real advantage: the procedure was written by the company whose platform you are moving onto. If your stack is complex, or an outage would cost more than the engagement fee, that advantage shrinks.
DIY Migration: Best Fit, Benefits and Limits
The self-managed route fits readers with working Linux and DNS skills, moderate downtime tolerance, and workloads that map onto the published guides.
Its benefits are straightforward. The procedures are Hetzner-specific and free to follow. You keep full control of timing, credentials and data handling. You also learn the new environment in the process, which helps when something breaks later.
Its limits are equally real. The partition guide expects comfort with dd, rescue mode and partition layouts. A single mistyped device name in a dd command can destroy data, and no guide can remove that risk. Mailbox imports and domain transfers bring their own lead times: one to two business days for order processing, up to five business days for some transfers, and a 60-day registration lock on many TLDs.
Paid Migration Help: Best Fit, Benefits and Limits
A specialist engagement fits teams with complex or interdependent services, low downtime tolerance, limited in-house migration experience, or data that needs a documented, staged cutover.
The clearest benefit is process coverage. A structured playbook forces the scoping and parallel-setup work that DIY migrations often skip, and it keeps cutover and hardening on the schedule. Independent cutover guidance adds the safety habits worth demanding from any provider: early TTL reduction, pre-cutover validation by hostname, certificate checks, and a rollback plan built from exported zone records.
The main limitation is evidence. Prices and savings figures in vendor-authored material, including claims of up to 90% cost reduction, come from companies selling migration work, so treat them as marketing rather than benchmarks. Ask for a fixed scope, a named cutover window and a written rollback procedure, and get the quote in writing.
Risks and Rollback Planning Before Cutover
Plan the failure case before you touch DNS. Export your current zone and record the key entries (A/AAAA, CNAME, MX, TXT, SRV) so the old values are available for rollback. An IP-only cutover, keeping the same DNS provider and changing A/AAAA records, is the lowest-risk option for most moves.
Certificate problems on the new server are one of the fastest ways to turn a clean cutover into an outage, so confirm TLS works before the switch. Database consistency during live migration is a genuine planning concern; schedule it deliberately rather than migrating a live database ad hoc. Choose the least busy time to start, so a problem affects as few users as possible.
For domains, the documented paths have built-in delays. Lower the TTL early, not on cutover day. If you are transferring rather than repointing, remember the registration lock on many TLDs and the multi-day processing windows.
Post-Migration Verification Checklist
Work through these checks before you cancel anything at the old provider:
- Load the site through the new server, then again through public DNS, and confirm content and forms behave.
- Confirm TLS certificates are valid on the live hostname.
- Send and receive test mail on each migrated mailbox, and check that mail flow reaches the new server.
- Verify the mobile and desktop experience for key pages.
- Keep the old server or hosting active until the checks pass, then delete it as Hetzner's guide advises after verification.
Mail authentication records deserve a deliberate check after any move. The material reviewed here does not provide a detailed post-migration deliverability procedure, so treat SPF, DKIM and DMARC review as a task to schedule rather than a step covered by these guides.
Who Should Choose Which Route
Choose Hetzner's documentation and tutorials if you have hands-on Linux and DNS ability, your workload matches a published guide, and you can accept a defined maintenance window. The cost is your team's time and the risk inherent in commands like dd.
Choose a third-party migration specialist if your stack is complex, your downtime tolerance is low, or you want a documented staging, cutover and rollback process without doing the execution yourself. Budget for it as you would any professional engagement, and discount vendor savings figures.
A middle path is reasonable for many readers: follow Hetzner's own guides for the parts you can handle, such as domains or mailboxes, and bring in help for the server and database move. Whichever route you take, decide on your rollback trigger before cutover day, verify before you delete the old environment, and you will have removed most of the risk that makes migrations stressful.


