Webflow to Framer Migration Guide

What you need first

You need a clear inventory of your existing Webflow site — page count, CMS collections, item counts, and bandwidth usage — before starting, since Framer's tiers are gated on exactly those numbers and there's no automatic import to fall back on. Framer's free plan covers 30 pages, 1 GB of bandwidth, 2 CMS collections, and 1,000 CMS items, which is enough to prototype the migration and test whether Framer's editor fits your workflow before paying anything.

• A full inventory of your current Webflow site: page count, CMS collections, item counts
• A sense of your actual traffic and bandwidth needs, since Framer's free tier caps at just 1 GB
• A Framer account, starting free to test the rebuild before committing to a paid tier
• A plan for your domain, since re-pointing DNS is part of any platform migration

If your site is large — approaching or beyond 150 pages — plan for Basic at $10/mo (annual billing) or Pro at $30/mo, since the free tier's 30-page limit will be exhausted immediately by a real migration of that size.

Step-by-step

The migration itself is a manual rebuild, not a file import, so budget real time for recreating layout and interactions rather than expecting a one-click transfer. Start by exporting or documenting your Webflow site's content — copy, images, and structure — since that's the part that transfers cleanest, while layout and custom interactions need to be recreated using Framer's own design tools.

1. Document every page, CMS collection, and CMS item count from your current Webflow site
2. Set up the equivalent structure in Framer, starting on the free plan to validate the rebuild fits your needs
3. Recreate page layouts and interactions natively in Framer's editor rather than trying to import Webflow's design files directly
4. Migrate CMS content into Framer's collections, checking your item counts against your plan's limit — 1,000 on Free, 1,000 on Basic, or 2,500 on Pro
5. Test the site thoroughly on Framer's free tier or a paid plan's staging setup before re-pointing your live domain
6. Once verified, update your domain's DNS to point at Framer and retire the Webflow site

If your page count exceeds Basic's 150-page allowance, Pro accommodates further growth at $20 per additional 100 pages, up to a hard ceiling of 700 pages total — plan your tier around that ceiling if your site is large or growing. For a broader comparison of how Framer stacks up against Webflow beyond just the migration mechanics, see our Webflow vs Framer comparison.

Common problems

The most common problem is underestimating bandwidth needs, since Framer's free plan caps at just 1 GB — very little for anything that gets real traffic or hosts heavy media. The fix is moving to Basic's 50 GB or Pro's 100 GB bandwidth allowance before launch, rather than discovering the free tier's limit after your migrated site goes live and starts serving real visitors. A second common problem is hitting page-count limits partway through a migration of a large site — Pro's ceiling is a hard 700 pages even with the per-100-page add-on, so a site larger than that needs to talk to Framer about Enterprise pricing before committing to the migration at all.

A third issue is treating the migration as a straightforward import rather than a rebuild — since Framer has no documented automatic import from Webflow, teams that budget migration time as if it were a file transfer often run over, because layout and interactions genuinely need to be recreated by hand. Planning for that upfront, rather than discovering it mid-migration, avoids a stalled project. If you're also weighing whether Framer fits your use case better than a simpler landing-page tool, our Carrd vs Framer comparison covers that narrower decision.

What to do next

Start the migration on Framer's free plan to validate the rebuild process on a subset of your site before committing to a paid tier — 30 pages and 1,000 CMS items is enough to test the workflow honestly. Once you're confident in the approach, move to Basic at $10/mo for a small-to-mid site needing 150 pages and 50 GB bandwidth, or Pro at $30/mo if you need more CMS collections, higher bandwidth, or room to grow past 150 pages using the per-100-page add-on.

Because Framer prices per site rather than per seat, a migration that adds collaborators later won't increase your monthly cost the way a per-seat platform would — worth factoring in if your team is expected to grow. If, after evaluating Framer directly, you're still unsure it's the right platform versus staying on Webflow or moving to WordPress instead, our Webflow vs WordPress and Framer vs WordPress comparisons cover those alternative paths in more depth before you commit to the migration.

Timing the migration matters as much as the technical steps. Doing the rebuild in Framer while your Webflow site stays live means you can take your time validating layout, content, and CMS structure without any downtime risk, and only switch DNS once everything on the new site checks out. Rushing the DNS cutover before the Framer site is fully tested is the most common way a migration turns into an outage — broken CMS references, missing pages, or bandwidth limits hit under real traffic are all much cheaper to catch before the domain switch than after. Budgeting a few days of parallel operation, where both the old Webflow site and the new Framer site are reachable and you're comparing them side by side, is worth the extra time for anything beyond a trivial personal site.

It's also worth deciding upfront whether you're doing a like-for-like migration or using the move as an opportunity to simplify the site. A large Webflow site with years of accumulated pages and unused CMS items is a natural moment to prune before rebuilding in Framer, both because it reduces the manual rebuild effort and because it may keep you under a lower, cheaper tier's page and item limits instead of paying for capacity you don't actually need.