Migrate WordPress to EmDash, the right way
Done-for-you migration from WordPress to Astro + EmDash. Marketers edit via Claude or Codex. Devs stop firefighting plugins.
The premise of this engagement is simple: a 20-to-80-page WordPress marketing site, off WordPress in four weeks, on a stack your marketing team can drive without a developer in the loop. The first week catalogs every plugin, custom field, and shortcode currently in play — what migrates as-is, what gets cut, what gets rebuilt — and lands a content map you sign off on. The second week is the theme port, against typed EmDash schemas, with a working preview by Friday. The third week is the content move, link audit, and a 1:1 redirect map for every URL that changes. The fourth week is DNS cutover, a 60-minute training session on the Claude / Codex / MCP edit workflow, and the start of a 30-day support window. What you have at handoff is a Core Web Vitals-green Astro site on your own Cloudflare account — no developer tax for copy edits, no plugin treadmill, redirects validated against Search Console before we leave. Fixed-price, starting at $3,000.
The argument for moving in the first place lives in our manifesto post, and the side-by-side decision framework is in the WordPress vs EmDash comparison. Analytics wiring follows the open-source GA4 + GTM + UTM recipe. For gaps the EmDash ecosystem has not filled yet we run a custom plugin engagement, and most clients keep us on a maintenance retainer for the 60–90 days after cutover.
Built for the team that wants this solved.
- Agencies running 5–50 WordPress sites for clients who keep asking "can I just edit it myself?"
- In-house marketing leads on a slow, plugin-bloated WordPress site that takes a developer to update the hero copy.
- Anyone tired of WP plugin breakage on every Claude or Cursor edit.
8 things, in scope from day one.
- 01 Full content audit of your existing site (pages, posts, custom fields, embedded forms).
- 02 WordPress WXR export + EmDash content-type modeling (typed schemas, not "blob fields").
- 03 Astro theme port, mobile-first, Core Web Vitals green at handoff.
- 04 GA4 + GTM + UTM injector configured to your tracking goals, agreed on the intro call.
- 05 Cloudflare Pages deploy + DNS migration with zero-downtime cutover plan.
- 06 301 redirect map for every URL change.
- 07 One 60-minute training session on the AI-editing workflow (Claude, Codex, or your MCP agent of choice).
- 08 30 days of post-launch support (bug fixes + small content tweaks).
4 phases over 4 weeks, then you ship.
Audit + content modeling. We catalog every page, post, and form. You sign off on the content map.
Theme port. We build your Astro components against the EmDash schemas. You see a working preview by end of week.
Content migration + redirects. We move WXR data, run link audits, and stage the redirect map.
Cutover + training. DNS flip, training session for your team, 30-day support window opens.
Investment
Starting price, fixed scope.
Final scope after intro call.
4 steps. No surprises.
The tools we'll be using.
Frequently asked.
How long does this take?
Four weeks for a 20–80-page marketing site. Bigger sites scale linearly; we scope on the intro call.
What about my plugins?
We replace what we can with first-party EmDash plugins or Astro components. Anything we cut, you sign off on. Most plugin functionality (forms, GA, redirects, schema) gets handled by the new stack natively.
Do I lose my SEO rankings?
No, if we do this right. We build a 1:1 redirect map for every URL change, preserve title/meta/canonical structure, and validate with Search Console post-cutover. Done well, rankings hold or improve as Core Web Vitals catch up.
Can my team still write blog posts?
Yes. EmDash gives them a rich-text editor for posts and a typed editor for landing-page content. They can also edit through Claude, Codex, or any MCP-compatible agent — that is the headline benefit.
What happens if EmDash itself fails?
Your site is portable. Astro components + structured content move to Sanity, Payload, or Decap with a few weeks of work. You are not locked in.
Do you handle hosting?
Yes. We deploy to Cloudflare Pages on your account. You own the deployment, the domain, and every credential. We can also keep optimizing on a monthly retainer if you want.
Not quite a fit? Try one of these.
Field notes from the work.
Ready to talk?
30 minutes, no obligation. We'll either tell you it makes sense — or that it doesn't.