wordpress2astro

Move beyond WordPress. Build for what’s next.

Content sites rebuilt on Astro — lighter pages, fewer moving parts, an editing experience your team chooses. Everything that isn’t simply content gets assessed on its own terms.

THREE POSSIBLE OUTCOMES

Not every WordPress site should become the same thing.

A

Astro site, static or SSR

Content in Markdown or MDX inside the repository. Ideal for sites that change weekly, not hourly.

blogsdocscompany sites
B

Astro + headless CMS

Editors keep a visual editing interface; the site is rendered by Astro. CMS chosen to fit your team.

editorial teamsmulti-authormultilingual
C

Custom application

When the “site” is really an application — accounts, transactions, workflows — it’s rebuilt as one, often beyond Astro.

portalsplatformsvia php2modern
ASSESSED SEPARATELY

There is no one-click WordPress migration.

These features carry business logic and data. Each needs its own functionality assessment before any outcome is recommended.

  • WooCommerce
  • Memberships
  • Booking
  • Payments
  • Custom plugins
  • User accounts & roles
PLUGIN PARITY

What your plugins become.

Typical outcomes for common plugins. Your site’s actual list is reviewed one by one before anything is recommended.

WordPress plugin to Astro parity
WORDPRESS PLUGINAREAIN ASTROPARITY
Yoast SEO / Rank MathSEOMetadata in content front-matter, sitemap and schema generated at buildFULL
Advanced Custom FieldsContent modelTyped content collections with validated schemasFULL
RedirectionURLsRedirect map maintained at the host or in configFULL
Contact Form 7 / Gravity FormsFormsRebuilt against a chosen form service; entries stored outside the sitePARTIAL
WPML / PolylangLanguagesBuilt-in i18n routing; translation workflow chosen per projectPARTIAL
Elementor / page buildersLayoutLayouts rebuilt as components; editors lose free-form drag-and-dropREBUILD
CommentsCommunityThird-party service or removed by agreementPARTIAL
WooCommerceCommerceSeparate assessment — kept, replaced by a platform, or rebuilt via php2modernASSESS
Memberships / bookingsAccountsSeparate assessment — needs a backend, not a static siteASSESS
Full — equivalent outcomePartial / Rebuild — works differently; agreed in scopeAssess — needs its own functionality assessment
CONTENT & SEO

What we carry across, deliberately.

Search visibility is protected by planning, not hoped for. Each item below is scoped and checked during the project.

Posts, pages & taxonomiesexported and mapped to content models
Media libraryre-encoded, responsive sizes
URLs & redirectsfull redirect map before launch
SEO metadatatitles, descriptions, canonicals, schema
Formsrebuilt with a chosen form service
Will our editors lose the WordPress dashboard?+

With outcome B they get a headless CMS editor instead. With outcome A, editing happens in files or a Git-based editor. We choose together.

How do we start?+

A conversation, then an Assessment of your site and plugins. Any migration follows as a separate Proposal and Contract.

Send us the URL. We’ll start there.

A public URL and a list of plugins is enough for a first conversation. No admin access needed.

Review my WordPress site