Documentationmigrationwordpresscontent

Importing WordPress Content Into AstroWEBTheme

Q: Does AstroWEBTheme import a WordPress XML export automatically?

Not out of the box. This guide documents the mapping; `pnpm cms:import:dry` previews a content import against your configured content source before anything is written.

Q: What happens to old WordPress URLs?

Preserve them with redirects at the Cloudflare routing layer, or match the new slug to the old URL, before removing the old site.

How WordPress posts, pages, media, taxonomies, and redirects map into AstroWEBTheme's content collections when moving a site from WordPress to Astro.

By AstroWEBTheme · Oct 26, 2026 · Updated Nov 2, 2026

Mapping WordPress content into AstroWEBTheme collections

Moving away from WordPress is mostly a content-mapping problem, not a design problem. This guide documents how WordPress content types line up with AstroWEBTheme collections so a migration can be planned before any content is moved.

Posts and pages

WordPress posts map to the blog collection; WordPress pages map to static entries under src/site/content/pages/ or the pages content source, depending on whether the page needs to stay fully custom. Post content, featured images, excerpts, and publish dates carry over directly into frontmatter.

Media

WordPress media library files map to AstroWEBTheme’s R2-backed media model — public images and downloads go to the public bucket, with responsive variants generated at the configured breakpoints. pnpm media:sync:dry previews what a media sync would upload before anything is written remotely.

Taxonomies

WordPress categories and tags map to AstroWEBTheme’s categories and tags field collections respectively. Custom taxonomies can map to a project-specific field collection if the content model needs one.

Authors

WordPress authors map to entries in the team collection when author pages or bylines are part of the migrated site’s content model.

Redirects and URL continuity

The most SEO-sensitive step is preserving old URLs. Before launch, build a full URL-to-URL mapping between the old WordPress paths and the new Astro routes, and configure redirects at the Cloudflare routing layer for anything that changes. Canonical URLs, metadata, and schema should be reviewed per collection rather than assumed to carry over automatically.

A practical migration order

Inventory WordPress content, media, and taxonomies.
Map each content type to an AstroWEBTheme collection.
Dry-run the content and media import (pnpm cms:import:dry, pnpm media:sync:dry) and review the plan.
Build the URL-to-URL redirect map.
Apply the import, verify detail pages, feeds, and sitemap, then launch.

Need the assessment, mapping, and redirect work done for you? NViewsWEB runs WordPress-to-Astro migrations as a dedicated engagement.