Updated 2026-11-10: rewritten as a decision guide with a decision matrix, a hypothetical feature mapping, work drivers, acceptance checks and rollback planning. Facts were checked against the linked EmDash, Cloudflare and WordPress documentation as of 2026-11-10.

Converting a WordPress site to EmDash CMS is a rebuild, not an upgrade. Content can be imported, but PHP code does not transfer, so each template, form and plugin behavior you still need must be rebuilt, replaced, or kept through a separate service that you test against the new site. This guide is about choosing well, not about selling the move. If you first want to know what EmDash is and how day-to-day editing works, start with our introduction to EmDash CMS.

Name the problem before naming the platform

WordPress is not broken by default, and plenty of WordPress sites are well run. It also handles structured content natively: custom post types organize content kinds with their own admin screens, and plugins can add custom meta boxes that save structured values as post metadata. Needing services, locations or case studies with their own fields is not by itself a reason to migrate.

Reasons that do hold up are more specific:

  • The site is being redesigned anyway and you want an Astro front end with the CMS in the same app.
  • Important content is locked inside page builder layouts and you want it as plain fields.
  • Plugins overlap and nobody is sure which are still needed.
  • Editors need a smaller, clearer set of screens.

Each has a WordPress answer too: reduce overlapping plugins, clarify roles, move builder content into post types with meta fields, improve theme templates. The question is which path gives the result with work you can fund and maintain afterwards.

Decision matrix

Your situationLeans toward improving WordPressLeans toward rebuilding on EmDash
Site mostly works and editors are comfortableYesNo
You only need structured fieldsYes, post types plus meta fields cover thisOnly if other reasons apply
A redesign with Astro templates is already plannedPossible with a headless setupYes
Revenue depends on commerce, booking, membership or course pluginsYes, unless each has a tested replacementOnly with a rebuild or replacement plan per feature
Most pages are page builder layoutsKeep the builder if it still meets your requirementsRebuild as Astro components after a rendered check of the import
No developer available for template changesExisting WordPress controls may be enough, though custom template changes still need supportNo, new fields need template work

The developer row matters more than it looks. EmDash is not a visual page builder: a schema field does not design or render itself, so every change that needs a new field also needs an Astro template update (see collections).

What moves and what does not: a hypothetical mapping

This is a hypothetical example, not a client site and not a default EmDash template. Imagine a services company with a service post type, a page builder homepage, a quote form plugin and a booking plugin.

Custom content fields. The service post type with summary, starting price and duration fields maps reasonably well. The importer can carry supported extra settings and metadata, but not every custom field or relation becomes usable automatically (migration guide). Each field you keep must be defined deliberately in a collection, and collection and field slugs cannot be renamed from the admin later, so naming is a design decision rather than a detail.

Layout and page builder content. The builder homepage will not arrive as a layout. Complex blocks and shortcodes need rendered checks after import, and server-rendered blocks may produce no visible content at all. Plan to rebuild those pages as Astro components and treat imported text as raw material.

Quote form. The form plugin does not come across. You can rebuild the form in the new site, replace it with a hosted form service, or keep an independent service the plugin only wrapped. In every case, fields, validation, spam control, the success message and delivery to email or a CRM must be tested on the new site. Importing the page that held the form does not create a working form.

Complex plugin behavior. The booking plugin is PHP and cannot run in EmDash unchanged (porting plugins). Simple post type behavior maps to collections, but business workflows, HTTP routes and integrations must be rebuilt, replaced with an external service or dropped. Native EmDash plugins run with application privileges, so anything rebuilt here needs the review you would give any custom code.

The rule across all four: content import is not functional compatibility. If a feature mattered on WordPress, it needs its own line in the plan.

What actually drives the work

The factors that move the price and timeline of a rebuild:

  • How many content kinds, fields and relations must keep working.
  • What share of pages are builder layouts versus plain content.
  • Media volume. The WordPress export holds attachment URLs, not files, so media download is a separate step and the source site must stay reachable while it runs.
  • How many plugin behaviors you rebuild, replace or drop, and how each one is tested.
  • URL preservation, redirects, canonical tags, locales and SEO metadata.
  • Rendering. Server-rendered pages read current published content on the next request, prerendered pages need a rebuild, and caches can delay what visitors see (why EmDash).
  • Hosting. Node hosting and Cloudflare are both documented. The Cloudflare option uses Workers with a D1 database and R2 media. Neither is static or maintenance free, and running cost depends on providers, storage and traffic.
  • Training, roles and permissions for editors.

Staying on WordPress has its own drivers: a plugin audit, role cleanup and template improvements are real work. Budget both options on their actual scope rather than assuming either one is cheaper.

Rehearsal, acceptance checks and rollback

Rehearse the import on a staging copy, and agree on acceptance checks before anything touches production:

  1. Counts by content type and status match your inventory. Private and pending items import as drafts, so visibility rules are not recreated and must be rechecked.
  2. Publication dates on imported drafts are reviewed before publishing, since they may be preserved from WordPress.
  3. Media resolves, URLs are preserved or redirected, canonical tags, locales and metadata are correct, and builder-heavy pages have been checked visually.
  4. Every retained critical workflow works end to end: forms are submitted and delivered, and any booking, checkout or member login completes on staging.
  5. Roles behave as intended, and drafts are not reachable when logged out.
  6. A tested recovery path exists: a full database backup suited to the database adapter, media backed up separately, the matching app and configuration, and secret keys stored safely (backups guide). EmDash JSON exports cannot be restored by EmDash, and content revisions, where enabled, recover individual entries rather than the whole site.

Keep the WordPress deployment and its backups recoverable through an agreed rollback window. It need not stay publicly live, but it must stay reachable while media downloads run. Freeze edits during the cutover, and plan how to reconcile edits, submissions or orders made on the new site if you roll back later. A freeze alone does not cover work done after cutover.

Who benefits, and who should not do this

A rebuild suits teams with a redesign already planned, a developer available for templates, and content worth restructuring. It is the wrong move when revenue runs through plugins you cannot rebuild or replace, when nobody can maintain templates, or when editors are already comfortable and the budget only covers content fixes.

Your next action

Make a two-column inventory of every content type and every active plugin. Mark each as content, behavior or both, and write rebuild, replace or drop next to every behavior item, with a note on whether a tested replacement exists. The decision rests on that feasibility and on the real scope, not on how many plugins you count. If must-keep behaviors have no workable replacement, improve WordPress. If every item has a credible plan and a redesign is coming, talk to us about EmDash CMS development with the inventory in hand.

Limits of this guide

The documentation was checked on 2026-11-10 and will change. We have no performance or cost comparison evidence and have not tested your specific plugins. Whatever you choose, updates, backups, access control and monitoring remain your responsibility.

Sources