Framer to Webflow Migration Guide (2026) | Studio Huncho blog
Webflow and Framer

9 min readMINUTES

How to Migrate from Framer to Webflow: A Step-by-Step Guide

Arpit Agrawal, Co-founder and Design Director, Studio Huncho
Arpit Agrawal
November 22, 2026
Framer to Webflow Migration Guide (2026) | Studio Huncho blog

The short answer

To migrate from Framer to Webflow, audit every URL, export each Framer CMS collection as CSV with Framer's CMS Export plugin, download the images, rebuild the design, components and effects in Webflow, import the CSVs into Webflow collections, redirect any URL that changes and launch with SEO checks. Framer designs cannot be imported into Webflow, so the site is rebuilt. For a startup marketing site with a blog, the move usually takes a few weeks.

We are a Webflow Certified Partner and a Framer Expert, and we build in both for AI and SaaS startups. This guide is the process we follow when a team moves from Framer to Webflow. Last checked: 22 November 2026, against Webflow's help centre, Framer's plugin listing and docs, Webflow's pricing page and Google's site move guidance.

The seven steps at a glance

  1. Audit: list every URL, collection, component and effect on the Framer site.
  2. Map: match each Framer collection and field to a Webflow collection and field.
  3. Export: export each collection as CSV and download the images.
  4. Rebuild: build the style guide, components and templates in Webflow.
  5. Import and check: import a small batch, check it on the template, then import the rest.
  6. Redirect: write a 301 map for any URL whose path or slug changes.
  7. Launch: switch DNS, submit the sitemap and watch Search Console for 30 days.

Should you move from Framer to Webflow at all?

Framer is fast for designers and great for launch pages. Teams move to Webflow when the site grows into a content operation: a bigger CMS with references between collections, a marketing team that edits every day, localisation, more control over code and SEO, or an enterprise buyer asking about security and roles. If the site is small and the team is happy designing in Framer, staying is often the right call. Our Webflow vs Framer comparison and Is Framer good enough for Series A? cover the decision.

What moves from Framer to Webflow, and what does not

  • Moves as data: CMS collections, exported as CSV, plus images and files you download.
  • Has to be rebuilt: every page, component, variant and breakpoint. Webflow's Framer migration guide is clear that Framer designs, layouts and interactions cannot be imported.
  • Rebuilt differently: Framer effects and animations, which become Webflow Interactions, GSAP or custom code. Some need a rethink rather than a copy.
  • Replaced: code components and overrides, which become Webflow custom code embeds or are dropped, and Framer plugins, which need a Webflow app or custom code.
  • Checked: fonts. Confirm your licence covers Webflow, then upload the files or connect Google Fonts or Adobe Fonts.

How to get your content out of Framer

CMS collections: the CMS Export plugin

Framer's own CMS Export plugin exports any CMS collection as a CSV file, with a preview before you download. Run it once per collection. Then rename the columns to match the Webflow fields you planned, and check rich text, reference and image columns closely, because those are the fields most likely to need clean-up.

Large or complex collections: the plugin API

For collections with many references, a developer can read every collection and item through Framer's plugin API and write the data straight into the Webflow API. It takes longer to set up, but it keeps references between collections intact on large sites.

Images and files

Image columns in the CSV point at Framer's servers. Download those images, rename them, compress them and upload them to Webflow's Assets panel, then point the image fields at the new files. Do not rely on Framer-hosted images after the Framer site is unpublished.

The Framer to Webflow migration, step by step

1. Audit what you have

Make a spreadsheet of every URL on the Framer site: static pages, blog posts, collection pages, legal pages and anything that only shows up in search. Add each page's traffic and backlinks from Google Search Console or your SEO tool, its title and meta description, and the forms, embeds and scripts it uses. This sheet becomes your redirect map later.

2. Map your content to the Webflow CMS

Decide what becomes a static page and what becomes a CMS collection. Blog posts, case studies, team members, job openings and customer logos are usually collections. Write down the fields each one needs (title, slug, summary, body, cover image, author, category, SEO title, meta description) before you build anything, because the CSV you import has to match them column by column.

3. Get the content out of Framer

Export each collection with the CMS Export plugin, download the images and files, and rename CSV columns to match the Webflow fields. Note which fields are references to other collections, and import those collections first.

4. Import into Webflow and check a small batch

Create the collections in Webflow, then import the CSV into each one. Webflow's CMS import guide walks through matching columns to fields. Import five or ten items first, check them on the collection template, fix the mapping, then import the rest. Images in rich text need a second look, because links that point back at the old platform break once it is switched off.

5. Rebuild the design

Nothing visual imports into Webflow, so every page and template is designed and built again. Start with a style guide (colours, type, spacing, buttons), then build the global parts such as the navigation and footer, then the templates. Many teams keep the brand and use the rebuild to fix structure, speed and the pages that never converted.

6. Set up 301 redirects

Go back to the audit sheet and give every old URL a new home: the same page at its new path, the closest page if it was merged, or a parent page if it was cut. Add them in Webflow under Site settings > Publishing > 301 redirects (see Webflow's redirect guide). Redirect one hop only, from the old URL straight to the final one.

7. Run SEO checks and launch

Carry every title, meta description and Open Graph image across, check headings and alt text, and publish to the staging domain for a full pass at desktop, tablet and mobile sizes. Then add the redirects, switch DNS and submit the new sitemap. Google's site move guide is the reference for this part.

A worked URL mapping example

Framer and Webflow both put CMS items under a collection path, so many URLs can stay the same. Redirects are needed where paths change:

  • /blog/how-we-price-our-product stays the same if the Webflow collection slug is also blog
  • /resources/guides/onboarding redirects to /guides/onboarding, because Webflow CMS items sit one level under their collection
  • /case-studies/company redirects to /work/company if you rename the collection
  • /lp/campaign-name (a landing page you are not rebuilding) redirects to the closest live page

Webflow's redirect guide covers the syntax for one-off and wildcard rules.

Where each Framer setting lives in Webflow

  • SEO title and meta description: page settings for static pages, and CMS fields bound in the collection template's settings for posts.
  • Open Graph title, description and image: the same settings panels, with an option to reuse the SEO values.
  • XML sitemap: generated automatically under Site settings > SEO.
  • Robots.txt: edited under Site settings > SEO.
  • Redirects: Site settings > Publishing > 301 redirects.
  • Schema: custom code in page settings, or an embed in the CMS template that pulls in CMS fields.
  • Framer custom code (head and body): Site settings > Custom code, or a page's own settings.
  • Locales: Webflow Localization, with a subdirectory, subdomain or separate domain for each locale.

A realistic migration timeline

Most of our website projects take 2 to 6 weeks. For a startup marketing site with a blog, a migration usually breaks down like this:

  • Week 1: audit, URL inventory, content export, CMS structure.
  • Weeks 2 to 3: design of key pages and CMS templates.
  • Weeks 3 to 5: Webflow build, content clean-up and import, redirect map.
  • Final week: QA, SEO checks, launch and monitoring.

Hundreds of posts, several languages or content that has to be copied by hand add time. So does content that is rewritten rather than moved. We redesigned Itilite's website and rebuilt it on Webflow, and organic deals now land about 2.5x better.

Launch day and the first 30 days

  • Before DNS: publish to the staging domain, click through every template and test every form.
  • At cutover: add the 301 redirects first, then point DNS at Webflow, then publish to the custom domain.
  • Same day: submit the new sitemap in Google Search Console and test a sample of old URLs to check they land on the right page.
  • First 30 days: watch the Pages report for 404s and pages that drop out of the index, and fix redirects as they show up.
  • Keep the old site: leave the old plan running and a full copy of the content for at least a month before you cancel it.

Migration checklist

  • Every URL listed with traffic, backlinks, title and meta description
  • CMS collections and fields written down before the build
  • Content exported and a backup copy kept outside both platforms
  • Images downloaded, renamed and given alt text
  • Fonts licensed for use on Webflow
  • Five to ten items imported first and checked on the template
  • Forms rebuilt and test submissions received
  • Analytics and tag manager added in site settings
  • 301 redirect for every old URL with traffic or links
  • Staging site checked at desktop, tablet and mobile sizes
  • DNS TTL lowered a day before the switch
  • New sitemap submitted in Search Console on launch day
  • Each Framer collection exported with the CMS Export plugin
  • Effects and code components listed with their Webflow replacement

What mistakes should you avoid?

  • Trying to copy every effect: some Framer effects do not translate one to one. Decide which ones matter and rebuild those well.
  • Forgetting nested paths: Webflow CMS items sit one level under their collection, so deeper Framer paths need redirects.
  • Leaving images on Framer: re-upload them to Webflow before you unpublish the Framer site.
  • Breaking references: import referenced collections, such as authors and categories, before the posts that point at them.
  • Switching DNS before redirects are live: add redirects first, then point the domain at Webflow.

Migrate it yourself or bring in a Webflow partner?

A small site with a few pages and a short blog is a realistic do-it-yourself project if someone on the team knows Webflow. It gets harder with hundreds of posts, content that has to be copied by hand, several languages, or organic traffic you cannot afford to lose. That is when a team that has done it before earns its place, because the redirect map and the CMS structure are where most migrations go wrong.

We are a Webflow Certified Partner and design and build in Webflow for AI and SaaS startups. See our Webflow development service, or read what a Webflow partner does and the questions to ask before you sign.

Related reading: Webflow to Framer migration, WordPress to Framer migration, Webflow vs Framer for Startups (2026), How to Migrate from WordPress to Webflow, What is a Framer Expert?, How Do You Maintain a Webflow Site After Launch?, All Webflow and Framer guides

FAQ

Can you export a Framer site to Webflow?

Not the design. Framer layouts, components and interactions cannot be imported into Webflow, so they are rebuilt. CMS content moves across as CSV using Framer's CMS Export plugin.

How do you export Framer CMS content?

Use Framer's CMS Export plugin, which exports any CMS collection as a CSV file. For large sites with many references, a developer can read the collections through Framer's plugin API.

Can we keep the same URLs when moving from Framer to Webflow?

Often, yes. Both put CMS items under a collection path such as /blog. URLs nested more than one level deep, or collections you rename, need redirects.

Will moving from Framer to Webflow hurt our SEO?

Not if you keep the content, carry over titles and meta descriptions, and redirect any URL that changes. Expect some movement in rankings for a few weeks.

How long does a Framer to Webflow migration take?

A few weeks for most startup marketing sites. Many effects, code components or locales add time.

What happens to Framer effects and code components?

They are rebuilt with Webflow Interactions, GSAP or custom code embeds, or dropped if they no longer earn their place.

How many CMS items does Webflow allow?

It depends on the site plan. As of November 2026 the free Starter plan allows 50 CMS items and the Premium site plan allows 20,000, with custom limits on Enterprise.

Should we move from Framer to Webflow?

Move when the site needs a bigger CMS, daily editing by marketers, localisation or more control over code and SEO. Stay on Framer if the site is small and the team is happy designing there.

Sources

  1. pricing pagewebflow.com
  2. CMS import guidehelp.webflow.com
  3. redirect guidehelp.webflow.com
  4. site move guidedevelopers.google.com

Facts in this post were checked against these pages on 22 November 2026. Prices and plans change, so confirm current details on each site.

Studio Huncho rated 4.9 on Clutch
Need a brand, website or launch video for your startup?
One studio in Bengaluru for funded AI and SaaS startups. A scoping doc and timeline follow within 48 hours of a brief.
Ask AI about Studio Huncho

Thinking about moving from Framer to Webflow? Talk to us. We build in both through our Webflow and Framer development services.

Work with Studio Huncho

We're a creative studio for AI and SaaS startups. We design brands, websites, products and launch videos, and build sites in Webflow and Framer.

Link Copied Successfully
VIEW CASE STUDY