How to Move a WordPress Site to a New Server

Moving WordPress to a new server sounds simple until you actually do it — three moving parts (files, database, and configuration) all have to arrive intact and stay in sync, and a mistake in any one of them breaks the site. Here is exactly what has to happen, the manual way and the fast way.

Three things, and all three matter: the wp-content folder (your themes, plugins, and uploaded media), the database (every post, page, product, order, comment, and setting), and wp-config.php or its equivalent (database credentials, which differ on the new server). Missing any one of these gives you a site that looks broken in a different way — a database with no images, files with no content, or a database that connects to nothing.

Export the database through phpMyAdmin or a command-line mysqldump, download the full wp-content folder over FTP or SFTP, create a fresh database on the new server, import the SQL file there, upload the files, and update wp-config.php with the new database name, username, password, and host. Then comes the part that trips most people up: if the domain is staying the same but the server IP is changing, this is usually enough. If the domain itself is also changing, every URL stored inside the database — including ones buried inside serialized data from page builders and widgets — needs to be rewritten too, and a plain search-and-replace on serialized data corrupts it rather than fixing it.

The most common failure isn’t a missed step — it’s a partial one. A database export that times out on a large site and silently truncates. An FTP transfer that drops a few files on a flaky connection. File permission differences between the old host and the new one that leave WordPress unable to write to its own uploads folder. None of these show up immediately; they show up as a broken image here, a missing plugin there, discovered days later.

A backup-and-restore plugin sidesteps all three failure points at once: it packages the database and files together as one verified archive instead of two separate manual exports that have to stay in sync, it validates the archive before offering it for restore, and it handles URL rewriting automatically — including the serialized-data cases that break a manual find-and-replace. Quick Restore is built specifically around this scenario: take a backup on the old server, install the plugin on the new one, restore, and the site is live with URLs already correct — no SSH session, no manual database editing, and chunked upload means even a restrictive PHP upload limit on the new host doesn’t block a large restore.

Before you start: confirm the new server’s PHP version meets WordPress’s current minimum, confirm the new database credentials work before you need them mid-migration, and keep the old server running until you’ve fully verified the new one — don’t cancel the old hosting the same day you migrate. If something looks wrong on the new server, you want the old one still there as the source of truth.