Quick answer: To move WordPress to a new host: (1) take a full backup, (2) ask your new host for free migration or use a migration plugin (or move files and the database manually), (3) test the site on the new server before changing DNS using a temporary URL or your computer’s hosts file, (4) point your domain’s nameservers or A record to the new host, (5) wait for DNS propagation (often a few hours, up to 24–48), and (6) keep the old hosting active for a few days while you check everything.
Three ways to migrate
| Method | Difficulty | Best for |
|---|---|---|
| Free migration by your new host | Easiest | Most people — many hosts offer it |
| Migration plugin | Easy | Small and medium sites |
| Manual (SFTP + phpMyAdmin) | Advanced | Large sites, developers, plugin limits |
Before you start: migration checklist
- Full backup of files and database — see backup guide.
- Logins for old host, new host, domain registrar and DNS provider.
- Note your email setup: if email is hosted with your old host, plan where it will live.
- Pause big content changes and new orders if possible.
- Lower the DNS TTL a day before to make the switch faster.
Method 1: Let your new host do it
Many hosts migrate WordPress sites for free. You usually provide your old hosting or WordPress login, and they copy everything and give you a test link. This is the safest option for beginners — just check the result before you switch DNS.
Method 2: Use a migration plugin
- Install WordPress on the new host (a temporary URL or the same domain on the new server).
- Install the same migration plugin on both sites (popular options include Duplicator, All-in-One WP Migration, Migrate Guru and UpdraftPlus).
- Export (package) the old site: files and database in one archive.
- Import it on the new site and follow the installer.
- Log in on the new server and check pages, images and settings.
Free versions often have file-size limits; large sites may need a paid version or the manual method.
Method 3: Manual migration
- Download all files from the old server via SFTP (especially
wp-contentandwp-config.php). - Export the database from phpMyAdmin as SQL.
- Create a new database and user on the new host.
- Import the SQL file into the new database.
- Upload the files to the new server.
- Update
wp-config.phpwith the new database name, user, password and host. - If the domain changes, update URLs in the database with a search-and-replace tool that handles serialized data.
Test before switching DNS
You can preview the site on the new server before the world sees it. Either use the temporary URL your host provides, or edit your computer’s hosts file to point your domain to the new server’s IP address — only your computer will see the new site. Click through key pages, log in, test forms and checkout. Remove the hosts entry when done.
Switch DNS
At your domain registrar or DNS provider, either change the nameservers to the new host’s, or update the A record (and AAAA record if used) to the new server’s IP. Propagation usually takes a few hours but can take up to 24–48 hours. During that time some visitors see the old server and some the new one — another reason to keep the old hosting active and avoid changes on the old site.
After the move: what to check
| Check | How |
|---|---|
| Permalinks | Settings → Permalinks → Save (refreshes rewrite rules) |
| HTTPS | Install SSL on the new host; check for mixed-content warnings |
| Forms and emails | Send test messages; set up SMTP if emails don’t arrive |
| Caching | Re-enable caching plugins; clear CDN cache |
| Search Console | Watch for crawl errors and 404s |
| Backups | Set up backups on the new host |
Common migration problems
| Problem | Fix |
|---|---|
| Error establishing a database connection | Check wp-config.php details — see our fix |
| Images missing | Check wp-content/uploads copied fully; check URLs |
| Redirects to the old site | Update siteurl and home in the database |
| 404 on all posts | Re-save permalinks |
| White screen | PHP version or plugin issue — see white screen fixes |
Frequently asked questions
Will moving hosts hurt my SEO?
Not if URLs stay the same, the site stays online and it’s at least as fast. Avoid long downtime.
How long does a migration take?
The copy takes minutes to hours depending on size; DNS can take up to 48 hours.
Can I move WordPress to a new domain at the same time?
Yes, but do it in steps and add 301 redirects from the old domain.
When can I cancel my old hosting?
After DNS has fully switched and you’ve checked the new site — usually a few days to a week.
Final thoughts
Back up, migrate, test before DNS, switch, then check. Choosing a new host? Read how to choose hosting for WordPress. Official reference: Moving WordPress.
A real-world example
A small consultancy moved its WordPress site from a slow shared host to a managed host. The owner used the new host’s free migration service, which copied the site to a temporary URL. She checked every page, tested the contact form, logged in to the dashboard and confirmed images loaded. Only then did she change the domain’s DNS records. She kept the old hosting account active for two weeks in case anything was missed. Two days later she noticed that contact form emails weren’t arriving — the new host blocked PHP mail. Installing an SMTP plugin fixed it. Because the old host was still active, there was no panic and no lost data.
Choose a host that patches quickly
Moving hosts is a good moment to check how the new host handles security. Ask how quickly they apply critical patches to server software. In October 2026, the PHP2Shell vulnerabilities affected nearly every PHP server, and the best hosts patched within hours and told customers clearly. A host that patches slowly or communicates poorly puts your site at risk no matter how carefully you maintain WordPress itself.
Post-migration checklist
- Test every important page, form and checkout flow.
- Confirm SSL works and the site loads on https.
- Check emails arrive — set up SMTP if needed.
- Re-enable caching and CDN settings on the new host.
- Set up backups on the new host.
- Submit your sitemap again in Search Console and watch for errors.
- Cancel the old host only after a week or two of smooth running.
Reducing downtime during the switch
To keep downtime close to zero, lower your domain’s DNS TTL (time to live) to five minutes a day before the move, so the change spreads faster. Avoid publishing new content or taking orders during the final sync, or put a store into maintenance mode for a few minutes. After switching DNS, both servers may receive visitors for a short time, so keep the old site unchanged until DNS has fully updated. With these steps, most visitors never notice the move at all.
Write down each step you take during the move, so you can repeat it easily for other sites in future.
WordPressPrime.com is an independent guide and is not affiliated with the WordPress Foundation, WordPress.org or Automattic. Always back up your website before making changes, and check official sources for the latest details.
