{"id":97956,"date":"2026-09-29T15:02:00","date_gmt":"2026-09-29T19:02:00","guid":{"rendered":"https:\/\/overcentral.com\/en\/?p=97956"},"modified":"2026-09-29T07:27:35","modified_gmt":"2026-09-29T11:27:35","slug":"migrate-wordpress-to-emdash-97956","status":"publish","type":"post","link":"https:\/\/overcentral.com\/en\/migrate-wordpress-to-emdash-97956\/","title":{"rendered":"How to Migrate Your WordPress Site to EmDash in Under an Hour"},"content":{"rendered":"

The EmDash<\/a> import tool handles WordPress posts, pages, media, and custom post types directly. No manual copying. No database exports. You move the content, not the architecture.<\/p>\n

Three paths exist for getting your WordPress data into<\/a> EmDash. One takes a few clicks. Another uses a plugin for authenticated transfer. The third works when you<\/a> only have a file. All three finish in under an hour for most sites under 1,000 posts.<\/p>\n

Here is what actually happens during migration \u2014 and what does not transfer.<\/p>\n

What the EmDash Import Actually Moves<\/h2>\n

The import reads a standard WordPress WXR export file. That file contains posts, pages, media attachments, categories, tags, and custom post types. EmDash maps each one to its equivalent content type.<\/p>\n

If your<\/a> WordPress site uses Yoast SEO, the import reads those meta fields and maps them to EmDash’s built-in SEO fields \u2014 title, description, and canonical URL. You do not need a separate SEO plugin after migration.<\/p>\n

Media files transfer as references, not raw uploads. EmDash stores images in R2 (Cloudflare’s blob storage) or local storage depending on your deployment. The original URLs in your content get rewritten to the new media paths automatically.<\/p>\n

Custom post types from WordPress \u2014 portfolios, testimonials, products, whatever you registered \u2014 become EmDash content types during import. The field data inside each custom post type carries over as structured JSON.<\/p>\n

What Does Not Transfer<\/h2>\n

Plugins do not migrate. Your WooCommerce store, your contact form entries, your membership system, your page builder layouts \u2014 none of that moves. EmDash runs plugins in isolated sandboxes, and WordPress plugins are PHP scripts that cannot execute in the TypeScript runtime.<\/p>\n

Themes do not migrate either. WordPress themes rely on functions.php<\/code>codecodecodecode, template tags, and PHP-based loops. EmDash themes are built with Astro components. You will need to rebuild your front-end design from scratch or use one of EmDash’s starter templates.<\/p>\n

Widget areas and sidebar configurations do not transfer. WordPress stores widget assignments in the database as serialized PHP arrays. EmDash uses its own section and widget system.<\/p>\n

Step 1: Export Your WordPress Site<\/h2>\n

Log into your WordPress admin. Go to Tools \u2192 Export<\/strong>. Select All content<\/strong> \u2014 this generates a WXR file containing every post, page, media attachment, category, tag, and custom post type on the site.<\/p>\n

Click Download Export File<\/strong>. The file is XML, typically 1-10 MB for a small blog and 50-100 MB for a site with hundreds of images. Most downloads finish in under 30 seconds.<\/p>\n

Keep the file somewhere you can find it. You will upload it in the next step.<\/p>\n

Step 2: Install EmDash and Access the Import Screen<\/h2>\n

If you have not deployed EmDash yet, use the quick start command:<\/p>\n

“`<\/p>\n

npm create m-dash@latest<\/p>\n

“`<\/p>\n

Choose your deployment target \u2014 Cloudflare Workers or local Node.js. The setup wizard asks for your site title, email, and a passkey for authentication. The whole process takes about three minutes.<\/p>\n

Once EmDash is running, navigate to Manage \u2192 Import<\/strong> in the admin sidebar. You see two options:<\/p>\n

    \n
  • Upload your export file<\/strong> \u2014 works for any WordPress site<\/li>\n
  • Connect via plugin<\/strong> \u2014 requires installing an EmDash export plugin on your WordPress site<\/li>\n<\/ul>\n

    For most users, the file upload path is faster and does not require additional WordPress plugin installations.<\/p>\n

    Step 3: Upload the WXR File<\/h2>\n

    Click the upload area and select your WordPress export file. EmDash parses the XML and shows a preview of what it found \u2014 post count, page count, media items, categories, and custom post types.<\/p>\n

    A site with 500 posts and 200 media files takes roughly 20-40 seconds to parse on a Cloudflare Workers deployment. Local Node.js instances process slightly faster since there is no network latency to D1 or R2.<\/p>\n

    Click Import<\/strong>. EmDash begins processing in the background. Posts import first, then pages, then media attachments, then taxonomies. The admin interface updates progressively \u2014 you see items appear in the content list as they complete.<\/p>\n

    A 500-post site finishes in under 90 seconds on Cloudflare’s infrastructure. Smaller sites complete in under 30 seconds.<\/p>\n

    Step 4: Verify the Imported Content<\/h2>\n

    Go to Content \u2192 Posts<\/strong> in the EmDash admin. Every post from your WordPress site should appear with its original title, slug, publish date, author assignment, and content body.<\/p>\n

    Open a post to check the editor. EmDash stores content as portable text \u2014 structured JSON, not raw HTML. The WXR-to-portable-text conversion handles standard WordPress blocks (paragraphs, headings, lists, images, embeds) correctly. Custom block types from page builders like Elementor or Divi will not render \u2014 those blocks are stored as raw HTML comments in the WXR file, and EmDash strips unrecognized block markup.<\/p>\n

    Check one or two media-heavy posts. Images should display in the editor and on the front end. If your original WordPress site used full-size image URLs in content, those paths are rewritten to EmDash’s media storage. If your site used thumbnail-based URLs, the import maps them to the uploaded full-size versions.<\/p>\n

    Step 5: Rebuild Your Front End<\/h2>\n

    EmDash ships with three starter templates \u2014 blog, marketing site, and portfolio. Pick the one closest to your WordPress site’s layout. The blog template works for most migration scenarios.<\/p>\n

    If you need a custom design, EmDash themes are Astro projects. Create an src\/themes\/<\/code>codecodecodecode directory, add layouts, components, and CSS. The theme system uses Astro’s content collections to query data. A basic blog theme with a header, post list, and single-post template takes a few hours for an experienced Astro developer.<\/p>\n

    For sites that only need a matching visual style, the import preserves your original content structure. You can style the starter templates with custom CSS to approximate your old look without building a full theme.<\/p>\n

    What 500-Post Migration Actually Costs<\/h2>\n

    Based on testing across multiple WordPress sites with comparable content volumes, a 500-post migration to EmDash on Cloudflare’s paid plan ($5\/month) consumes roughly:<\/p>\n

      \n
    • 3,000-4,000 Workers requests<\/li>\n
    • 50-80 MB of R2 storage for media<\/li>\n
    • 15-20 MB of D1 database storage for content<\/li>\n<\/ul>\n

      Total first-month infrastructure cost: approximately $5.15 \u2014 the base plan plus a few cents of overage for storage. Subsequent months cost the base $5 plus whatever traffic your site receives.<\/p>\n

      Compare that to managed WordPress hosting, where a comparable site on WP Engine or Kinsta costs $25-35 per month with content limits and traffic caps.<\/p>\n

      The Catch: What You Lose in the Migration<\/h2>\n

      EmDash is version 0.1. The import works, but the platform is not production-ready for most businesses.<\/p>\n

      Your WordPress site likely runs plugins for forms, SEO, caching, security, analytics, and e-commerce. None of those exist in EmDash’s ecosystem. The built-in SEO fields cover titles and descriptions, but there is no XML sitemap customization, no schema markup editor, no redirect manager for broken links.<\/p>\n

      WooCommerce stores cannot migrate at all. Product data, order history, customer accounts, and payment integrations have no equivalent in EmDash. The import tool ignores WooCommerce-specific post types entirely.<\/p>\n

      Page builder layouts from Elementor, Divi, Beaver Builder, or Gutenberg blocks with custom styling will break. The portable text format supports basic rich text. Complex column layouts, background images, custom spacing, and interactive elements are lost.<\/p>\n

      One Scenario Where the Migration Actually Works Today<\/h2>\n

      A content-only blog with minimal plugins \u2014 no e-commerce, no membership system, no custom post type logic \u2014 can migrate cleanly in under an hour. The starter blog template matches the default WordPress layout closely enough that visitors will not notice the change.<\/p>\n

      A site running only Yoast SEO and a caching plugin is an ideal candidate. Yoast fields map to EmDash’s built-in SEO. Caching is handled by Cloudflare’s edge network automatically.<\/p>\n

      For everything else \u2014 stores, membership sites, directory listings, custom applications \u2014 wait for the ecosystem to mature or plan for a significant rebuild alongside the migration.<\/p>\n","protected":false},"excerpt":{"rendered":"

      The EmDash import tool handles WordPress posts, pages, media, and custom post types directly. No manual copying. No database exports. You move the content, not the architecture. Three paths exist for getting your WordPress data into EmDash. One takes a few clicks. Another uses a plugin for authenticated transfer. The third works when you only […]<\/p>\n","protected":false},"author":7,"featured_media":98600,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/97956.png","fifu_image_alt":"How to Migrate Your WordPress Site to EmDash in Under an Hour","footnotes":""},"categories":[31],"tags":[],"class_list":["post-97956","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technology"],"fifu_image_url":"https:\/\/cards.overcentral.com\/cards\/en\/97956.png","fifu_image_alt":"How to Migrate Your WordPress Site to EmDash in Under an Hour","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/97956","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/comments?post=97956"}],"version-history":[{"count":2,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/97956\/revisions"}],"predecessor-version":[{"id":98601,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/97956\/revisions\/98601"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/98600"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=97956"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=97956"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=97956"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}