Honest scoping before export
We inventory custom post types, page builders, commerce plugins, and integrations that will not translate literally—so migration cost reflects reality, not a best-case demo.
WordPress · EmDash · Astro
WordPress to EmDash—Without Pretending Plugins Translate
If WordPress plugin updates keep breaking your site—or security stakeholders are nervous about extension supply chains—migrating to EmDash on Astro can be a sensible path. We scope migrations honestly: content export first, theme rebuild second, integrations third, with redirects and SEO parity baked into cutover.
How we approach migration
Content first, theme second
Posts, pages, and media move via WXR or the EmDash exporter. Theme rebuild in Astro/EmDash comes after content validation, with redirects and SEO parity planned alongside design.
Sandboxed behaviour, not plugin roulette
Must-have workflows become small, capability-scoped plugins or integrations—not a trolley of legacy PHP extensions sharing one runtime.
Typical migration steps
-
1 / Inventory
URLs, forms, memberships, analytics, and editorial workflows that must survive cutover.
-
2 / Export & validate
WXR or EmDash exporter; verify media, metadata, and custom post type mapping.
-
3 / Rebuild theme
Astro/EmDash components with intentional performance and accessibility—not accidental via plugins.
-
4 / Cut over
Redirects, monitoring, and a rollback plan—commerce and membership edge cases scoped separately.
Read more in our posts on EmDash and a practical path off WordPress and WordPress is dead .
Common questions
What is EmDash?
EmDash is Cloudflare’s open-source CMS built on Astro. It keeps a familiar publishing model while sandboxing plugins and supporting serverless or Node hosting. It is early software—we will tell you plainly if preview limitations block your timeline.
How long does a WordPress migration take?
Exporting posts, pages, and media often takes minutes for typical blogs. Harder work is schema mapping, theme rebuild, commerce or membership plugins, redirects, and cutover testing. We quote after an inventory of what must survive.
Will our URLs and SEO rankings survive?
We plan redirects, canonical tags, and sitemap updates as part of cutover—not as an afterthought. Rankings depend on many factors, but we treat URL parity and metadata as non-negotiable migration deliverables.
When should we stay on WordPress?
If deeply customised membership, marketplace, or ERP-linked workflows only exist as fragile plugin stacks—and those integrations still earn their keep—staying put can be rational. We will say so if that is your situation.