WordPress to EmDash Migration: Honest Guide

EmDash is one of the more interesting projects in the CMS space right now. Built on Cloudflare's edge infrastructure, it wants to be a modern WordPress successor — native performance, built-in image optimization, developer-first architecture. That's a compelling pitch.

Here's what nobody else will tell you: EmDash is at v0.1.0 beta. It's not ready for production. We can't recommend migrating your WordPress site to EmDash today.

This page exists because we believe in technical honesty. We'll cover what migration looks like technically, what EmDash can do right now, what's missing, and — most importantly — what you should actually do while EmDash matures.

What EmDash Gets Right (Even at v0.1.0)

EmDash's architecture is genuinely compelling. It runs entirely on Cloudflare Workers and D1, meaning your CMS lives at the edge. Content gets served from the nearest Cloudflare data center to your visitor. That's not marketing fluff — it's a fundamentally different model than WordPress's origin-server approach.

Key technical wins:

• Edge-native by default — no origin server, no caching layer needed
• Built on Cloudflare Workers + D1 — SQLite at the edge
• Native image optimization via Cloudflare Images
• Modern content modeling with collections (similar to content types)
• No PHP — the entire stack is JavaScript/TypeScript

If you're tired of WordPress's PHP legacy, this stuff is exciting. But excitement doesn't equal production-readiness.

The Technical Migration Path (Theoretical)

If you were to migrate WordPress to EmDash today, here's what you'd actually be getting into:

Step 1: Export Content via WP REST API

WordPress's REST API (/wp-json/wp/v2/) gives you structured access to posts, pages, categories, tags, media, and custom post types. You'd write a Node.js script to pull all content and normalize it into clean JSON.

GET /wp-json/wp/v2/posts?per_page=100&page=1
GET /wp-json/wp/v2/pages?per_page=100&page=1
GET /wp-json/wp/v2/media?per_page=100&page=1

Custom post types registered with show_in_rest get included. ACF fields, custom meta — all extractable.

Step 2: Map Post Types to EmDash Collections

EmDash uses a collection-based content model. WordPress post types map roughly like this:

• post → Blog collection
• page → Pages collection
• Custom post types → Custom collections
• Categories/Tags → EmDash taxonomies (limited support currently)

Conceptually straightforward. Requires manual configuration. There are no automated migration tools for EmDash — none.

Step 3: Convert PHP Templates to Astro Components

EmDash pairs well with Astro for front-end rendering. Your WordPress theme's PHP templates need complete rewrites — not adjustments, full rewrites:

• header.php → Header.astro
• single.php → [slug].astro dynamic route
• archive.php → Collection listing pages
• functions.php → Astro integrations + middleware

This isn't a find-and-replace operation. It's a full rebuild.

Step 4: Plugin Replacement

This is where things fall apart. WordPress gets much of its power from plugins. EmDash has almost none of that.

WordPress Plugin	EmDash Equivalent
Yoast SEO	❌ Does not exist
WooCommerce	❌ Does not exist
Gravity Forms / CF7	❌ Does not exist
WPML / Polylang	❌ Does not exist
Elementor / Gutenberg	❌ No visual editor
Wordfence	Not needed (Cloudflare native)
W3 Total Cache	Not needed (edge by default)

Two out of seven is not a passing grade.

Step 5: Media Migration to Cloudflare R2

WordPress media files (wp-content/uploads/) would move to Cloudflare R2 object storage. This part actually works well — R2 is S3-compatible, so migration scripts are straightforward. Rewriting URLs from old WordPress paths to R2 is mechanical, just tedious.

What Is NOT Ready Yet

Here's specifically what's missing from EmDash v0.1.0:

No Migration Tooling

Zero. No importer, no CLI migration tool, no WordPress plugin that exports to EmDash format. Every migration is 100% custom code.

No SEO Plugin Ecosystem

No equivalent to Yoast, Rank Math, or All in One SEO. No XML sitemap generation, no meta tag management UI, no schema markup tools, no redirect managers. You'd build all of this yourself or handle it in Astro.

No Visual Editor

EmDash's editing experience is early-stage. No block editor, no page builder, no drag-and-drop. Content editors used to Gutenberg or Elementor will find it extremely limiting.

No E-commerce

No WooCommerce equivalent. No product management, no cart, no checkout. If you sell anything, EmDash isn't an option right now.

No Form Handling

No native forms. You'd wire up third-party services like Formspree or build custom Workers.

No Multilingual Support

No WPML or Polylang equivalent. No locale routing, no translation management.

No Community or Plugin Ecosystem

WordPress has 59,000+ plugins and millions of developers. EmDash has a small (growing) community and essentially zero third-party plugins. When you hit a problem, you're largely on your own.

Our Honest Recommendation

We track EmDash closely. We've written about what it means for the WordPress ecosystem and how it compares to WordPress architecturally. It has real potential.

But potential isn't production-readiness.

If you need to leave WordPress today, here's what we actually recommend:

Option A: Migrate to Next.js

For dynamic sites, applications, and e-commerce, WordPress to Next.js migration gives you a proven stack with mature tooling, strong community support, and production-grade performance.

Option B: Migrate to Astro

For content-heavy sites, blogs, and marketing sites, WordPress to Astro migration delivers near-perfect Lighthouse scores with a stable framework and excellent DX.

Both support headless CMS backends — Sanity, Contentful, Payload, Strapi — that have the content modeling, SEO tools, and editor experience EmDash doesn't have yet.

Then Evaluate EmDash at v1.0

When EmDash reaches v1.0 — with migration tools, SEO features, a mature editor, and a plugin ecosystem — we'll be among the first agencies running production migrations. We'll update this page as things develop.

The smart play: migrate to a proven headless stack now, keep your content layer clean, and you'll be positioned to swap in EmDash later with minimal friction. That's the beauty of headless — your CMS is a replaceable component, not a monolith.

Timeline and Pricing (When EmDash Is Ready)

We're not quoting EmDash migrations today because we'd essentially be charging you to beta-test. That's not how we operate.

For the recommended alternatives:

• WordPress to Next.js: 4-8 weeks, starting at $12,000
• WordPress to Astro: 3-6 weeks, starting at $8,000

Both include full SEO preservation, content migration, 301 redirect mapping, and team training.