From Framer to Webflow
Moving from Framer to Webflow: CMS, Pages and Rankings Done Right
Key takeaways
- Moving from Framer to Webflow pays off mainly when the CMS hits its limits, because according to the pricing pages Framer Pro allows 2,500 CMS items in 10 collections, while Webflow Premium allows 20,000 items in 40 collections.
- Rankings are preserved when every old URL points to the matching new URL with a 301, set in Webflow under Site settings, Publishing, 301 redirects.
- The design is rebuilt in Webflow, content comes in through CSV import and redirects through a clean mapping table.
- Webflow recommends no more than 1,000 redirect rules, so folders are combined with wildcards.
- If your Framer site is small, rarely grows and works well, you don't need to move. We check page count, collections, languages, editors and growth plans.
Short answer: Moving from Framer to Webflow makes sense when your CMS, your page count or your editorial process hits the limits of your Framer plan. You rebuild the design in Webflow, the content goes into the CMS via CSV import, and every old URL gets a 301 redirect to its new target. That way rankings and backlinks stay intact. When you are better off staying with Framer is covered further down.
Who should switch?
Framer is a strong tool for landing pages and small to mid-sized company sites. Problems usually show up only once the website grows. Typical triggers for a move:
- The CMS is no longer enough. According to the pricing pages (as of October 31, 2026), Framer Pro offers 2,500 CMS items in 10 collections and 150 pages, expandable for an extra fee up to 700 pages, 40 collections and 40,000 items. Webflow Premium includes 20,000 CMS items in 40 collections (Framer Pricing, Webflow Pricing).
- Many languages or many editors. Both providers charge for localization and additional seats. If you have several languages and a larger team, run the numbers for both plans with your real figures.
- Complex relationships between content. Integrations, use cases, industries and features that reference each other need a reliable CMS with carefully planned reference fields.
- A wish for more control over motion and interaction. Webflow documents interactions based on GSAP with scroll triggers and reduced-motion variants (Webflow: Interactions).
- A team or agency that already works in Webflow. A single stack then saves effort in maintenance and further development.
For a detailed comparison of the two systems, see the guide Webflow or Framer.
When you should stay with Framer
A move is work and carries risk. Stay with Framer if:
- your website is small, such as a landing page or a compact site, and stays far from the plan limits,
- a team member enjoys maintaining the site in Framer and does so confidently,
- you don't plan additional languages, collections or editors,
- the site ranks and converts well. In that case the numbers argue against a rebuild, not for it.
"I find Webflow more interesting" is not a reason to migrate. The limits of your current plan are.
What gets carried over and what gets built new
| Bereich | Was passiert | Hinweis |
|---|---|---|
| Design und Layout | wird in Webflow neu aufgebaut | In der Framer-Hilfe ist kein Export als Webflow-Projekt beschrieben, ein HTML-Export zum Selbsthosting wird dort ausdrücklich verneint. Das ist die Chance, Struktur und Komponenten sauber neu zu planen. |
| Texte und Seiteninhalte | werden übernommen und bei Bedarf bereinigt | Doppelte oder veraltete Inhalte können zusammengeführt werden. |
| CMS-Collections | Export aus Framer, Import per CSV in Webflow | Felder werden zugeordnet, Referenzen und Bilder gesondert geprüft. |
| Bilder und Dateien | werden übernommen und für Webflow optimiert | Dateien lassen sich nicht per CSV importieren und werden hochgeladen. |
| Meta-Daten und Alt-Texte | werden übernommen | Titel, Beschreibungen, Alt-Texte, Open-Graph-Bilder. |
| URLs | bleiben möglichst gleich, sonst 301-Redirects | Jede alte URL bekommt ein Ziel. |
| Animationen | werden als Webflow Interactions neu gebaut | Effekte sind Design-Entscheidungen und keine 1:1-Kopie. |
| Formulare und Tracking | werden neu angebunden und getestet | Consent, Analytics, CRM-Anbindung. |
How a migration typically works
This is how it typically goes, similar to a migration from WordPress to Webflow.
1. Inventory. We crawl all URLs of your Framer site and record which pages exist, how they rank, which backlinks point to them and which forms and tracking scripts are running. Without this inventory there is no safe migration. The checklist for it is in the guide CMS Migration Checklist.
2. Structure and plan. For every old URL we define a target: keep, merge, redirect or remove. At the same time we plan the new structure, above all the CMS collections and their fields.
3. Design and build in Webflow. If the look should change, we start with moodboards and the first three sections in Figma. Development starts only after you approve (more on this on the process page). If the design stays, it is recreated cleanly in Webflow.
4. Content transfer. Copy, images, meta data and CMS entries move into the new site. Blog posts and other collections go into the CMS via CSV import.
5. Launch and SEO protection. We set the redirects, submit the sitemap, check Search Console and monitor indexing and error pages after go-live. Launch includes a personal training session so your team can maintain the site.
How does the CMS move work technically?
The route is unspectacular, but it has pitfalls.
Export from Framer. According to Framer's help center, CMS content can be exported as CSV or JSON via plugins (Framer Help: Porting your data from Framer). The "CMS Export" plugin in the marketplace exports a collection as CSV (Framer Marketplace). How complete the export is for your fields is something to test on one collection beforehand. If it has gaps, the fallback is a script or manual transfer.
Import into Webflow. Webflow imports CSV files into collections. According to Webflow's help center, the following applies (Webflow Help: Import into the CMS):
- The file can be at most 4 MB, and the number of importable items depends on the site plan.
- Rich text fields expect HTML, images come in as URLs, and multiple images are separated by semicolons.
- Files can't be filled via CSV and are uploaded manually.
- Reference fields are matched by name or slug, and multiple values are separated by semicolons.
- Images from CSV don't generate responsive variants, so we upload optimized images separately.
- If a required reference field is empty or has no match, the item ends up as a draft.
One point that often gets overlooked: image URLs in the export point to Framer hosting. If the old Framer site is deleted, those links break. That's why images are moved to Webflow before the old site is switched off.
How do rankings stay intact?
Google describes the process of a site move with URL changes like this: map all old URLs to the new ones, redirect server-side with 301 or 308, submit a sitemap, monitor (Google: Site move with URL changes). For Framer and Webflow, that means in practice:
- In Framer, redirects are under Site Settings, Hosting, Redirects, with placeholders for entire folders. If a path changes in the canvas or in the CMS, Framer does not adjust the redirects automatically (Framer Help: Redirects).
- In Webflow you create 301 redirects under Site settings, Publishing, 301 redirects. Webflow recommends no more than 1,000 rules and advises using wildcards to keep the file small. Redirects refer to the root domain, and localized slugs need their own rules (Webflow Help: 301 redirects).
- Same domain? Then often only a few URLs change. The goal is to keep paths 1:1 so that hardly any redirects are needed.
- Changing domain? Then you set up redirects at the hosting of the old domain. Framer can only redirect subpaths within the current domain.
What matters is that after go-live you actively monitor indexing, error pages and rankings. A complete checklist is in the guide CMS Migration Checklist.
Typical pitfalls in a Framer move
From migrations in general and from both providers' help pages, a few spots emerge where things tend to snag:
- Image URLs in the export. They point to Framer hosting. If you switch off the old site too early, the new CMS ends up with broken images.
- Changed paths. If a subpath changes in the canvas or in the CMS, Framer does not adjust the redirects automatically. So for the mapping, crawl the live state, not the plan in your head.
- Localized paths. Framer offers localization with separate page paths per language (Framer Help: Localization). In Webflow, localized slugs need their own redirect rules, for example one for /old-url and one for /en/old-url.
- Code components and effects. Custom code components from Framer have no direct counterpart in Webflow. Their function is rebuilt in Webflow with interactions, components or custom code.
- Forms and tracking. They are often tied to third-party services. After the move they are reconnected and verified with a test lead.
- References between content. If integrations, industries or authors are linked through references, these have to be rebuilt in Webflow as reference fields. Webflow matches them during import by name or slug.
Checklist before the move
- [ ] All URLs of the Framer site are recorded, including CMS pages and language variants
- [ ] For every URL it is decided: keep, redirect, merge or remove
- [ ] The domain's Search Console is set up, and rankings and clicks are saved as a baseline
- [ ] All CMS collections, fields and references are documented
- [ ] Images and files are stored locally or secured for the import
- [ ] Forms, tracking and consent are inventoried
- [ ] The Webflow project is finished and tested except for the domain
- [ ] The switch date is chosen so that there is time to monitor afterward
What to check after launch
The most important phase begins after the domain switch. Check indexing in Search Console, crawl the site for 404 errors and redirect chains, compare rankings and clicks with the baseline, and test forms and tracking with a test lead. Google recommends keeping redirects in place permanently after a move wherever possible (Google: Site move with URL changes). Switch off the old Framer site only when images, files and redirects are safely in the new system.
What does the move cost and how long does it take?
A flat number would not be credible, because the effort depends on a few factors:
| Faktor | Wirkung auf Aufwand |
|---|---|
| Zahl der Seiten und Collections | mehr Inhalte bedeuten mehr Zuordnung und Prüfung |
| Zahl der CMS-Items | große Collections brauchen Bereinigung und gestaffelten Import |
| Neues Design oder Abbild des bestehenden | ein Redesign braucht Konzept- und Designphase |
| Sprachen | jede Sprache braucht eigene URLs, Slugs und Redirect-Regeln |
| Formulare, CRM, Tracking | jede Anbindung wird neu aufgebaut und getestet |
| Zustand der Altseite | gewachsene Seiten haben mehr Altlasten |
On request, after a short conversation and a look at your project, we give you a concrete range. For orientation on the ongoing costs of both platforms, the guide Webflow or Framer helps, and the guide Webflow and WordPress: Running Costs shows general operating costs compared with WordPress.
How we do it
Webwavers (founded in 2021) is one of seven Webflow Premium Partners in Germany and also delivers projects in Framer, WordPress, TYPO3 and headless. That's why we advise neutrally on the choice of system. In a migration we take care of the inventory, structure, the build in Webflow, content transfer, redirects and the checks after launch. You can find our awards under Awards and our projects under Work. You get a dedicated project manager as your contact, and at launch there is a personal training session.
Frequently asked questions
Will I lose my rankings when I switch from Framer to Webflow? Not necessarily. What matters is that every old URL points to the matching new URL with a 301, that titles, descriptions and headings are carried over, and that you monitor indexing and error pages after launch. Google expects temporary fluctuations with any move.
Can I simply import my Framer site into Webflow? Not as a finished project. Framer's help center describes neither an export as a Webflow project nor an HTML export for self-hosting. The layout is rebuilt in Webflow. CMS content, on the other hand, can be transferred via CSV, and copy and images are carried over.
What happens to my CMS collections? They are exported, cleaned up and imported into Webflow collections. Along the way we map fields and check references, images and rich text. Files are uploaded manually.
How many redirects can I create in Webflow? Webflow sets no hard limit, but recommends no more than 1,000. For larger sites we combine folders with wildcards.
Can my team maintain the site on its own after the move? Yes, with the right role in Webflow and some onboarding. The guide Maintaining Your Webflow CMS Yourself explains how it works.
Is the move worth it for a small landing page? Usually not. As long as the site is small, works well and doesn't reach the plan limits, a move is effort without payoff.
Talk about your move
Want to know whether switching makes sense for your site? Write to us through the contact page. We'll look at your Framer site and tell you honestly whether a move is worth it or whether you're better off staying.
Sources
- Framer: Pricing
- Webflow: Pricing
- Webflow: Interactions und Animationen (Interactions and animations)
- Webflow Hilfe: Import ins CMS (Help: Import into the CMS)
- Webflow Hilfe: 301-Redirects (Help: 301 redirects)
- Framer Hilfe: Redirects (Help: Redirects)
- Framer Marketplace: CMS Export Plugin
- Framer Hilfe: Daten aus Framer übernehmen (Help: Porting your data from Framer)
- Framer Hilfe: HTML-Export und Selbsthosting (Help: HTML export and self-hosting)
- Google: Seitenumzug mit URL-Änderungen (Site move with URL changes)
- Webwavers: Process
- Webwavers: WordPress to Webflow
Last updated on October 31, 2026.
