Migrate WordPress to EmDash: The Cloudflare Guide

Migrating a WordPress site to EmDash involves two distinct projects: content migration and theme/plugin rebuild. The content migration process uses an importer to move posts, pages, media, authors, and taxonomies. The theme and plugin rebuild, however, requires a complete rewrite of PHP templates, page builder layouts, shortcodes, and plugin behavior, as EmDash does not support WordPress themes or plugins.

Cloudflare's importer simplifies the content side of the migration, typically completing within a day or two. But it is the theme and plugin rebuild that determines the overall schedule and feasibility of the migration. The guide covers the entire migration process, including factors that may influence whether the migration is worth undertaking.

EmDash is an open-source content management system developed by Cloudflare. It is built on TypeScript and Astro, and offers a React-based admin interface. Content is stored in D1 (SQLite) and media in R2 when deploying to Cloudflare. Plugins run in sandboxed Worker isolates with declared capabilities, and authentication is passkey-first, utilizing providers such as GitHub, Google, and Microsoft. EmDash is not a WordPress fork, PHP runtime, theme engine, or visual page builder.

One of the key advantages of EmDash over WordPress is the potential cost savings. Cloudflare's pricing model, which includes Workers, D1, and R2 services, can lead to monthly bills of $5 to $15 for a content site with under 100,000 page views. In comparison, managed WordPress hosting typically ranges from $15 to $60 per month, with premium plugins adding $200 to $800 annually. The gap in cost is estimated at $20 to $50 per month, but the investment may not justify a 40-hour rebuild at a typical consulting rate.

The decision to migrate to EmDash should be based on specific criteria. Content sites with multiple sites, slow or plugin-heavy WordPress stacks, developers working with Astro or TypeScript, those seeking enhanced security, or organizations launching new sites from scratch are more likely to benefit from the migration. However, for a single small blog with minimal technical requirements, the savings may not outweigh the effort involved.