Migration
Webflow to Framer
CMS Collections come across as CSV and the design is redrawn in Framer. Matching CMS paths and a permanent redirect for each changed URL protect the traffic.
Trusted by teams from pre-seed to the S&P 100
What moves, and what gets rebuilt
Each part of the site, what it becomes, and whether it comes across, needs converting or is rebuilt.
WebflowCollections, each exported from the CMS panel as its own CSV, archived items included
CMS contentNeeds convertingFramerFramer CMS collections, fields made first, then filled by CSV matched on column name
WebflowPages, classes and components built in the Webflow Designer
Pages and designRebuiltFramerPages and components drawn again on the Framer canvas; no import route is documented
WebflowWebflow Interactions, which leave only as JavaScript inside a code export
InteractionsRebuiltFramerFramer effects, component variants or custom code, rebuilt one at a time
WebflowAssets on Webflow’s servers, listed in each CSV as Webflow-hosted URLs
Images and filesNeeds convertingFramerImages fetched by URL during import; files and images inside rich text re-hosted by hand
WebflowCollection items at /collection-url/item-slug; redirects under Site settings, Publishing
URLs and redirectsNeeds convertingFramerCMS pages on a path you set, such as /blog/:slug; redirects under Site Settings, Hosting
WebflowTitles set per page and template, a sitemap switch and a canonical URL you enter
Search settingsNeeds convertingFramerTitles site-wide or per page; the sitemap and canonical tags are generated for you
WebflowWebflow forms, with submissions kept under Site settings, Forms
FormsRebuiltFramerFramer forms that send to email, Google Sheets or a webhook; old entries exported first
WebflowWebflow site search and Ecommerce, plus any gated pages run by a separate membership service
Search, store and loginsRebuiltFramerFramer’s Search component; a store only through third-party plugins; the membership service reconnected
Moving from Webflow to Framer, step by step
What Webflow’s CSV holds, how fields map to Framer’s CMS, the rebuild, the redirects, the checks, and the sites that should stay on Webflow.
Why teams move from Webflow to Framer
The usual reason is a small team in which designers do most of the work on the site. In Framer they lay out a page on a canvas and publish it the same day, with no class system to keep tidy and no developer to wait for.
Editing changes too. On Framer, people with content permission edit text, images and CMS content on the live page and can add CMS pages, on the Content Editor seat Framer introduced in May 2026. That editing stops at layout templates and overlays, which go back to a designer. Framer also generates the sitemap and the canonical tags from the connected domain, where Webflow has you switch the sitemap on and type in a canonical URL.
The move suits a site of a few dozen pages with a blog and some case studies. It does not suit a site whose value is a growing body of content. Some reasons do not hold up: the platform will not lift your rankings, and a Webflow site that feels slow usually carries heavy images and scripts that would come with you.
Neither vendor offers a conversion. Framer’s own guide to this move has you rebuild the structure, the layouts and the interactions, and import the CMS content by CSV.
What Webflow lets out, and what Framer takes in
Webflow releases content one Collection at a time. In the CMS panel, open a Collection and click Export for a CSV of every item, archived ones included, or select items first to export only those. The file holds the locale you are viewing, so a localised site exports once per locale. Rich text comes out as HTML, a reference as plain text, a multi-reference as a comma-separated list, and images and files as URLs on Webflow’s servers. Webflow warns that those URLs break if the site is deleted, so keep it until Framer holds every asset.
Webflow’s code export, on a paid Workspace plan, is a ZIP of HTML, CSS, JavaScript and images. It is useful for collecting assets and reading the old markup, which is all Framer’s guide uses it for. Webflow leaves the CMS content, forms, site search, Ecommerce and localised content out of it.
Members-only pages are a separate job. Webflow closed its own User Accounts on 29 January 2026, so a Webflow site that still gates content does it through a separate membership service. That service comes with you or is replaced, whichever platform the site is on. Check that it works with Framer before you plan the rebuild.
Framer’s CMS takes CSV from the Import button in a collection. It matches columns to fields by name and ignores any column with no field, so build the collection first and name the CSV headers after its fields. Framer downloads images from absolute URLs in the file, which is how the images leave Webflow’s servers. Rich text has to be HTML, which is what Webflow writes. Dates need ISO 8601 and true or false must be lowercase, so check those columns in a spreadsheet first. The slug is the key: import a corrected file and Framer updates the items with matching slugs instead of adding copies.
Framer also offers an AI-assisted first build of pages and CMS content through its MCP server. Its guide still has a person compare the result with the old site, and we would too.
How Webflow fields map to Framer’s CMS
Framer’s CMS has collections, fields and CMS pages, much as Webflow has Collections, fields and Collection pages. Most Webflow field types have a match. Create these in Framer before the first import:
- Name, Slug and Plain text become text fields. Keep the slug column exactly as Webflow wrote it, because it decides each address.
- Rich text becomes a formatted text field. Images placed inside the body still load from Webflow until you re-host them and update the links.
- Image becomes an image field. Multi-image becomes a gallery in Framer, and we did not find how the CSV importer fills one, so test a few items or add those images by hand.
- Option becomes an enum field, with its choices defined in Framer before the import. Switch becomes a boolean field, written as lowercase true or false.
- Email, Phone and Video have no field of their own. Use text for email and phone, a link field for the video URL, and rebuild the player on the CMS page.
- File arrives as a Webflow URL. Download each file, upload it to Framer and point the field at the new copy.
- Reference and Multi-reference become Framer’s single and multi-reference fields.
Import the referenced collections first, as Framer’s guide says: authors and categories before posts. Webflow writes a reference as the item’s plain text, and we did not find what Framer’s importer expects in a reference column. Import ten posts and check every reference before importing the rest. If they arrive empty, bring the column into a text field and set the references by hand, which is Webflow’s own advice for moving references between projects.
Count the items in each Collection before choosing a plan. Framer caps collections, items and pages by plan, and a large blog or resource library can reach the cap by itself.
The order of work
We work in this order, and it suits a team doing the move on its own:
- Inventory. Pull every URL from Webflow’s /sitemap.xml and add the pages that earn visits or links in analytics and Search Console. List each Interaction, form, embed and script as you go.
- Redirect map. Put each old address in a spreadsheet with its Framer address beside it, including the ones that will not change, so the launch test covers them all.
- Content model. Create the Framer collections and fields from the mapping, set each CMS page path to the old Collection URL, and import ten items from each CSV.
- Rebuild. Draw the pages and CMS page layouts on the Framer canvas, turn repeated sections into components, and rebuild each Interaction as an effect, a variant or code.
- Content. Import the full CSVs with referenced collections first, upload the files, re-host images inside rich text and connect each form to its destination.
- Checks. Fill in titles and descriptions, test forms, search and internal links, and compare every important page with its Webflow original.
- Launch. Add the redirects, connect the domain in Framer and add its DNS records, publish, test the redirect map on the live domain and submit the sitemap in Search Console.
- Watch. For several weeks, follow the pages Google reports as not found and the visits to the pages that mattered most, add rows for what the map missed, and only then close the Webflow site.
A large site can go across in stages. Framer documents a page-by-page migration in which it serves the pages already built and hands other requests to the old site, and says to check that your account can use the Advanced Hosting it needs.
Keeping URLs, redirects and search
This pair is easier on URLs than most. A Webflow Collection item sits at its Collection URL and slug, such as /blog/post-name. Framer lets you set a CMS page’s path, so /blog/:slug gives the same address as long as the slugs come across unchanged. Static pages can keep their paths as well. Done this way, most rows of the redirect map need no redirect.
Redirects cover the rest: merged pages, dropped posts and renamed slugs. Framer keeps them under Site Settings, Hosting, Redirects, and treats them as permanent. An asterisk matches a path segment, :1 and :2 carry matched parts into the new address, and :slug names a segment. Framer’s SEO guide says redirects import in bulk as a CSV with from and to columns, so export Webflow’s redirect list as CSV and merge it into the map. They work only within the one domain. We did not find a cap on their number in Framer’s documentation, and its help article does not say which plan includes them, so check yours.
A localised site needs more care. Webflow’s redirects do not apply to its locale paths, and we did not find in Framer’s help how its locale addresses are built. Settle that before you write the rows for each language.
Titles and descriptions can be set for the whole site and per page, and CMS fields can fill them on CMS pages. Where Webflow’s SEO titles were Collection fields, import those columns and bind them on the CMS page; static page titles are copied by hand. Structured data goes in through custom code as JSON-LD.
We inventory valuable URLs, plan redirects and check canonicals, indexability, content and internal links. We also monitor after launch. These steps manage migration risk; they cannot guarantee that rankings will stay unchanged. Expect some movement in the first weeks while Google recrawls the site.
When this site’s own addresses changed, we matched each old address by hand to the page that replaced it and used permanent redirects, with no wildcard rule. Where nothing replaced a page, it returns a 404, and nobody is sent to the homepage instead.
Checks before you switch the domain
Work through these on Framer’s preview address, then repeat the redirect checks once the domain points at Framer:
- Each Framer collection holds as many items as the Webflow CSV it came from.
- Five CMS pages opened at random show every image served by Framer, with no Webflow asset address left in the rich text.
- Reference and multi-reference fields show the right authors, categories or related items on a sample of pages.
- Files linked from the CMS are uploaded to Framer and the links open the new copies.
- Each CMS page path matches its old Collection URL, or the redirect map covers the change.
- Every rebuilt Interaction plays as intended on a phone and a laptop, and the page still works with reduced motion switched on.
- Each form delivers a test entry to its destination, and the old Webflow submissions are downloaded as CSV.
- The Search component, after a publish, returns results from the pages and collections it should.
- Every page and CMS page meant for search has its own title and description, and none is set to stay out of search.
- Each old address in the map, typed into a browser on the live domain, reaches its new page with a single redirect.
- Analytics and consent scripts are in Framer’s custom code and recording visits.
- The Webflow site is still published or backed up, and its CSVs, redirect list and assets are saved somewhere you control.
When to stay on Webflow
A Webflow site that works for its team is rarely worth rebuilding in Framer, and some are worse off after the move. Stay on Webflow if:
- Marketing publishes every week into several content types that reference and filter one another. Webflow’s CMS goes further for that kind of site.
- The content is close to Framer’s plan caps on collections, items or pages, or will be within a year.
- Marketers build new pages themselves. Framer’s on-page editing changes content and adds CMS pages, and stops short of layout templates.
- More than 10 people edit. Framer’s self-serve plans allow 10 editing seats in a workspace.
- The site sells through Webflow Ecommerce. We found no store built into Framer, so a third-party plugin would carry your checkout.
- Posts are scheduled ahead. Webflow can schedule an item’s first publish on its higher Site plans, and we did not find scheduled publishing in Framer’s documentation.
- You may want the site’s code one day. Webflow exports it on a paid Workspace plan. Framer says it may not be the right tool if you need source code, and its CMS content leaves only through plugins.
- The complaint is the Designer’s class system. Tidying the classes and an afternoon of training for the editors cost far less than a rebuild.
Teams whose site is turning into a content operation usually make the opposite move, and its guide sets out what that involves.
What decides the time and the cost
Drawing the layouts again takes most of the time. Count the distinct layouts: twelve landing pages built from three layouts go quicker than six that each differ. A CMS page layout is one piece of work however many items it shows.
Interactions are the cost people miss. A site with scroll-driven sequences on every page takes far longer than one with hover states, because each sequence is rebuilt by hand. The CMS work grows with the fields that have no match, the reference fields and the images inside rich text. A store or a second language each bring a system to replace on top of the pages, and a membership service has to be connected again.
Our websites start from $15,000, and most take four to eight weeks. We price a migration as a website project, on the page system, content work, integrations, publishing requirements and migration complexity, and settle scope and price with you before work begins. We work on any platform; we have no published Framer project to show you.
Doing it yourself, the costs are Framer’s site plan, its editor seats and any Localization add-on, on Framer’s pricing page, and the hours of whoever rebuilds and checks the site. Keep the Webflow plan running until the watch period is over.
We checked the vendor details against Webflow’s and Framer’s own help pages and guides on 15 November 2026. Plans and features on both change often: confirm them before you commit.
Moving from Webflow?
Short answers, from the guide above.
Not the design. Neither Framer nor Webflow documents a way to bring Webflow pages, classes or interactions into Framer, and Framer’s own guide says to rebuild them. The CMS content can come across: export each Collection from Webflow as CSV and import it into a Framer collection whose fields match. Framer also offers an AI-assisted first build through MCP, which a person still checks page by page.
Nobody can promise every position holds, and a dip while Google recrawls is normal. We inventory valuable URLs, plan redirects and check canonicals, indexability, content and internal links. We also monitor after launch. These steps manage migration risk; they cannot guarantee that rankings will stay unchanged. On Framer, set each CMS page path to the old Collection URL, so most addresses need no redirect.
Most of our website builds take four to eight weeks, and we scope a migration as a website project. The number of distinct layouts decides most of it, because each one is drawn again in Framer. Interactions add time one by one. A store, a second language or a membership service to reconnect take longer still, because each is a system to replace or wire up again as well as pages to rebuild.
Usually, yes. A Webflow Collection item lives at its Collection URL plus its slug, such as /blog/post-name. In Framer you set a CMS page’s path yourself, so /blog/:slug gives the same address if the slugs come across unchanged. Static pages can keep their paths. Anything that does change gets a permanent redirect under Site Settings, Hosting, where wildcards and named segments work.
Interactions are rebuilt as Framer effects, component variants or code. Site search becomes Framer’s Search component, which indexes the published pages. We did not find a built-in store in Framer’s documentation: selling comes from plugins by third parties, listed in its Marketplace. If the store carries the business, that is a reason to stay on Webflow, or to move to a platform built for it.
Where to go next
- Framer vs WebflowFramer if a design-led team wants to launch fast and keep shipping pages. Webflow if a marketing team will run a growing, structured site.
- WordPress to WebflowPosts come across as CSV, pages and the design are rebuilt, and posts move under a folder. A 301 for each changed address protects the search traffic.
- Webflow to custom codePages are written again as components, CMS content leaves as CSV or through Webflow’s API, and a permanent redirect for each changed URL protects search.
Planning this move?
Tell us where it is now and where it is going. We’ll say what we’d keep, what we’d rebuild and how long it takes.
Most teams start with a call, then a sprint or an audit.
The people you’d work with, from the first call to launch