Our ServicesPlatform & Support

Website migration and replatforming without losing traffic

Migrations go wrong in predictable ways: URLs change without redirects, staging gets indexed, email stops working because MX records moved with the site, and nobody notices the drop until the month-end report. We plan around every one of those, and we have moved sites between hosts, builders, domains and stacks enough times to know where the traps are.

What You Get

Included as standard on every engagement — not an upsell list.

Pre-migration inventory and crawl

We crawl the live site to capture every indexed URL, its title, canonical, status code and internal links, and record current rankings, traffic and conversion baselines. That inventory becomes the checklist we validate against once you are live on the new platform.

Complete redirect mapping

Every old URL is mapped to its closest new equivalent with a permanent 301 — including paginated archives, category and tag URLs, uploaded PDFs and images, and legacy query-string pages. Anything genuinely retired gets a considered destination rather than a lazy redirect to the homepage.

Content, media and database migration

Posts, pages, custom post types, taxonomies, custom fields, users, product catalogues, orders and the full media library are transferred with structure intact. Where the old platform stored content in shortcodes or a discontinued builder, we convert it into clean, maintainable blocks or Breakdance elements.

DNS, email and TLS cutover plan

A written cutover runbook with lowered TTLs ahead of the switch, a clear record of which DNS entries move and which must not, mail and MX continuity, SSL provisioning on the new host, and a rollback path if anything behaves unexpectedly during propagation.

Replatforming rebuilds, not lift-and-shift copies

Moving off Wix, Squarespace, an abandoned theme or a dead page builder means rebuilding templates properly in WordPress with Breakdance or blocks. You get a maintainable system with reusable components instead of an exported approximation nobody can edit later.

Post-launch verification and monitoring

We re-crawl after launch to catch broken links, redirect chains, missing metadata and orphaned pages, resubmit sitemaps, watch Search Console coverage and index status for several weeks, and fix regressions while they are still small.

Multilingual and RTL continuity

For sites shipping in more than one language we preserve hreflang relationships, per-language URL structures and translation links through the move. We have delivered builds in eight languages, including Hebrew RTL, so we plan the language layer up front rather than repairing it after.

How We Deliver It

Stage by stage, with the approval points marked. Website Migration & Replatforming follows the same rhythm on every project.

  1. Discovery and risk assessment

    We document the current stack, hosting, DNS, email, integrations and traffic profile, then agree what "no regressions" means in measurable terms: indexed URL count, top landing pages, form endpoints, tracking and revenue paths.

  2. Build and migrate on staging

    A full copy or rebuild is assembled on a password-protected, noindexed staging environment. Content, media and integrations are migrated there, and you review the real thing with real data before anything touches the live domain.

  3. Redirect map and QA

    The redirect map is written, applied on staging and tested URL by URL. We check templates, forms, payment flows, tracking tags and any language variants, then run a Lighthouse and accessibility pass so the new site does not launch slower than the old one.

  4. Cutover

    TTLs come down, the switch happens in a low-traffic window, DNS is updated, SSL is verified, and we work through the launch checklist — redirects, robots.txt, sitemap, search console, analytics, email — with the rollback plan ready.

  5. Stabilisation window

    For the weeks after launch we monitor crawl errors, index coverage, 404 logs, rankings and conversions, add redirects for any URL patterns we missed, and hand over documentation for the new stack.

What You Receive

The concrete artefacts handed over at the end — files, access and documentation you keep.

  • Full URL inventory and pre-migration performance baseline
  • Complete 301 redirect map as a reviewable spreadsheet
  • Staging build of the migrated or rebuilt site for sign-off
  • Written DNS, email and TLS cutover runbook with rollback steps
  • Migrated content, media library, users and commerce data
  • Preserved or corrected hreflang and language URL structure
  • Post-launch crawl report covering broken links and redirect chains
  • Refreshed XML sitemap, robots.txt and Search Console submission
  • Handover documentation for the new hosting and platform

Ideal for

If two or three of these sound like your situation, this is the right place to start.

  • You are leaving a slow or unreliable host and cannot risk downtime
  • You are moving off Wix, Squarespace or a discontinued page builder
  • A rebrand means a new domain and you need the equity to follow
  • A previous migration cost you rankings and you want it done properly
  • You are consolidating several microsites into one platform
  • Your multilingual site must keep its hreflang and per-language URLs

Tools we use

Standard, portable tooling. The licences, accounts and source stay in your name, so nothing here is a reason you cannot leave.

  • WordPress
  • Breakdance
  • WooCommerce
  • WPML
  • ACF
  • PHP
  • MySQL
  • Kinsta
  • Hostinger
  • Cloudflare
  • Screaming Frog
  • Google Search Console
  • GA4
  • Lighthouse

Live projects where this work did the heavy lifting:

What we have written about this, in more depth than a service page allows:

Frequently Asked Questions

The questions we get asked most about Website Migration & Replatforming.

It should not. The new site is built and fully tested on staging while the old one keeps serving, so the only moment of change is the DNS cutover. With TTLs lowered in advance, propagation is quick, and both origins stay live during the overlap so visitors reach a working site either way. We schedule the switch for your quietest traffic window and keep a rollback ready.
A well-executed migration keeps URLs identical wherever possible and 301-redirects the rest, which preserves the overwhelming majority of ranking signals. Expect some short-term fluctuation for a few weeks while Google recrawls and consolidates — that is normal. What causes real, lasting losses is missing redirects, a stray noindex left over from staging, or blocked resources, and those are exactly the items on our launch checklist.
Website hosting and email hosting are separate services that often share a DNS zone, which is why migrations break inboxes. We record your MX, SPF, DKIM and DMARC records before touching anything and carry them across unchanged unless you have asked us to move mail too. If you are also switching to Google Workspace or Microsoft 365, we sequence that separately from the site cutover.
Then it is a replatforming project rather than a copy. Exported builder markup is usually unmaintainable, so we rebuild the templates natively — commonly in Breakdance — and migrate the content into that structure. It is more work up front, but you end up with a component system your team can actually edit, and page weight typically falls sharply once the old builder is gone.
Yes. Products, variations, categories, customers, orders and coupons all move across. The sequence matters: we migrate the catalogue and test checkout end to end on staging with the payment gateway in sandbox, then run a final delta sync of orders and customers immediately before cutover so nothing placed during the build window is lost. Store downtime is measured in minutes, not hours.

Ready to start on Website Migration & Replatforming?

Send us the brief — or just the problem. You will get a written scope, a timeline and a fixed price, usually within one working day.