Plan your move from Framer to Webflow
Move your Framer site to Webflow with the content, design and integrations planned together. I rebuild the layouts, map the CMS and reconnect the tools your team uses, keeping existing URLs where practical.
- Content export
- CMS collections export to CSV with a Framer plugin. Pages are rebuilt.
- Rebuilt in Webflow
- Layouts, Framer effects and code components.
- Biggest risk
- Animations that don’t translate one to one, and CMS paths that change.
- The look stays
- The design can be rebuilt closely, from the live site or the original files.
Is the move worth it?
Why teams move from Framer to Webflow
A CMS for a growing content team
Collections with references and multi-references, a template per collection and content-editing roles for writers.
Separate design and content roles
Writers publish content without touching layouts, and designers keep control of the system.
Integrations and apps
Forms connected to CRMs, a Marketplace of apps and a full API for content.
A design system for larger sites
Variables, components and classes keep many pages consistent as more people build them.
When staying on Framer is the better call
Framer is quick for design-led sites and has its own CMS. If the site is small, the team designs in Framer every day and publishing works, there isn’t a strong reason to move. Prove the specific gap first: a content workflow, permissions or an integration.
What moves
Where each part of the Framer site goes
Everything is listed before anything moves. This is how each kind of content usually maps; your inventory decides the final plan.
| On Framer | In Webflow | How it gets there |
|---|---|---|
| Pages | Static Webflow pages | Rebuilt from the live site or the original Figma or Framer files. |
| CMS collections | Webflow collections | Exported to CSV with a Framer CMS export plugin, then imported. |
| Rich text and CMS images | Rich text and image fields | Images uploaded to Webflow, so nothing depends on Framer’s hosting. |
| Components and variants | Webflow components with properties | Rebuilt as reusable components. |
| Effects, scroll and hover animations | Webflow interactions | Rebuilt, starting with the ones that matter most. |
| Code components | Webflow code components or custom code | Compatible React components can be adapted and imported through DevLink. Framer-specific dependencies, overrides and APIs may need rewriting. |
| Forms | Webflow forms | Rebuilt and connected to email or your CRM. |
| Localized pages | Webflow Localization | Rebuilt per locale, keeping the same URL pattern where possible. |
Rebuilt rather than moved
- Layouts and breakpointsFramer’s stacks and breakpoints are rebuilt with Webflow’s layout tools and classes.
- Page transitions and effectsSome Framer effects need custom interactions or a simpler alternative.
- PluginsFramer plugins are replaced with Webflow apps or integrations.
Step by step
How to move a Framer site to Webflow
Before the move
Prove the reason to move
Test the missing workflow in Webflow with the person who will use it.
List pages, collections and effects
Note which animations matter most and which can be simplified.
Export the CMS
Each collection to CSV, with images saved locally.
Write the redirect map
Every changed URL against its replacement.
The move
Rebuild the design system
Variables, classes and components matching the Framer design.
Import the collections
A sample with the longest and most complex item first, then the rest.
Rebuild interactions
Hero, navigation and scroll effects first, then the details.
Review on staging
Side by side with the Framer site, on desktop and phone.
After the move
Connect the domain
Point DNS at Webflow and publish the redirects.
Submit the sitemap
Then watch Search Console for 404s.
Check animations on real devices
Especially on slower phones.
Hand over
A walkthrough of the CMS and components for the team.
Search traffic
Keeping your rankings through the move
Google treats a migration as a site move. These are its rules, then the risks that are specific to Framer.
What Google asks for
- A permanent (301) redirect from every changed URL straight to its closest replacement, with no chains.
- No redirecting old pages to the home page in bulk. Pages with no replacement return a 404 or 410.
- Redirects kept for at least a year, and a new sitemap submitted in Search Console.
- Some ranking movement is normal while Google recrawls. On a medium-sized site it can take a few weeks or more to settle.
The migration SEO checklist lists every check before, during and after the move.
If traffic drops anyway, these are the checks to run.
CMS paths
Framer CMS pages use the collection’s path, such as /blog/post-name. Matching the Webflow collection slug keeps them.
Titles and social images
Copy each page’s title, description and social sharing image.
Locale prefixes
If the site is localized, keep the same locale prefixes so each language keeps its rankings.
Sitemap and canonicals
Check the Webflow sitemap includes every page and each template sets a canonical.
Your part
What your team does during the move
One person who decides
Someone who can approve the content structure, what gets retired and the final sign-off.
A short content freeze
Publishing pauses on the old site between the final content import and launch, usually a few days. Anything urgent in that window is added to Webflow by hand.
A staging review
Your team clicks through the staging site, checks the content and submits every form before the domain switches.
What you provide
- Framer access
- Access to the domain and DNS
- The original design files, if you have them
- Search Console access
Questions about the move
Can I export my Framer site?
For a Webflow migration, the CMS content is exported through an available export plugin, and the layouts and components are rebuilt in Webflow. That creates an editable Webflow site rather than importing the published website as a finished project.
Will the animations look the same?
Most can be rebuilt closely with Webflow interactions. A few Framer effects need custom code or a simpler version, and those are agreed before the build.
Why move from Framer to Webflow?
Usually for the CMS, editing roles or integrations as the site and content team grow. If Framer covers what you need, staying is fine.
Will I lose SEO?
Not if URLs are kept where possible, every change gets a 301 redirect and titles and descriptions move with the content.
Can we keep designing in Figma?
Yes. New pages can be designed in Figma and built in Webflow from the same components.
How long does the move take?
It depends on the number of pages and posts, how many features need replacing and how much content needs cleaning. The first step is an inventory of pages, posts, forms and integrations, and the estimate follows from it. Nothing is estimated before that list exists.
Moving to Webflow
Move the site without losing pages or rankings.