To move a WordPress site to a new host, you back up the files and the database, copy both to the new server, test the copy while the old site still serves visitors, and only then point the domain’s DNS at the new server and set up SSL. As of November 2026, Hostinger, Kinsta, Cloudways and WP Engine each document a tool or service that does the copying, but the preparation, the DNS switch and the checks afterward are still your job.
If you are leaving Bluehost specifically, the Bluehost migration guide covers the account-side details.
In this guide
Moving a WordPress site: key facts
| Question | Answer | Documented at |
|---|---|---|
| What has to move | The files (wp-content, wp-config.php, anything custom in the root) and the database. One without the other does not restore a site. | WordPress backup handbook |
| What a host migration usually does not move | Email, DNS records, cron jobs, custom SSL configuration and FTP accounts. | Hostinger, Kinsta |
| Who can do the copy | You (manual), a plugin from the new host, or the new host’s migration team. | Kinsta and Hostinger document services; WP Engine and Cloudways document plugins |
| When the site goes live | Only when the domain’s DNS points at the new server. Every host doc says test first, then point the domain. | Hostinger, Kinsta, WP Engine docs linked below |
| What breaks most moves | Changing the URL in the database without handling serialized data. | WP-CLI search-replace |
Step 1: Before you start
Most failures surface after the old host is cancelled. Inventory first:
- Plugins and themes, with license keys, and which plugins the new host disallows.
- PHP version (Tools, Site Health, Info). Match it on the new host first.
- Email on the domain. Who hosts the mailboxes, and where the MX records live. Hostinger says you migrate email yourself; Kinsta says email setup is not part of its migration.
- DNS records. Export the whole zone: A, CNAME, MX, the TXT records for SPF, DKIM and DMARC, and verification records.
- SSL. Kinsta asks whether to issue a new certificate through its Cloudflare integration or upload an existing one.
- Cron jobs and root files. Hostinger’s migration excludes cron jobs, and WP Engine does not use .htaccess, so rules in one will not carry over.
Then take a full backup and restore it once, on a local install or staging. The WordPress backup handbook is blunt: a backup has two parts, database and files, and you need both to restore. A backup you have never restored is a guess. Last, loosen the locks that block migration tools: Hostinger recommends disabling two-factor authentication and anti-bot verification on the current host, and WP Engine notes that firewall plugins such as Wordfence can rate-limit a migration.
Step 2: Pick the method
The new host’s migration service
Kinsta’s docs describe unlimited free migrations from any host for standard WordPress installations. Its migration guide says the original site stays live, you must not change it once the migration starts, and stores and membership sites should go into maintenance mode.
Hostinger’s migration request lives in hPanel under Websites, Import site. A free migration requires a WordPress site hosted elsewhere, on a Web, Cloud or Agency plan (VPS plans are excluded). You give WordPress admin or cPanel credentials, or upload the files and an .sql export. Email is not migrated, and the copy excludes cron jobs, DNS records, custom SSL configuration and FTP accounts. Hostinger tells you to point the domain only after it finishes.
A migration plugin
WP Engine’s Site Migration plugin is installed on the WP Engine side from the User Portal, then on the source site, and given the connection details. The full-site option copies the database tables and wp-content and updates every instance of the domain in the database, including serialized data. A custom option picks tables, media by date, themes and plugins, and can be saved as a profile for a second run just before the DNS switch.
The Cloudways WordPress Migrator works the other way: install it on the source site, give it the SFTP details of your Cloudways server, and it pushes the site over, updating database values automatically. It migrates only to Cloudways.
Manual
Files over SFTP or rsync, database by export and import, URL changes with a search-replace tool. It works between any two hosts; step 4 covers it in detail. Whether a managed host is worth its premium at all is covered in Is managed WordPress hosting worth it?
Step 3: Lower the DNS TTL a day ahead
Every DNS record carries a time to live, the number of seconds resolvers may cache it. With a one-day TTL, some visitors keep hitting the old server for a day after the switch. Kinsta’s checklist puts numbers on it: 12 to 24 hours before the migration, reduce the TTL to 300 seconds (5 minutes), then raise it back to around 3600 seconds (1 hour) after launch. Google’s hosting-move guide says the same. Cloudflare users need not change TTL, Kinsta adds.
If the old host runs the zone, move it somewhere independent first: a hosting account that closes takes its DNS zone with it.
Step 4: Copy the site
Export the database with phpMyAdmin or wp db export. The WordPress migration handbook‘s own sequence is export the database, download the installation, edit wp-config.php for the new server, upload both.
Copy the files: wp-content in full (themes, plugins, mu-plugins, uploads), wp-config.php, .htaccess, and anything custom in the root.
Create the database on the new host, import, then edit wp-config.php with the new database name, user, password and host. The $table_prefix must match the imported tables; the wp-config reference describes it as the value placed in front of every table name.
Search-replace the URL only if it changes. Same domain, same scheme: skip this. Otherwise run wp search-replace 'https://old.example' 'https://new.example' --skip-columns=guid --dry-run, then again without the dry run. WP-CLI’s search-replace handles PHP serialized data and does not change primary keys. The handbook is emphatic that the guid column in wp_posts must not be changed.
Plugin method, in brief: install the plugin where the host says, connect it, run the full migration. WP Engine recommends a second run just before pointing DNS, pulling only changed tables and new media. Either way, stop editing the live site once the first run begins.
Step 5: Test before switching
Never let the DNS change be your first look at the new server. Three ways to look first:
- Edit your computer’s hosts file so the domain resolves to the new server’s IP for you alone. The site loads under its real domain, so the database needs no change. Delete the entry when you finish.
- Use the host’s temporary URL or preview tool. Hostinger points you to its SkipDNS tool and the plan’s IP address. Kinsta’s Site Preview shows the migrated site over the temporary URL without touching the database, files or DNS.
- Migrate to staging first, where the new host offers it.
Check the home page, a deep post with images, login, every form (submit one and confirm the email arrives), search, and checkout or member pages. Stores and membership sites should also check PHP worker capacity; see PHP workers explained.
Step 6: Switch DNS, then SSL, then force HTTPS
Add the domain in the new host’s panel, then change the A record (or the nameservers, if the whole zone is moving). Leave the old site running during propagation: both servers serve the same content, as long as nobody publishes.
SSL comes next because most hosts can only issue a certificate once DNS resolves to them. WP Engine says it adds SSL and CDN automatically when DNS points to its network; Kinsta issues one through its Cloudflare integration or accepts an upload.
Then force HTTPS. Set WordPress Address and Site Address to the https:// form with no trailing slash, as the handbook specifies, and switch on the host’s HTTPS redirect. The HTTPS handbook adds FORCE_SSL_ADMIN in wp-config.php for logins and admin sessions.
Step 7: After the move
- Email records. If the zone moved, recreate MX, SPF, DKIM and DMARC from your step 1 export.
- Redirects. Old .htaccess redirects do not exist on hosts that ignore .htaccess. WP Engine documents its Web Rules Engine for this.
- Caching and CDN. Purge everything, point the CDN’s origin at the new server, and check that login and checkout pages are excluded from page caching.
- Cron and integrations. Recreate server cron jobs; they were not copied.
- Search engines. If the URLs did not change, submit nothing. Google asks only that your Search Console verification survives the move and that temporary crawl blocks are removed. If the domain changed, redirect every old URL to its new one and use the Change of Address process in Search Console.
- The old plan. Google’s guide says to watch the old server’s logs and shut it down once traffic stops. If the new host has a money-back window, finish testing inside it so you can still back out. Download one last backup from the old host, then cancel.
Step 8: Common problems
Mixed content
The page loads over HTTPS but images or scripts are still referenced as http://. WP Engine’s troubleshooting note says a search and replace may be needed so every domain reference uses the intended domain; run it with a serialized-aware tool, replacing the http:// form with https://.
Missing images
The uploads folder did not copy completely, permissions are wrong, or image URLs still point at the old domain. The handbook notes that image links live in post_content in wp_posts, so a URL change needs the same search-replace.
Permalinks return 404
The home page works but every post is a 404. On Apache the rewrite rules in .htaccess are missing or stale; the handbook says to back up .htaccess, then regenerate it from the Permalinks screen (Settings, Permalinks, Save Changes).
Serialized data
Widgets vanish or theme options reset. Those settings are PHP serialized arrays that record each string’s length, so a plain find-and-replace with a URL of a different length corrupts them. Restore the database from backup and redo the replacement with WP-CLI, which switches to PHP for serialized columns and offers a --precise flag for complex structures.
How to decide
Standard install, host with a migration service: request it, lower the TTL the day before, test on the preview URL, point DNS, keep the old plan until the logs go quiet. Custom code, or a host that offers a plugin: run the plugin yourself with a second run for the final sync. Custom root files or a huge uploads folder: go manual and dry-run the search-replace. If a Black Friday hosting deal prompted the move, buy during the sale but migrate in a quiet week.
Frequently asked questions
How long does it take to move a WordPress site to a new host?
It depends on the size of the site and how fast the old host lets you pull files. Kinsta’s docs say most of its migrations take 1 to 3 hours, with a similar window for review, and that DNS propagation typically takes around an hour but varies with the TTL.
Does a website go down when it changes hosts?
Not if you copy first, test, and only then change DNS. What cannot be avoided is a content freeze: posts or orders made on the old server after the copy will not exist on the new one, hence Kinsta’s maintenance-mode advice for stores.
Should you change the nameservers or just the A record?
Changing the A record moves only the website and leaves email and every other record where it is. Changing nameservers moves the whole zone, so MX, SPF, DKIM and verification records must be recreated at the new host first.
Can you move a WordPress site to a new host for free?
Often, yes. Kinsta’s docs describe unlimited free migrations for standard WordPress installations, and Hostinger offers a free migration request for sites moving from another provider onto its Web, Cloud or Agency plans. WP Engine and Cloudways provide migration plugins you run yourself.
Last checked: November 2026. Prices and plans change; check the vendor’s page before you buy.





