WordPress migration
From WordPress to Astro and Cloudflare, without losing your place in Google.
I move larger WordPress sites to a fast setup without plugins. Every old URL keeps working, and your editors keep publishing on their own.
- Projects
- From €10,000
- Way of working
- Fully remote
- Stack
- Astro · Cloudflare · headless CMS
When it pays off
A migration is for sites that have a job to do. The site brings in leads, holds a knowledge base or catalogue, runs in several languages, or has editors working in it every week.
That is usually also when WordPress starts to pinch. The site gets slower as content piles up, every update is a gamble, and the hosting plan keeps needing a bigger size.
For a small site on a tight budget, WordPress with a good theme is fine. In that case I’ll tell you not to migrate.
How a migration runs
- 01
Inventory
I pull every URL from your sitemap, Search Console and analytics, and work out what each plugin does. After that you know what moves over, what can go and what it costs.
- 02
Content model and CMS
Your content gets fixed fields instead of loose HTML. We pick the CMS your editors will use together. That can be a headless CMS like Sanity, or WordPress itself as the source if your team is used to it.
- 03
Building on a staging link
I build the site in Astro. You follow along on the staging link whenever you like, with your real content in it.
- 04
Moving the content
I move the content with scripts, not by hand. Images go to Cloudflare as originals and are served at the right size for each screen.
- 05
Redirects and launch
Every old URL gets a 301 to its new address, in a single hop. Titles, descriptions and structured data come along. After launch I keep an eye on Search Console for a few weeks.
What you get
A page is built once when you publish, not on every visit. Cloudflare serves it from the server closest to your visitor. The homepage of this site is 47 kB of HTML and goes over the wire in under 10 kB.
There are no plugins left to update every week, and no database or login page on your domain for bots to hammer. Before a new version goes live, the whole site is built and checked. If something fails, the old version stays up.
Because content lives in fixed fields and the site is code in a repository, an AI agent can safely help out. It fills in fields or prepares a translation, and everything goes through the same checks.
Questions I often get
Will we lose our rankings in Google?
A migration often causes a few weeks of movement. With a complete redirect map, the same titles and descriptions and a faster site, that stays small.
Before launch I check that every old URL reaches its new address in a single hop, with no redirect chains.
Can our editors still publish on their own?
Yes. Your editors work in a CMS that only deals with content. They build pages from fixed blocks and see a preview of the real page before anything goes live.
The design can’t break along the way, because the CMS knows nothing about it.
What happens to forms, search and other plugins?
I go through every plugin. Some aren’t needed anymore, like caching and security. Forms and search get a small function on Cloudflare or a service that fits.
What does a migration cost?
Projects start at €10,000. The price depends on the number of pages, content types and languages.
After the inventory you get a proposal with scope and planning.
What does hosting cost afterwards?
Static pages on Cloudflare cost next to nothing. For forms and server functions a paid Workers plan is enough, and that is usually cheaper than a managed WordPress plan.
Do you work on site?
No, I work fully remote from the north of the Netherlands, for clients in Europe and beyond. We meet on video and work async in between.
Do you work with agencies?
Yes. An agency that wants to outsource a migration can bring me in as the developer behind the scenes.
Send me the URL of your site.
Tell me how many pages and languages it has and what is pinching now. I’ll take a look and let you know within two working days whether a migration makes sense.