Migrate
Leaving Webflow or Framer? Your site on Astro, every URL kept.
We move your marketing site onto Astro page by page, check every page against the original, and hand you a repository that is yours. The estimate arrives in under 24 hours.
- Under 24 hours for the estimate
- From $5k for up to 15 pages
- Every URL kept or redirected
- Your code in your repository
What is a migration to Astro?
It moves a marketing site off Webflow, Framer or WordPress onto Astro, a framework that builds plain HTML pages, in a repository you own. The pages, URLs and structured data stay. It starts with an estimate in under 24 hours; our own 15-page site moved in one working week.
Who it is for
You need this if
- Your Webflow workspace or legacy site is repriced on or after 16 November 2026.
- You built on Framer and found there is no code export.
- Your WordPress site runs on more plugins than anyone can name.
- You want the HTML, the structured data and the redirects back, in code you own.
Included
What you get
- A URL inventory and a redirect map. Never a 404.
- Every page ported one to one, down to the meta tags.
- Structured data from one data file.
- Images sized at build time, assets cached for a year.
- A build that fails if any URL that has ever been live would answer nothing.
- The repository in your account, with notes on editing and deploying.
Timeline
How migration to Astro runs
-
Under 24 hours
The estimate
Every URL, template, CMS collection, form and redirect, counted into an inventory and a fixed quote that are yours either way.
-
Before a page moves
The capture
Every page saved as it is today, so the build cannot quietly lose a meta description.
-
To the date in the estimate
The port
Same copy, URLs and structured data, without the platform’s scripts.
-
Launch day
Check, switch, hand over
Every page and old URL checked, the sitemap resubmitted, the repository and hosting in your name.
Price
What migration to Astro costs
- First step
- An estimate in under 24 hours, with the URL inventory, the redirect map and a fixed quote
- Then
- Moved as it is: up to 15 pages from $5k; 15 to 50 pages from $10k; over 50 pages quoted from the estimate.
With a redesign, design and build included: $10k to $12k with basic interaction; from $15k with advanced motion, visuals and micro-interactions.
Templates, CMS items, forms and whether your editors need a CMS move the number. A larger redesign is quoted from a product sprint.
Results
Products we have shipped.
“…their ability to accurately estimate the timeline and effort required for each feature.”
Compare
Astro, Webflow, or Framer for a marketing site
| Astro | Webflow | Framer | |
|---|---|---|---|
| When it fits | You want speed, control of the markup and code you own. | A marketing team at an established company edits visually every week. We build it in Webflow. | A design-led team ships landing pages on the canvas often. Stay. |
| Who owns the code | You do, on hosting you choose. | Webflow hosts it. The export carries no working CMS. | Framer hosts it. There is no code export. |
| What it costs to run | Static hosting, plus a CMS if you add one. | A site plan and seats. Agency workspaces and legacy sites repriced on or after 16 November 2026. | A site plan and editor seats. |
Questions
Common questions about migration to Astro.
Do you always move sites to Astro?
No. When the people who run the site are a marketing team at an established company, Webflow is often the better home, and we build or rebuild the site there instead.
What happens to our rankings and URLs?
Every URL stays as it is or redirects to its new home, and none returns a 404. Each page is checked against the original, and the build fails if a URL that has ever been live would answer nothing.
How long does a migration take?
It depends on the number of pages, templates and CMS items, and the estimate gives you the date. Our own site, 15 pages with 33 redirects, took one working week.
Who edits the content after the move?
If your team works in Git, the content lives as files in the repository. If editors need a visual interface, we connect a headless CMS, and the estimate names it and what it costs to run.
Who owns the code afterwards?
You do. The repository and the hosting are in your accounts from the start, and a static site does not need us to keep running.
One way forward.
Thirty minutes with a builder, not a salesperson, to work out whether we are the right team for it. If we are not, we will say so.