--- title: "Webflow to Astro Migration: Leave Webflow, Keep Your SEO" description: "We move Webflow sites to Astro: CMS Collections, Localize locales, interactions and assets, with every old URL mapped and crawled on staging first." url: "https://dardo.studio/en/services/webflow-to-astro/" language: "en" translations: {"es":"https://dardo.studio/es/servicios/migracion-webflow-a-astro/","pt":"https://dardo.studio/pt/servicos/migracao-webflow-para-astro/"} updated: "2026-10-22T12:00:00Z" --- # Webflow to Astro migration with CMS, design and URLs carried over We rebuild Webflow sites in Astro, with the content in a headless CMS you own. Collections leave Webflow locale by locale with their references intact, every asset comes off Webflow's CDN, the interactions worth keeping are recreated, and each URL keeps its address or gets a 301. Before DNS moves, staging is crawled against the full old-URL list to confirm SEO parity. By [Nicolas Ceron](https://dardo.studio/en/nicolas-ceron/) · Updated Oct 22, 2026 · 12 min read [Get a proposal](https://dardo.studio/en/contact/?service=webflow-to-astro) · [Message us on WhatsApp](https://wa.me/573132340197?text=Hi%20Dardo%2C%20I%27d%20like%20a%20proposal%20for%3A%20Webflow%20to%20Astro%20migration%20with%20CMS%2C%20design%20and%20URLs%20carried%20over) ## Why teams leave Webflow for Astro Teams rarely leave Webflow over design. They leave when developers make most of the changes, when seats and locales keep raising the bill, or when the site needs things Webflow's hosting can't run, such as forms that write to your own systems or code shared with your product. - Seats. Webflow retired its legacy Editor on 5 October 2026, so every new editor needs a paid seat: USD 15 a month for a Limited seat or USD 39 for a Full seat, billed yearly, as of October 2026. - Plans. In May 2026 Webflow merged its CMS and Business plans into Premium, at USD 25 a month billed yearly or USD 39 monthly, and existing sites move to it at renewal. - Languages. As of October 2026, Localize Essential costs USD 9 a month per locale for up to three; translated URLs need Advanced, at USD 29 per locale. - Limits. Premium includes 20,000 CMS items, 40 Collections, 300 static pages and 50 GB of bandwidth; two months in a row over the bandwidth limit trigger an automatic upgrade. - Engineering ownership. A repository can share components with your product and go through code review; a visual canvas can't. For most sites the 2026 plan change moved the bill by tens to a few hundred dollars a year, which won't pay for a rebuild on its own. Our [Webflow pricing 2026](https://dardo.studio/en/blog/webflow-pricing-2026/) guide works through who pays more at renewal, and from which date. ## Webflow and Astro compared for this move Webflow sells hosting, a visual Designer and a CMS as one subscription per site. Astro separates them into a framework in your repository, a host and a CMS you pick. Webflow figures are its October 2026 prices. If your site behaves like a signed-in app rather than a set of pages, read [Astro vs Next.js](https://dardo.studio/en/blog/astro-vs-nextjs/) first. __Webflow and Astro compared for this move__ | Area | Webflow | Astro on Cloudflare | | ------------ | --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | | Hosting | Webflow's CDN, billed per site; Premium includes 50 GB, and 100 GB costs USD 20 a month more | Any static host or edge platform; Cloudflare serves static assets without a request charge | | Editing | Full seats work in the Designer; Limited seats change content and assemble pages from existing components | Fields with preview in a headless CMS; new layouts go through a developer | | CMS limits | 20,000 items in 40 Collections and 300 static pages on Premium | The CMS plan's own: 10,000 documents on Sanity Free, none on self-hosted Payload | | SEO controls | Titles, descriptions, canonicals, sitemap and 301s built in | The same controls as template code and CMS fields; 301s set in a \_redirects file or Worker code at the host | | Languages | Localize, priced per locale; translated URLs on Advanced only | i18n routing with one URL per language and hreflang written by the templates | | Lock-in | Code export on paid Workspace plans, without CMS content, form processing or secondary locales | Templates in a Git repository you control; a CMS that can be replaced or self-hosted | | Running cost | Premium at USD 25 a month billed yearly, plus seats and locales | Hosting from USD 0, or USD 5 a month for Workers Paid, with the CMS priced separately | Want Dardo to do this for you? Tell us what you need. Nico replies personally within one business day. [Get a proposal](https://dardo.studio/en/contact/?service=webflow-to-astro) ## What comes out of Webflow, and what doesn't A Webflow site runs on Webflow's servers, so no single file holds it. Each part has its own exit, and some parts have none. That is the main difference from [moving off WordPress](https://dardo.studio/en/services/wordpress-to-astro/), where the database and uploads are yours to copy. - Collections export as CSV from the CMS panel, one at a time and only in the locale on screen. References turn into plain text, multi-references into comma-separated lists and rich text into HTML. - The Data API returns up to 100 items per request and keeps references and locales together; at Premium's 120 requests a minute, 20,000 items take about 200 calls per locale. - Images and files in the CMS, rich text included, remain links to Webflow's CDN, and Webflow warns they break once the project is deleted. - Code export, on paid Workspace plans such as Core at USD 19 a month billed yearly, gives HTML, CSS, Webflow's JavaScript and the Assets panel images. Collection lists come out empty. - Secondary locales, form processing, site search, password-protected pages and code components don't leave in any export. - Existing 301s export as CSV from Site settings, and form submissions download as CSV on paid site plans. ## How Webflow content maps to Astro The new content model starts from your Collections and their relationships, not from the CSV columns, so a post still points to its author and editors still find the fields they know. __How Webflow content maps to Astro__ | In Webflow | In Astro | How it moves | | ------------------------------------ | --------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | | Static pages | Astro pages assembled from components | Rebuilt one template at a time, using the published page and the code export as the reference | | Collections and Collection pages | Content collections or CMS types, one route per Collection page | Read through the Data API, with every slug kept as it is | | Reference and multi-reference fields | References between types | Joined by Item ID, not by the names the CSV prints | | Rich text | Rich text with local images | HTML converted, and every image moved off website-files.com | | Collection lists and filters | Queries inside each template | Rebuilt from what the published page shows, since the export leaves them empty | | Interactions and GSAP | CSS transitions, keyframes or a small script | Each one kept, simplified or dropped, with reduced-motion settings respected | | Localize locales | i18n routes with reciprocal hreflang | Exported locale by locale and checked against the live URLs | | Forms | An endpoint you own, such as a Worker on Cloudflare or your CRM | Past submissions downloaded; delivery confirmed by sending a real one | | Site search | A static index such as Pagefind | Generated during the build | | 301 redirects in Site settings | Rules in the host's redirects file | Exported as CSV and merged into the new map | ## How we move a Webflow site to Astro On Webflow the order of work matters, because the project holds the assets, the form history and the redirect list until the day the plan is cancelled. We take everything out before anything there changes. - We record everything the site does: Webflow's sitemap, every Collection page, at least twelve months of top landing pages from Search Console and analytics, backlinks, forms with their destinations and every script. - Each old URL gets one decision in a 1:1 map: keep, 301, merge, or 404 or 410. Our [redirect map generator](https://dardo.studio/en/tools/redirect-map-generator/) drafts the first pass from the old and new sitemaps. - The content model is designed next; then the Collections, locales, assets, existing redirects and form submissions are exported. - The Astro build is filled on a noindexed staging address, and Webflow keeps serving the live site until launch. - Before launch we crawl staging with every old URL, including each Collection item, and fix each mismatch. - Launch is an agreed window: DNS moved off Webflow, redirects live at the new host, the sitemap submitted, forms tested with real submissions. - On day 30 and day 60 we set indexing and clicks against the baseline, then hand over the repository, CMS, DNS and redirect list. The how-to version, with every export quirk and Astro setting, is our [Webflow to Astro guide](https://dardo.studio/en/blog/webflow-to-astro/). Handing it to us means our [website migration service](https://dardo.studio/en/services/website-migration/): the templates are built through [Astro development](https://dardo.studio/en/services/astro-development/), and the Collections become a model in [a headless CMS](https://dardo.studio/en/services/headless-cms-development/) that your editors can use the day after launch. ## Launch checks for a site leaving Webflow After a Webflow move, problems usually come from leftovers: a file still served by Webflow, a webflow.io staging address still in the index, or a Collection slug that changed on the way. - Every old URL, Collection items included, crawled against staging: each answers 200, redirects once with a 301, or returns an intentional 410 or 404. - Paths served without a trailing slash, as Webflow serves them, so no redirect is needed just for the format. - No remaining links to website-files.com in pages, CMS entries, PDFs or Open Graph images. - Titles, descriptions and Open Graph images from every static page and Collection template compared with the live site. - Each new address carries its own canonical tag, and every locale that Localize served links to the others with hreflang. - Schema added through Webflow's custom code, including any filled from CMS fields, rebuilt in the templates and tested in the Rich Results Test. - Forms delivered to their real destinations, and analytics events that respect the consent banner. - Staging noindex removed, the sitemap submitted, and the webflow.io address checked for indexed pages before the project closes. - Clicks and impressions compared by page at 30 and 60 days. Our [website migration SEO checklist](https://dardo.studio/en/blog/website-migration-seo-checklist/) has the full sequence. ## When to stay on Webflow Staying is often the right call. For most sites a rebuild outweighs years of Webflow fees, so the move has to pay off in ownership, editing or features. - Marketers build and rearrange pages visually every week. A headless CMS gives them fields and preview, not a canvas. - You pay monthly and the renewal is the only complaint. Yearly billing takes Premium from USD 39 to USD 25 a month. - Your Collections fit within Premium's 20,000 items and 40 Collections, and the content isn't needed outside the website. - No one will own the repository after launch: package upgrades, the CMS and the host all need a named person. When the answer is to stay, we can improve the site where it is through [Webflow development](https://dardo.studio/en/services/webflow-development/). If you want out but your team must keep designing on a canvas, [Webflow to Framer](https://dardo.studio/en/services/webflow-to-framer/) is the closer move, and our [Webflow alternatives](https://dardo.studio/en/blog/webflow-alternatives/) guide compares every option on running cost and effort. ## What Astro costs to run after Webflow Running costs usually drop, because seats, locales and bandwidth stop being per-site add-ons. The example: one owner, two editors, a second language and under 50 GB of traffic a month, at the vendors' October 2026 prices, billed yearly, in US dollars. __What Astro costs to run after Webflow__ | Line | Webflow | Astro on Cloudflare | | --------------------- | ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- | | Plan or hosting | Premium: USD 25 a month | USD 0 for static assets; Workers Paid at USD 5 a month once forms and functions pass the free 100,000 requests a day | | Owner and two editors | One full seat included with the Workspace; two Limited seats at USD 30 a month | Sanity Free at USD 0 (Administrator and Viewer roles only); Sanity Growth for three seats, USD 45 | | Second language | Localize Essential: USD 9 a month; Advanced at USD 29 for translated URLs | No platform fee; the cost is writing and reviewing the language | | Traffic above 50 GB | USD 20 a month more for 100 GB | No bandwidth charge on Workers Paid | | Monthly total | USD 64, or USD 768 a year | USD 0 to 50, or up to USD 600 a year | Fees alone rarely repay a rebuild, so price both sides. Our [Webflow pricing calculator](https://dardo.studio/en/tools/webflow-pricing-calculator/) sets your renewal next to the yearly cost of a coded site. The migration is quoted from the URL inventory, without a fixed price: Collections and items, templates, interactions worth keeping, locales, forms and integrations move it. For published market prices, see [what a website migration costs](https://dardo.studio/en/blog/website-migration-cost/). ## Questions before you choose **Will leaving Webflow hurt our search traffic?** A short period of movement is normal; Google's guidance for site moves says rankings can fluctuate while pages are recrawled. Lasting damage has avoidable causes: a Collection page left without a redirect, an Open Graph image or PDF still on Webflow's CDN, or SEO fields that didn't come across. Our crawl of staging and the 30- and 60-day reviews exist to catch those. No one can promise rankings. **Can we keep our Webflow URLs and Collection slugs?** Yes. Static pages and Collection pages keep their paths, slugs come out with each item, and the new site serves addresses without a trailing slash, as Webflow does. Any path that has to change gets a 301 at the host, and the redirects already set in Webflow are folded into the same map. **Does Webflow's code export include our CMS content?** No. The export holds pages, CSS, Webflow's scripts and the Assets panel images, but Collection lists come out empty and Collection pages lose their bound content. The CMS comes out separately, as CSV per Collection and locale or through the Data API, which keeps references and locales linked. **Can our marketers still publish without a developer?** They can write, edit and publish content in the headless CMS, with preview, and the site rebuilds after each publish. What changes is layout: building a new kind of page on a canvas becomes a developer task. If that happens every week, staying on Webflow or moving to Framer suits the team better. **What happens to our Webflow Interactions?** None of them import into Astro, because they run on Webflow's own JavaScript. We list them, keep the ones that help a visitor understand the page, and rebuild those with CSS or a short script. Heavier motion can use GSAP, free for commercial use since April 2025. Visitors who ask for reduced motion get a calmer version. **What happens to our Webflow forms and submissions?** Webflow processes form submissions on its own hosting, so an exported form sends nothing. Each form gets a destination you own, for example your CRM or a small Worker, and we confirm delivery with a real submission before launch. Past submissions download as CSV; we save them before the plan ends. **When can we cancel our Webflow site plan?** Once the Astro site answers every old URL, nothing points at Webflow's CDN, and you hold the Collection exports, the redirect list and the form history. Keep the plan until that check passes; on monthly Premium billing, each month of overlap costs USD 39 at October 2026 prices. **How much does a Webflow to Astro migration cost?** There is no fixed price: we quote after the URL inventory, since the number of Collections and items, templates, interactions, locales and integrations sets the work. On running costs, the example bilingual site with three people pays USD 768 a year on Webflow, seats and Localize included, and USD 0 to 600 on Astro with Cloudflare and Sanity, as of October 2026. ## From the blog - [Astro vs Webflow: editing, yearly cost, speed and lock-in for a marketing site in 2026](https://dardo.studio/en/blog/astro-vs-webflow/) Webflow suits marketing teams that build pages visually; Astro suits developer-run sites. Yearly costs, September 2026 speed data and what moving takes. - [Webflow to Astro: how to migrate a Webflow site without losing content, design or rankings](https://dardo.studio/en/blog/webflow-to-astro/) Webflow's code export leaves out the CMS, forms, search and localized pages. What to take out of Webflow, what to rebuild in Astro and how to keep rankings. ## Sources & further reading Sources behind this page, with further detail from the original publishers. - [Webflow Help: How do I export my Webflow site code?](https://help.webflow.com/hc/en-us/articles/33961386739347-How-do-I-export-my-Webflow-site-code) · help.webflow.com - [Webflow Help: Import and export CMS Collection content](https://help.webflow.com/hc/en-us/articles/33961290794771-How-do-I-import-content-into-the-Webflow-CMS) · help.webflow.com - [Webflow Help: Import and export 301 redirects](https://help.webflow.com/hc/en-us/articles/33961211526291-Import-export-301-redirects) · help.webflow.com - [Webflow Help: Create a sitemap in Webflow](https://help.webflow.com/hc/en-us/articles/33961355371667-Create-a-sitemap-in-Webflow) · help.webflow.com - [Webflow: Pricing](https://webflow.com/pricing) · webflow.com - [Webflow: We're updating our pricing and simplifying our plans](https://webflow.com/blog/simplified-plans-and-updated-pricing-2026) · webflow.com - [Webflow Help: Updated pricing and simplified plans for May 2026](https://help.webflow.com/hc/en-us/articles/51059955082387) · help.webflow.com - [Webflow Help: Legacy Editor deprecation FAQ](https://help.webflow.com/hc/en-us/articles/48412420902675-Legacy-Editor-deprecation-FAQ) · help.webflow.com - [Webflow Developers: Rate limits](https://developers.webflow.com/data/reference/rate-limits) · developers.webflow.com - [Webflow Data API: List Collection Items](https://developers.webflow.com/data/reference/cms/collection-items) · developers.webflow.com - [Webflow: Webflow makes GSAP 100% free](https://webflow.com/blog/gsap-becomes-free) · webflow.com - [Astro docs: Internationalization (i18n) routing](https://docs.astro.build/en/guides/internationalization/) · docs.astro.build - [Astro docs: Configuration reference](https://docs.astro.build/en/reference/configuration-reference/) · docs.astro.build - [Astro docs: Content collections](https://docs.astro.build/en/guides/content-collections/) · docs.astro.build - [Google Search Central: Site moves with URL changes](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) · developers.google.com - [Cloudflare: Workers pricing](https://developers.cloudflare.com/workers/platform/pricing/) · developers.cloudflare.com - [Sanity: Pricing](https://www.sanity.io/pricing) · sanity.io - [Payload: Get started](https://payloadcms.com/get-started) · payloadcms.com - [Pagefind: static search](https://pagefind.app/) · pagefind.app [Dardo](https://dardo.studio/) · [Services](https://dardo.studio/en/services/) · Webflow to Astro ## Plan the move off Webflow Send your Webflow site's address, its plan and how many Collections and locales it uses. We reply with what can be exported, what needs rebuilding and which URLs need attention. [01 · **Map your redirects** · Free redirect map generator](https://dardo.studio/en/tools/redirect-map-generator/) · [02 · **Read the step-by-step guide** · Webflow to Astro, from CSV export to launch](https://dardo.studio/en/blog/webflow-to-astro/) · [03 · **Discuss your brief** · Request a scoped proposal in your language](https://dardo.studio/en/contact/?service=webflow-to-astro) ## Keep exploring. - [Service · **Astro development: fast content sites and migrations**](https://dardo.studio/en/services/astro-development/) - [Service · **Website migration services without losing SEO**](https://dardo.studio/en/services/website-migration/) - [Service · **Headless CMS development: Sanity, Payload, Contentful and more**](https://dardo.studio/en/services/headless-cms-development/)