How to Migrate From Webflow to Framer Without Losing SEO

Teams usually move from Webflow to Framer so marketers can build and change pages without a developer. Webflow sites are easier to move than most, because the content already sits in structured collections and the URLs are usually clean. Four things still don’t move by themselves: CMS collections, interactions, form endpoints and redirects. This guide covers each one. For the checklist that applies to any platform, read how to migrate your website without losing SEO.

We build on both Webflow and Framer, so part of the job is checking that the move makes sense at all.

Check the fit first

Framer suits marketing sites that a marketing team edits every week. A few Webflow setups need a closer look before you commit:

• Ecommerce or memberships. If the Webflow site runs a store or member logins, those need a platform built for them. We don’t build online stores in Framer.
• Heavy CMS logic. Many collections with nested references, filters and conditional visibility can move, but build one template in Framer first to test it.
• Webflow API automations. Anything that writes into the Webflow CMS from another tool needs a new home.

Step 1: Inventory the site

• URLs. Start with Webflow’s sitemap at /sitemap.xml, then crawl the site and export the Performance report by page from Search Console. Together they show every URL and which ones earn traffic.
• Collections. List each collection with its fields, field types, item count and template path.
• Existing redirects. Copy every rule from Webflow’s 301 redirects list in the site settings, under Publishing. These move too.
• Interactions and custom code. Note every interaction, embed and script, including tools like Finsweet Attributes.
• Forms and integrations. List each form, where it sends data and every automation it triggers.

Step 2: Export CMS collections as CSV

Webflow exports each collection as a CSV file from the CMS panel. Framer’s CMS imports CSV, so the content moves table by table.

• Match the field names. Framer only imports columns whose names match a field in the collection, and it needs a unique Slug column. Rename the headers in the spreadsheet before you import.
• Rich text. Webflow exports rich text as HTML, which is the format Framer’s importer expects.
• Webflow’s own columns. The export adds item IDs, dates and archived and draft flags. Drop the IDs and filter out archived items unless you want them back.
• Images. The export lists images as links to Webflow’s file hosting. Re-host them in Framer, so the new site doesn’t depend on the old account.
• References. Check reference and multi-reference fields after import, so every post still links to the right author, category or related item.
• File limits. Framer wants UTF-8 files under 5 MB, so split large collections into batches. Re-importing with the same slugs updates existing items.

Step 3: Rebuild interactions

Webflow interactions don’t export. Framer has its own tools: appear, hover and scroll effects, scroll-linked animation and component variants. Treat the rebuild as an edit. Keep the interactions that explain the product or guide the eye, and drop the decorative ones that slow the page down. Webflow add-ons such as CMS filters and load-more lists need a Framer equivalent, either a collection list setting or a small code component.

Step 4: Keep slugs and folder paths

Webflow serves static pages in folders, such as /solutions/fintech, and CMS items under the collection path, such as /blog/post-name. Framer supports both patterns. Pages can sit in folders, and CMS pages live at a path you choose, such as /blog/:slug. For most Webflow sites, nearly every URL can stay exactly the same, and a URL that stays the same needs no redirect.

Check the details: collection paths match, slugs are identical including case, and localized pages keep their language folders. If a collection path does change, for example from /post/ to /blog/, a single wildcard redirect covers the whole folder.

Step 5: Move the 301 redirects into Framer

Build one map with three columns: old URL, new URL, status. It holds two kinds of rows.

• Old Webflow rules. Every existing 301 moves across. Point each one straight at its final page, so a link that already passed through one redirect doesn’t pass through two.
• New changes. Every URL that changes in the move gets a row that sends it to its closest match.

In Framer, add the rules under Site Settings, Hosting, Redirects. Use * to match a folder and :1 to reuse the matched part, so /post/* can send to /blog/:1. Rules apply when you publish, and you drag them to set priority. Renaming a page or collection path later doesn’t update existing rules, so update the map whenever a path changes. Framer redirects work on paths within your own domain. If the domain changes too, set the domain-level redirect at the old host. Also check that your Framer plan supports the number of redirects you need.

Step 6: Replace Webflow form endpoints

Webflow forms submit to Webflow’s own form handler, and Webflow sends the notification emails. Once the domain points at Framer, that handler is out of the loop, and everything triggered by a Webflow form submission stops with it: Zapier or Make scenarios, CRM syncs and Slack alerts.

• Rebuild each form. Use Framer’s native forms, which send to email or a webhook, or embed your CRM’s own form. On Lava’s Framer site, forms feed straight into Customer.io.
• Re-point automations. Every zap or scenario that used the Webflow form trigger needs the new source.
• Export old submissions. Download past submissions from Webflow before you close the account.
• Test with real data. Send a test through every form before launch.

Step 7: Carry over metadata and code

Recreate the SEO title, description and Open Graph image for every static page in Framer’s page settings. On CMS templates, bind the title and description to collection fields, as Webflow did. Move every script from Webflow’s head and footer code: analytics, consent, verification tags and any JSON-LD schema. Then check that canonical tags point at the live domain.

Pre-launch checklist

• Crawl both sites. Compare the Webflow and Framer crawls for missing pages, titles and descriptions.
• Check the map. No chains, and no redirect pointing at a missing page.
• Indexing is on. The new site can be indexed and robots.txt allows crawling.
• Search Console access. Verify the domain through DNS, so the property keeps working after the switch.
• Forms and tracking. Every form tested, with analytics and conversion events firing.
• Keep the Webflow project. Leave it in place until the post-launch checks are done.

Post-launch checklist

• Day one. Run every old URL through a crawler. Each should return a 301 to the right page, then a 200. Submit the new sitemap in Search Console and in Bing Webmaster Tools, since ChatGPT search and Copilot lean on Bing’s index. Inspect your top pages with URL Inspection and request indexing.
• First week. In the Search Console Pages report, watch Not found (404), Redirect error and Duplicate without user-selected canonical. Every 404 with traffic or links gets a redirect.
• Weeks two to four. Compare clicks and impressions on your top pages against the baseline from step 1. Some movement while Google recrawls is normal. A page that keeps falling usually has a broken redirect or lost metadata.

A realistic timeline

Most of our builds ship in 2 to 6 weeks. A Webflow move with clean collections can sit at the shorter end, since the content is already structured.

• Week one. Inventory, fit check, collection exports and the redirect map.
• The middle weeks. Design and build, CMS import, interactions and forms.
• The final week. Metadata pass, crawl comparison, redirects loaded, launch.
• Two weeks after launch. Search Console checks and fixes, covered by included support.

Several languages or heavy integrations push the project toward the longer end. Here’s how we run Webflow to Framer migrations from start to finish.