All posts
Platform migrations

Webflow to Framer Migration Checklist (Free Template)

Webflow to Framer migration checklist: what to check before launch, on launch day and in the 30 days after, including Framer redirects and locale slugs.

By Mehdi Hassan6 min read

The short answer

A Webflow to Framer migration checklist covers three phases. Before launch: inventory every URL, export CMS and form data, rebuild, import and map redirects. On launch day: switch DNS, load redirects in Framer's settings, submit the sitemap and test forms. For 30 days after: watch Search Console, fix 404s and keep Webflow active until assets are confirmed.

Key takeaways

  • Start with a full URL inventory. Every redirect, metadata check and crawl depends on it.
  • Download Webflow form submissions and CMS CSVs before you change anything.
  • Load redirects into Framer's redirects settings before DNS switches, not after.
  • Check localized slugs and metadata for every locale, not just the default language.
  • Keep the Webflow plan running for weeks after launch, until every image is confirmed on Framer.

Part of Webflow to Framer Migration: The Complete Guide (Pages, CMS, SEO and Redirects)

What goes on a Webflow to Framer migration checklist?

A Webflow to Framer migration checklist has three parts: pre-launch preparation, launch-day switching and a 30-day watch. Most traffic losses after a move come from skipping the first and third parts, not from the build itself.

Use this list alongside our Webflow to Framer migration guide, which explains each phase in depth, and how to migrate from Webflow to Framer in 9 steps for the build order. Copy the items into your project tool and assign each one an owner.

What should you check before migrating from Webflow?

Before migrating, capture everything the Webflow site does and holds: URLs, metadata, CMS content, form data, assets, scripts and integrations. If it isn't on the list, it won't be on the new site.

  1. Crawl the live site and export every URL, title, meta description, canonical and status code.
  2. Pull top pages from Search Console for the last 12 months, so you know which URLs matter most.
  3. Export every CMS collection as CSV, and keep the raw files untouched.
  4. Download form submissions from Webflow, because they stay behind when the site goes.
  5. List custom code, tracking scripts, cookie tools and third-party embeds per page.
  6. List integrations: CRM forms, newsletter tools, chat widgets, scheduling links.
  7. Note what doesn't export: interactions, Webflow Ecommerce and memberships each need a plan.
  8. Decide what not to move: thin, outdated or duplicate pages, each with a redirect target.

Webflow's code export won't help with any of this, since it leaves out the CMS. We explain why in exporting Webflow code.

What should you check during the Framer build?

During the build, check that structure, content and SEO fields match the plan, page by page. These checks are cheap during the build and expensive after launch.

  1. Page paths match the old URLs wherever possible, including CMS collection paths such as /blog/.
  2. CMS fields map correctly, including references and rich text, as in our Webflow CMS to Framer CMS mapping.
  3. Images are hosted by Framer, including images inside rich text, not hotlinked from Webflow's CDN.
  4. Titles, descriptions and social images are set for every static page and on CMS templates.
  5. Locale slugs are translated where needed, and each locale has its own metadata.
  6. Forms send to the right inbox or CRM, with spam protection and a success message.
  7. Staging isn't indexed, so the Framer preview domain doesn't compete with your live site.
  8. Speed and accessibility pass a check on mobile, using our Core Web Vitals fixes.

What should you do on launch day?

On launch day, freeze content, load redirects, switch the domain and test the live site within the first hour. Do it early in the week, never right before a weekend or a campaign.

  1. Freeze and sync content

    Stop edits in Webflow, import any items published since the last export and recheck counts.

  2. Load redirects in Framer

    Add every 301 from your redirect map in Framer's site settings. Test a sample on the staging domain if possible.

  3. Connect the domain

    Update DNS records as Framer's custom domain setup describes, then confirm SSL is active on both www and the root domain.

  4. Test the critical paths

    Submit every form, click the main CTAs, check analytics events and open the top 20 URLs from Search Console.

  5. Submit the sitemap

    Add the Framer sitemap in Google Search Console and request indexing for the homepage and key pages.

What should you check in the 30 days after migrating?

In the 30 days after migrating, watch for 404s, indexing drops and broken assets, and fix each within a day. Rankings usually wobble a little after any move; problems that persist point to a missing redirect or a changed page.

  1. Day 1 to 3: crawl the live site and fix any 404s, redirect chains or missing metadata.
  2. Week 1: check Search Console coverage and the pages report for new errors.
  3. Week 2: compare clicks and impressions for your top pages against the weeks before launch.
  4. Week 3: check backlinks to old URLs still resolve, and update the most valuable ones at the source.
  5. Week 4: confirm every image and file loads from Framer, then cancel the Webflow site plan.
What to do if traffic drops sharply after launch

A small dip is normal. A large, lasting drop usually has one of four causes: missing or wrong redirects, pages accidentally set to noindex, changed titles and copy on pages that ranked, or the staging domain being indexed instead of the live one.

Work through them in that order. Pull the top 50 URLs from the old crawl and test each one. Check the robots settings and the page source for noindex tags. Compare old and new titles on top pages. Search for your brand name to see which domain appears. Our research found community threads where traffic fell sharply after a domain move, and the pattern behind them is almost always URL mapping.

How do you run this checklist as a team?

Run it as a shared sheet with one owner per item and a date, and keep the URL inventory as the master tab. Every other check points back to it.

Our general website launch checklist covers items that apply to any launch, and the website redesign checklist adds the audit work if you're redesigning at the same time. If you'd rather hand the whole thing over, our guide to hiring a Webflow or Framer migration agency covers what to ask before you sign, and Webflow to Framer migration cost covers budgets.

Frequently asked questions

Do I need to tell Google I moved from Webflow to Framer?
Not if the domain stays the same. Google sees the same URLs served by a new host. Submit the new sitemap and watch coverage reports. The Change of Address tool in Search Console is only for moving to a different domain. If paths change, 301 redirects are how you tell search engines where each page went.
Does Framer support 301 redirects?
Yes. Framer lets you add redirects in the site settings, mapping an old path to a new path or external URL. Add them before you switch DNS, so visitors and crawlers never hit a 404. For large sites, check whether your plan supports wildcard or pattern rules, which save writing hundreds of individual redirects.
What happens to my Webflow forms data after migrating?
Submissions stored in Webflow stay in Webflow, and you lose access when the site plan ends. Export them as CSV before you cancel. If forms already send data to a CRM or email tool, that history is safe there. Rebuild forms in Framer or embed your CRM's form, then test every one on the live domain.
How long should I keep my Webflow site after launch?
Keep the Webflow site plan for at least a few weeks after launch. Images inside old rich text, PDFs and other files may still load from Webflow's CDN, and you'll want the old site as a reference when checking content. Cancel only after a full crawl confirms nothing on the new site loads from Webflow.
Can I migrate from Webflow to Framer without downtime?
Yes. Build and test on Framer's staging domain, then switch DNS when everything is ready. DNS changes spread over minutes to hours, and during that window some visitors see the old site and some the new one, which is fine if both are live. Freeze Webflow edits shortly before, so no content is lost in the gap.

· CEO & Design Director

Copywriter, designer and developer, and founder of Designify Studio. Over five years, 60+ projects across 14+ industries, for startups that have raised $300M+.

Want this done for you? Website, $8,000.

A multi-page marketing site, designed by us, developed in Next.js and animated. $8,000, one-time, up to 6 pages. Book a free 30-minute call to see if it fits.

Schedule Call