Webflow is a good place to start and an expensive place to stay. Moving to Astro means the same site, faster, on code you own, hosted wherever you like, with no collection or field limits to design around.
Every platform transfers some things cleanly and forces a rebuild of
others. Here is the honest split for Webflow, so you can see
the shape of the work before you talk to anyone.
Comes across
Your CMS contentCollections export to CSV from the CMS panel, one file per collection. Fields come out as text, which is exactly what we need to import them into the new site.
Your 301 redirectsWebflow can export every redirect you have already set up as a CSV, from Site settings under Publishing. We take that as the starting point for the new URL map rather than rebuilding it from memory.
Your assets, if you grab them in timeThis is the one that catches people. Image and file fields do not export as files, they export as URLs pointing at your Webflow-hosted assets. They keep working right up until the site is cancelled, and then every one of them breaks. We pull them all down before anything gets switched off.
Your rankingsEvery existing URL is mapped to its new address and the redirects go live at the same moment the site does, not days later.
Gets rebuilt
The front endMoving to Astro means the design is rebuilt in code. We can match what you have faithfully so nothing visibly changes, or improve it while we are in there. Either way it is a rebuild, and we would rather say that than imply the design somehow transfers.
InteractionsWebflow interactions do not survive as code. Anything animated gets rewritten, which in practice is usually a small amount of work and a large amount of weight removed.
FormsWebflow handles form submissions on its own servers, so that stops when you leave. Forms get wired to something you control, and the submissions land somewhere you can actually query.
Anything using a Webflow-only featureSite search, User Accounts, ecommerce and code components are Webflow platform features rather than parts of your site. If you use them, we replace them, and we tell you which ones during the audit rather than after.
Where the work actually is
On a Webflow site the hours do not go where people expect. The content is the easy part, because the CSV export is genuine. The work is the front end rebuild, pulling every asset down before the plug is pulled, and replacing whatever Webflow was quietly doing for you on its own servers.
A brochure site with three collections is straightforward. A site leaning on forms, search and interactions is a bigger job, and we will say so before you commit rather than after.
FAQ
Straight answers.
Can I just export the code from Webflow instead?
You can, and it will not give you what you want. Webflow's code export ships the HTML, CSS, JavaScript and the files in your Assets panel, but it deliberately leaves out CMS content, ecommerce, native forms, site search and User Accounts. Your exported 301 redirects also stop working once the site is self-hosted, because those were being served by Webflow. What you get is a snapshot of a static site with the dynamic parts removed, which is why the export alone is not a migration.
Will our blog posts and case studies come across?
Yes. Each CMS collection exports to CSV and we import it into the new site, keeping the slugs so the URLs do not change. The one thing to watch is images: in the export they are URLs pointing at your Webflow assets rather than the files themselves, so we download every one before the Webflow site is cancelled. Leave that step out and the posts arrive with broken images the day the subscription lapses.
What happens to the 301 redirects we already set up in Webflow?
They come with you. Webflow exports every redirect you have configured as a CSV, from Site settings under Publishing, and we use that as the starting point for the new URL map rather than rebuilding it from memory. Worth knowing: those redirects are served by Webflow, so they stop working the moment the site is self-hosted or cancelled. Ours go live on the new site at the same moment it does, which is why nothing returns an error in between.
Can our team still edit the site afterwards?
Yes, and that is a decision we make with you rather than for you. If your team publishes regularly we put a CMS in front of the content, so editing feels much like the Webflow Editor did. If the site barely changes, content can live in the repository and skip the CMS entirely. We will tell you which one your actual publishing habits justify.
Why Astro rather than another framework?
Because a marketing site should ship almost no JavaScript, and Astro is built around that. Pages render to static HTML and load fast without work, which is the thing Webflow sites most often lose points on. It also keeps content in a form your team or an AI assistant can edit directly, rather than locked inside a visual editor.
How long are we running two sites at once?
Not long, and never by accident. The new site is built and reviewed on a staging URL while the Webflow site carries on serving as normal. The switch happens once, when you approve it, with the redirects going live at the same time. You keep the Webflow subscription until every asset is pulled down and the new site is confirmed live, then you cancel it.
The parts that are the same either way
How we map URLs before rebuilding anything, what you keep, and what
you stop paying for all live on the migrations page rather than being
repeated here.
Book a 30-minute call. We'll look at what you have, tell you what moving actually involves, and quote it fixed. If you're better off staying where you are, we'll say so.
