Migrate a site to Webflow

All videos

Migrate a site to Webflow

Trouble with this video? YouTube may be blocking it for you. Watch it directly on YouTube instead.

Webflow developer Keegan Leary takes you through a realistic, AI-assisted site migration, from auditing a legacy site and planning the work to building, launching, and verifying the new site in Webflow.

This episode follows Keegan as he makes decisions, adjusts his approach, and checks his work throughout the migration, rather than explaining every step in detail.

Copy the prompts Keegan used in the video and adapt them for your own migration project. →

The process

From planning to launch in three phases

  1. Plan the migration. Gather the existing site’s URLs, CMS content, redirects, analytics, scripts, forms, and designs. Review these inputs together to define the scope and identify dependencies, then decide what to migrate, revise, consolidate, or retire.
  2. Build and refine. Put the plan into action by setting up the CMS and design system, then test the build and content migration on a small sample. Check the work in Webflow, fix anything that doesn’t match the plan or designs, and only then apply the approach more broadly.
  3. Ship and QA. Before launch, set up redirects and analytics, publish to staging, and test important pages, links, and forms. Once the new site is live, check them again, confirm tracking still works, and watch for changes in search traffic or indexing.

Best practice • Check your setup

Before applying this approach to your own migration, look for the differences that could change your plan:

  • Content and structure: What can you export? Do the fields, rich text, and image URLs fit the new CMS and designs, or will they need cleanup or remapping?
  • Connected systems: Where do forms send submissions? Which scripts, analytics events, CRM connections, or dashboards need to keep working?
  • URLs and search: Which URLs bring in traffic or appear in search? Which slugs are changing, and what redirects, metadata, or indexing settings need to carry over?
  • Access and launch: Who can access the source platform, analytics, and domain settings? How much downtime is acceptable, and who will test the site after launch?

Use your answers to decide what to automate, import, rebuild, or handle manually.

Additional resources

Want to dig deeper? These resources can help with migration planning, Webflow MCP, and launch prep:

<details>

<summary>

Video transcript

</summary>