How to Migrate a WordPress Website Without Breaking It (2026 Guide)

Migrate WordPress website to a new host is one of those tasks that sounds completely straightforward until you are halfway through it, looking at a broken site and a DNS that has half-propagated. Done carefully and in the right sequence, a WordPress migration is a clean, low-risk operation. Done carelessly, it causes downtime, lost emails, and occasionally lost data that cannot be recovered. This guide covers how to migrate WordPress website properly — in the exact order the steps need to happen — and what to do when things do not go to plan.

Before You Migrate WordPress Website: What to Prepare

Before touching anything on either host, take a full manual backup: download your entire wp-content folder via FTP or cPanel File Manager, and export your database via phpMyAdmin. Even if your migration tool creates its own backup, having a manual copy you control entirely is the safety net that matters. If the migration tool corrupts something or the destination host has an issue during import, a manual backup means you can start over from a known-good state.

Note your current setup: WordPress version, PHP version (confirm in your hosting dashboard or phpinfo.php), any server-specific configuration in .htaccess, and any environment-specific constants in wp-config.php (custom upload paths, memory limits, debug settings). Your new host needs to match or exceed these PHP version requirements — migrate wordpress website to a host running an older PHP version than your current theme or plugins require will cause errors immediately after migration.

Finally, reduce your domain’s DNS TTL to 300 seconds at least 24 to 48 hours before migration day. This shortens how long old DNS records stay cached in ISP resolvers during the changeover, meaning the cutover happens faster and the window of visitors being split between old and new servers is shorter.

Best Tools to Migrate WordPress Website

Duplicator Pro is the most reliable WordPress migration plugin for moving between hosts of different configurations. It creates a single archive file containing your entire site — all files and the database — plus an installer script. You upload both to the new host’s public directory and run the installer by visiting that URL in a browser. The installer handles URL replacement in the database automatically when your staging URL differs from your live domain. It works across PHP configurations, server types, and hosting panels.

All-in-One WP Migration is the most user-friendly option for smaller sites to migrate wordpress website — export is one click, import is drag-and-drop. The free version has a 512MB upload limit, which is sufficient for most brochure sites but not for sites with large media libraries. The premium extensions remove the limit.

Many managed WordPress hosts — SiteGround, Kinsta, WP Engine — offer free migration services for new customers. A SiteGround engineer will do the entire migration for you within 24 hours, including URL replacement and basic post-migration testing. For non-technical site owners, this is often the best option. Our maintenance service includes hosted migrations for clients moving to better infrastructure.

Step-by-Step WordPress Migration Process

The correct sequence matters more than the individual steps. Set up your new hosting account first and note the server’s IP address — you will need this to preview the migrated site before DNS changes. Create a temporary staging URL or use the host’s provided preview domain if available. Install WordPress on the new host at that staging URL, matching your current PHP version. Use your migration plugin to export from the old site and import to the new host. After import, update the site URL in the database if the staging URL differs from your live domain — Duplicator handles this automatically; for other methods, the Search Replace DB tool (run locally, not on the server) is the safest approach.

Preview the migrated site at the staging URL or via a hosts file edit on your computer to confirm everything works before touching DNS. Check every page type, all forms, image loading, and any custom functionality. Only after this verification is complete should you update your DNS records. Do not update DNS first and then migrate — that sequence creates downtime because visitors are sent to the new host before it is ready.

DNS Changeover: The Step Most People Get Wrong

DNS propagation after changing nameservers or A records can take anywhere from minutes to 48 hours depending on your domain registrar, the TTL values previously in place, and ISP caching. After you update your DNS, some visitors will hit the old host and some will hit the new host until propagation is complete worldwide. This is why you migrate the content first and change DNS second — with both hosts serving identical content during the transition, it does not matter which server a visitor hits. The experience is the same either way.

Keep the old hosting account active and the old site intact for at least 72 hours after DNS changeover before cancelling. whatsmydns.net lets you check propagation status across global DNS servers in real time — useful for confirming when the majority of visitors are resolving to the new host. If something goes wrong on the new host after DNS changeover, having the old site still live means you can revert the DNS immediately and restore service.

Email During a WordPress Migration

This is the part of hosting migrations that catches people off guard most often. If your email is hosted on the same server as your website — using your hosting provider’s mail service — then changing your domain’s DNS records to point to the new host will also affect your email unless you handle it separately. Before updating DNS, confirm where your email is hosted by checking your domain’s MX records (use MXToolbox).

If your MX records point to your current hosting provider, you need to either migrate email to the new host first, or migrate email to a dedicated provider (Google Workspace, Microsoft 365, Zoho Mail) before updating DNS. Moving email to a dedicated provider at the same time as a hosting migration is a sensible approach — it separates your email infrastructure from your website hosting, which means a future hosting change will never affect email again.

What Can Go Wrong and How to Avoid It

The most common WordPress migration problems and how to prevent them: database import fails due to file size limits (solution: increase PHP memory limit on the destination host, or split the database export); images appear broken after migration because hardcoded absolute URLs reference the old domain (solution: run Search Replace DB to update all occurrences of the old URL to the new one);

SSL certificate not installed on the new host causing mixed-content warnings (solution: install SSL on the new host before going live, most managed hosts do this automatically); email stops working after DNS changeover (solution: migrate email before changing DNS, as described above); and custom plugins or themes fail due to PHP version differences (solution: confirm PHP version compatibility before migration).

WooCommerce Store Migrations: Extra Considerations

WooCommerce stores require additional attention during migration. Any orders placed during the migration window may be lost if you are not careful — either the old site receives them after you have stopped monitoring it, or the database export does not include the last few hours of transactions. For active stores, schedule the migration during the lowest-traffic period and put the store in maintenance mode (WooCommerce > Settings > Advanced > maintenance mode or a dedicated plugin) for the two to four hours needed to complete the export and import.

Re-enable and verify payment processing on the new host before removing maintenance mode. Test a real checkout transaction end-to-end — place a small order, verify payment processes, confirm the order appears in WooCommerce, and confirm the confirmation email sends. Do not consider the migration complete until this test passes.

What to Test After You Migrate WordPress Website

A migration is not complete until you have verified: every page loads correctly with images, fonts, and CSS intact; all contact forms submit and deliver emails to the correct address; SSL is active and all pages load over HTTPS without mixed-content warnings in the browser console; the WordPress admin dashboard is accessible and updates correctly; WooCommerce checkout completes a test transaction (for stores); Google Search Console is still verified and showing data; Google Analytics is recording sessions; and your performance benchmark — run PageSpeed Insights on the new host and compare to the old host’s baseline. Our performance service includes a post-migration audit to verify Core Web Vitals have improved, not regressed, on the new host.

Frequently Asked Questions

Will migrating my WordPress site affect my Google rankings?

A migration done correctly — same content, same URL structure, SSL active, no broken links, faster host — should not negatively affect rankings and will often improve them over three to six months as Google recrawls and re-evaluates the site on faster infrastructure. A poorly executed migration that breaks URLs, creates redirect chains, or slows the site can temporarily drop rankings.

How long does a WordPress migration take?

The technical migration takes two to four hours for a standard small business site with a modest media library. WooCommerce stores with large product catalogues take four to eight hours. Allowing for DNS propagation, the full process from starting the export to confirmed stable on the new host is typically 24–48 hours.

Can I migrate WordPress website myself or do I need a developer?

Small to medium brochure sites can be migrated without developer help if you are comfortable with cPanel, FTP, and phpMyAdmin, and you follow the steps carefully. WooCommerce stores processing regular orders, sites with complex custom functionality, or migrations involving simultaneous email changes are safer with a developer — the cost of a migration going wrong typically exceeds the developer’s fee.

Do I need to tell Google I am changing hosts?

No. Google discovers the site has moved through its normal crawl. Keeping the same URLs and installing Google Search Console on the new host is sufficient. There is no “change of address” tool for a hosting-only migration (only for domain changes).

Need your WordPress site moved without the stress? Get a fixed-price migration quote →