Webflow migration to Next.js or AstroMove off Webflow.
Next.js or Astro with a headless CMS. Your design, CMS content, URLs, and publishing workflow stay intact.
- Free assessment, fixed price in writing
- Redirect map before any code
- Search Console checks at launch, day 30, and day 60
How do you migrate from Webflow without losing SEO?
Treat every URL that earns traffic as something to move, not something to rebuild. Four steps, and Webflow stays live until the cutover.
- /blog/pricing-guide1,240
- /features860
- /customers/acme410
- /blog-categories/news120
- /team-members/ana35
● Top 3 URLs bring 94% of clicks. They’re protected first.
Illustrative example
Every indexed URL from Search Console, the sitemap, and a full crawl, ranked by clicks and backlinks. CMS collections come out through the Webflow API, not CSV, so references and metadata stay intact.
URLs stay 1:1 wherever the new structure allows. Every URL that changes gets a reviewed 301, and redirects already set in Webflow are carried over and flattened so nothing chains.
Titles, descriptions, canonicals, Open Graph, structured data, and alt text, compared page by page against the live Webflow site on staging.
On launch day we test every redirect and submit the new sitemap. Then we check Search Console for 404s and lost queries at launch, day 30, and day 60.
Great to launch. Hard to scale.
Four limits teams hit as their site grows.
- 01
Costs scale with the plan, not your needs
Pricing tied to plans, seats, locales, and bandwidth means growth often arrives as an upgrade you didn’t plan for.
- 02
CMS limits shape your content strategy
Item and collection caps, plus limited relational content, force workarounds as your blog, docs, or resources grow.
- 03
Your content isn’t fully portable
Webflow’s code export leaves out CMS content, localized pages, and ecommerce. CMS data comes out as CSV, and the site itself stays on the platform.
- 04
Custom logic hits a ceiling
Gated content, product data, pricing calculators, or app integrations end up as embeds and third-party scripts.
Three years on Webflow.
What Webflow costs over three years vs. a stack you own. Change any number.
Staying on Webflow costs you
19.1× more€4,350a year
- Every month
- €363
- Over three years
- €13,050
The €13,050 is your break-even budget: the most a migration could cost and still pay for itself in three years. Every month you wait adds another €363.
| Year | Webflow | Own stack | Difference |
|---|---|---|---|
| 1 | €4,368 | €240 | €4,128 |
| 2 | €4,586 | €240 | €4,346 |
| 3 | €4,816 | €240 | €4,576 |
| 3 years | €13,770 | €720 | €13,050 |
Starting values are rough examples, not quotes. Use your invoices. Migration cost isn’t included.
Every feature gets a new home.
What your Webflow setup becomes in the new stack.
- CMS CollectionsTyped CMS collections with relations, drafts, and versioning
- Rich text fieldsStructured rich text with reusable embedded blocks
- Components & symbolsReact or Astro components, documented in one library
- Interactions (IX2)Rebuilt in CSS and a small motion library
- Webflow FormsForm handling connected to your CRM (HubSpot, Salesforce…)
- Localizationi18n routing with localized fields and hreflang
- Webflow hostingVercel, Cloudflare, Netlify, or EU / self-hosted
- Site settings & SEOPer-page metadata, canonicals, Open Graph, JSON-LD in code
Memberships, ecommerce, and Logic flows are scoped individually during the assessment.
SEO preserved.
Nobody can promise rankings. We guarantee the process: Search Console checks at launch, day 30, and day 60, and any redirect or indexing issue from the move fixed within the project price.
- Crawl of every indexed URL, cross-checked with Search Console and analytics
- 1:1 URL parity where possible; reviewed 301 map where not
- Titles, descriptions, canonicals, and Open Graph carried over
- Structured data preserved or improved
- XML sitemap and robots.txt regenerated
- Image alt text and file paths migrated
- Pre-launch crawl on staging to catch broken links and redirect chains
- Search Console checks for indexing, 404s, and lost queries at launch, day 30, and day 60
Six steps.
Webflow stays live until the new site is ready.
Audit
Every URL, collection, and integration, mapped.
When to stay.
If most of these apply, we'll say so and help you get more out of Webflow instead.
Moving likely pays off.
Nothing here keeps you put. A migration is worth scoping.
Tick what applies to you.
Staying still has a cost.
AI agents now draft, translate, and update content. A headless CMS gives them structured content and an API to work with, and your team approves every change.
- Content as data, not pages
- API access for agents
- Drafts and review built in
- Any channel, any language
- Drafting…
Draft 3 posts from the product changelog
Blog
- Queued
Translate the pricing page to German
Pages · de
- Queued
Rewrite 12 weak meta descriptions
SEO
- Queued
Add the new integration to the docs
Docs
Every change lands as a draft. Your team decides what gets published.
Webflow migration guides.
What we've learned moving sites off Webflow.
Guides3 min read
Webflow to Next.js: a practical migration guide
What moves, what gets rebuilt, and the order we do it in. A step-by-step plan for taking a Webflow site to Next.js or Astro with a headless CMS.
Read →Platforms2 min read
Webflow vs a headless CMS: when it's time to switch
Webflow is a good tool. These are the signs a team has outgrown it, and the signs it hasn't.
Read →Platforms2 min read
Webflow CMS limits, and what to do when you hit them
Item caps, collection caps, references, and localization costs. Where Webflow's CMS gets tight for growing content teams, and the options you have.
Read →
Webflow questions.
Anything else, ask on the call.
Can you keep our design exactly as it is?
Yes. We can rebuild your Webflow design pixel for pixel, interactions included. If you want a redesign, we plan it as a separate phase.
What happens to our Webflow CMS content?
We export your collections through the Webflow API, transform them into the new content model, and import everything, with references, images, authors, and metadata. Nobody retypes anything by hand.
Will our marketers have to learn a completely new tool?
They’ll learn a new editor, but one we set up around your existing pages and workflow: live preview, drafts, scheduled publishing, and reusable page blocks. Every migration includes hands-on training.
What about Webflow interactions and animations?
We go through every interaction in the assessment and rebuild the ones that matter with CSS and a small motion library. If something won’t transfer 1:1, the assessment says so before you commit.
Our Webflow renewal is coming up. What should we do?
Book the assessment early. You get the scope and timeline before the renewal date, so you can decide whether to renew for a shorter term, switch plans, or plan the cutover.
Next.js or Astro?
Astro suits content-heavy marketing sites that should ship little JavaScript. Next.js fits when the site sits close to your product, with login, dynamic pricing, or app features. We recommend one in the assessment and explain why.
What would it take?
URLs, CMS, integrations, and risks, ending in a fixed scope and timeline.