Moving a WordPress site to a new host sounds simple until you're the one staring at a broken homepage, a missing database connection, or a client asking why their site has been down for six hours. Migrations go wrong more often than they should, not because the process is complicated, but because people skip steps under time pressure or assume their current host's export tool will handle everything on its own. If you're planning a move because your current host is too slow, too expensive, or too unreliable during traffic spikes, this guide walks through the actual steps that keep a site intact during the switch, in the order that matters, without the guesswork.
Back Up Everything Before You Touch a Single File
The single most important step in any migration is a full, verified backup, and it has to happen before you do anything else. This means your entire WordPress files directory, your complete database, uploads, themes, and plugins, all saved somewhere outside your current host. Don't rely on your host's automatic backup system alone, since you're about to leave that host and may lose access to it. Download a full backup to your own computer or a cloud storage account you control. If something breaks mid-migration, this backup is what saves you from starting over from nothing.
Set Up Your New Hosting Environment First
Don't cancel or downgrade your old hosting plan until the new one is fully configured and tested. On your new host, create the hosting account, note the server details you'll need such as database name, username, and password, and check that the PHP version matches or exceeds what your site currently runs on. Mismatched PHP versions are a common source of plugin errors after migration, so confirm compatibility before moving a single file. Many businesses handle this step through professional wordpress migration services instead of doing it manually, especially when the site has custom code, multiple environments, or heavy traffic that can't afford extended downtime.
Move Your Files and Database
There are three practical ways to do this, and the right one depends on your comfort level and site size.
Migration plugin: Tools like Duplicator or All-in-One WP Migration package your entire site into a single file you can import on the new host. This works well for most small to mid-sized sites and requires no command-line knowledge.
Manual transfer: Export your database through phpMyAdmin, then transfer files via FTP or SFTP to the new server, and import the database on the new end. This gives you more control but requires more technical comfort.
Host-assisted migration: Many hosts offer free migration as part of onboarding a new customer, where their team handles the technical transfer for you. This is worth asking about before doing it yourself.
Whichever method you choose, don't delete anything from the old host until the new site is confirmed working.
Update Your wp-config.php File
If you migrated manually, your new database will likely have different credentials than the old one. Open wp-config.php on the new server and update the database name, username, password, and host to match your new environment. Getting even one character wrong here causes the "Error establishing a database connection" message, which is the most common issue people hit right after a migration.
Test the Site Before Changing DNS
Before pointing your domain to the new host, test the site using a temporary URL or by editing your local hosts file to preview it without affecting live traffic. Click through key pages, test contact forms, check that images load, and confirm that the checkout process works if you run an online store. According to WordPress.org's official migration documentation, verifying the site fully before changing DNS is one of the most overlooked steps, and skipping it is what causes most post-migration scrambling.
Update DNS and Point Your Domain
Once you've confirmed everything works, update your domain's DNS records to point to the new host's server. DNS changes can take anywhere from a few minutes to 48 hours to propagate fully across the internet, depending on your domain's TTL settings and your registrar. During this window, some visitors may still land on the old server while others reach the new one, so avoid making content changes on either site until propagation finishes.
What to Check After the Move
Once DNS has fully propagated, go through a final checklist: confirm SSL is active and working on the new host, check that all pages load without mixed content warnings, verify email functionality if your site sends transactional emails, and submit your sitemap again through Google Search Console to make sure crawlers pick up the new server without issues. Keep the old hosting account active for at least a week or two as a safety net in case anything surfaces that you missed.
Common Mistakes That Cause Migration Problems
Most migration headaches come from a small set of repeated mistakes: skipping the backup step because "it should be fine," forgetting to update hardcoded URLs in the database, canceling the old host too early, or not checking file permissions after the transfer. Search-and-replace tools within migration plugins usually handle the URL issue automatically, but if you migrated manually, you'll need to run a database search-and-replace for your old domain to avoid broken links and images.
Bringing It All Together
A safe WordPress migration comes down to sequence: back up first, prepare the new environment fully, transfer files and database carefully, test before switching DNS, and confirm everything after the switch completes. Rushing any one of these steps is what turns a routine host change into hours of downtime and lost trust with visitors or clients. If you're still working to write a business plan for your company, factoring in hosting costs and site reliability early on saves you from a rushed, reactive migration down the line. Follow the order, verify each stage before moving to the next, and the switch becomes a non-event instead of an emergency.
Frequently Asked Questions
1. How long does a WordPress site migration usually take?
A straightforward migration typically takes one to three hours of active work, plus up to 48 hours for DNS propagation to complete fully across all visitors.
2. Will my website go down during migration?
Not if done correctly. Keeping the old site live while testing the new one on a temporary URL means visitors experience no downtime until DNS switches over.
3. Do I need to update my SSL certificate after migrating?
Yes. Most hosts issue a new SSL certificate for your domain once DNS points to them, so confirm it's active before considering the migration complete.
4. Can I migrate a WordPress site without losing my SEO rankings?
Yes, as long as URLs stay the same and the new site is fully functional before DNS switches. Rankings are tied to your domain, not your hosting server.
Top comments (0)