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.
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
- REST API, XML, or database content capture
- Shortcode and plugin dependency report
- Media localization and missing-file checks
- Legacy URL redirect map
- SEO metadata normalization
- WordPress removal acceptance evidence
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.