Our USP: migration

Website migration: domain, DNS and email without downtime.

Migrations often mean lost emails or a website that’s down for days. We handle the entire move of website, domain, DNS, mailboxes and server. Planned, tested and with a fallback plan. You simply keep working.

Key points

  • Domain transfer to the new provider, every DNS record carried over cleanly.
  • Email migration to Microsoft 365, Google Workspace or your provider of choice, including old emails, contacts and calendars.
  • Server migration from old hardware or shared hosting to a secured EU environment.
  • 301 redirects for every old URL so your rankings move with you.
  • We only switch over after testing. With a fallback plan.

Why migrations so often go wrong

A website or domain migration looks simple on paper. In practice, a lot depends on details you only notice once they’re missing. A forgotten MX record that suddenly stops emails from arriving. A missing SPF or DKIM record that sends outgoing emails to spam. Old URLs without redirects that make Google rankings vanish overnight.

On top of that comes coordinating the old provider, the new provider, the agency and the IT service provider. We take all of that off your hands. You have one contact who keeps all the threads together.

What we move for you

Domain and DNS migration

We transfer your domain to the new provider and carry over every record: A, MX, SPF, DKIM and DMARC. Before switching, we lower the DNS time to live (TTL) so changes propagate quickly.

Email migration to Microsoft 365

We migrate all mailboxes with old emails, contacts and calendars in advance. The destination can be Microsoft 365, Google Workspace or your provider of choice. Only once everything is in sync do we switch the MX record. No email gets lost.

Servers and hosting

From old hardware or shared hosting to a modern, secured environment in the EU. If you like, we take over hosting, monitoring and backups afterwards.

Moving your website without losing rankings

Every old URL gets its new destination via a 301 redirect. Your Google rankings move with you. Read more about the search side on our SEO agency page.

Migration on its own or with a relaunch

You can book a migration on its own, for example if you want to switch to Microsoft 365 or change hosting providers. You can also combine it with a new website, a new online shop or a business app. In a relaunch, we plan the migration from the start. That way there are no surprises on go-live day.

How it works: your migration step by step

Every migration follows the same plan. We test before switching over, not after.

  1. 01

    Inventory

    We record domains, DNS records, mailboxes, servers and every URL of the old website. Nothing gets forgotten because everything is on one list.

  2. 02

    Migration plan

    Order, switchover time and fallback plan. You know exactly what happens when.

  3. 03

    Preparation

    Lower DNS TTLs, sync mailboxes in advance, set up the website on the new server, create redirects.

  4. 04

    Switchover

    We switch DNS and MX once everything is tested. Then we check mail flow, website and redirects.

  5. 05

    Completion

    Finish the domain transfer, final check. After that you can cancel old contracts. We remain your contact.

How much does a website migration cost?

The effort depends on the number of domains, mailboxes and URLs. Plus the question of whether a server is moving too. Typical projects:

  • Domain and DNS migration
  • Email migration per mailbox, e.g. to Microsoft 365
  • Website migration with 301 redirects
  • Server migration

Prices on request: every project is different, so the price depends on the scope.

In the intro call we clarify the scope. After that you get a transparent quote with no hidden costs.

Case study: Elliniki, Leipzig

Website Elliniki
Case study · Restaurant · Leipzig Elliniki A traditional Greek restaurant with almost 1,900 Google reviews: new website, a custom table booking for rooms and seating, SEO & GEO and a system that brings guests back with events, offers and birthday discounts.
  • Website relaunch
  • Table booking
  • Guest loyalty
  • SEO & GEO
Read the full case study →

A relaunch is the moment visibility can get lost. Elliniki, a long-established restaurant with almost 1,900 Google reviews, got a new presence: warm imagery, the lunch menu at a glance and table booking with a single tap. Local SEO was a fixed part of the project. That’s exactly why we plan redirects and the switchover from the start in every relaunch.

Frequently asked questions

Will emails get lost or will the website go offline during the move?

No. We migrate mailboxes in advance, lower DNS TTLs before switching and only switch over once everything is tested. Old URLs get 301 redirects so you don’t lose any Google rankings.

How does an email migration to Microsoft 365 work?

We create the mailboxes in Microsoft 365 and copy old emails, contacts and calendars in advance. Shortly before the switchover we sync one last time. Then we switch the MX record and adjust SPF, DKIM and DMARC.

Can I keep my domain?

Yes. Your domain stays your domain. We transfer it to the new provider or just change the DNS records if it should stay with the old provider.

Will I lose my Google rankings when moving my website?

Not if every old URL is redirected to its new destination with a 301. That’s always part of our work. Your Google rankings move with you.

How long does a migration take?

It depends on domains, mailboxes and data volume. The actual switchover is short because we prepare and test everything beforehand. You’ll see the exact timeline in the migration plan.

What are SPF, DKIM and DMARC?

Three DNS records that protect your email. SPF defines which servers may send for your domain. DKIM signs every email. DMARC tells the recipient what to do with emails that fail these checks. Without them, your emails quickly end up in spam.

Do you migrate servers too?

Yes. From old hardware or shared hosting to a modern, secured environment in the EU. If you like, we take over hosting, monitoring and backups afterwards.