Webflow gave a generation of designers a way to build real websites without hand-coding them, and for many teams it is still a good home. But growing companies often hit the same wall. The CMS starts to feel tight, the editor is too fiddly for marketers, costs rise as the team grows, and only one person really understands how the site is built. When that person is busy or gone, the site stops moving.
This guide is for teams weighing whether to leave Webflow. It covers why teams move, the signs it is time and the signs it is not, the destinations worth considering, a step by step migration plan, how to get your CMS and assets out, how to keep your rankings with a proper redirect map, what it costs, how long it takes, the mistakes we see most and a checklist to work through. We are a website design and development studio, not an agency for any one platform, so the aim is to help you pick the right destination, which may mean staying put.
Why Teams Leave Webflow
Teams rarely leave Webflow because it is a bad tool. They leave because the way they work has changed and the platform no longer fits. These are the reasons we hear most often.
The editor is built for designers, not marketers. Webflow's Designer is powerful, but its class system and box model take real skill. Marketers often stick to the simpler editing mode, which limits them to changing existing content rather than building new pages. New landing pages wait for whoever knows the Designer.
CMS limits and relationships. Webflow caps CMS items, collections and reference fields by plan. Teams with growing resource libraries, multiple locales or richly related content start designing around the limits instead of around the content.
Cost as the team grows. Site plans, workspace seats, localisation and add-ons all add up. For a growing marketing team the bill can climb faster than the value.
Dependence on one builder. Many Webflow sites were built by a single freelancer or agency. Without careful documentation, every change goes back through them.
Performance creep. Interactions, embedded scripts and large images accumulate. Webflow sites can be fast, but many end up heavy, which hurts conversion and Core Web Vitals.
Lock-in. Code export gives you static HTML, CSS and JavaScript, but not a working CMS. Owning your content and code in a portable form matters more as the company grows.
If a couple of these ring true, read on. If none do, there is a good chance the honest answer is to stay.
Signs It Is Time to Leave, and Signs You Should Stay
A migration is a rebuild plus a content move plus a redirect map. It should solve a real problem, not chase a fashionable stack.
Signs it is time to leave
Your marketing team cannot launch a new page without the one person who knows the Designer.
You are working around CMS item, collection or reference limits.
Plan and seat costs are rising faster than the site is improving.
Pages are slow because of stacked interactions and embeds, and fixing them means a rebuild anyway.
You need the front end in a code repository, alongside your product or with proper review.
A rebrand or repositioning is coming and the current build cannot carry it.
Signs you should stay
Your team still ships pages comfortably in Webflow and the CMS is not in the way.
You run Webflow Ecommerce happily and would need to replace it.
You have a strong Webflow developer or team who keeps the site moving.
The problems are specific (slow pages, messy classes, missing metadata) rather than structural.
If you are in the second group, a Tune-Up may be all you need. It is a fixed $5,000 technical pass on the platform you already have, covering speed, redirects, metadata and indexing. If CMS limits or the editing model are the real problem, a Tune-Up will not fix that.
Where to Go: Your Options Compared
The most useful question is not which platform is best, but who will edit the site after launch, and how. Answer that and the choice narrows quickly.
Framer
Framer is the closest move for teams that still want a visual canvas, just a simpler one. Marketers can build and edit pages without learning a class system, and it includes a CMS, hosting, localisation and animation. It is not built for ecommerce checkouts or very large, deeply related content models. Read Framer vs Webflow, then the Webflow to Framer route or the step by step Webflow to Framer article.
Astro
Astro builds pages ahead of time and ships very little JavaScript by default, so sites are fast without much tuning. Content lives in Markdown or a headless CMS, and the code lives in a repository you own. It suits teams with a developer and a need for speed and control. See Astro vs Webflow and the Webflow to Astro route.
Next.js
Next.js is a React framework for sites that act more like applications: logged-in areas, product data, personalisation, or shared code with your app. It is the most flexible option and needs an engineering team to run it. Read Framer vs Next.js and the Webflow to Next.js route.
Sanity or another headless CMS
A headless CMS such as Sanity, Storyblok or Contentful holds your content separately from the front end, so you can change the design or framework later without moving content again. It is the answer to most Webflow CMS frustrations: flexible content models, rich relationships and editing that suits marketers. The trade-off is more moving parts, because you also need a front end such as Astro or Next.js. Read Sanity vs WordPress for how a headless setup compares with a traditional CMS, and Contentful to Astro for a headless route in practice.
AI-built sites
AI builders and coding assistants can now produce a working site fast, as code you own. That is useful for a prototype or a simple site. For a marketing site that has to rank and be edited by non-developers, someone still needs to own the code, set up SEO properly, connect a CMS and handle redirects. If you have already built something this way and outgrown it, see Lovable to Next.js, and for the wider picture our guide to moving to an AI-built site.
WordPress
Some teams consider WordPress for its plugin ecosystem and familiarity. It brings its own maintenance and security load, so read Webflow vs WordPress and our guide to leaving WordPress before you go that way. You can see every option side by side in our website platform comparison.
How to choose in one pass
Marketers edit, design matters, no shop: Framer.
Speed and control matter, a developer owns the code: Astro, with a headless CMS if non-developers publish.
The site behaves like an app or shares code with one: Next.js, usually with a headless CMS.
The CMS is the main frustration: Sanity or another headless CMS, with Astro or Next.js.
Your team is happy in the Designer: stay, and consider a Tune-Up.
How a Webflow Migration Works, Step by Step
Whatever the destination, a good move follows the same order. Skipping steps is where rankings and leads get lost.
Step 1: Audit and crawl the current site
Crawl every live URL, including CMS item pages and paginated lists. Pull a year of search performance data, list the pages that earn traffic, conversions or backlinks, and record every integration: analytics, tag manager, CRM, forms, chat, consent and any custom code in the site settings or page settings.
Step 2: Decide what moves, merges or retires
Build a content inventory. Every static page and CMS item is moved as it is, rewritten, merged into a stronger page or retired. Retired pages still need a destination in the redirect map.
Step 3: Model the content for the new platform
Map each Webflow collection and field to the new content model. Pay special attention to reference and multi-reference fields, option fields, rich text with embedded components and any fields used only for filtering or styling. This is the chance to fix the workarounds you made for Webflow's limits.
Step 4: Export the content and assets
Export the CMS, download the assets and capture anything that lives only in the Designer. The next section covers this in detail.
Step 5: Decide what replaces each Webflow feature
CMS collections: the new platform's CMS, a headless CMS or Markdown files.
Interactions: platform effects, CSS or a motion library. Keep the ones that help, drop the ones that slow pages down.
Forms: the platform's own forms, a form service or a serverless function, with the same notifications and CRM connections.
Ecommerce: a dedicated commerce platform. Plan product URLs and order history carefully.
Localisation: the new platform's localisation or framework routing, keeping locale folders and hreflang consistent.
Custom code and embeds: components or managed scripts. Document the analytics and consent scripts nobody remembers adding.
Existing 301 redirects: copied from the hosting settings and merged into the new map.
Step 6: Design and build the templates
Design page types first, then build them as reusable components so the marketing team can assemble new pages without a developer. A move off Webflow is a good moment to replace one-off sections with a system.
Step 7: Build and sign off the redirect map
Map every old URL that carries traffic, links or conversions to its closest new equivalent, and have the business sign it off before launch. The SEO section below shows an example.
Step 8: Rebuild technical SEO
Carry over titles, meta descriptions, open graph images, headings and alt text. Set self-referencing canonical URLs, rebuild structured data, generate a new XML sitemap and check that staging is blocked from indexing while production is open.
Step 9: Test on staging
Test every template on desktop, tablet and phone, submit every form, confirm analytics and consent work, and run the redirect map so every rule resolves in one hop.
Step 10: Launch
Point the domain at the new host at a quiet time, confirm redirects are live, submit the sitemap in Google Search Console and check your highest-traffic URLs by hand. Keep the Webflow project available, unpublished, until you are confident nothing is missing.
Step 11: Monitor for 30 days
Watch crawl errors, index coverage, rankings and conversions closely. Most problems appear as 404s in Search Console within the first fortnight, and each one is a redirect you can still add.
Getting Your CMS and Assets Out of Webflow
Webflow export is not a migration. It gives you pieces of the site, and the work is in putting them back together on the new platform. Our article on Webflow code export covers exactly what ships and what you will rebuild.
CMS content. Each collection can be exported as a CSV from the CMS panel. Rich text comes out as HTML, images as URLs, and reference fields as identifiers that need remapping to items in the new CMS. Export collections that others depend on, such as authors and categories, first.
Code export. The Designer can export static HTML, CSS and JavaScript. It is a useful reference for styles and structure, but CMS pages come out as templates without your content, and forms, search and other hosted features stop working.
Assets. Images and files sit on Webflow's asset CDN. They cannot be redirected once the site moves, so download them, re-host them and update the links in your content.
Things that live only in the Designer. Page settings such as titles, meta descriptions, open graph images and custom code, plus site-wide settings such as existing redirects and scripts, need capturing page by page or from the settings panels.
Locales and ecommerce. Localised content and product data need their own export and mapping plan.
Expect to clean the content too: rich text with custom embeds, inline styling, internal links that need updating to the new URL pattern, and alt text that was never filled in.
How to Keep Your Rankings Through the Move
Rankings are rarely lost because of a platform change. They are lost when URLs change without redirects, when content gets thinner, or when metadata goes missing. The signed-off redirect map is the most important document in the project. Our glossary explains redirect maps and 301 redirects if you want the basics.
The Webflow URL patterns to plan for
CMS item pages under the collection slug, such as /post/your-post or /blog-posts/your-post
Category or tag collection pages, such as /category/design
Paginated lists with a query string, such as /blog?a1b2c3_page=2
Author pages, such as /author/jane
Locale folders, such as /fr/ or /de/, if you use localisation
Existing 301 redirects in the hosting settings
Files and images on Webflow's asset CDN, which cannot be redirected
A redirect map example
Here is part of an example map for a Webflow site moving to a cleaner /blog structure. Each line is a permanent 301 from the old URL to the new one.
/post/series-a-announcement goes to /blog/series-a-announcement (one to one, every collection item)
/category/product goes to /blog/product if it ranks, otherwise /blog
/blog?a1b2c3_page=2 goes to /blog, or to /blog/page/2 if the new site paginates
/author/jane goes to /blog/authors/jane, or /about if there are no author pages
/resources/case-study-template goes to /resources/templates/case-study (restructured section)
/fr/post/annonce goes to /fr/blog/annonce (locale folder kept)
Every existing Webflow 301 is kept, updated to point at the final new URL
Three rules keep the map healthy: every redirect resolves in one hop, retired pages go to the closest relevant page rather than the homepage, and redirects that already exist keep working.
Want the move planned for you? Plan my migration free. Enter your site and where it is moving, and the Migration Planner plans it for you: which URLs keep their address, which need a redirect and a realistic timeline. Or book a call and we will build the redirect map with you.
The rest of the SEO checklist
Keep URLs that already rank unchanged wherever the new structure allows.
Carry over titles, meta descriptions, headings, body content and alt text, then improve them after launch.
Update internal links to final URLs instead of relying on redirects.
Rebuild structured data for articles, FAQs, breadcrumbs and your organisation.
Submit the new sitemap and watch index coverage in Search Console.
Our SEO migration checklist walks through the full process, and the migration planner gives you a first read on your own sitemap.
What It Costs to Leave Webflow
Cost depends on the number of page types, how much CMS content needs cleaning and remapping, how many integrations must keep working, and whether you have locales or ecommerce. Platform fees on the new stack are a separate, usually much smaller line. Here is how our pricing works.
Tune-Up, $5,000 fixed: a defined technical pass if you are staying on Webflow.
Landing Page, from $2,500: one new page, built fast, without moving the whole site.
Migration or new build, from $10,000: audit, design, rebuild, content move, signed-off redirect map and 30 days of monitoring after launch.
Embedded Team, from $2,000 a month: ongoing design and build help after launch.
Projects go above the starting price for predictable reasons: many distinct templates, complex CMS relationships, several locales, ecommerce, heavy integrations, or a rebrand alongside the move. We scope all of it after the audit so the number is agreed before the build starts. See our pricing page and the migration service for the detail.
How Long a Webflow Migration Takes
A full marketing site typically goes live in three to six weeks, depending on page count, how much CMS content needs remapping and how quickly feedback comes back. Sites with many collections, locales or ecommerce take longer. A typical plan looks like this.
Week one: audit, crawl, content inventory, CMS export and a first draft of the redirect map.
Weeks two to four: design, templates, component library and the content move.
The final week: staging review, redirect sign-off, testing and launch.
The 30 days after launch: monitoring rankings, crawl errors and conversions, and fixing anything that turns up.
Moves We Have Run
Zen Educate. Zen Educate is a Series B edtech operating across the UK and US. Its existing site was slow to update and blocking growth experiments. We migrated it to Framer page by page with zero downtime, built UK and US variants into reusable components, moved the CMS into four content hubs and kept every integration working, from Google Tag Manager to Zoho CRM. The new site went live in March 2026. Read the Zen Educate case study.
Sydecar. Sydecar had just raised a Series A, and its website had been stitched together from freelance hand-offs. We rebuilt it as a system of reusable templates, CMS collections and interactive calculators across a site of more than 50 pages, launched in February 2026, so the marketing team can launch campaigns without engineering. Read the Sydecar case study.
Common Mistakes When Leaving Webflow
Treating code export as a migration. The export is a static snapshot. The CMS, forms and hosted features still need rebuilding.
Forgetting the asset CDN. Images and PDFs on Webflow's CDN cannot be redirected. Re-host them and update every link.
Losing reference fields. Collection relationships export as identifiers. Without remapping, authors, categories and related posts break.
Dropping existing redirects. The hosting settings may hold years of 301s. Copy them into the new map.
Redirecting everything to the homepage. Map each URL to its closest equivalent instead.
Ignoring paginated and filtered URLs. Query string pages pick up links and need a deliberate destination.
Rebuilding every interaction. Keep the motion that helps the story and drop what slows the page down.
Losing tracking and custom code. Scripts in site and page settings are easy to miss. Inventory them before the build.
Choosing a platform your editors cannot use. Moving from one hard-to-edit tool to another solves nothing.
Stopping work at launch. The first 30 days are when missing redirects show up. Watch Search Console and fix them quickly.
Your Webflow Migration Checklist
Before you decide
List the problems you want the move to solve, and check a Tune-Up would not solve them.
Agree who will edit the site after launch, and how often.
Shortlist destinations using the comparison above.
Before the build
Crawl every URL, including CMS items and paginated lists, and export a year of search data.
Build the content inventory: move, rewrite, merge or retire.
Export every CMS collection to CSV and download all assets.
Copy existing 301 redirects, custom code and page settings.
Define the new content model and URL structure, including how references map.
During the build
Clean and import CMS content, remapping references and re-hosting images.
Build templates as reusable components.
Draft the redirect map and get it signed off.
Carry over titles, meta descriptions, open graph images, alt text and structured data.
Rebuild forms, analytics, tag manager and consent, and test each one.
Launch day
Confirm staging is not indexable and production is.
Point the domain at the new host, confirm redirects resolve in one hop and spot-check top URLs.
Submit the new sitemap in Search Console.
The 30 days after launch
Check crawl errors and add any missing redirects.
Track rankings and conversions against the baseline.
Only then cancel the Webflow site plan and start improving content and design.
Keep Exploring
Compare platforms: Astro vs Webflow, Webflow vs WordPress, Framer vs Next.js and all website platforms.
Migration routes: Webflow to Framer, Webflow to Astro, Webflow to Next.js and Contentful to Astro.
Further reading: Framer vs Webflow, Webflow code export, Framer vs WordPress, Astro vs WordPress and our guide to leaving WordPress.
Tools: the migration planner and the resources hub.
Leave for the Right Reason, Then Move Carefully
Leaving Webflow makes sense when the platform has become the bottleneck: when the CMS is tight, the editor holds marketers back or the site depends on one builder. Choose the destination by who edits the site, plan the CMS export and asset move properly, and treat the redirect map as the most important document in the project.
Ready to plan the move? You have two options. Plan my migration free: test your site in the Migration Planner and let it plan the move for you. Or book a call and we will tell you what we would do, including when staying or a Tune-Up is the better choice. Our work includes three clients that have each been acquired for over $1 billion.
Frequently asked questions
Should we leave Webflow?
When is a Tune-Up enough instead of a migration?
What is the best alternative to Webflow?
Can I export my Webflow site and host it elsewhere?
Will we lose SEO rankings if we leave Webflow?
How much does it cost to move off Webflow?
How long does a Webflow migration take?
Do we have to move to Framer?
Harish Malhi
Founder of Goodspeed
Harish Malhi is the founder of Goodspeed. He left Google in 2019 to build his own product, and started Goodspeed to give other founders the same head start. Today the studio designs and builds websites and the whole digital experience around them for funded tech companies, at the moments that matter: a raise, a launch, a press cycle. Goodspeed is a Framer Enterprise Expert, was Bubble’s Agency of the Year in 2024, and has shipped 300+ products, including launch pages for an NVIDIA-backed AI lab and a Webby-nominated site for a Boeing-backed aviation company. It holds a 5.0 rating from 46 reviews on Clutch.
