Migration
Framer to Webflow
CMS collections leave Framer as CSV through a plugin, every page and animation is rebuilt, and a 301 for each changed CMS path protects 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.
FramerCollections of items, exported one at a time as CSV or JSON by a plugin
CMS collectionsNeeds convertingWebflowWebflow Collections filled from CSV, with references matched by name or slug
FramerWeb pages, CMS page templates and components laid out on the Framer canvas
Pages and componentsRebuiltWebflowStatic pages, Collection templates and components built again in the Webflow Designer
FramerAppear, scroll and hover effects built on Motion, plus any React code components
Animations and effectsRebuiltWebflowWebflow Interactions with GSAP, or custom code where an effect has no match
FramerImages in CMS fields and on the canvas; fonts chosen or uploaded in Framer
Images and fontsNeeds convertingWebflowCMS images pulled in by URL; canvas images and licensed font files uploaded by hand
FramerCMS page paths set by hand, such as /blog/:slug, and redirects in Site Settings
URLs and redirectsNeeds convertingWebflowEach Collection under one folder, a 301 for each changed path, old rules merged in by CSV
FramerA sitemap and canonical tags made for you, and a site-wide title and description
Search settingsNeeds convertingWebflowThe sitemap switched on, a global canonical URL entered, a title on each page
FramerFramer forms that send to email, Google Sheets, a webhook or HubSpot
FormsRebuiltWebflowWebflow form blocks with notifications, or a connector to the same tools
FramerYour domain, pointed at Framer’s hosting
DomainComes acrossWebflowThe same domain, connected to Webflow once everything else is ready
Moving from Framer to Webflow, step by step
What leaves Framer and in what form, how its field types land in Webflow, what happens to the animations, the paths and redirects, the checks, and who should stay on Framer.
Why teams move from Framer to Webflow
The usual story is a launch site that turned into a content operation. It started as a few pages and a blog that a designer could build in a fortnight. A year later there are case studies, a resources library, a team page, events and a changelog, each its own collection, and marketing wants to publish into them every week without waiting for the designer.
Framer starts to strain in three places. The plan caps how many collections, items and pages the site can hold. A workspace on the self-serve plans stops at 10 people with edit access. Its on-page editing lets a content editor change text, images and CMS items on the live site, but layout templates and overlays stay with a designer. Webflow’s CMS is made for more structure: collections that point at each other through up to 10 reference fields, a content editor role in which the design cannot be touched, and imports and exports by CSV whenever the content needs a bulk change.
Some reasons will not carry the move. Webflow will not rank the site higher, and the move puts every CMS address at risk for a while. A design refresh is quicker in Framer. If what you need is logins, an app or parts shared with your product, Webflow is the wrong destination and custom code is the one to look at.
Webflow’s own Framer guide says it plainly: no tool converts a Framer site, and the designs, layouts and interactions cannot be imported. You rebuild the site in Webflow with the Framer one open beside it as the reference.
What Framer lets out, and what Webflow takes in
Framer has no export button for the CMS. Its help centre says CMS content leaves through plugins, as CSV or JSON, and Webflow’s guide warns that some Framer setups need the content extracted or recreated by hand. Choose CSV, because that is what Webflow imports. Export one collection at a time and open each file before you import it, since what a plugin writes decides most of the work ahead.
The design does not leave in any form Webflow can use. Framer’s help articles disagree about whether a published site can be downloaded as files, and for this move it makes no difference: Webflow imports neither HTML nor Framer projects. Framer’s asset export saves a selected layer or page as a PNG or JPG, which is fine for an icon and no way to collect a whole image library. Take canvas images from your design files or the original folders.
Two more things come out cleanly. Framer’s Redirect Sync plugin exports every redirect you already have as a CSV of from and to paths. And the sitemap Framer publishes for every site is the start of your list of URLs.
On the Webflow side, the CMS takes a CSV of up to 4 MB into one Collection at a time, and you map each column to a field. Images arrive from their URLs and get no responsive variants, so export them at the size the template will show. Fonts do not travel with anything: Webflow’s guide asks you to confirm each font’s licence, then upload the files, connect Google Fonts or Adobe Fonts, or choose a replacement.
How Framer fields map to Webflow fields
Each Framer collection becomes a Webflow Collection, and each Framer CMS page becomes that Collection’s template. Most field types have a direct match. Map them like this:
- Slug: Framer’s export example puts it in the first column. Map it to Webflow’s Slug field, so every item keeps its slug.
- Plain text maps to plain text, and the title to Webflow’s Name field.
- Formatted text maps to rich text. It exports as HTML, which Webflow accepts, though it may strip elements and attributes it does not support.
- Image maps to an image field, as a direct URL. The export example writes the alt text in a separate column, and we did not find a way in Webflow’s import documentation to map that column to an image’s alt text. Import it as plain text and bind it in the template, or enter it by hand.
- Gallery maps to a multi-image field, with the URLs separated by semicolons. Framer’s export example leaves galleries out, so collect those URLs another way or rebuild them in Webflow.
- File maps to a file field, which takes nothing from a CSV. Upload each file by hand after the import.
- Toggle maps to a switch field, which takes any column with two values.
- Option maps to an option field. Each distinct value becomes an option, up to 100.
- Color maps to a colour field, which takes colour names, hex codes with a # in front, or RGBA. Framer also allows HSL, so convert those values first.
- Number, date and link map to number, date and link fields. A number with a comma in it will not import.
- Reference and multi-reference map to reference and multi-reference fields. Webflow wants the referenced item’s name or slug, with semicolons between several. The export example joins multi-references with commas, so change them before you import.
Import the collections that others point at first. If a required reference finds no match, Webflow imports the row as a draft and leaves the field empty, so count the drafts after each import. The export also marks Framer drafts in a column of their own: decide whether they come across before you map it.
The order of work
This is how we run a Framer to Webflow move, and the order works as well if you do it yourself:
- Inventory. List every URL in Framer’s sitemap, add the pages Search Console and analytics show bringing in visits or links, and note every animation and effect page by page.
- Redirect map. Export Framer’s existing redirects with Redirect Sync, then write each old CMS path beside its new Webflow address in one spreadsheet.
- Content model. Create the Collections and fields from the mapping, then import ten rows of each collection and open every field.
- Rebuild. Set up the fonts, colours, type and classes, build the components, then the static pages and Collection templates, then the interactions, on the staging address.
- Content. Import the full CSVs, referenced Collections first, then upload the files, add the galleries and paste in the static page copy.
- Checks. Set each page’s title and description, the canonical URL and the sitemap, and test the forms and internal links on staging.
- Launch. Import the redirects, publish, and only then move the domain’s DNS from Framer to Webflow, which is the order Webflow’s guide gives. Submit the sitemap in Search Console.
- Watch. Read Search Console’s not found report and the old top pages’ traffic for several weeks, and add a redirect for each address the map missed.
Paths, redirects and search
In Framer you set each CMS page’s path by hand, such as /blog/:slug or /resources/guides/:slug. In Webflow every item lives under its Collection URL, which Webflow describes as the slug for one folder. Where the Framer path is one folder deep, give the Collection the same URL and the item addresses stay as they were. Where it is deeper, check whether Webflow can match it before you plan on it. If it cannot, the items move, and one wildcard rule can usually carry them: /resources/guides/(.*) to /guides/%1. Static pages can keep their paths and sit in folders, which Collection items cannot.
Framer’s exported redirects need rewriting before Webflow takes them. Framer writes wildcards as *, and Webflow uses capture groups, (.*) in the old path and %1 in the new. Webflow runs redirects oldest first, a CSV import replaces every existing one, and redirects need a paid Site plan or paid Workspace. A path that a live Webflow page still answers cannot be redirected until that page is unpublished or re-slugged. Webflow also lowercases page slugs and strips punctuation, so a Framer path with capitals needs its own row.
Translated sites need more rows. Framer can translate page paths and CMS slugs for each locale, and Webflow’s redirects do not apply to localised paths, so every translated address needs its own rule.
Framer did several search jobs for you that Webflow leaves as settings. Switch on the sitemap and enter the global canonical URL, since Webflow adds no canonical tags until you do. Framer let a site-wide title and description cover any page without its own; Webflow has no site-wide setting, so give every page and template a title and description. JSON-LD added through Framer’s custom code moves into each page’s schema field.
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. Some movement in the first weeks while Google recrawls the site is normal.
When this site’s addresses changed, we mapped each old address by hand to the page that replaced it, used permanent redirects and wrote no wildcard rule. Pages with no replacement return a 404 instead of sending people to the homepage.
Checks before you move the domain
Work through these on the staging site, then repeat the redirect checks once the domain points at Webflow:
- Each Webflow Collection holds as many published items as its Framer collection, and no row was left as a draft by an unmatched reference.
- Every gallery, file and multi-reference field that the export skipped or changed has been filled in.
- Open five items from each Collection: their images load from Webflow, and none still points at Framer.
- Rich text bodies keep their headings, links and embedded images.
- Each font is licensed for the new site and renders on every breakpoint.
- Each animation on the inventory has been rebuilt or deliberately dropped.
- Every static page and Collection template has its own title and description.
- The sitemap is switched on and the global canonical URL matches the live domain exactly.
- Each row of the redirect map, Framer’s old rules included, lands on the right page in one hop.
- Each form has a name, notifies a named person or tool, and a test entry has arrived.
- Analytics and tag scripts are in the site-wide custom code and recording visits.
- Every inbox, sheet or CRM that Framer’s forms fed now gets entries from the Webflow forms, or has been retired on purpose.
- The Framer site stays published until the Webflow one is live on the domain.
When to stay on Framer
Plenty of Framer sites should stay where they are. Keep yours on Framer if:
- The site is still a set of pages and a blog, and the designers who built it keep it current. Framer is the quicker tool for that, and a rebuild buys nothing.
- The motion is the brand. Every effect is rebuilt in Webflow and Webflow says some will need redesigning, so the site you launch will not move quite like the one you have.
- The complaint is that editors need the designer. Framer’s content editor seat and on-page editing may be enough, as long as nobody needs to change layout templates.
- You have hit a CMS cap. Framer’s plans differ in how much the CMS holds, so price the next plan up before you price a rebuild.
- The site runs in several languages with translated paths. On Webflow that means the Localize add-on and a redirect for every translated address.
- A launch is weeks away. Ship it on Framer and move once the content has settled.
- What you need next is logins, gated content or parts shared with your product. Look at custom code for that.
If the trouble runs the other way, and a Webflow site has become slow to change for a small design team, read the reverse move.
What decides the time and the cost
The design takes most of the time. Every page, component and template is built again, and the count of distinct layouts matters more than the count of pages. Motion adds to it: a site with an effect in every section takes far longer than one with a few hover states, and each effect built as a React code component becomes a small piece of custom code.
The content work depends on the export. Collections that hold only text, images and dates need little beyond a test import. Galleries, files, references between collections and colour values in HSL each add a step. Each locale adds its content, its paths and its redirects. If the CMS paths fit one folder, redirects are a handful of rows; if not, there is a rule per Collection and a row for each odd slug.
Our websites start from $15,000, and most take four to eight weeks. A migration is priced as a website project, on the page system, content work, integrations, publishing requirements and migration complexity, and we agree the scope and the price before we start. We build websites in Webflow, and Morse Micro’s is one.
Doing it yourself, you pay for a Webflow Site plan and a Workspace seat for each editor, on Webflow’s pricing page, and for the Framer plan until the domain has moved. The rest is the hours of whoever rebuilds the pages and checks the content.
Vendor details were checked against Framer’s and Webflow’s own documentation on 15 November 2026. Both change their plans and features often, so read theirs before you start.
Moving from Framer?
Short answers, from the guide above.
No. Webflow’s own guide says there is no automated way to convert a Framer site, and that Framer designs, layouts and interactions cannot be imported. The CMS content can come across: a Framer plugin exports each collection as CSV, and Webflow imports CSV into a Collection. Every page, component and animation is built again in the Webflow Designer.
Nobody can promise every position holds. We inventory valuable URLs, plan redirects and check canonicals, indexability, content and internal links, then monitor after launch. On Webflow that means a 301 for every CMS path that changes, the sitemap switched on and the global canonical URL entered, since Framer did both for you. Expect some movement in the first weeks.
Most of our website builds take four to eight weeks, and a migration is scoped as a website project. The design takes most of it, because every page and component is rebuilt, and every animation is made again. A site with many collections, references between them or several languages takes longer than a launch site with a blog.
Framer has no export button of its own for the CMS. Its help centre says content leaves through plugins, as CSV or JSON, one collection at a time. Check what the plugin leaves out before you rely on it: Framer’s own export example skips gallery fields, and writes multi-references with commas where Webflow wants semicolons. Files are uploaded again by hand, since Webflow’s file field takes nothing from a CSV.
Not as they are. Framer’s effects run on Motion, a React animation library, and Webflow cannot import them. Each one is rebuilt with Webflow Interactions with GSAP, and Webflow says some will need redesigning or custom code. List every animation on every page before you start, then decide which ones the new site needs.
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