Website migration without losing the useful parts.

Start with a full inventory

List every URL along with its owner, associated forms, third-party integrations, current search traffic and any legally required pages before comparing platforms. A migration that skips this step tends to lose exactly the pages that were quietly doing the most work.

• Every indexed URL and its current search traffic
• Content owners for each section
• Forms and where their submissions currently go
• Third-party integrations (booking, payments, CRM)
• Legally required pages (imprint, privacy policy, terms)

Map old URLs to new ones before you build

Decide which URLs stay identical, which change, and which disappear — then write the redirect map before development starts, not after launch. A same-day 301 redirect plan is the single biggest factor in whether search rankings survive a move.

Protect what visitors don't see

Analytics tracking, cookie consent behaviour, and server-side integrations such as payment webhooks or CRM syncs need to keep working through the cutover, not just the pages visitors read. Test these on a staging domain before the DNS switch, not after.

Plan the cutover window

A DNS change can take anywhere from minutes to 48 hours to propagate depending on the previous TTL setting — lower the TTL a few days in advance, and keep the old host reachable during the transition so no visitor lands on a dead page.