WordPress powers roughly 43% of all websites, but its aging PHP architecture, plugin security crisis (11,300+ new vulnerabilities in 2025), and server-dependent hosting model are pushing teams to look for modern alternatives. Cloudflare's EmDash is the most compelling option to emerge in years: TypeScript-native, serverless, sandboxed plugins, and MIT-licensed.

But migrating a production WordPress site isn't trivial. You need to move content, preserve URLs for SEO, handle custom post types, migrate media, and rebuild theme functionality. This guide walks through every step of the process with practical examples and gotchas we've encountered in real migrations.

Whether you're running a personal blog or a multi-author publication, this step-by-step guide will get you from WordPress to EmDash without losing content, rankings, or your sanity.

1Pre-Migration Audit & Planning

Before touching any export buttons, audit your WordPress site to understand the scope of the migration:

• Content inventory: Count posts, pages, custom post types, and media files. Use wp post list --post_type=any --format=count via WP-CLI.
• Plugin audit: List all active plugins and categorize them as content-affecting (ACF, Yoast SEO), functional (WooCommerce, contact forms), or cosmetic (sliders, galleries). Content-affecting plugins need the most migration planning.
• URL structure: Document your permalink structure. EmDash uses Astro file-based routing, so you'll need to match your existing URL patterns.
• Custom fields: If you use ACF or custom meta fields, map each field to an EmDash schema field type.
• Media dependencies: Check for hotlinked images, CDN configurations, and any media processing plugins.

2Method 1: WXR File Export

The simplest migration path uses WordPress's built-in export format:

1. In WordPress admin, go to Tools → Export
2. Select "All content" to export posts, pages, comments, custom fields, categories, tags, and navigation menus
3. Download the WXR (WordPress eXtended RSS) XML file
4. In your EmDash project, run the import command with the WXR file path

# Export from WordPress (via WP-CLI)
wp export --dir=/tmp/exports

# Import into EmDash
emdash import wordpress /tmp/exports/site.xml

The WXR import automatically maps WordPress posts and pages to EmDash content collections and pulls attached media into EmDash's media library.

3Method 2: EmDash Exporter Plugin

For larger sites or sites you want to migrate incrementally, the EmDash Exporter plugin is the better option:

1. Install the EmDash Exporter plugin on your WordPress site
2. Generate a WordPress Application Password for secure API access
3. The plugin creates a secure endpoint that only your EmDash instance can access
4. Point your EmDash instance at the endpoint and it pulls content directly

This method is faster for large sites because it streams content directly rather than going through an intermediate file. It also handles incremental syncing, so you can run it multiple times during a migration window.

4Migrating Custom Post Types & ACF Fields

WordPress custom post types (CPTs) and Advanced Custom Fields (ACF) require manual schema mapping in EmDash. For each CPT:

1. Create a matching EmDash schema in the admin panel with the same fields
2. Map ACF field types to EmDash field types (text → text, image → media, repeater → array)
3. Run the import with the --map-types flag to route CPTs to the correct EmDash collections

// Example: seed.json schema for a WordPress "portfolio" CPT
{
  "collections": {
    "portfolio": {
      "fields": {
        "title": { "type": "text", "required": true },
        "client_name": { "type": "text" },
        "project_url": { "type": "url" },
        "gallery": { "type": "media", "multiple": true },
        "technologies": { "type": "tags" },
        "featured": { "type": "boolean" }
      }
    }
  }
}

5Media Library Migration

Both migration methods automatically import attached media (images, PDFs, videos) into EmDash's media library. However, there are edge cases to watch for:

• Hotlinked images: Images referenced by URL but not in the WordPress media library won't be imported. Run a scan for external image URLs before migrating.
• Image sizes: WordPress generates multiple thumbnail sizes per image. EmDash handles responsive images differently through Astro's image optimization. You only need the original files.
• CDN references: If your WordPress site uses a CDN plugin that rewrites image URLs, you may need to revert URLs to local paths before export.

6URL Structure & SEO Preservation

Preserving your URL structure is critical for maintaining SEO rankings. EmDash uses Astro's file-based routing, so you need to create page files that match your WordPress permalink structure:

# WordPress permalink: /%postname%/
# EmDash Astro route: src/pages/[slug].astro

# WordPress permalink: /%category%/%postname%/
# EmDash Astro route: src/pages/[category]/[slug].astro

# WordPress permalink: /blog/%postname%/
# EmDash Astro route: src/pages/blog/[slug].astro

For any URLs that change, set up 301 redirects. On Cloudflare, you can use Page Rules or Bulk Redirects. For self-hosted deployments, configure redirects in your web server or use Astro's redirect configuration.

Don't forget to migrate your XML sitemap, update Google Search Console with the new sitemap URL, and submit a change of address if your domain changes.

7Rebuilding Theme Functionality in Astro

WordPress themes can't be directly ported to EmDash. You'll need to rebuild your theme as an Astro project. The good news: EmDash includes a Block Kit Agent Skill that lets you instruct an AI agent to convert WordPress theme components to Astro.

Key mapping from WordPress to EmDash/Astro:

8Plugin Replacement Strategy

Most WordPress plugins fall into categories with EmDash equivalents or alternatives:

9DNS Cutover & Go-Live Checklist

• Run a final content sync from WordPress to EmDash
• Verify all pages render correctly on the EmDash staging URL
• Test all forms, interactive components, and third-party integrations
• Set up 301 redirects for any changed URLs
• Update DNS records to point to Cloudflare (or your Node.js server)
• Submit updated sitemap to Google Search Console
• Monitor 404 errors for the first 48 hours and add redirects as needed
• Keep WordPress running in read-only mode for 30 days as a fallback

10Post-Migration Verification

After going live, verify these critical items:

• Content parity: Spot-check 10-20 pages across different content types
• Image rendering: Verify all images load correctly and responsive sizes work
• Core Web Vitals: Run Lighthouse on key pages — Astro typically scores 95+ on performance
• Search Console: Monitor for crawl errors and indexing issues over the first week
• Analytics continuity: Confirm tracking codes are firing on all pages

11Common Migration Pitfalls

• Shortcodes: WordPress shortcodes like [gallery] or [contact-form] won't render in EmDash. Search your content for shortcode patterns and replace them with Astro components before or during migration.
• Hardcoded URLs: Content with hardcoded https://yoursite.com/wp-content/uploads/ paths needs URL rewriting.
• Database-dependent plugins: Plugins that store data in custom WordPress tables (e.g., WooCommerce orders) need separate data migration strategies.
• PHP-generated content: Any content generated dynamically by PHP (e.g., calculated fields, dynamic sidebars) needs to be rebuilt as Astro components or EmDash plugins.
• Comments: If you use WordPress comments, plan for a migration to a third-party system like Disqus or a custom EmDash plugin.

12How Lushbinary Handles WordPress-to-EmDash Migrations

At Lushbinary, we've been building on modern CMS platforms and serverless architectures for years. Our WordPress-to-EmDash migration service covers the full lifecycle:

• Pre-migration audit with content inventory and plugin dependency mapping
• Custom schema design for complex content types
• Astro theme development matching your existing brand and design
• SEO preservation with redirect mapping and Search Console monitoring
• Deployment on Cloudflare Workers or AWS infrastructure
• 30-day post-migration support with monitoring and issue resolution

❓ Frequently Asked Questions

📚 Sources

• Cloudflare Blog: Introducing EmDash
• Patchstack: State of WordPress Security 2026

Content was rephrased for compliance with licensing restrictions. Technical details sourced from official Cloudflare documentation as of April 2026. Features may change — always verify on the official EmDash documentation.