Backups & maintenance · Guide
How to Migrate a Website to WordPress (From Any Platform, Step by Step)

Short answer
To migrate a website to WordPress, first list every page and URL on the old site, then set up WordPress on new hosting or a staging address. Import content with a WordPress importer or by hand, rebuild the design with a theme, and add 301 redirects from old URLs to new ones. Finally, test everything, point your domain to the new site and monitor Search Console.
Key takeaways
- Start with a full list of pages, posts, images and URLs on the old site.
- Build the new WordPress site on staging before switching the domain.
- WordPress importers cover some platforms; others need manual copying.
- 301 redirects from old URLs protect traffic and rankings.
- Test thoroughly, then switch DNS and watch Search Console.
How do you plan a migration to WordPress?
List every page, post, image, form and URL on the current site, decide what to keep, merge or drop, and note which pages bring traffic, so nothing important is lost in the move.
A crawl of the old site, or its sitemap, gives you the URL list.
Export the list to a spreadsheet. It becomes your checklist for content, redirects and testing.
Check analytics and Search Console for the pages with the most visits and links. Those need the most care.
Decide whether the domain stays the same. Keeping it makes the move simpler for search engines.
Write down any forms, integrations and tracking codes on the old site too. They are easy to forget because they are not visible pages.
| Phase | Main tasks |
|---|---|
| Plan | Inventory content and URLs, pick hosting |
| Build | Install WordPress, theme, plugins |
| Move content | Import or copy pages, posts, media |
| Redirect | Map old URLs to new ones |
| Launch | Test, switch DNS, monitor |
Where should you build the new site?
Build on new WordPress hosting using a temporary address or staging site, so the old site stays live until the new one is ready.
Most hosts give a temporary URL or let you preview a site before pointing the domain.
Install only the plugins you need at first. Add others once the content is in place and you know what is missing.
Block search engines from the temporary site so it is not indexed early.
Password protection is the safest way to keep a work-in-progress site private.
Our explainer on what WordPress hosting is helps you choose a plan for the new site.
How do you move content into WordPress?
Use a WordPress importer if your old platform has one, export to an RSS or XML format WordPress can read, or copy pages manually for small sites and platforms without exports.
The WordPress documentation on importing content lists the built-in importers under Tools > Import.
For large WordPress-format files, the wp import command can import from the command line.
Check formatting after any import. Imports rarely bring over layouts exactly.
Plan time for clean-up. Imported content often has odd spacing, inline styles or old shortcodes that need fixing.
Which platforms have dedicated guides?
Common sources such as Wix, Squarespace, Blogger, Medium and Joomla each have their own export quirks, so follow a platform-specific guide when one exists.
Our guide on migrating from Wix to WordPress covers a platform without a full export.
Our guide on migrating from Squarespace uses Squarespace's own export file.
Our guide on migrating from Blogger uses WordPress's built-in Blogger importer.
Our guide on migrating from Joomla covers a platform with its own database structure.
What about images and files?
Importers often download images automatically, but some leave them linked to the old site, so check every page and re-upload images into the Media Library where needed.
Images still hosted on the old platform will break when it closes.
A media import plugin can download remote images into your Media Library and update the links in posts automatically.
Use descriptive file names and alt text while re-uploading.
Remove images that no longer serve a purpose. A migration is a good time to slim down the media library.
Compress large images before uploading to keep the new site fast.
How do you rebuild the design?
Choose a theme close to the look you want, recreate headers, footers and key layouts with blocks or a page builder, and match brand colours and fonts.
A migration is a good moment to simplify. Remove sections nobody uses.
Keep the brand recognisable, though. Returning customers should feel they are on the same business's site.
Rebuild the most visited pages first, then work down the list.
Rewrite thin or outdated pages while you move them, instead of copying old problems into the new site.
Test on mobile as you go, since most visitors use phones.
Recreate navigation menus carefully. Menus are how most visitors find important pages.
How do you keep URLs and rankings?
Keep the same URL paths where possible, and create 301 redirects from every old URL that changes to its closest new page.
Google's guide to site moves with URL changes explains the redirect and monitoring steps it recommends.
Our guide on setting up 301 redirects in WordPress shows how to add them.
A spreadsheet with old URL, new URL and status columns keeps redirect work organised on larger sites.
MDN explains the 301 status code that tells browsers and search engines a page has moved permanently.
How do you match old URLs in WordPress?
Set the permalink structure and page slugs to match the old paths where you can, so many URLs need no redirect at all.
Our guide on setting up permalinks explains the options.
What should you test before launch?
Check every key page, internal links, forms, images, mobile layout, page titles and descriptions, redirects from a sample of old URLs, and site speed.
Submit each form and confirm the email arrives.
Check analytics and tracking tags too, so you do not lose visitor data from launch day.
Crawl the new site for broken links. Our guide on fixing broken links after migration covers common causes.
Remove the search engine block before launch.
Check that the SSL certificate works on the new host before switching, so visitors never see security warnings.
How do you launch the new site?
Point your domain to the new hosting by updating DNS records or nameservers, install SSL, then confirm the site loads on the real domain with HTTPS.
Our guide on pointing a domain to WordPress hosting covers the DNS steps.
Keep the old site available for a while, in case you need to copy anything you missed.
Lower the DNS record's time to live a day before the switch, so the change spreads faster.
Launch at a quiet time and stay available to fix issues quickly.
Have a rollback plan. Keeping the old DNS settings noted lets you switch back quickly if something serious goes wrong.
What should you do after launch?
Submit the new sitemap in Search Console, watch crawl errors and traffic for several weeks, fix any missed redirects, and update links on social profiles and directories.
Some ranking movement is normal during a move.
Most sites settle within a few weeks if redirects and content are in place. Large drops usually point to missing redirects.
Compare traffic to key pages before and after the move, rather than only looking at the site total.
Our guide on changing hosting without losing SEO covers monitoring after a move.
Tell regular customers about the new site if the design changed a lot.
Update the website address in email signatures, ads and printed material if any URLs changed.
What about online stores?
Stores need products, customers, orders and payment setups moved carefully, often with dedicated migration tools or services, plus thorough checkout testing.
Our guide on migrating a WooCommerce store covers store-specific steps.
Plan store migrations for low-sales periods.
Tell customers if they need to reset passwords, since passwords may not transfer between platforms.
Should you hire help?
Hire help for large sites, stores, custom features or sites that earn significant traffic, where mistakes in redirects or data cost more than professional fees.
Get a written plan and timeline from anyone you hire, including how they will test redirects before launch.
Small brochure sites and blogs are realistic do-it-yourself projects.
Even then, a professional review of redirects before launch is a cheap way to avoid expensive mistakes.
Ask any developer how they will handle redirects and SEO, not just design.
Agree who owns the hosting, domain and logins after the project, so the business stays in control of its website.
Frequently asked questions
How do I move my website to WordPress?
List your pages and URLs, build WordPress on new hosting, import or copy content, rebuild the design, add 301 redirects, test, then point your domain to the new site.
Will I lose SEO when moving to WordPress?
Not if you keep URLs where possible, redirect every changed URL with 301 redirects, keep titles and content, and monitor Search Console after launch.
Can WordPress import content from other platforms?
Yes, for some. Tools, then Import has importers for platforms such as Blogger and Tumblr, plus RSS. Others need exports, plugins or manual copying.
How long does a WordPress migration take?
A small site can take a day or two. Large sites and stores can take weeks, mainly for content checks, design and redirects.
Do I need new hosting to migrate to WordPress?
Usually yes, unless your current host supports WordPress. Build the new site there on a temporary address, then switch the domain.
Sources
- Importing Content WordPress.org Documentation
- wp import WP-CLI Command Reference
- Site moves with URL changes Google Search Central
- 301 Moved Permanently MDN Web Docs
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


