Quick answer: To migrate a WordPress site to a new host, back up the files and database, copy both to the new hosting account, update wp-config.php with the new database details, test the copy before DNS changes, then point your domain at the new host. Keep the old hosting active until everything on the new server checks out.
Knowing how to migrate a WordPress site to a new host saves you from the two things people fear most: losing content and taking the site offline. WordPress is easier to move than most platforms because it is only two pieces, a folder of files and a database. This guide covers both the plugin route and the manual route, the checks to run before you switch DNS, and the small fixes that catch people out afterwards. For the general, non-WordPress version of this process, see our step-by-step guide to website migration.
What does a WordPress migration actually move?
A WordPress migration moves your files and your database. Everything you see on the site lives in one or the other.
- Files. WordPress core, your themes, your plugins and the
wp-content/uploadsfolder with every image and PDF you have added. Thewp-config.phpfile is here too; it tells WordPress which database to use. - The database. Posts, pages, comments, users, menus, widget settings and most plugin settings. Your site address is stored here as well, which matters later.
Email and the domain registration are separate from both. If your mailboxes sit with your current host, plan for them on their own. Your domain can stay with its current registrar; you only change where it points.
Before you start: three things to get ready
Get a full backup, a new hosting account and access to your domain’s DNS before you touch anything. That way nothing on the live site changes until you choose to switch.
- A full backup you have downloaded. Take a copy of the files and a database export, and keep it on your own computer, not only on the old server. WordPress explains what a complete backup includes in its backup documentation (last checked 23 October 2026).
- The new hosting account, active. On our shared hosting plans, Starter runs one website, Business runs three and Pro runs ten, so pick the plan that fits how many sites you are bringing over.
- Your DNS login. You need access to wherever your domain’s nameservers or DNS records are managed, usually your domain registrar.
One habit worth adopting: pause publishing for the day of the move. A post or a WooCommerce order made on the old site after you copy the database will not exist on the new one.
Option 1: Migrate WordPress with a migration plugin
A migration plugin packs your files and database into one archive, which you then restore on a fresh WordPress install at the new host. It is the quickest route for small and medium sites.
The general flow is the same whichever plugin you use:
- Install the migration plugin on the old site and create an export or package.
- Download the archive to your computer.
- Install a clean copy of WordPress on the new hosting account.
- Install the same plugin there and import or restore the archive.
- Log in again. The imported database replaces the fresh install’s users, so you sign in with your old username and password.
Watch for upload limits. Free versions of some plugins cap the archive size, and large media libraries can hit the PHP upload limit on the new account. If that happens, the manual method below avoids the problem because you move the uploads folder separately.
Option 2: Migrate a WordPress site manually
The manual method copies the files with a file manager or FTP, exports the database to a .sql file and imports it at the new host. It takes longer, but nothing is hidden from you, and it works for sites of any size.
Step 1: Copy the files
Download the whole WordPress folder from the old host. Most hosting file managers can zip it for you first, which is much faster than copying thousands of small files over FTP. Upload the zip to your site’s web folder on the new account and extract it there.
Step 2: Export and import the database
Export the database from the old host as a .sql file, usually with phpMyAdmin. On the new account, create a new database and a database user, give that user full rights on it, then import the .sql file into the new database.
Step 3: Update wp-config.php
Open wp-config.php on the new host and change four values to match the database you just created: DB_NAME, DB_USER, DB_PASSWORD and DB_HOST. If these are wrong, you will see “Error establishing a database connection”, which is the single most common migration error and almost always a typo here.
Step 4: Only change URLs if the domain is changing
If the site keeps the same domain, you do not need to replace any URLs. If you are moving to a new domain at the same time, the old address is stored throughout the database. WordPress’s own guide to moving WordPress warns that some of those values are serialized, so a plain find and replace on the .sql file can break widgets and plugin settings. Use a search and replace tool built for WordPress, which handles serialized data properly.
How to test the new site before you switch DNS
Test the copy on the new server while your domain still points at the old one. Visitors keep seeing the live site, and you get to fix problems in private.
The usual way is your computer’s hosts file. Add a line that maps your domain to the new server’s IP address, and only your computer will load the site from the new host. Then check:
- The home page, a few posts and a few pages load with images.
- You can log in to wp-admin and save a draft.
- Contact forms send, and if you sell online, a test checkout goes through.
- Permalinks work. If posts return 404 errors, open Settings, Permalinks and click Save once; that rewrites the rules file.
Remove the hosts file line when you are done, or you will keep seeing the new server even after you think you are looking at the old one.
Switch DNS and finish the move
Once the copy checks out, point your domain at the new hosting by updating its nameservers or its A record. Our guide on how to point a domain to your hosting walks through both options.
DNS changes take time to spread, so for a while some visitors reach the old server and some reach the new one. That is why the old hosting account should stay active and untouched until the change has settled. After the switch:
- Turn on the free SSL certificate for the domain on the new account, then confirm that the WordPress Address and Site Address under Settings, General start with https://.
- Update the email settings on your phone and laptop if your mailboxes moved too.
- Set up backups on the new account straight away. Do not assume the old host’s backup schedule came with you.
- Cancel the old hosting only after a few days of the new site running normally, and after you have your own downloaded backup.
Common WordPress migration problems and fixes
Most migration problems come from three places: database details, file permissions and leftover caching. Here is where to look first.
| What you see | Likely cause | What to check |
|---|---|---|
| Error establishing a database connection | Wrong database details | The four DB values in wp-config.php |
| Posts return 404, home page works | Rewrite rules not set | Save Settings, Permalinks once |
| Images missing | Uploads folder not copied in full | Compare wp-content/uploads on both servers |
| Redirect loop or old domain appears | Site URL still the old address | Settings, General, or the siteurl and home values |
| White screen after import | A plugin conflicts with the new PHP version | Rename the plugins folder to disable all plugins, then turn them back on one at a time |
Or let us migrate your WordPress site for free
If you would rather not do any of this yourself, free website migration is included on every ResellerBytes SSD hosting plan. You order a plan, then open a migration ticket with the domain you are moving, access to your current host (a hosting login or a full backup) and access to your DNS, or the name of whoever manages it. Mention anything unusual, such as cron jobs or specific software versions.
Your current site stays live while we copy it, and the only change visitors notice is the DNS switch. The free website migration page lists exactly what we need from you and how the switch works. If you are still setting up from scratch rather than moving, our guide on how to host a WordPress website is the better starting point.
FAQ
Will my WordPress site go down during a migration?
It should not. The old site stays live while you copy and test the new one. The only moment that matters is the DNS switch, and keeping the old hosting active until the change settles covers it.
Do I need to transfer my domain to move WordPress hosting?
No. Hosting and domain registration are separate. You can keep the domain where it is and just point it at the new hosting. Transferring it later is optional.
Is a plugin or manual migration better?
A plugin is faster for small and medium sites. The manual method is better for large media libraries, or when a plugin hits upload limits, because you move the files and database separately.
Do I have to change URLs after migrating WordPress?
Only if the domain changes. Moving the same domain to a new host needs no URL changes. If the domain changes, use a WordPress-aware search and replace tool so serialized data stays intact.
What happens to my emails when I change hosts?
That depends on where your mailboxes live today. If they are with your old host, plan to recreate them on the new account and update your devices after the switch. If you use our free migration, list the mailboxes in your ticket and we will confirm what can be moved.
Share this content:
