Webflow migration
Migrating from Webflow to a Hand-Coded Site
For small business owners and agencies who built on Webflow and want off the $23 to $39 USD/month site plan dependency. You'll own your code outright, keep your content and SEO via CMS Collection exports and 301 redirects, and hit 90+ PageSpeed (measured on Google PageSpeed Insights desktop at delivery). Webflow's clean export makes this one of the more straightforward migrations.
45 → 91
PageSpeed after Serene Family Dental migration
90+
PageSpeed guaranteed at handover
Zero platform fees.
No site plan. SEO preserved via 301s.
Why people leave Webflow
The specific pain points that bring Webflow users to us.
Webflow is a respectable tool. These are the concrete reasons businesses still move off it.
-
$23-$39 USD/month CMS site plan required
If your Webflow site uses CMS Collections (most do - for blog, services, case studies), you need the CMS Site Plan at around $23 USD/month or the Business Site Plan at around $39 USD/month to keep the CMS-driven pages live. Three years is $828 to $1,404 USD - paid to Webflow rather than building equity in your own site.
-
PageSpeed ceiling around 70-85
Webflow produces cleaner output than WordPress, Wix, or Squarespace - but it still loads its own JavaScript runtime, generates verbose CSS from the visual builder, and adds overhead a hand-coded static file doesn't have. Webflow sites typically land in the 70-85 range on PageSpeed Insights. Hand-coded sites hit 90+ because the code contains nothing we didn't deliberately write.
-
The "Webflow look"
Webflow's visual canvas generates class-based CSS following its own naming conventions. Designers familiar with Webflow can spot a Webflow site the way anyone can spot a Squarespace one. Every site carries the fingerprints of the tool that built it.
-
CMS data tied to the platform
You can export CMS Collections as CSVs from the Designer, but the runtime that turns those Collections into live pages stays inside Webflow. If you stop paying, the dynamic pages stop generating. The data exports cleanly enough for a hand-coded rebuild to recreate the structure as static pages plus a PagesCMS editing interface.
-
Site goes dark if billing stops
Webflow hosts the site and the CMS data. Cancel the site plan and the live site goes offline. The exported HTML is yours, but it needs developer work to re-host elsewhere. With a hand-coded site on your own Cloudflare Pages account, the static files keep serving regardless of who built them.
-
Over-tooled for a 15-page local business site
Webflow shines for design-led teams building complex marketing sites with frequent updates. For a local dental clinic, accounting firm, or trade business with a fixed 10-30 pages and a small blog, the platform is more tool than the job needs. The ongoing subscription is paying for capability that isn't being used.
Migration honesty
What carries over - and what doesn't.
Webflow exports more cleanly than other builders. Most content survives intact. The visual canvas itself does not.
What carries over
- ✓ All page copy and body content
- ✓ All CMS Collection data (via CSV export from Designer)
- ✓ All images (re-optimised to WebP)
- ✓ Your existing domain
- ✓ SEO authority and Google rankings (via 301 redirects)
- ✓ Brand assets - logo, colour palette, type direction
- ✓ URL structure (Webflow URLs are usually clean enough to mirror)
- ✓ Form submission destination (email, webhook, CRM)
What doesn't carry over
- × The Webflow Designer canvas (you'll edit content via PagesCMS)
- × Webflow CMS as a runtime (Collections become static pages plus PagesCMS)
- × Webflow hosting (replaced with Cloudflare Pages)
- × Webflow-generated class names and inherited CSS conventions
- × Webflow Interactions (rebuilt as lightweight vanilla JS where they still matter)
- × Logic / Memberships add-ons (audited and replaced case-by-case)
- × Webflow Ecommerce (replaced with Shopify or static product pages)
The migration process
Seven steps from Webflow to live hand-coded site.
No surprises. Every step is timed, scoped, and reviewed with you before the next one starts.
- 1 Discovery and scoping call Free 30-minute call. We audit your current Webflow site, count CMS Collection items, identify Interactions / Logic / Ecommerce dependencies, agree the tier, and fix the price.
- 2 Content audit and URL mapping We list every page including every CMS Collection item URL, and map each old URL to its destination on the new site. Webflow URLs are usually clean enough to mirror directly, which simplifies redirects.
- 3 Content export (Webflow-specific) Webflow Designer exports each CMS Collection as a CSV (Collections > Export). Static pages export as HTML. Images and assets come out of the Webflow Assets panel. Webflow's API is also available for larger Collections via scripted export. Cleanest of all the platform migrations.
- 4 Hand-coded rebuild 1 to 3 weeks depending on tier. Hand-coded HTML, CSS, JavaScript. WebP images. JSON-LD schema. PagesCMS connected to your GitHub repo so you keep a browser-based editing experience for blog and CMS content - without the Webflow monthly fee.
- 5 Preview and revisions You see the new site on a staging URL before anything goes live. Round of revisions, content updates, copy tweaks. We confirm PageSpeed hits 90+.
- 6 DNS cutover and 301 redirects Point DNS at Cloudflare Pages. Activate 301 redirects from any old Webflow URLs that changed structure. Where URLs mirror, no redirect needed. Existing rankings and link equity transfer.
- 7 Cancel Webflow site plan (after 7 days stable) Only cancel the Webflow site plan after the new site has been live and serving correctly for at least 7 days. This protects against any window where the live URL is offline before Google has fully indexed the new site.
SEO continuity
Will I lose my Google rankings when I migrate?
This is the question that holds most Webflow users back. The answer is no - not if URL mapping and 301 redirects are implemented properly. Google's own documentation treats a 301 redirect as a near-full pass of link equity from the old URL to the new one.
Webflow's URL structure is generally clean (no platform-specific path noise), so most URLs mirror directly into the hand-coded rebuild. Where URLs need to change, the mapping table feeds into the Cloudflare Pages _redirects file at cutover. Inbound links keep working, link equity flows through, and rankings transfer.
Serene Family Dental's PageSpeed went from 45 to 91 after their migration (measured on Google PageSpeed Insights desktop at delivery). Faster site, same rankings, no monthly platform fee.
What changes when you migrate
Webflow today vs hand-coded after the migration.
A clean side-by-side of what your day-to-day looks like before and after migrating off Webflow.
| Feature | Webstallion | Webflow |
|---|---|---|
| Platform dependency | None - static files hosted anywhere | Site goes offline if you stop paying Webflow |
| Monthly ongoing fees | Hosting only (typically $0-$19/month) | $23-$39 USD/month site plan (required) |
| PageSpeed score | 90+ guaranteed | Typically 70-85 - better than WordPress, but not 90+ |
| Design uniqueness | Unlimited - built from scratch to your brand | Class-driven system - recognisably "Webflow look" |
| Maintenance | None required - static files | Platform updates managed by Webflow; CMS requires active subscription |
| Price | Fixed from $1,500 - no recurring platform fee | Agency build cost + $23-$39 USD/month ongoing |
| Code ownership | You own every file - fully portable | Export available but CMS data and structure are tied to Webflow |
Webflow pricing sourced from webflow.com/pricing (CMS and Business Site Plans, USD). PageSpeed ranges are typical desktop scores as of May 2026; mobile scores typically run lower and depend on the build, interactions and content. Verified May 2026; subject to change by the vendor.
A real migration
Serene Family Dental - migrated to 91 PageSpeed.
Serene Family Dental came to us with a slow site scoring 45/100 on PageSpeed Insights. It was hard to navigate on mobile, had no proper online booking flow, and required maintenance they had no time for.
We mapped every URL, exported content, and rebuilt from scratch as hand-coded HTML, CSS, and JavaScript. No platform subscription. The rebuilt site scored 91/100 on PageSpeed Insights at delivery. They manage content through PagesCMS. Search rankings transferred via 301 redirects through the cutover.
Read the full case study"We had been putting up with our old website for too long - it was embarrassing to hand out the URL. Webstallion turned it around in two weeks and the new site actually looks like a proper dental clinic. Patients have commented on it. The booking process is smoother, it loads fast, and we can finally update our own content without calling a developer."
Pricing
Migration cost is your tier price plus a small import fee.
Packages lean from $799 (Lean - 5 pages, about 2 weeks), $1,500 (Starter - 15 essential pages), $2,500 (Growth - 35 pages, blog setup), $4,500 (Scale - up to 100 pages, multi-location). Migration cost is typically the tier you'd choose anyway, plus a small migration-content-import fee that we quote on the scoping call. Webflow migrations are often the lowest import fee of the four platforms because the CMS Collection CSV export is clean.
Migration questions
What people ask before migrating off Webflow.
Will I lose my Google rankings if I migrate from Webflow?
No - not if we handle the URL mapping and 301 redirects properly. Webflow's URL structure is generally clean (often mirrored cleanly in the hand-coded rebuild), which makes URL mapping more straightforward than for Wix or Squarespace migrations. Before launch we map every existing Webflow URL to its new destination. At cutover, 301 redirects activate in Cloudflare Pages so link equity and rankings transfer. Google treats 301s as a near-full pass of authority.
How long does a Webflow migration take?
From scoping call to live site is typically 2 to 4 weeks. Webflow migrations are usually quicker than Wix or Squarespace because Webflow's content export is cleaner. Starter (15 essential pages) is about 2 to 3 weeks. Growth (35 pages) about 3 to 4 weeks. Scale (up to 100 pages) about 4 to 5 weeks.
Can I keep my domain when I leave Webflow?
Yes. Your domain is separate from your Webflow site plan. We point your DNS at Cloudflare Pages (where the new hand-coded site is hosted) and your existing domain keeps working. Most Webflow customers keep their domain at a third-party registrar already, which makes this even simpler.
What happens to my Webflow CMS Collections during the migration?
Webflow lets you export each CMS Collection as a CSV from the Designer (Collections > Export). We use those CSVs to bring blog posts, case studies, team members, and other CMS-driven content into the hand-coded site as either static pages, or as PagesCMS-managed content (PagesCMS gives you a similar browser-based editing experience without the subscription).
What if my Webflow site has more pages than your tier covers?
We size the tier to the actual page count, including CMS Collection items. Scale covers up to 100 pages. If your Webflow CMS has hundreds of items (a long-running blog, a large case study library), we either move you to a custom-quoted tier, or we audit which CMS items actually earn traffic and consolidate or archive the rest. The scoping call covers exact counts so the quote is honest.
When do I cancel my Webflow site plan?
Not until the new hand-coded site has been live and stable for at least 7 days. We do DNS cutover first, confirm 301 redirects are firing, verify the new site is serving correctly, and only then do you cancel your Webflow site plan. This avoids any window where the live URL is offline before Google has fully indexed the new site.
Will I lose the Webflow CMS structure?
The Webflow CMS as a runtime - the dynamic page generation, the Designer interface - doesn't carry across. The data does. Each CMS Collection becomes a folder of static pages (one per item) plus a listing page, with PagesCMS connected so you keep a browser-based editing experience on the new site. For most local business use cases (services, locations, blog, case studies) the result is functionally equivalent without the monthly platform fee.
Related reading
- → Dental website design in Australia - the complete guide
- → Web design packages and pricing
- → Case study: Serene Family Dental - PageSpeed 45 to 91
- → Why your PageSpeed score matters (and what's killing it)
- → Why cheap websites cost more in the long run - 3-year total cost breakdown
- → Migrate from WordPress to a hand-coded site
- → Migrate from Squarespace to a hand-coded site
- → Migrate from Wix to a hand-coded site
Webflow migration
Ready to leave Webflow?
Get a free 30-minute migration scoping call. We'll audit your current Webflow site, map URLs, and quote the migration before you commit.