Toolkit capability
WordPress to Astro migration
Plan a WordPress to Astro migration that preserves posts, pages, media, redirects, metadata, forms, and publication state.
WordPress to Astro migration
Replace the WordPress runtime, not the content model.
WordPress hides critical behavior across themes, plugins, shortcodes, media libraries, and database fields. A durable migration identifies those dependencies before choosing the Astro content model.
What the process produces
06 concrete deliverables- 01REST API, XML, or database content capture
- 02Shortcode and plugin dependency report
- 03Media localization and missing-file checks
- 04Legacy URL redirect map
- 05SEO metadata normalization
- 06WordPress removal acceptance evidence
Capability and requirements
What this workflow does, and what it needs.
Required inputs apply to this workflow. Conditional tools apply only when the project, platform, or chosen service needs them. A missing optional integration does not block unrelated Go for Launch checks.
Required for this workflow
Inputs and evidence
- A WordPress export, REST API response, or equivalent content capture
- A media, route, redirect, publication-state, and plugin-output inventory
- An Astro project checkout for the replacement site
Only when applicable
Conditional tools and access
- Database or administrator access only when exports and public output are insufficient
- Plugin credentials only for behavior that must be reproduced
- Hosting and DNS access only for staging, cutover, and public verification
Inventory the WordPress surface
Collect post types, taxonomies, menus, users, media, templates, redirects, custom fields, plugin output, and publication status. Rendered pages alone do not expose the full contract.
Normalize before import
Convert blocks, shortcodes, embedded media, and plugin fields into a stable intermediate format. Preserve source identifiers so every Astro page can be traced back to evidence.
Retire the runtime safely
Validate routes, feeds, sitemaps, forms, search, canonical URLs, and redirects before decommissioning WordPress. Keep a rollback path until the canonical site is verified.