WHY LEAVE
Why people leave Webflow.
And when it's time.
I enjoy working in Webflow, and it's enough for most company sites. Leaving makes sense when you hit its limits, or when the site is built in a way that can't be maintained.
CMS limits
Your plan sets the number of items, collections and fields. A large catalog or article archive won't fit.
Custom logic and data
Filters, calculators, connections to your systems. In Webflow you solve them with embedded code and external tools that are hard to maintain.
An app, not a website
A client portal or logins. Webflow switched off User Accounts in January 2026 and doesn't offer app logic.
Content that only works on the site
Content in Webflow CMS is harder to reuse in an app, a newsletter or an AI assistant. It lives mostly in pages.
A messy build
Hundreds of classes with no system, styles in embeds, copied sections instead of components. Every edit breaks something elsewhere.
Slow loading
Heavy interactions, unoptimized images and third-party scripts. Weak Core Web Vitals then drag your SEO down too.
MIGRATION TARGET
Where to from Webflow?
Depends on what's holding the site back.
Not sure? I'll recommend one after an audit.
WHAT CARRIES OVER
What carries over.
And what replaces the add-ons.
I export the collections from Webflow via CSV and the API, download the assets and move everything into the new structure. Here's where everything goes.
| WEBFLOW | SANITY CMS |
|---|---|
| CMS collections | Documents in Sanity |
| Pages and sections | Pages built from blocks |
| References and multi-references | References between documents |
| Assets | Sanity media library |
| SEO settings and Open Graph | The same fields on every document |
| Forms | Forms connected to your system |
| Interactions and animations | Animations in code (GSAP, CSS) |
| E-commerce and user accounts | Not migrated, handled separately |
What replaces the add-ons
| ADD-ON | SANITY CMS |
|---|---|
| Custom code in embeds | Code directly in Astro components |
| Finsweet Attributes (filters, loading) | Sanity queries and filters in website code |
| Memberstack, Outseta | Authentication and permissions in a custom app |
| Weglot, Webflow Localization | Language versions in Sanity and Astro |
| Zapier, Make | A custom backend and direct API integrations |
| CMS sync from Airtable | Content in Sanity or an API integration |
PROCESS
How a Webflow migration works.
From audit to rank monitoring.
Webflow audit
I go through the build, collections, interactions and embedded code and list the pages, limits and URLs. Then I recommend either a rebuild or custom development.
URL map and redirects
URLs that change become clean new URLs, each with a 301 redirect. Where a URL stays the same, I leave it alone.
Content conversion and cleanup
I move rich text and collection fields into a clean structure, with no inline styles or embeds in the content.
Your content review
You go through the site in a dedicated feedback tool. You leave comments right on the page, and I fix them.
Launch
I switch the domain, check redirects, forms and analytics, and submit the new sitemap. You keep the original Webflow project as a backup.
Post-launch monitoring
I watch Search Console and traffic. Whatever shows up after launch, I fix.
Send me your site's URL. I'll tell you what it takes.
I'll go through your build, collections and embedded code and suggest whether to rebuild in Webflow or go custom. No commitment, no sales pitch.
STATUS:OPEN FOR PROJECTS· REPLY WITHIN 2 DAYS· NO COMMITMENT
FAQ
What people ask
about leaving Webflow.
Webflow rebuild or custom development: how do I decide?
If you fit within Webflow's limits and the main problem is how the site is built, a Webflow rebuild is enough. If you want marketing to compose pages from modular blocks, or you need custom logic or an app, custom development pays off. I'll recommend one after the audit.
Can I export my content from Webflow?
Yes, but in parts. Collections come out via CSV and the API, and I download the assets separately. The code export doesn't include CMS content or localization, so I don't use it for migrations.
What does a badly built Webflow site look like?
Classes with no system, styles written in embeds, sections copied instead of turned into components, or a CMS with no structure. I rebuild it on a class system, variables and components, so you can edit it without worrying.
Will the animations and interactions stay?
Yes. In Webflow I rebuild them lighter, in Astro as animations in code. The look and motion stay, the dead weight doesn't.
We used User Accounts. What now?
Webflow switched them off on 29 January 2026. I connect logins to an external service such as Memberstack or Outseta, or build them as part of custom development.
Can I edit the site myself after the migration?
Yes. With a Webflow rebuild, just as before, only tidier. With custom development, in Sanity, with a page preview and fields named after your content.
Does the site have to go offline during the migration?
No. Your current site keeps running until you approve the new one. I do the rebuild in a copy of the project and don't touch the live site.
DIDN'T FIND YOUR ANSWER? .
MORE PLATFORMS