How Do You Move a Site From Framer to Webflow?

Can You Move a Framer Site to Webflow at All?

Yes, but not by exporting and importing. There is no button that turns a Framer site into a Webflow site. What moves cleanly is your content and your URL structure. The design and the build get recreated, which sounds worse than it is and is often the point of moving.

We do this kind of migration regularly, and the teams that struggle are the ones who expected a conversion tool. The teams that go smoothly treat it as a rebuild with a content transfer attached, and plan accordingly.

Here is exactly what transfers, what does not, and the order we work in so nothing breaks on launch day.

What Can You Actually Take With You?

Your CMS content and your copy, reliably. Framer's own documentation states that Framer CMS content can be exported using plugins into structured formats such as CSV or JSON. That covers text, images and collections, which is the bulk of what is expensive to recreate by hand.

Your assets come too. Images, video and documents can be pulled down and re-uploaded, though this is a good moment to audit them rather than move everything blindly. Most sites we migrate are carrying assets nobody has referenced in two years.

What does not transfer is the build itself. Components, interactions, breakpoints and styling all get rebuilt in the Webflow Designer. So does anything custom in code. Budget for that honestly at the start rather than discovering it in week three.

Why Can't You Just Export the HTML?

Because Framer does not offer it. Framer's documentation is explicit on this point, stating that Framer does not offer HTML export for self-hosting, and that sites built in Framer rely on platform managed services that power performance, optimization and publishing features behind the scenes.

The reasons it gives are worth understanding, because they explain what you are giving up and gaining. Framer names page pre-rendering, dynamic image resizing and optimization, font subsetting, server side rendering, and global content delivery and caching as capabilities tied to its hosting.

Its documentation is direct about the consequence: published sites are not fully static and cannot be exported as standalone HTML files for self-hosting. So scraping your own site is not a migration strategy either. Plan on rebuilding, and treat the existing site as a reference design rather than a source file.

How Should You Plan the Migration?

Work backwards from launch, in four stages. Inventory first, build second, content transfer third, redirects and launch last. Doing content before the build is the most common sequencing mistake, because your Webflow collection structure has to exist before content has anywhere to land.

Start the inventory with a full URL list from your current site. Every page, every CMS item, every asset. This single document drives the collection design, the redirect map and the sign off, and skipping it is why migrations slip.

Then design the CMS structure before touching the Designer. Decide your collections, your fields, your reference relationships and your slug patterns while it is still cheap to change them. Restructuring collections after content is loaded is painful in any platform.

How Do You Move the CMS Content?

Export to CSV, clean it, then import. Framer's plugin export gives you CSV or JSON. Your job in the middle is the part nobody enjoys and everyone underestimates: matching field names, fixing date formats, resolving image URLs and deciding what happens to fields that have no equivalent on the other side.

Do the cleaning in a spreadsheet, not in the platform. It is faster to fix two hundred rows in one column than to correct two hundred items one at a time. Keep the original export untouched so you can start again, because you will want to at least once.

Slugs deserve special care. If your Framer slugs and your intended Webflow slugs differ, decide now and record both in the spreadsheet, because that mapping becomes your redirect file later. Our guide to importing CMS content by CSV in Webflow covers the mechanics in detail.

Should You Use the CSV Import or the API?

CSV for a one off, the API for anything repeated or large. Webflow's Data API documents a bulk endpoint that can create up to 100 items in a single request, with name and slug as required fields on each item.

A few details in that documentation shape how you use it. Items are created as drafts by default, and the isDraft parameter controls that, with a false value queueing the item for publishing on the next site publish. The endpoint returns a 202 status, meaning the request is accepted for asynchronous processing rather than completed immediately.

Localisation is the case where the API clearly wins. Webflow's documentation notes that if the cmsLocaleIds parameter is omitted, an item is only created in the primary locale. Migrating a multilingual site through the interface is slow, and this is exactly what scripting is for. Writing to the CMS needs the CMS:write scope on your token.

What Happens to Your URLs and Rankings?

Nothing bad, if you do the redirect work. Everything bad, if you do not. This is the step where migrations actually lose traffic, and it is entirely preventable with the URL inventory you built in stage one.

Map every old URL to its new destination before launch, including CMS item URLs, which are the ones most often forgotten because there are hundreds of them and nobody lists them by hand. Any old URL without a mapping needs a deliberate decision, not a default.

Then set up the 301 redirects and verify them after publishing rather than assuming. We walk through the setup in our guide to 301 redirects in Webflow. Check a sample of live URLs yourself on launch day, and keep watching Search Console for the following month.

What Will You Have to Rebuild by Hand?

The interesting parts, which is the honest tradeoff. Every interaction and animation. Every breakpoint. Your typography and colour system. Any custom code, forms, embeds and third party integrations. None of this converts, and all of it is where the design lives.

Treat that as an opportunity rather than a tax. Most sites we migrate are carrying three years of accumulated exceptions, and rebuilding is the cheapest chance you will ever get to remove them. Rebuild the system you want, not the one you have.

Adopt a class naming convention on day one while the project is still empty. Whether that is Client First or your own, the decision costs nothing now and is expensive to retrofit. A migration is the only moment when a codebase is genuinely clean.

How Long Should This Take?

It depends on the CMS, not the page count, and that surprises people. A twelve page marketing site with no collections is quick. A twelve page site with five interlinked collections and two thousand items is a different project, because the content mapping and the reference relationships carry the effort.

Three factors drive the estimate more than anything else. How many CMS collections exist and how they reference each other. How much custom code and how many third party integrations are wired in. And how many URLs need redirecting, which sets the size of the verification job at the end.

We will not put a number on your project without seeing those three things, and we would be sceptical of anyone who does. The page count in the brief is the least useful figure in the conversation.

Should You Migrate at All?

Only for a reason you can name. Wanting a deeper CMS, needing structures the current platform does not model well, or wanting the API access to automate publishing are good reasons. Preferring the interface is not, on its own, worth a rebuild.

Be clear eyed about what you lose too. Framer names real capabilities in its hosting stack, and a Webflow build has to earn back that performance through its own construction rather than inheriting it. That is achievable and it is work.

If you are weighing the two platforms rather than the move itself, we compared them directly in our piece on Webflow versus Framer. Start there before committing to a migration plan.

And if you want someone to scope the CMS mapping and the redirect job before you commit, we are happy to look at it with you. Find us at phoenix.studio.