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.
Who this is for
- 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.
What's included
- Full content audit of your existing site (pages, posts, custom fields, embedded forms).
- WordPress WXR export + EmDash content-type modeling (typed schemas, not "blob fields").
- Astro theme port, mobile-first, Core Web Vitals green at handoff.
- GA4 + GTM + UTM injector configured (TBD: confirm tracking goals on intro call).
- Cloudflare Pages deploy + DNS migration with zero-downtime cutover plan.
- 301 redirect map for every URL change.
- One 60-minute training session on the AI-editing workflow (Claude, Codex, or your MCP agent of choice).
- 30 days of post-launch support (bug fixes + small content tweaks).
Timeline
- Week 1 Audit + content modeling. We catalog every page, post, and form. You sign off on the content map.
- Week 2 Theme port. We build your Astro components against the EmDash schemas. You see a working preview by end of week.
- Week 3 Content migration + redirects. We move WXR data, run link audits, and stage the redirect map.
- Week 4 Cutover + training. DNS flip, training session for your team, 30-day support window opens.
Investment
Final scope after intro call.
Not a quote. Final scope is set after the intro call so we both know what success looks like before any contract is signed.
How we work
- 01
Audit
We catalog your current stack — every plugin, every custom field, every shortcode. You get a written report and a decision on what migrates, what gets cut, and what gets rebuilt.
- 02
Plan
Content types, redirect map, training plan. Locked before any code is written.
- 03
Migrate
Theme port + content move. You see preview URLs from day one; no big-bang reveal.
- 04
Train
Your marketing team learns the AI-editing workflow over MCP. We watch them do a real edit before we leave.
Tech stack
- Astro 6 — content stays portable; no framework lock-in.
- EmDash CMS — typed content, MCP-native, runs on Cloudflare Workers.
- Cloudflare Pages — sub-1s page loads, free tier covers most clients.
- Resend + Cloudflare Turnstile — form handling without third-party tag bloat.
FAQ
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. We have not lost a client rankings on a migration.
Can my team still write blog posts?
Yes. EmDash gives them a TinyMCE 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.
Ready to talk?
30 minutes, no obligation. We'll either tell you it makes sense — or that it doesn't.