HTML to Markdown for Content Migration How to Move Your Blog from WordPress to a Static Site Generator Without Losing Your Formatting

You have been blogging on WordPress for 10 years. 500 posts. All written in HTML — some in the Classic Editor, some in Gutenberg blocks, some in a page builder you no longer remember the name of. You want to migrate to a static site generator — Hugo, Astro, or Next.js with Markdown. The new platform is faster, cheaper, and more secure. But it requires your content to be in Markdown, not HTML. You have 500 HTML posts. You need them in Markdown by the end of the week.

An HTML to Markdown converter handles the bulk conversion. But the conversion is a starting point, not a finished product. Here is the content migration workflow from WordPress HTML to static site Markdown.

Step 1: Export Your WordPress Content

WordPress provides a built-in export tool: Tools → Export → Export All Content. This downloads an XML file containing all your posts, pages, and metadata. The XML file is the master copy of your content. Every post's title, date, category, tags, and HTML body is in this file. Do not lose this file. The export is the source of truth for the migration.

Step 2: Extract and Convert Each Post

For each post in the XML export: extract the post title, date, slug, categories, and HTML body. Use the HTML to Markdown converter to convert the HTML body to Markdown. The converter handles: headings (h1-h6 → # through ######), links and images (a href and img src → Markdown link and image syntax), lists (ul/ol/li → Markdown list syntax), bold and italic (strong/em → ** and *), and code blocks (pre/code → Markdown code block syntax).

The converter handles 90% of the conversion. The remaining 10% requires manual attention: embedded content (YouTube embeds, Twitter embeds, Gutenberg blocks — these may not convert cleanly), shortcodes (WordPress-specific shortcodes like [gallery] or [caption] — these have no Markdown equivalent and must be manually replaced), and tables (complex HTML tables with merged cells, alignment, and nested content may not convert cleanly).

Step 3: Review and Fix the Converted Markdown

For each converted post: preview the Markdown with the Markdown preview tool. Compare the preview to the original WordPress post. Look for: broken links (URLs that were relative in WordPress and are now absolute — or vice versa), missing images (image URLs that point to the old WordPress site), and formatting errors (headings that did not convert, lists that lost their nesting, code blocks that lost their language tags).

For a 500-post migration, you cannot manually review every post in detail. Triage: spot-check 10-20% of posts (50-100 posts) at 100% detail. For the remaining 80%, check the title, first paragraph, and any complex elements (tables, embeds, code blocks). The bulk conversion handles the straightforward content. The manual review catches the edge cases. The combination produces a migrated blog that is 95% clean — with the remaining 5% of issues fixable as you discover them.

Step 4: Import into Your Static Site Generator

Each converted post becomes a Markdown file with frontmatter: the title, date, slug, categories, and tags as YAML frontmatter, and the converted Markdown as the file body. The static site generator reads the Markdown files and generates the static site. The migration is complete. The blog is now running on a static site generator — faster, cheaper, and more secure than WordPress. The HTML to Markdown converter handled the bulk of the work. You handled the edge cases. The migration took a week instead of a month.