Move a content-led WordPress website to a modern, open-source CMS built around Astro, TypeScript and serverless deployment.
I help businesses assess whether EmDash is a practical fit, model the destination content, move WordPress posts and media, and protect important URLs through a staged launch. Because EmDash is currently in beta preview, the first deliverable is an honest fit assessment rather than an automatic recommendation to replatform.
What is EmDash?
EmDash is an open-source CMS introduced by Cloudflare as a modern, spiritual successor to WordPress. It provides an admin interface, structured content, media management, roles, plugins and migration tooling while using a TypeScript and Astro foundation.
On Cloudflare, an EmDash site can run on Workers with D1 for content data and R2 for media. It can also run on a Node.js server, so the CMS itself is not limited to one hosting provider.
The architectural difference is significant:
- No PHP application or traditional WordPress hosting stack.
- Astro for content-driven frontend development.
- Structured content that is separated from its rendered HTML.
- Sandboxed plugins with declared capabilities on Cloudflare.
- Passkey-first authentication and role-based access.
- Programmatic content management through a CLI and MCP server.
Why migrate WordPress to EmDash?
The strongest reason is not novelty. It is the opportunity to reduce the maintenance and security exposure of a traditional WordPress stack while keeping an editor-friendly CMS.
EmDash may offer a better direction when you want:
- A content-first website built with a modern TypeScript stack.
- Fewer dependencies on PHP hosting, caching plugins and server tuning.
- Plugin permissions that are explicit rather than full access to the application.
- Content schemas designed around the business instead of forcing everything into posts and metadata.
- A performance-focused Astro frontend deployed close to users on Cloudflare.
- A CMS people can edit while approved AI tools operate it programmatically.
- Open-source ownership without being tied to a hosted website builder.
When EmDash is a good fit
An EmDash migration is worth evaluating when:
- Publishing, documentation, marketing content or a resource library is central to the website.
- The current WordPress site is slowed down by accumulated plugins and theme code.
- You want a custom frontend and have access to ongoing TypeScript development support.
- Custom post types and fields would benefit from a cleaner content model.
- Cloudflare Workers, D1 and R2 fit your preferred operational stack.
- You are comfortable adopting a promising platform during its beta phase.
When not to migrate yet
EmDash is still in beta preview. WordPress has a much larger and more mature ecosystem, and many long-standing plugins have no direct EmDash equivalent.
I would not recommend an immediate production move when:
- A business-critical WordPress plugin has no tested replacement.
- The site needs a commodity theme and plugin ecosystem more than a custom build.
- The organisation cannot support ongoing development and platform updates.
- Ecommerce, membership or multilingual requirements have not been proven in the destination.
- The risk profile requires a mature platform with a long production history.
In those cases, the right outcome may be a pilot, a staged content section, or improving the existing WordPress site while EmDash matures.
What can move from WordPress?
EmDash documents WordPress import support for:
- Posts and pages.
- Featured images and attached media.
- Categories and tags.
Custom migration work can additionally cover:
- Authors, publication dates, drafts and content status.
- Custom post types mapped into purpose-built collections.
- Custom fields mapped into typed schema fields.
- Navigation and important site settings.
- SEO titles, descriptions, canonical decisions and social images.
- Redirects from old WordPress paths to the new routes.
Custom content and older page-builder output need more deliberate work than standard posts. The destination should preserve meaning and editorial control rather than reproduce serialized HTML and plugin metadata unchanged.
Themes and plugins are rebuilt, not copied
A WordPress theme cannot be installed in EmDash. Its design and useful behaviour need to be translated into Astro layouts, routes and components.
The same principle applies to plugins. I map what each plugin does for the business, then decide whether the capability is available in EmDash, should be rebuilt as a scoped plugin, belongs in Cloudflare, or is no longer needed.
This is an opportunity to remove years of accumulated technical debt, but it also means the migration needs real product and engineering decisions. It is not a one-click clone of the existing site.
SEO and launch protection
A new CMS does not justify losing established search visibility. Before launch, the migration should inventory indexed WordPress routes, preserve useful metadata, rewrite internal links and create specific redirects for paths that change.
The deployed Astro site also needs verified canonicals, robots rules, structured data, Open Graph metadata and sitemap coverage. Preview environments should remain non-indexable until the production domain and redirect behaviour are ready.
A sensible adoption path
For a beta platform, I recommend four commercial stages:
- Fit assessment covering plugins, content types, editorial workflow and operational risk.
- Migration prototype using a representative sample of content and media.
- Full migration and acceptance testing in a protected environment.
- Controlled launch with redirects, monitoring and a documented fallback position.
This gives the business useful decision points before committing the entire website.
Frequently asked questions
Is EmDash a Cloudflare CMS?
Cloudflare introduced and open-sourced EmDash. It is designed to run especially well on Cloudflare Workers with D1 and R2, but it can also run on Node.js with other supported database and object-storage options.
Is EmDash ready to replace WordPress?
It is currently in beta preview. It can be evaluated for real projects, but readiness depends on the site's features, risk tolerance and access to development support. A proof of concept should come before a high-risk production migration.
Can WordPress posts and images be imported?
Yes. EmDash includes WordPress migration support for posts, pages, media and taxonomies. Custom post types, page-builder content and plugin-owned data need additional mapping and validation.
Can WordPress plugins move to EmDash?
Not directly. Their capabilities need to be replaced, rebuilt or removed. EmDash plugins use a different architecture, including sandboxed execution with declared permissions when deployed on Cloudflare.
Should an online store move from WordPress to EmDash?
That depends on the commerce requirements and maturity of the required integrations. If selling products is the core requirement today, Shopify may be the more appropriate destination. EmDash is currently a more natural discussion for content-led websites and carefully scoped pilots.
Evaluate the destination before committing to it
If EmDash fits the direction you want for your content platform, I can assess the WordPress site, prototype the migration and give you a clear view of the opportunity and the current risks.