What moves automatically and what you rebuild
A Webflow to Framer move is a content transfer plus a rebuild, not a one-click conversion. Framer's own Webflow-to-Framer guide maps the concepts like this: Webflow classes become Framer styles, components or variables; Webflow components become Framer components; Collections become CMS collections; interactions become effects, variants or code; breakpoints stay breakpoints. Only the CMS content has a bulk path (CSV). Everything else is recreated in the Framer editor.
This guide is based on Webflow and Framer documentation and pricing pages read on 30 October 2026. We did not run a live migration for it. Treat the effort column as a planning estimate, not a measured time.
| Webflow item | Framer equivalent | How it moves | Planning note |
|---|---|---|---|
| CMS Collections and items | CMS collections and items | CSV export from Webflow, CSV import into Framer | Import referenced collections first, one collection at a time |
| Classes and combo classes | Text and color styles, components, variables | Rebuilt by hand | Set up styles before rebuilding pages |
| Components (main and instances) | Components and instances | Rebuilt by hand | Rebuild the header, footer and cards first; they repeat everywhere |
| Interactions (GSAP or Classic) | Effects, component variants or code overrides | Rebuilt by hand | Highest variance item; list every animation before quoting time |
| Breakpoints | Breakpoints | Rebuilt by hand | Webflow's tablet breakpoint covers 991px and below; recheck every layout |
| Forms, site search, localization, ecommerce | Framer forms or a third-party tool; Framer locales | Rebuilt or replaced | Webflow code export does not carry any of these |
| 301 redirects | Framer redirects | Re-entered; Webflow can export its redirects as CSV | Framer's pricing page lists redirects in the Pro plan summary; confirm for Basic |
Export the CMS: what the Webflow CSV actually contains
In Webflow, open the CMS panel, click the Collection name and click Export. You can also select specific items first. Webflow documents several details that matter for a migration: the export includes archived items, it only contains items from the current locale view, rich text fields export as HTML, reference fields export as plain text, multi-reference fields export as a comma separated list, and images and files export as Webflow-hosted URLs.
That last point decides your cancellation date. Webflow warns that if you delete the site, those asset links break, including images inside rich text fields. If Framer's import keeps pointing at a Webflow asset URL instead of storing its own copy, your blog images would vanish when the Webflow site goes. Check a few imported items in Framer: if any image still loads from a Webflow address, upload it to Framer before you shut anything down.
Framer's migration guide says to import one collection at a time, create referenced collections first, map CSV columns to fields, test a few representative items, and check slugs, dates, formatted text, images, files, options and references. It also advises testing long, short and missing values, because a template that looks fine with a 40-word excerpt can break with a 400-word one.
- Export one CSV per Collection and per locale, and keep the files as a dated backup.
- Archived items are in the export; delete those rows before import unless you want them live again.
- Rich text arrives as HTML: open two long posts in Framer and check headings, lists and embedded images.
- Reference fields export as plain text, so import the referenced collection (authors, categories) first and check every link.
- Spot-check every image field after import and re-upload anything still served from Webflow.
Webflow code export: useful for assets, not for content
Webflow code export is a paid Workspace feature, not a Site plan feature. On 30 October 2026 Webflow's pricing page listed code export on the Core Workspace plan at $19 a month billed yearly. If you only need the export for one migration, you may be able to upgrade the Workspace for a single billing period, but check Webflow's refund terms first: its cancellation article states that Webflow purchases are nonrefundable.
The ZIP contains HTML, CSS, JavaScript and images, but Webflow states that Collection items are left out (collection lists show their empty state), ecommerce and checkout do not work, forms and site search do not work, and only the primary locale is included. So the export helps you collect image files and inspect the original markup. It does not save you any CMS or form work, and you cannot paste the HTML into Framer as a working site.
Interactions and other features with no direct equivalent
Webflow now has two interaction systems. Interactions with GSAP is the default and uses a trigger, target and action model with a timeline, stagger, split text and scroll triggers. Classic interactions is the older system, and Webflow lists some things only Classic can do, such as navbar, dropdown, tab and slider change events and page branching. Find out which system each animation on the old site uses before estimating, because neither one imports into Framer.
In Framer, most entrance animations become Appear effects, which Framer can trigger on appear, on scroll direction, when a layer reaches a trigger point, or when a section is in view. Hover and press states belong to component variants. Anything more custom becomes a code override, which is a small React function. Framer notes that overrides are not active on the canvas, only in preview and on the published site, so they are harder for a non-developer client to maintain.
| Webflow feature | Likely Framer route | Effort and risk |
|---|---|---|
| Fade or slide in on scroll | Appear effect with a scroll or in-view trigger | Low; rebuild per section |
| Button hover state | Component variant with a hover state | Low once the button component exists |
| GSAP timeline with stagger or split text | Effects where possible, otherwise a code override | Medium to high; budget developer time |
| Classic tab, slider or dropdown change events | Component variants or a code override | Medium; test on phone sizes |
| Webflow forms | Framer forms or a third-party form tool | Medium; retest delivery, spam protection and integrations |
| Webflow site search | A third-party search embed or no search | Decide before quoting; Framer's guide says the export does not recreate it |
| Webflow Localize locales | Framer locales (pricing page: $20 per locale add-on, up to 20) | Medium; re-import each locale CSV |
| Webflow Ecommerce | A separate commerce platform linked or embedded | High; plan it as its own project |
Map redirects before the domain moves
If your Framer slugs match the Webflow slugs, you need no redirect for those pages. Redirect only changed or removed paths, send each old URL to the closest relevant new page, and avoid chains where A goes to B goes to C. Webflow can bulk export its existing 301 redirects to CSV, so pull that file first: the old site may already be redirecting URLs from an even earlier site, and those rules need to survive.
In Framer, redirects live in Site Settings under Hosting. A * matches the rest of a path, even across several segments, captured parts can be reused with :1, :2 and so on, and named segments such as :year can be matched. Framer only redirects sub-paths within the connected domain, so if the domain itself changes, the old-domain redirect has to be set up wherever the old domain is hosted. On 30 October 2026 Framer's pricing page listed site redirects in the Pro plan summary; check its comparison table to confirm your chosen plan includes them before you rely on them.
| Old Webflow URL | New Framer URL | Rule type |
|---|---|---|
| /blog/post-slug | /blog/post-slug | None needed; same path |
| /post/post-slug | /blog/post-slug | Wildcard: /post/* to /blog/:1 |
| /services/web-design | /services | Single redirect; page merged |
| /team/old-member | /about | Single redirect to closest relevant page |
| /old-landing (already redirected on Webflow) | Final destination only | Carry over without creating a chain |
Cutover day and when to cancel the Webflow Site plan
Test the Framer site on its Framer address first: routes, internal links, forms, page titles, the 404 page, sitemap.xml and robots.txt. Then, in Framer, go to Site Settings, Hosting, Domains, choose to connect a domain you own, and add the records Framer shows. For an apex domain that is two A records and one CNAME for www; Framer warns that no other A or AAAA records should remain on the domain. Framer says DNS changes can take up to 48 hours to propagate, though usually less.
Framer's guide says to keep the Webflow project available until the new site and redirects have been checked on the production domain. Webflow's rules make a gentle exit easy: downgrading a paid Site plan to the free Starter plan normally takes effect at the end of the current billing period, at which point custom domains are removed and the site is unpublished. Choosing Downgrade now removes the domains and unpublishes immediately. Lower paid plans take effect immediately, and Webflow purchases are nonrefundable, so schedule the downgrade near the renewal date rather than early.
A sensible order is: cutover, verify for a week, confirm no image or file in Framer loads from a Webflow URL, then downgrade to Starter at period end. You keep editing access to existing Collection items on Starter but cannot add more, which is fine for an archive.
| Plan (pricing pages, 30 Oct 2026) | Listed price | Why it matters in the move |
|---|---|---|
| Webflow Basic Site plan | $15/mo billed yearly | No CMS; typical for brochure sites |
| Webflow Premium Site plan | $25/mo billed yearly | Includes Webflow CMS; what most blogs pay |
| Webflow Core Workspace plan | $19/mo billed yearly | Needed only if you want code export |
| Framer Basic | $10/mo | 30 pages, 2 CMS collections, 1,000 CMS items |
| Framer Pro | $30/mo | 150 pages, 10 collections, 2,500 items; staging and redirects listed |
Questions before you decide
Does the Webflow CSV export include images?
It includes image and file fields as Webflow-hosted URLs, not the files themselves. Webflow warns that if you delete the site those asset links break, including images in rich text, so confirm Framer stores its own copies before you delete or unpublish the Webflow site.
Can I use Webflow code export to move CMS content?
No. Webflow states that exported code leaves out Collection items, so collection lists show their empty state, and forms, site search and ecommerce do not work. Code export also needs a paid Workspace plan. Use the per-Collection CSV export for content.
When should I cancel my Webflow Site plan?
After the Framer site and redirects are verified on your domain and no image loads from Webflow. Downgrading to Starter normally takes effect at the end of the billing period, while Downgrade now unpublishes immediately, and Webflow says purchases are nonrefundable.
Do Webflow interactions carry over to Framer?
No. Framer's guide maps interactions to Framer effects, variants or code, so each one is rebuilt. Appear effects cover most scroll and entrance animations; complex GSAP timelines may need a code override.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Framer: Webflow to Framer step-by-step guide Accessed 30 Oct 2026
- Webflow Help: How do I import content into the Webflow CMS (import and export of Collection items) Accessed 30 Oct 2026
- Webflow Help: How do I export my Webflow site code Accessed 30 Oct 2026
- Webflow Help: Downgrade or cancel your Site plan Accessed 30 Oct 2026
- Webflow Help: How do I set up redirects in Webflow Accessed 30 Oct 2026
- Webflow Help: Interactions with GSAP vs Classic Interactions Accessed 30 Oct 2026
- Webflow pricing Accessed 30 Oct 2026
- Framer Help: How to set up redirects Accessed 30 Oct 2026
- Framer Help: How to connect a custom domain Accessed 30 Oct 2026
- Framer Academy: Appear effect Accessed 30 Oct 2026
- Framer pricing Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.