Moving a static HTML site into WordPress is a publishing and information architecture project, not a simple copy and paste job. A careful migration preserves useful URLs and content while giving editors reusable templates, blocks, navigation, search and a safe update process.
How this guide was produced
Documented practice reviewed on 10 September 2026. Confirm current hosting, plugin and platform requirements before you start a migration.
The eight steps
| Step | Best fit | First thing to verify |
|---|---|---|
| Inventory the existing site | Every migration before design work | URLs, assets, forms, analytics and owners |
| Plan the WordPress structure | Content that needs reusable fields | Post types, taxonomies, roles and editing needs |
| Build a staging installation | Safe development and review | PHP, database, HTTPS, backups and access |
| Create theme templates | Consistent headers, footers and content | Responsive behaviour and block support |
| Migrate content and media | Approved pages and posts | Metadata, captions, filenames and rights |
| Rebuild forms and functions | Interactive pages and business actions | Delivery, validation, consent and spam controls |
| Map redirects and metadata | URLs that change | One to one targets, canonicals and status codes |
| Test and launch | Completed staging migrations | Content parity, performance, analytics and rollback |
How we assessed the process
We assessed content integrity, URL preservation, editor usability, template reuse, media handling, accessibility, structured data, forms, search, security, performance, backups, analytics, launch risk and the ability to maintain the result without editing raw templates.
Implementation workflow
Crawl the old site and keep a signed off URL inventory. Define WordPress fields and templates before importing content. Build on staging, migrate a representative section and have editors test it. Create a redirect map for every changed URL. Before launch, compare page titles, headings, copy, media, links, forms, analytics, consent, mobile layouts, keyboard use, search, error pages, sitemaps, robots rules, performance, backups and rollback. Monitor logs and search reports after the switch.
Read next
- Import and export plugins - move content safely
- Hosts with free migration - let the host do the move
- Best SEO tools - crawl and verify after launch
- Run the free speed test - compare before and after
Common questions
Can I import raw HTML automatically?
Automation can help with predictable pages, but templates, malformed markup, embedded scripts, duplicate assets and inconsistent metadata usually need review.
Do all old URLs need redirects?
Keep useful URLs when practical. For changed or consolidated pages, map each old URL to the closest relevant destination and avoid redirect chains.
Should I recreate the old design exactly?
Preserve the parts users recognise and depend on, then improve accessibility, responsive behaviour, editing and performance where evidence supports the change.
Fast WordPress editorial
Independent research edition · Published 10 September 2026. We update field guides when a plugin's documented capabilities change.
