Moving a Website to a New CMS Without Losing Traffic

Short answer: a CMS migration is not “redoing the site” — it is moving the data under a new hood, and the main danger is not design but losing what already works: indexed URLs, link equity, image content and lead intake. 90% of failures come from three things: no map of old URLs and redirects, media moved under new paths, and forms that go silent after launch because analytics never saw them. The checklist below closes all three.

First, the honest question: do you need a migration at all

Change a CMS when at least one of these is true:

• content is edited through a developer — the admin panel died or is too complicated (typical for a WordPress that grew 30 plugins);
• the site is slow and cannot be sped up inside the current system (heavy themes, render on every request);
• you need features the system cannot have: B2B price lists, client accounts, multi-language, deep CRM/1C integration;
• security: constant hacks and black redirects — the disease of cheap builds.

If the only problem is looks, that is a redesign on the current CMS, not a migration. Useful to know the line before you get a quote — our guide why your website does not convert helps with the diagnosis.

Why migrations break SEO: anatomy of three failures

1. Broken URLs. The old page /services/order-page/ became /services/order/ without a redirect → every external link and bookmark now hits a 404, equity zeroes out.
2. Lost “synthetic” content. Old CMSs kept data in fields the new one does not have: tags, extra descriptions, schema markup, category order. Exporting “the article text” does not carry them.
3. Silent forms. After the move the form still sends email but fires no GA4 event — a month later you conclude “the site got worse”, when you simply stopped seeing the leads.

Preparation: what happens BEFORE the move

The move: mandatory technical items

• 301 redirects per the URL map — at server/edge level, not via a “redirect plugin”, which just becomes plugin №31.
• Canonical URLs on the new site: self-referencing; old ?utm= junk must not migrate into the address bar.
• XML sitemap regenerated and submitted to Search Console alongside the old one during the transition.
• hreflang — if multilingual: re-verify translation pairs after the move; they break most often.
• Structured data (Organization, LocalBusiness, Article, Product) — rebuilt in the new CMS: in headless it is assembled by code, not a plugin, and it will not “migrate itself”.
• Speed: the move is the moment to confirm the new build is faster than the old one (LCP, INP) — otherwise the migration loses its point: how site speed affects revenue.
• Forms and integrations: CRM, email notifications, spam protection, payments — test every scenario with a real submission; verify email delivery (SPF/DKIM survive only if DNS was untouched).

Day X: the switch and the first 72 hours

1. Switch during low traffic (night; Sunday for B2C).
2. Check the top 50 pages by hand: open the old URL → land on the new one via 301.
3. Search Console: old + new sitemap submitted, coverage errors checked daily for the first week.
4. A test lead/call/order — every channel, every day.
5. No “small design tweaks” in the first week — every change complicates the diagnosis if something drops.

30-day monitoring: metrics, not feelings

Daily: 4xx/5xx errors in logs and Search Console. Weekly: positions by top clusters, form conversion, organic traffic by the pages from the old snapshot. Success criterion on day 30: organic ≥ 85–90% of baseline on top pages, leads flowing, the 404 list empty. If not — surgical redirect fixes, not “rollback”.

An example from practice

A client with a manufacturing catalogue on a “heavy” WordPress: 40+ plugins, crashes, price edits only through the programmer. We moved products and articles to a headless stack (Strapi + fast storefront): a map of 680 URLs covered by redirects, media moved without path changes, prices now edited by a manager. Result: three times the speed, organic recovered within 3 weeks and then grew — because the migration was prepared, not pasted together. We do this kind of move inside redesign and migration without SEO loss.

FAQ

Bottom line

A CMS migration is a project about preserving what accumulated — rankings, links, content, lead flow. Three tools remove 90% of the risk: a snapshot of the old site before you start, a complete URL map with 301s, and 30-day monitoring against the baseline. We do these moves turnkey — start with a free audit of your old site, and we will honestly say whether you need a migration or treatment is enough. Further reading: redesign without losing rankings and the SEO migration checklist.