DEV Community

Cover image for The CMS migration that stalls on redirects, not on the API
Samer Alsayegh for Draftbase

Posted on Originally published at draftbase.co

The CMS migration that stalls on redirects, not on the API

The API part of a CMS migration is the easy half. You can script it in a weekend. The part that costs you a year is a spreadsheet nobody wanted to own.

A CMS migration to headless loses search traffic on redirects, not on content transfer. 17% of site migrations never regain their old traffic, even after 1,000 days, and average recovery runs 523 days across a study of 892 moves (CausalFunnel). Draftbase's fix is ordering: build the one-to-one redirect map during the content audit, before a single entry moves.

The failure rate is not a rounding error either. 38% of migration projects fail outright, and traffic drops of 30 to 60% show up in the ones that work (Solix).

Here's the mechanic. A specific one-to-one redirect passes 90 to 99% of a page's rank signal to its new URL. A blanket redirect that dumps a whole section on the home page reads to Google as lost content, not a move. Same HTTP status, completely different outcome.

Most guides file redirects under "SEO checklist", assign one person, and schedule it near the end. So it becomes the last thing built and the first thing rushed against a launch date.

Flip the order instead. While you're listing old URLs in the audit, pair each one with its new type and its new path in the same sheet. By the time content is ready to move, the map already exists.

The rest of the sequence that keeps a move off the 523-day curve:

  1. Audit, and cut the thin pages rather than moving them.
  2. Model content into typed fields before migrating anything.
  3. Build the redirect map in that same pass.
  4. Migrate, and bring meta text and alt text with the body.
  5. Test mobile, any app on the same API, and the editor's own preview.
  6. Launch redirects the moment the old site goes down.
  7. Check rankings weekly for a month, not monthly.

Full walkthrough, with the 200-post worked example, is on the canonical: CMS Migration Guide.

Sincerely: the goal of a migration is to stop thinking about the CMS. Draftbase keeps content as structured data with no locked export format, so the next move is cheaper than this one. Hobby is free, Startup is $49/mo. Migration war stories welcome at r/draftbase_cms.

Top comments (0)