Migrating a Small Business Site from WordPress to Astro and Cloudflare Pages

We are seeing more and more small businesses move their websites off WordPress and onto a static stack. This article walks through the Astro + Cloudflare Pages migration flow we actually run in production, step by step.

Why migrate at all

WordPress is flexible, but that flexibility comes at the cost of ongoing maintenance. Patching plugin vulnerabilities, keeping PHP up to date, backing up the database — these are too much for a business owner to carry alone.

Moving to a static site dramatically shrinks the attack surface. Because the code that builds the site only runs at build time, there is far less for an attacker to target in production.

The shape of a migration

A migration breaks down into four phases.

1. Content extraction — convert existing posts to Markdown/MDX
2. Template rebuild — reconstruct the layouts as Astro components
3. Redirect design — prepare 301 mappings from old URLs to new ones
4. DNS cutover — point the domain at Cloudflare Pages

Content extraction is almost always the most time-consuming step. When the post count is high, writing a conversion script is the reliable path.

Do not underestimate redirects

The most common way a migration goes wrong is a gap in the redirects. If you fail to carry forward the old URLs that search engines already value with proper 301s, you lose the organic traffic you spent years building.

The rule we follow: cross-reference the old sitemap against analytics, enumerate every URL that still receives traffic, and only then cut over.

In closing

A migration is not a one-off task. It is only complete once the ongoing operational design is in place too. By taking on maintenance and monitoring after the cutover as well, we aim for a state where the business never has to think about the technical layer.