WordPress to Astro migration

Move from WordPress to Astro without losing your rankings

We replace your theme and plugins with code you own, move your content to Sanity and protect every URL. After launch, your team describes a change, checks the preview and approves it.

  • 50+ B2B SaaS teams trust us
  • 5.0 out of 5 stars
  • 5.0 out of 5 stars
  • 5.0 out of 5 stars
Timeline
8–12 weeksIncluding Sanity setup and the AI workflow.
SEO risk
MediumAstro carries over no URLs by itself. We rebuild your permalinks exactly.
Content
Carried overPosts, pages, images with alt text, categories, SEO titles
Design and features
RebuiltTheme, page builder layouts, plugin features, forms
Price
Fixed priceSet once we have checked every URL.

Why teams switch

Why teams pick Astro over WordPress

01

Nobody owns the plugin stack

Lots of plugins, some barely maintained and no one knows what the next update will break. In Astro, every feature is code you can read and version.

02

The site is slow and nobody knows why

Theme, builder and tracking plugins load scripts on every page. Astro ships plain HTML with no JavaScript by default and only adds scripts where a component needs them.

03

Your team wants to work with AI agents

Claude and Codex work best with real code and structured content. A database full of page builder markup is a poor place to start.

04

The site should match the product

With your own code, the website can share the design system, data or integrations of your product app, without a plugin in between.

WordPress vs. Astro

What changes for your team

CriterionWordPressAstro
MaintenanceCore, theme and plugin updates on a PHP server with a database.Pages built ahead of time from your own code, dependencies tracked in the repository.
Editing contentBlock editor or page builder in the WordPress admin.Sanity Studio, with fields shaped around your page types.
New pages and layoutsBuild it in the page builder or file a ticket with a developer.Your team describes the page, the AI workflow builds it from existing components, you approve the preview.
RedirectsThrough a plugin or the server config.In the Astro config, which the hosting adapter turns into real 301 rules.
New featuresFind a plugin, install it and hope it stays maintained.Built as code, with a development partner or your tech team.

WordPress

  • Core, theme and plugin updates on a PHP server with a database.
  • Block editor or page builder in the WordPress admin.
  • Build it in the page builder or file a ticket with a developer.
  • Through a plugin or the server config.
  • Find a plugin, install it and hope it stays maintained.

Astro

  • Pages built ahead of time from your own code, dependencies tracked in the repository.
  • Sanity Studio, with fields shaped around your page types.
  • Your team describes the page, the AI workflow builds it from existing components, you approve the preview.
  • In the Astro config, which the hosting adapter turns into real 301 rules.
  • Built as code, with a development partner or your tech team.

What moves

What comes over from WordPress

Content moves to Sanity. Anything that was a theme or plugin in WordPress becomes Astro code or goes away.

  • Migrated
  • Partly
  • Rebuilt
  • Replaced
  • Posts and pages

    Migrated

    We read them through the REST API and create Sanity documents with author, date, categories and slug.

  • Gutenberg blocks and shortcodes

    Partly

    Paragraphs, headings, lists and images become Portable Text. Custom blocks and shortcodes become their own content blocks.

  • Custom post types and ACF

    Partly

    Each post type becomes a Sanity document type and ACF fields become typed fields. Anything the REST API hides, we expose before the export.

  • Images and files

    Migrated

    We pull them from the media library with file name, alt text and caption, upload them to Sanity and link them to the content.

  • SEO data

    Migrated

    Titles and meta descriptions from Yoast or Rank Math go into dedicated SEO fields on each document.

  • Theme and page builder

    Rebuilt

    Elementor, Divi or theme layouts don't convert cleanly. We rebuild them as Astro components that Sanity fills with content.

  • Forms

    Rebuilt

    Contact Form 7 or Gravity Forms become form components that post straight to HubSpot or your CRM. We test every submission.

  • Plugins

    Replaced

    Each plugin gets a decision: custom code, an external service or drop it. Many solve problems Astro doesn't have, such as caching.

For your marketing

What keeps running for your marketing

Rankings are only one part. We also protect everything your team uses to measure leads and pipeline.

Tracking and attribution

GA4, the tag manager, UTM parameters and conversion events keep running from day one. In Astro tracking scripts load only after consent and do not slow the page. Before launch we compare every event on staging with the old site.

Forms and CRM

We replace Contact Form 7, Gravity Forms and similar plugins with custom forms connected straight to your CRM. Fields, hidden fields for the lead source and the handover to HubSpot, Salesforce or Pipedrive stay the same. We check test leads right in the CRM.

Demo booking

Demo and contact pages, calendars like HubSpot Meetings, Calendly or Chili Piper and your chat stay in place. Old demo URLs from ads, emails and sales decks redirect straight to the new page.

Visibility in AI search

Structured data, clear headings and an up-to-date sitemap are in place from launch. That helps Google and AI search like ChatGPT or Perplexity find your pages again quickly.

Content mapping

How WordPress content maps to Sanity

In WordPressIn Astro
PostsAn "Article" document type in Sanityauthor and category as references, not free text
Post body (HTML or blocks)Portable Textstructured text that Astro and AI agents can both read
Custom post typesTheir own document typessuch as case studies, integrations or use cases
ACF field groupsSchema fields with validationrequired fields and option lists instead of free input
Page builder pagesPages made of sectionseach section is an Astro component with fixed fields
PermalinksAstro routessame path where possible, otherwise a 301 to the new target

Process

How we migrate
your WordPress site

An example project: 10 weeks to launch. Afterwards we monitor rankings and redirects for four more weeks.

Migration from WordPress, example project

path digitalYour team

Your team

Access, sign-offs

SEO

URLs, redirects, tests

Build

Pages, content in Astro

Point at a step to see what happens there.

  1. Week 1 · Your team

    Kickoff

  2. Week 1 · SEO

    Audit and URL inventory

  3. Weeks 1–2 · SEO

    Redirect plan and content model

  4. Weeks 2–6 · Build

    Components and page templates

  5. Week 2 · Your team

    Redirect plan sign-off

  6. Weeks 6–8 · Build

    Content migration

  7. Weeks 8–10 · SEO

    SEO parity, QA and AI workflow

  8. Week 10 · Your team

    Launch

  9. After launch · SEO

    Launch and monitoring

Pre-launch checklist

What we check before launch

Stage 1 of 4

Before the build

Stage 2 of 4

During the build

Stage 3 of 4

Before launch

Stage 4 of 4

After launch

To be honest

When you should stay on WordPress

  • You have no development partner

    Your team handles copy and new pages from existing components. New features in Astro still need someone who writes code.

  • Your team wants to build pages visually

    If people want to lay out pages by drag and drop, Webflow is a better fit than Astro.

  • WooCommerce or a members area is central

    Checkout, logins and subscriptions would have to become their own application in Astro. That's a different project from a marketing site.

  • The site works, it just looks dated

    If plugins and load times aren't a problem, a redesign on WordPress is the shorter path.

Frequently asked questions about migrating from WordPress to Astro

What B2B SaaS teams want to know before moving from WordPress to Astro.

Can Astro import a WordPress site?

No, there's no one-click import. We read the content through the WordPress REST API, create it in Sanity and rebuild the pages as Astro components.

Can we keep WordPress as a headless CMS?

Technically yes, Astro can load content from WordPress. But then the server, updates and plugins stay with you. For structured content and the AI workflow, we recommend Sanity.

How does my team update the site after launch?

Copy, images and entries are edited in Sanity Studio. For bigger changes, your team describes them to Claude or Codex, checks the preview and approves it. It's the same workflow we use for our AI-native websites.

Will we depend on developers again?

Not for content or for pages built from existing components. New features, integrations or new kinds of components need a development partner. We'd rather say that up front.

How do redirects work in Astro?

We define them in the Astro config or directly at the host. The hosting adapter turns them into real 301 redirects and we test each one before launch.

Does WordPress stay live until launch?

Yes. Your site stays online until the domain switches over. Anything published in the meantime is picked up by the migration script before launch.

Plan your migration
from WordPress to Astro

Show us your site and your plugin list. We'll tell you what moves to Sanity, what becomes new code and how your team will work afterwards.