Webflow to Astro: how to migrate a Webflow site without losing content, design or rankings

The short answer

Webflow is easier to leave than Framer, which has no HTML export at all, but only part of the way. On paid Workspace plans you can export your site's HTML, CSS, JavaScript and images and host them anywhere. Webflow's help center is just as clear about what stays behind: CMS content, form processing, site search, password protection, localized pages and code components aren't in the export, and Collection lists show their empty state (Webflow Help).

So moving from Webflow to Astro is part export, part rebuild. You export what Webflow gives you, pull the CMS out as CSV or through the API, rebuild each template as Astro components, replace forms and search, recreate the interactions you want to keep and give every URL that changes a permanent redirect. Done in that order, the new site keeps its design, its content and its rankings.

Why teams move from Webflow to Astro

Webflow is a strong visual builder, and plenty of marketing teams should stay on it. The reasons to leave are usually about ownership and cost rather than design:

• The site becomes engineering-owned. When developers make most changes, a codebase in your own repository is faster to work in than a visual canvas, and it can sit next to your product, your backend and your tests.
• Plan costs per site. On Webflow's pricing page, checked on 13 October 2026, the Basic site plan is USD 15 a month and Premium, the plan with the Webflow CMS, is USD 25 a month, both billed yearly. Localization is an add-on from USD 9 a month.
• Features that need a real backend: forms that write to your CRM, gated content, search across more than one site or anything that has to run on your own infrastructure.
• Exporting doesn't get you out on its own. Code export needs a paid Workspace plan, not just a site plan, and it leaves out the CMS. A clean exit takes planning either way.

If your marketing team publishes pages visually every week and the site does its job, staying on Webflow is a reasonable choice. A migration should buy something specific.

What Webflow's code export includes and leaves out

Source: Webflow's help article on exporting site code.

What we saw inspecting published Webflow sites

On 13 October 2026 we downloaded the homepages of seven sites built with Webflow, including webflow.com itself, and looked at what a migration would have to carry over:

• All seven load jQuery and their images from Webflow's servers. Images come from cdn.prod.website-files.com, and Webflow's own help center notes that image and file fields exported to CSV are links to the original project's hosting, which break if that project is deleted (Webflow Help). Every asset has to be downloaded and hosted again.
• All seven serve their social share image from Webflow too. The Open Graph image is easy to forget, and link previews on LinkedIn or WhatsApp lose their image once the old project is closed.
• All seven render their CMS lists directly in the published HTML, between 3 and 19 Collection lists per homepage. That's good news: unlike a Framer site, which our Framer to Astro guide shows is rebuilt by a runtime after it loads, a published Webflow page is a complete reference for what content goes where, even though the code export leaves those lists empty.
• Five of the seven use Webflow Interactions, marked by data-w-id attributes on up to 109 elements of one homepage. Each one is a small piece of behavior to recreate, or a decision to drop it.

Webflow to Astro, step by step

1. Inventory every URL. Webflow generates /sitemap.xml automatically when that option is on (Webflow Help). Add every Collection page, pull the Pages report from Google Search Console for the longest range available, and export your existing 301 redirects as CSV from Site settings, Publishing (Webflow Help).
2. Export the content. Export each CMS Collection to CSV from the CMS panel, once per locale if you use Localize, and keep the Item ID column. The CSV flattens things: reference fields come out as plain text, multi-references as comma-separated text and rich text as HTML. For anything with references, the Webflow Data API lists items with their fields and locales, which is usually cleaner than stitching CSV files back together.
3. Download every asset. Images, PDFs, fonts you're licensed to self-host, the Open Graph images and the favicon. Don't close the Webflow project until the new site no longer points at website-files.com.
4. Export the code as a reference. If you're on a paid Workspace plan, export the HTML and CSS. Don't deploy it as the new site: it would carry webflow.js, jQuery and empty CMS lists. Use it to read exact spacing, breakpoints and class structure.
5. Model the content in Astro. Turn each Collection into an Astro content collection or a headless CMS model, with references kept as references, then rebuild each template as Astro components and move images to astro:assets.
6. Recreate the interactions that carry meaning. Most Webflow Interactions become CSS transitions, keyframes or a few lines of JavaScript. For heavier motion, GSAP has been free for commercial use since Webflow made it so in April 2025 (Webflow). Respect prefers-reduced-motion either way.
7. Replace forms, search and protected pages. Give each form a real endpoint (a Cloudflare Worker, a form service or your CRM), add a static search index such as Pagefind if the site needs search, and move any password protection to your host or app.
8. Rebuild localized pages properly. Only the primary locale comes out in the code export, so build each language with Astro's i18n routing, one URL per language, with hreflang between them.
9. Match the URL format. Webflow serves pages without a trailing slash and redirects /pricing/ to /pricing. Set Astro's trailingSlash and build.format so the new site produces the same addresses (Astro configuration reference); every mismatch is a redirect you didn't need.
10. Redirect at the server, then launch and watch. A static Astro build without an adapter turns configured redirects into meta-refresh pages, so set 1:1 301s where the site is hosted, for example in a Cloudflare _redirects file. Switch DNS, keep the Webflow project until the new site is verified, and follow Search Console's indexing reports for the next few weeks. Our website migration SEO checklist covers launch day and the 90 days after it.

What changes after the move

Keeping SEO intact

Google's guidance on site moves with URL changes applies here: map every old URL to its closest new equivalent, use permanent server-side redirects and keep them for at least a year. If the URLs stay identical, which a careful rebuild can often achieve with Webflow, you mostly need to check that titles, descriptions, canonical tags, structured data and Open Graph images came across.

The Webflow-specific traps are the leftovers: an Open Graph image or a PDF still served from website-files.com, a webflow.io staging address still indexed, or a CMS page whose slug changed in the move. Check all three before you close the Webflow project.

How Dardo runs a Webflow migration

We run Webflow moves as part of our website migration service: URL and content inventory, CMS export, a representative page rebuilt first and reviewed at agreed widths, then the rest of the templates, forms and redirects. The build itself is web development in Astro, and motion work is creative development. This site, dardo.studio, runs on Astro on Cloudflare Workers with its content in a headless CMS, and we write and publish this blog through that CMS.

If you're weighing a move, send us the site and what you want to change. We'll tell you whether leaving Webflow is worth it before quoting one.