Move your site from Framer to Webflow
A plan for moving a growing site to Webflow when its content, team or technical needs have outgrown Framer. We carry the pages across and redirect every URL that changes.
When the move makes sense, and when it doesn’t
Move to Webflow if:
•
Your CMS is outgrowing Framer, with more collections, more items and more references between them.
•
Developers now own the site and want class-based styles that map directly to CSS.
•
You need Webflow features such as Ecommerce, workflows built on the CMS API, or a static code export, which comes with paid Workspace plans.
•
Your content team works best inside a fixed structure, with limited editing rights.
Stay on Framer if:
•
Designers publish changes every week and that speed matters to marketing.
•
The site is mostly marketing pages and sits comfortably inside Framer’s limits.
•
The real problem is the design or the message. A redesign in Framer may fix it for less.
What moves over and what gets rebuilt
Pages
Rebuilt in Webflow. Framer components, variants and effects are recreated as Webflow classes, components and interactions.
CMS content
Exported from Framer to CSV or JSON with a CMS export plugin, then imported into Webflow collections. Reference fields are linked again after import, and rich text is checked item by item.
SEO and redirects
We carry over titles, meta descriptions, Open Graph images and slugs for every page and CMS item. Redirects are set up in Webflow’s 301 redirect settings or imported as one CSV file.
Forms
Rebuilt with Webflow forms, or with the form tool you already use, and connected to the same destination.
Integrations
Scripts for analytics, consent and chat are added back. Framer plugins are replaced with Webflow apps, embeds or custom code.
Code components
Custom React components built for Framer need a new approach in Webflow, such as custom code or Webflow’s code components, which bring React components into Webflow.
Media
Images, video, fonts and files are downloaded and uploaded to Webflow, so nothing depends on the old Framer site.
The plan, step by step
01
Site review
We list every live URL and check Search Console and analytics to see which pages bring traffic, leads and backlinks.
02
Content inventory
Every page, collection, field, form, script, plugin and file goes into one sheet, each marked keep, merge, rewrite or retire.
03
Redirect map
Each old URL gets its new address. Paths stay the same wherever Webflow’s URL structure allows. Retired pages point to the closest relevant page, since search engines can treat a redirect to the homepage as a missing page.
04
Rebuild
We set up the class system and components in Webflow, build the templates, then import the CMS.
05
QA
We check every page on desktop and mobile, test every form and interaction, compare metadata against the inventory and test the redirects before launch.
06
Launch
We publish, switch the domain to Webflow, confirm the redirects are live and submit the new sitemap in Search Console.
07
Post-launch checks
For the period agreed in the scope, we watch Search Console for 404s, crawl errors and changes in indexed pages, and fix anything that slipped through.
Risks and how we avoid them
Rankings
Some movement is normal while Google recrawls a moved site, and Google says new URLs can take a few weeks or more to show. Keeping URLs the same where possible, and using permanent redirects for the rest, gives search engines the clearest signal.
Broken links
Webflow builds CMS URLs from the collection’s slug and the item’s slug, which may differ from your Framer paths. Every difference goes into the redirect map. Webflow’s redirect CSV import replaces all existing redirects, so we keep one complete file and import it once. Google recommends keeping redirects for at least a year.
CMS limits
Webflow’s Basic site plan has no CMS, and the Premium plan caps it at 40 collections and 20,000 items. We size the plan to your content before the build starts.
Motion that doesn’t translate one to one
Most Framer effects can be rebuilt with Webflow interactions, but some will look slightly different. We flag those during QA, before launch.
How we handle it
We design in Figma and build in Webflow and Framer, so we know both platforms’ strengths and limits. Daniel G. Bright leads strategy, creative direction and every relationship, and specialist designers and developers handle production and builds. For Arteway, an online art school taught from working artists’ studios, we designed the brand and the website, then built the site in Webflow.
We scope and price each move as a flat-fee website project, agreed in writing before work starts. If Framer still suits you, we’ll say so.
Questions
Daniel G. Bright
Founder, BrightStudios
Still have a question?
Book a call with me to talk through your project and agree the next step.
Keep exploring
Webflow to Framer
For teams whose designers want to publish changes themselves.
WordPress to Framer
For marketing sites where every change waits on a developer.
WordPress to Webflow
For content-led sites that want a hosted CMS with no plugin upkeep.
Wix to Framer
For companies that have outgrown a template and need a site built around the product.
Squarespace to Framer
For companies that need page types and design control beyond a template.
Wix to Webflow
For growing sites that need a structured CMS and full design control.
Squarespace to Webflow
For content-led sites that have outgrown their template.
Plan your move
Bring your current site to the call and tell us why you’re thinking of moving. We’ll tell you whether a move is worth it and what it involves.