If you would rather not use a terminal, a migration plugin can transfer a WordPress site to a new host for you. It packs your files and database into one archive, which you import on the new site. This guide explains how that works, the steps that apply to any of them, and the problems that appear on bigger sites.
Install a migration plugin on the old site, export everything to a single package, install a fresh WordPress on the new host, install the same plugin there, and import the package. Test the new site using a hosts-file entry or temporary URL before you change DNSDNS The internet’s phone book. It turns a name people can remember, like example.com, into the number address computers use to find the server. More about DNS →. Large sites can fail on upload limits, so check the size first.
What a migration plugin actually does
WordPress is two things: files (themes, plugins, uploads) and a database holding your posts and settings. A migration plugin exports both into one archive, then on the new site unpacks the files and imports the database. It also rewrites any web addresses stored in the database if the domain is changing. It is the same job as the manual move with WP-CLI, automated.
Well-known examples include Duplicator and All-in-One WP Migration. Their screens differ between versions, so this guide describes the steps rather than exact buttons. Always follow the plugin’s own instructions for the menu names.
Before you start
- Take a full backup on the old host. Do not rely on the plugin alone.
- Check the size of the site (
wp-contentfolder plus database). Free plugin versions often cap uploads. - Check the new host’s PHP version and upload limits match or exceed the old ones.
- Lower the TTL on your DNS records a day ahead so the final switch is fast.
- Note the old site’s admin login. Imports replace the new site’s users with the old ones.
Step by step
1. Export from the old site
Install and activate the plugin, then run its export or package builder. Choose to include the database and all files. Download the resulting file, plus any installer file the plugin asks for. Keep it somewhere safe.
2. Prepare the new host
Install a clean WordPress at the destination. If the new host uses cPanel, the one-click installer is the quickest route. Log in to its admin area.
3. Import on the new site
Install the same plugin on the new site and use its import or restore function with your archive. If the plugin uses an installer file instead, upload the archive and installer to the new site folder and open the installer in your browser, as its instructions describe. When it finishes it will normally ask you to log in again, using the old site’s username and password.
4. Save the permalinks
In Settings » Permalinks, click Save Changes without changing anything. This rebuilds the rewrite rules and fixes pages that show a 404 error after a move. See how to fix 404 errors.
5. Test before switching DNS
Do not point the domain yet. Add a line to your computer’s hosts file that sends the domain to the new server’s IP addressIP address The number address of a device on the internet, like 203.0.113.10. Computers use it to find each other, the way post uses street addresses. More about IP address →, then browse the site. Check the home page, a few posts, images, the contact form, the checkout if you sell anything, and wp-admin.
6. Switch DNS
Update the domain’s A record to the new server, or change the nameservers if the new host gives you theirs. Propagation is usually quick when the TTLTTL How long other computers may remember a domain setting before checking again, in seconds. Short means changes show up faster. More about TTL → was lowered.
7. Add HTTPS
Once DNS points at the new server, issue the certificate. On cPanelcPanel The most popular hosting control panel: a website where you manage your email, files, databases and domains with point-and-click tools instead of commands. More about cPanel → it is in SSL in cPanel; on your own server use Let’s Encrypt with Certbot.
When the import fails
| Symptom | Cause | Fix |
|---|---|---|
| Upload fails or stops at a percentage | Host’s upload size limit | Raise upload_max_filesize and post_max_size, see PHP in cPanel |
| Import times out | max_execution_time too low, or a very large site | Raise the limit, or switch to the manual method |
| Blank page afterwards | PHP version or missing extension | White screen fix |
| Cannot log in | Imported users replaced the new ones | Use the old site’s login |
| Images missing | Uploads folder not fully imported | Re-run the import, or copy wp-content/uploads directly |
| Redirects to the old domain | Stored site address | Check Settings » General and see too many redirects |
Plugin or manual move?
| Plugin | Manual | |
|---|---|---|
| Needs terminal access | No | Yes |
| Best size | Small to medium | Any |
| Control and visibility | Limited | Complete |
| Free version limits | Often a size cap | None |
A plugin is a good first choice for a small blog. For a large shop or anything with tens of gigabytes of uploads, the manual route is safer and often faster.
After the move
Keep the old host for at least 72 hours, then take a final backup before cancelling. Remove the migration plugin from both sites, along with any leftover archive or installer file, because these can expose your database if left on the server. If your email was on the old host too, move it separately; see how to migrate email to a new host.
Related
- How to move a WordPress site to a new host, the manual version.
- Website migration checklist.
- How to move WordPress between cPanel accounts, when both hosts use cPanel.
Something out of date? Software changes. If a step no longer works, tell us and we will check it and update the page.


