There is no one-click way to move a Framer site to Webflow. Webflow's own Framer migration guide says "there's no automated way to convert a Framer site into a Webflow site," so the move is a rebuild: CMS content can travel as CSV files, copy and images come across by hand, and layouts, styles, components and animations are rebuilt in Webflow.
Below: what moves, the order to do it in, and the Webflow plans you'll pay for. If you're still choosing between the two platforms, read Framer vs Webflow first; this post doesn't repeat that comparison.
What carries over and what you rebuild
Moves across, with some work:
- CMS content. Framer's own CMS Export plugin can "export any CMS collection as a CSV file," and Webflow's CMS imports CSV files.
- Copy and images. Text is copied over. Images go into Webflow's Assets panel, or come in by URL during a CMS import.
- Redirects. Framer's Redirect Sync plugin exports your redirects as a CSV, and Webflow can import 301 redirects from a CSV.
- SEO text. Page titles, meta descriptions and Open Graph text are copied into Webflow's page settings by hand.
Rebuilt from scratch: page layouts and responsive behavior, color and text styles, components, effects and animations, forms, and code overrides (code components can be adapted rather than rebuilt; see step 5).
Does Webflow import anything useful?
Webflow's pricing FAQ is blunt about importing a site: "No, you can only develop websites in Webflow." Here is what does exist.
CMS import from CSV
The one real import path. Webflow accepts CSV files up to 4 MB and lets you map each column to a Collection field. How many items you can import depends on your site plan. Steps are in the plan below.
Figma to Webflow
The Figma to Webflow app, listed by Webflow Labs, syncs "components, variables, and styles" from Figma into Webflow. It works from Figma files, so it only helps if your Framer design started in Figma and you still have that file.
Pasting or embedding code
Webflow has no built-in HTML import, and its copy and paste is documented for moving elements between Webflow sites. The Code Embed element accepts HTML, CSS in <style> tags and JavaScript in <script> tags, up to 50,000 characters per embed. That suits a widget or a script, not whole pages: Framer says its published sites "are not fully static" because they depend on Framer's hosting services.
Third-party apps
Webflow's Apps marketplace lists a few import tools. None of their listings mention Framer.
- HTMLtoflow (by Creoglyph) says it can "convert raw HTML into Webflow elements" from HTML and CSS you paste into the app.
- PowerImporter syncs "Airtable, WordPress, CSV with Webflow CMS" and says it handles reference and multi-reference fields and uploads images and files.
Both listings show a free plan. Try them on a test site first.
A step-by-step migration plan
1. Inventory every page and URL
Framer automatically generates an XML sitemap, found by adding /sitemap.xml to your homepage URL. That's your list of every URL that must still work after the move. For each one, note the title, meta description, Open Graph tags and canonical tag, as Webflow's own checklist recommends.
While you're in Framer, also record:
- Your existing redirects (export them with the Redirect Sync plugin)
- Every form and where it sends submissions (Framer forms can send to email, Google Sheets or a webhook)
- Custom code, analytics and third-party scripts
- Fonts, and whether your license lets you use them on Webflow
- The animations on each page
2. Export your CMS collections
Run Framer's CMS Export plugin on each collection to get one CSV per collection. Open each file and check that image columns hold full image URLs, formatted text came through, and reference columns are filled in. Webflow's guide warns that, depending on your setup, Framer CMS content "may require manual extraction or recreation."
3. Import the CSVs into Webflow
Import collections that others point to first (authors, categories), then the collections that reference them. In the Designer, open the CMS panel, choose the Collection, click Import, drop in the CSV, confirm the header row, map each column, preview the items and click Import. Webflow offers to back up the site first, and lists any items that failed along with the reason.
Webflow's field rules decide what imports cleanly:
| Field type | What Webflow expects in the CSV |
|---|---|
| Name, slug | Plain text under 256 characters. Keep your Framer slugs so URLs don't change |
| Rich text | Any value, including HTML. Webflow may remove elements, classes and attributes it doesn't support |
| Image | A direct URL ending in a supported image extension. These images don't get responsive variants (srcset and sizes) |
| Multi-image | URLs separated by semicolons |
| Reference | The item's name or slug. A required reference that doesn't match imports as a draft |
| Option | Up to 100 unique values |
| Number | A plain number: no letters, symbols or commas |
| File | Nothing maps. Upload files by hand after the import |
Split any CSV over 4 MB. For large or repeated imports, Webflow's REST API can add, update and remove CMS items instead.
4. Rebuild the design system
Framer's color styles and text styles become Webflow variables (color, size, percentage, number and font) and classes. Webflow's guide suggests building the style guide first: color palette, typography, spacing, utility classes and reusable components. Add fonts by uploading files or connecting Google Fonts or Adobe Fonts.
5. Rebuild pages, components and interactions
Build global components first, then static pages, then CMS templates. Set each Collection URL to match the old Framer path. A Collection with the URL blog serves items at /blog/item-slug, and a template page can sit inside a parent folder for deeper paths.
Animations are the slowest part. Framer's effects run on Motion, a JavaScript and React animation library; Webflow uses Interactions with GSAP, or its older Classic Interactions. Nothing converts, and Webflow notes some Framer animations "may require redesigning interactions" or custom code.
Framer code components are React components, and so are Webflow's (imported through DevLink, on the Premium site plan), so that code can be adapted rather than retyped. Framer code overrides modify Framer elements; rebuild their behavior with interactions or custom code.
6. Rebuild forms
Recreate each form with Webflow's form element, then choose where submissions go: stored in Webflow, email notifications, webhooks, connected apps, or a custom action. Point any webhook or tool that received Framer submissions at the new form. The free Starter site plan caps a site at 50 form submissions in total.
7. Set SEO fields and 301 redirects
Set the SEO title and meta description for each page in Page settings, and the Open Graph title, description and image under Open Graph settings. Webflow can't set Open Graph tags globally, so every page needs its own. CMS template pages can fill these from Collection fields.
Add redirects under Site settings > Publishing > 301 redirects, singly or as a CSV with two columns (old path, new path), up to 16 MB. An import overwrites all existing redirects, so export first if you already have some. Before importing the file from Framer's Redirect Sync plugin, check that it has just those two columns (Framer's redirect CSVs use from and to columns and can carry an optional expandToAllLocales column) and that any wildcard rules use Webflow's (.*) and %1 syntax. A wildcard rule such as /old-collection-url/(.*) to /new-collection-url/%1 covers a whole folder. Redirects need a paid Site plan (for a free staging site, Webflow's pricing page lists them only with the Growth or Agency Workspace plan), and Webflow recommends no more than 1,000 as a best practice. Add them "before your domain cutover," as Webflow puts it.
8. Move the domain
In Webflow, go to Site settings > Publishing > Production, click Add a custom domain, and add your domain. This connects both the root domain and www. At your DNS host, delete the old A and CNAME records that point at Framer, then add the records Webflow shows for your site: an A record, a www CNAME and a TXT verification record. Copy them from that page; Webflow says they can differ between sites. Then click Verify domain and publish the site to the custom domain. Imported redirects also take effect only once you publish. Changes usually take effect within a few hours and can take up to 48 hours.
Launch checklist
- Every page checked on your
webflow.iostaging address at every breakpoint, before the DNS switch - Every URL from the Framer sitemap loads a page or redirects
- Titles, descriptions and Open Graph images match your inventory
- Forms deliver to the right inbox or tool
- Analytics and tag manager scripts are in Webflow's custom code settings
- The new sitemap is submitted in Google Search Console, and you're watching for 404s
- Only then end your Framer plan (see what happens when you stop paying for Framer)
Framer to Webflow feature map
| Framer | Webflow equivalent | How it moves |
|---|---|---|
| Pages and URL paths | Pages and folders | Rebuild; keep the same slugs |
| CMS collections | CMS Collections | CSV export and import |
| CMS page templates | Collection template pages | Rebuild; match the Collection URL |
| Text and images | Text elements, Assets panel | Copy and upload |
| Color and text styles | Variables and classes | Rebuild |
| Components | Components | Rebuild |
| Effects and animations | Interactions with GSAP | Rebuild |
| Code components (React) | Code components (React) | Adapt the code |
| Code overrides | Interactions or custom code | Rebuild |
| Forms | Webflow forms | Rebuild; repoint webhooks |
| Redirects | 301 redirects | CSV export and import |
| Page titles, descriptions, Open Graph | Page settings | Copy by hand |
| Custom code | Site or page custom code, Code Embed | Copy |
| Fonts | Uploaded fonts, Google Fonts, Adobe Fonts | Re-add; check licenses |
| Custom domain | Custom domain | DNS change at the end |
What it costs on Webflow
Webflow charges per site, in USD, plus tax. Prices as listed on webflow.com/pricing in November 2026:
| Site plan | Price | CMS | Good for |
|---|---|---|---|
| Starter | Free | 50 items, 20 Collections; webflow.io domain only; 2 static pages |
Testing an import |
| Basic | $15/mo billed yearly, $25 billed monthly | No CMS; 300 static pages; custom domain | Framer sites with no CMS |
| Premium | From $25/mo billed yearly, $39 billed monthly | 20,000 items, 40 Collections | Framer sites with a blog or any CMS |
Premium's price rises with the bandwidth you choose. A Framer site with a CMS needs at least Premium, since Basic has none.
Code export sits on paid Workspace plans, not Site plans: Freelancer is $16/mo billed yearly and Core is $19/mo billed yearly. Exported code leaves out CMS content, so Collection pages export empty.
Expect to pay for both platforms during the rebuild: the Framer site stays live until the DNS switch, and Webflow's free Starter plan allows only 2 static pages (a paid Workspace plan raises a staging site to 300 pages).
Should you migrate?
A rebuild is worth it when your team already works in Webflow or wants its CMS tools, Apps marketplace or code components. Code export is another real difference: Webflow's paid Workspace plans export HTML, CSS, JavaScript and assets, while Framer has no built-in export. Its self-hosting article says Framer "does not provide a way to export published sites as HTML files or static website bundles." A separate Framer article on porting your data says a site's published files can be downloaded and moved to any hosting provider, without naming a feature that does it, and Framer's marketplace lists third-party export plugins (see Framer export tools compared).
It's a weaker case if your main complaint is cost or lock-in. You'd swap one hosted builder for another with its own monthly plan, and pay for the rebuild on top.
Two options avoid the rebuild:
- Stay on Framer. If a plan limit is the problem, check Framer's plan limits first.
- Convert the published Framer site with FNJ. FNJ reads your live Framer URL and produces a Next.js project split into named React components, or static HTML, that you host on Cloudflare Pages, Vercel or anywhere else. Pages look and animate exactly as on Framer because Framer's runtime still loads from Framer's servers, along with fonts, so the Framer project should stay published. Forms need repointing to a service like Formspree or Tally, and password-protected pages can't be converted. FNJ is a paid tool (pricing). The trade-off: you get files to host yourself, and the site still depends on Framer's servers for its runtime and fonts.
For which platform is better overall, see the full Framer vs Webflow comparison.
Frequently asked questions
Can you import a Framer site into Webflow?
No. Webflow says there's no automated way to convert a Framer site, so layouts, styles and interactions are rebuilt by hand. Only CMS content and redirects move across, as CSV files.
How do I move Framer CMS content to Webflow?
Export each collection to CSV with Framer's CMS Export plugin, then import it from Webflow's CMS panel and map each column to a field. Each file can be up to 4 MB; import referenced collections, such as authors, first.
Which Webflow plan do I need for a Framer site with a blog?
The Premium site plan, from $25/mo billed yearly, which includes the CMS with up to 20,000 items. Basic has no CMS, and the free Starter plan allows 50 items on a webflow.io address only.
Will moving to Webflow hurt my Google rankings?
It can if URLs change without redirects. Keep your Framer paths where you can, add 301 redirects in Webflow for any that change before switching DNS, and watch Google Search Console for 404s after launch.
Do Framer animations carry over to Webflow?
No. Framer's effects run on the Motion library and Webflow uses Interactions with GSAP, so each animation is rebuilt by hand or with custom code.
Can I leave Framer without rebuilding in Webflow?
Yes. FNJ converts your published Framer site into a Next.js project or static HTML that you host, but Framer's runtime still loads from Framer's servers, so the Framer project should stay published.
Starting a new site instead? FNJ's AI website builder designs one from a description and a site you like, then gives you the code to host anywhere.