WEBFLOW TO ASTRO OR NEXT.JS
Webflow to Astro or Next.js, without losing a ranking
Outgrown the CMS limits and the seat pricing? We rebuild your site in code on Astro or Next.js, move every CMS collection and asset, and keep each URL that brings in traffic.
WebflowAstro or Next.jsWEBFLOW → ASTRO · NEXT.JS
TYPICAL TIMELINE
2 to 6 weeks, set by the page count
COST
From $2,500; ten pages run $6,500 to $14,500
SEO RISK
Low: Webflow paths map one-to-one to a code site
MOVES CLEANLY
CMS collections, assets, SEO settings and your 301 list
MUST BE REBUILT
Designer layouts, interactions, forms and embeds
IN SHORT
A Webflow to Astro or Next.js migration moves your site from a visual builder into a codebase you own. CMS collections come out as CSV or through the Webflow Data API, assets are downloaded, and both go into Sanity or Markdown. Webflow’s code export leaves the CMS behind and isn’t built to maintain, so pages are rebuilt as components that match the design. Your existing 301 list comes across, and every other URL keeps its path.
WHY TEAMS MOVE
Why teams leave Webflow for Astro or Next.js
01
CMS limits you keep hitting
Item caps, limited references and no real relations make large blogs, docs and directories awkward to run.
02
Seats and plans that add up
Editor seats, CMS and localization add-ons raise the bill each year, while hosting a code site costs little.
03
Features that need real code
Gated content, search, calculators and integrations end up as embeds and third-party scripts.
04
No review, no history
Changes go live from the Designer. In a repo, every change is a pull request you can review and roll back.
OLD VS NEW
Webflow vs Astro or Next.js, for this move
Webflow
Astro or Next.js
Editing
Designer for layouts, Editor for content
A headless CMS with approved blocks and live preview
CMS
Collections with item and field limits
Typed schemas with references and no item caps
Cost to run
Site plan, plus seats and add-ons
Hosting on Vercel, Netlify or Cloudflare, often free to start
Custom logic
Embeds and third-party scripts
Any API, auth or data, in your own code
Change control
Publish from the Designer
Pull requests, preview links and one-click rollback
Redirects
Set in site settings
Versioned in the repo, served as real 301s
WHAT MOVES, WHAT DOESN’T
What comes across from Webflow
Webflow exports your content, not a codebase you’d want to keep. Plan for the pages to be rebuilt in code and the collections to be moved with care.
CMS collections
Exported as CSV or through the Data API, mapped to CMS schemas, then checked item by item.
Assets
Images and files downloaded from Webflow’s CDN and re-uploaded, with alt text kept.
SEO settings
Titles, descriptions, Open Graph images and the 301 list carry over page by page.
Static pages
Copy comes across; layouts built in the Designer are rebuilt as components.
Interactions
Webflow interactions are rebuilt in CSS or a small motion library, kept where they help.
Forms
Webflow forms move to a form service or an API route, wired to your CRM.
Embeds & integrations
Each embed or Zapier hook is replaced with a native integration, or retired.
CONTENT MODEL
How Webflow content maps to Astro or Next.js
WEBFLOW · BEFORE
Collections
CMS collections with plain, rich-text and reference fields.
ASTRO / NEXT.JS · AFTER
Typed CMS schemas
A schema per collection, with validation and real references.
WEBFLOW · BEFORE
Collection templates
One template page per collection, built in the Designer.
ASTRO / NEXT.JS · AFTER
Page templates
A component template per type, at the same URL pattern.
WEBFLOW · BEFORE
Static pages
Pages laid out by hand in the Designer.
ASTRO / NEXT.JS · AFTER
Pages from blocks
Pages assembled from approved section blocks that editors can reorder.
WEBFLOW · BEFORE
Components & classes
Webflow components and global classes.
ASTRO / NEXT.JS · AFTER
Design system
Tokens and components in code, shared by every page.
PROCESS AND TIMELINE
How we move a Webflow site to Astro or Next.js
Our usual order for a marketing site with a blog. Sites with many templates or a members area take longer.
1
WEEK 1Audit & URL inventory
Crawl every URL, export the content, and pull rankings and backlinks from Search Console. This list decides what must not move.
2
WEEK 1Content model & redirect map
Turn content types and fields into CMS schemas, and give every URL a fate: keep, 301 or retire.
3
WEEKS 2–3Design system & templates
Tokens and section components in code, then the page templates, reviewed on preview links.
4
WEEKS 3–4Collections & assets
Pull collections through the Data API, move assets, then check every item and page by hand.
5
WEEKS 4–5SEO parity & QA
Titles, canonicals, schema and sitemap per template; redirects, forms and links tested on the preview.
6
LAUNCH + 4 WEEKSLaunch & watch
Switch DNS early in the week, submit the sitemap, then watch 404s, indexing and rankings daily.
SEO SAFETY
The pre-launch checklist for Webflow
Rankings are lost three ways: broken URLs, missing on-page signals, crawl problems. These four stages close all three.
STAGE 1
Before the build
- URL inventory, every live URL listed by template
- Webflow’s 301 list exported and merged
- Collection slugs kept as they are
- Trailing slash rules decided
STAGE 2
During the build
- Titles, descriptions and canonicals per template
- Structured data rebuilt per template
- Internal links rewritten to final URLs
- Image alt text carried over
STAGE 3
Before launch
- Real 301s at the edge, tested with a crawler
- Sitemap and robots.txt checked on the preview
STAGE 4
After launch
- Submit the sitemap and request indexing
- Watch 404s, indexing and rankings daily
FREE MIGRATION PLANNER
Plan your Webflow redirects
Enter your site to list every URL, see which keep their path, and get the 301 redirect map.
Run the planner →FREE SEO & AEO CHECKER
Check your new site for AI answers
See if ChatGPT, Claude, Perplexity and Google AI Overviews can find, read and cite your pages.
Run the checker →FAQ
What Webflow teams worry about
Not sure which move you need?
We’ll look at your site on a 30-minute call.
Book a callCan our marketing team still edit pages without a developer?
Yes. They edit in Sanity with live preview and build pages from approved sections. What they give up is free-form layout in the Designer; what they get is pages that can’t break the design.
Astro or Next.js: which should we choose?
Astro for content-led sites: marketing pages, blogs and docs. It ships almost no JavaScript by default. Next.js when the site also needs logins, a customer portal, dashboards or pages built from live data. We recommend one after the audit, and the content model works with either. See Astro vs Next.js.
Will we lose our Google rankings?
Not if the redirects and on-page signals are done right. Most URLs keep their exact path; anything that changes gets a one-to-one 301, and we watch 404s, indexing and rankings daily for four weeks against the pre-launch baseline.
Do we keep our Webflow animations?
The ones that help, yes. We list every interaction at the audit, agree which come across, and rebuild them in CSS or a small motion library so they don’t cost speed.
What does the migration cost?
From $2,500 for a single page; ten pages run $6,500 to $14,500, at a fixed price agreed after the URL inventory. Posts and CMS items moved by script don't count as pages; templates do. See the website cost calculator.
You've reached the end, so now…
Tell us what you’re building.
Send us your store. Within one business day you get a short Loom from a senior: the three things we'd fix first, what it would cost, and whether we're the right team for it.
- No pitch deck, no discovery-call theatre
- You keep the audit whether or not you hire us
- Fixed-scope quotes, no hourly surprises
Prefer to talk? Book 20 minutes with Haniel or call +1 855-764-4977