WordPress to Astro Migration Service, Backed by 28,502 Tracked Switches

• The flow runs 13.2 to 1 toward Astro. Since May 28, 2026, TechnologyChecker.io's crawl has seen 28,502 domains drop WordPress for Astro and 2,160 go the other way.
• 17.2% of the companies that moved are technology firms, against 3.4% of all WordPress companies (software, IT services and internet; 18,396 movers matched to a company).
• 67.8% of movers have 1–10 employees, close to WordPress's own base (66.1%). This is not only an enterprise move.
• WordPress runs on 33× as many live domains as Astro (287,180 vs 9,555,391), and companies with 501+ employees make up 1.1% of its users against 1.6% for WordPress.
• 7,113 domains run both today, often an Astro site on one host and a WordPress blog or headless backend on another, or a move still in progress.

WordPress can run almost any site, which is why it runs so many. Teams leave when a content site spends more time on plugins, updates and speed fixes than on publishing.

They work at different layers. WordPress is where editors write and how most sites are served; Astro is a framework that builds the public site to HTML, from files or from WordPress itself. That is why a move can retire WordPress or keep it behind the scenes.

Dimension	WordPress	Astro
What it is	CMS: editors write in wp-admin and the theme renders each page	Web framework that builds content sites to HTML from files or a CMS
Rendering	PHP on every request, unless a caching plugin or the host serves a copy	Built to static HTML; server rendering per page where you need it
JavaScript	Theme, plugin and page-builder scripts on most pages	None by default; a component loads its own only where it's used
Editing	The block editor in wp-admin, for anyone on the team	Markdown files, headless WordPress, or a CMS such as Sanity or Storyblok
Extensions	A plugin for almost everything, each one more code to update	Integrations for CMSs and hosts; other features are written into the site
Hosting	A PHP host with a database, often managed WordPress hosting	Any static host or CDN, such as Cloudflare, Netlify or Vercel
Security and updates	Core, theme and plugin updates, and a login page on the public site	No server code or admin login on a static site; dependencies update in the repository
AI agents	AI plugins and assistants inside wp-admin	Any coding agent in your repository: Claude Code, Cursor, Codex
Best for	Sites run by editors, and stores or member areas built on plugins	Content and marketing sites where speed and control matter

Counted by TechnologyChecker.io's crawl. Switched = dropped WordPress on every host we track since May 28, 2026 and currently runs Astro. A drop is a tag disappearing from our crawl, not a confirmed cancellation. 7,113 domains run both today. Counts are domains, not accounts.

We matched 18,396 of the 28,502 domains that moved to a company record. Technology firms lead at 17.2%, 5.1× their share of WordPress's base, followed by advertising services, business consulting and services, and construction. By size, the movers look like WordPress's own customers.

Astro ranks #2 among the destinations we measure for domains that drop WordPress.

Next.js

62,496

Astro

28,502

Wix

7,112

Squarespace

6,097

Webflow

5,815

Price follows the size of the site, counted in pages from your sitemap, CMS items included. Each package covers the rebuild, the content import, redirects, testing and launch. Stores, member areas, multilingual plugins such as WPML and custom plugins are scoped on the call, because that is where WordPress estimates go wrong.

The right method depends on whether you have React developers and whether marketing still needs to publish without them.

Costs and timelines are typical market ranges for planning, not figures from our data. Our own price for your site comes from the calculator above.

• Page-builder and shortcode markupPosts built with Elementor, Divi or WPBakery export as builder markup and shortcodes, not clean content. A converter copies the clutter across.

  Each builder layout becomes an Astro component that matches the design, and every post's content is cleaned of builder markup and shortcodes.

• Plugins doing real jobsForms, SEO metadata, redirects, search and analytics often come from plugins, and each one stops working the day WordPress goes.

  We list every active plugin on the scoping call and replace each job: a form handler, metadata in the content, redirects at the host, a search index built with the site.

• WordPress URLs and archivesDate-based permalinks, category and tag archives, /page/2/ pagination, feeds and attachment pages all have URLs Google already knows.

  We keep every URL we can, 301 the rest, rebuild the RSS feed and the sitemap, and check every old URL against the new site before launch.

• Images in /wp-content/uploads/Posts point at images in /wp-content/uploads/, often in several sizes, and other sites link straight to them.

  We move the media library, serve images through Astro's image pipeline, and keep or redirect the old upload paths so links and image search don't break.

• Editors losing wp-adminWriters who publish in wp-admin every day need somewhere to write after the move.

  We pick the editing setup with you: WordPress as a headless CMS, a CMS such as Sanity or Storyblok, or Markdown with an AI agent. The team is trained before launch.

• Stores, members and commentsWooCommerce, membership plugins and comments need a server and a database; a static site has neither.

  We scope them on the call. Comments move to a hosted service or become static, and a store or member area stays on its own platform or runs on Astro's server rendering.

You don't have to retire WordPress. In a headless setup, editors keep writing in wp-admin while Astro builds the public site from the WordPress REST API, with WordPress moved to a subdomain such as cms.yoursite.com. Visitors only ever load the Astro site.

Our crawl sees 7,113 domains running WordPress and Astro at the same time (Nov 5, 2026). Some are partway through a move; many are a deliberate split.

If your editors won't leave wp-admin, we build the Astro front end on your WordPress first and move the content later, or never.

Ask any partner these questions before you sign, us included. A fixed price before anyone has looked at your interactions and CMS is a guess you pay for later.

1. 01
   EstimateEnter your site's address. The calculator counts your posts, pages and archives from the sitemap WordPress or your SEO plugin publishes.
2. 02
   Scoping call and fixed quoteWe go through your plugins, page builder, forms and editing needs, agree a full move or headless, and send a fixed price and timeline.
3. 03
   BuildOur engineers rebuild the templates first, using AI agents for the repetitive parts such as content clean-up, then move the content and check every page against the live site.
4. 04
   LaunchWe switch DNS, watch errors and Search Console, and hand over the repository and the editing setup.

TechnologyChecker sells this migration. The switching numbers come from the same crawl that powers our technology profiles and are not adjusted for this page.