A website migration to Webflow should inventory valuable pages, map URLs, rebuild content systems, test integrations and monitor the change after launch.

The safest migration preserves useful search and visitor paths while improving the system underneath them. Build a complete inventory before changing URLs, content or platform behavior.

Migrations fail on the pages nobody remembered

The pages a team discusses during a migration are the ones they look at: homepage, services, contact. The pages that cause the damage are the ones nobody has opened in three years and that quietly earn a third of the organic traffic — an old comparison article, a landing page from a campaign, a resource with links pointing at it from elsewhere. A migration is mostly an exercise in finding those before launch rather than after, because after means reading about it in an analytics chart six weeks later.

Create the source-site inventory

List indexable URLs, page purpose, traffic or conversion value, backlinks where known, metadata, content owner and proposed destination. The inventory becomes the basis for keeping, improving, merging or retiring each page. Pull it from more than one source, because no single export is complete.

  • A crawl of the live site for what exists now.
  • Analytics for what earns traffic and conversions.
  • Search Console for what actually ranks and receives clicks.
  • A backlink source for pages other sites still point to.

Decide the fate of every page deliberately

Each URL should end the inventory with one of four decisions: keep as is, improve, merge into a stronger page, or retire. The default of copying everything carries the previous site's weaknesses into the new one, while the opposite default of a clean start throws away accumulated value that took years to build.

Design the Webflow content model

Map repeated content to Collections, fields and templates. Confirm which URLs and metadata can remain stable and which changes require permanent redirects.

  • Preserve valuable paths where practical.
  • Avoid copying obsolete duplication into the new CMS.
  • Test imported content and image handling.

Build and test the redirect map

Every moved URL with a relevant replacement should point directly to the final destination. Update internal links, canonicals and sitemap entries so they no longer rely on redirects. Test the map before launch rather than after, and check that chains have been collapsed: a redirect pointing at another redirect is a common and avoidable source of lost value.

  • One hop from old URL to final destination.
  • Redirect to the closest real equivalent, not the homepage.
  • Retired pages return a genuine 404 or 410, not a soft redirect.

Monitor the launch

Verify production responses, forms, analytics, robots rules, sitemap access and Search Console. Watch indexing and traffic patterns while distinguishing normal processing from actionable migration errors. Some ranking movement in the first weeks is ordinary as search systems reprocess the site; a sustained drop concentrated on specific templates is not, and usually points at a redirect or indexing rule rather than at the content.

Keep the old site reachable until you are certain

Retain a full export of the previous site, its database where one exists, and its URL inventory well past launch. The point is not a rollback plan so much as an answer to the question that always arrives a month later: what exactly was on that page before?

Practical decision checklist

  • Export the existing URL inventory from several sources.
  • Map each URL to a clear action.
  • Rebuild CMS and metadata deliberately.
  • Test one-hop permanent redirects.
  • Monitor indexing and conversions after launch.
  • Retain a complete source-site backup.

Frequently asked questions

Will migrating to Webflow hurt SEO?

Any migration can create risk when content, URLs or technical signals change. Careful planning reduces avoidable errors but cannot guarantee unchanged rankings.

Should every old page be copied?

No. Keep useful distinct pages, improve weak pages with demand, merge overlap and intentionally retire pages without value.

How long should redirects remain?

Permanent redirects should remain long enough for users and search systems to rely on the new destinations. Avoid treating them as a temporary launch-only file.