To migrate a website to a new host without downtime, copy everything (files, database and email) to the new server while the old one keeps running, test the copy privately, then switch your DNS. Because visitors always reach a working version of your site, nobody notices the move.
Whether you need to migrate website to new host servers for better speed, fairer pricing or real support, the secret is order. Most migration horror stories come from cancelling the old host too early, forgetting about email, or switching DNS before testing. This guide walks you through the full process step by step, with a checklist you can follow whether you run WordPress, a custom PHP site or a simple static site.
If you would rather not do it yourself, many hosts, including HostRiser, will handle the move for you for free. We cover that at the end.
Before you migrate: take inventory
Write down exactly what you are moving. It takes ten minutes and prevents the most common surprises.
- Websites: every domain, subdomain and add-on site on your current plan.
- Databases: names and which site uses each one.
- Email accounts: every mailbox, alias and forwarder, plus how much mail is stored.
- DNS records: screenshot or export all records, especially MX, TXT (SPF, DKIM, DMARC, verification codes) and any CNAMEs for third-party services.
- Scheduled tasks: cron jobs that send emails, run backups or sync data.
- Software versions: your PHP version and any special server settings.
- Access details: registrar login, old host login, and new host login.
Also note where your domain is registered. Remember that your domain and your hosting are separate. If that is new to you, see domain name vs. web hosting.
Step 1: Make a full backup
Before touching anything, take a complete backup of your site files, every database and your email, and download it to your own computer or cloud storage. This is your insurance if anything goes wrong on either server. Our website backups guide explains what a complete backup includes.
Step 2: Copy files, database and email to the new host
Website files
Copy your site files to the new server using SFTP, SSH or your new host’s file manager. For large sites, compress everything into a single archive first, which is much faster than transferring thousands of small files.
Database
Export each database from the old host (for example as an .sql file from phpMyAdmin or the command line), create a new empty database on the new host, and import the file. Then update your site’s configuration with the new database name, user and password. On WordPress, that is wp-config.php.
WordPress shortcut
For WordPress sites, a reputable migration plugin can bundle files and database into one package and restore it on the new host. This handles most of the steps above automatically.
Email is the part people forget. Create the same mailboxes on the new host, then copy existing messages across using an IMAP migration tool or by connecting both accounts in an email app and dragging folders over. Recreate forwarders and aliases too.
Step 3: Test on a temporary URL or with your hosts file
Never switch DNS until you have seen the new copy working. You have two ways to preview it:
- Temporary URL: many hosts give each site a temporary address you can open before DNS changes.
- Hosts file: add a line to your computer’s hosts file that points your domain to the new server’s IP address, for example
203.0.113.10 yourdomain.com. On Windows the file is atC:\Windows\System32\drivers\etc\hosts; on Mac and Linux it is/etc/hosts. Only your computer sees the new server, so you test the real domain privately.
Then check every important page, the menu on mobile, contact forms, logins, search and, for shops, the full checkout in test mode. Remove the hosts file line when you are done.
Step 4: Lower your TTL and switch DNS
Lower the TTL first
TTL (time to live) tells networks how long to cache your DNS records. A day or two before the move, lower the TTL on your main records to about 300 seconds (5 minutes). When you switch, the change then spreads much faster, and you can roll back quickly if needed.
Switch DNS
Pick a quiet time for your audience. Then either change your domain’s nameservers at your registrar to the new host’s nameservers, or update the A record (and MX records for email) to the new server. Our guide on pointing a domain to your hosting shows both methods.
If your site takes orders or bookings, consider pausing them for the switch window, or put the old site in maintenance mode once DNS is changed, so no new data lands on the old server.
Step 5: Keep the old host running, then check everything
DNS changes reach most visitors within a few hours, but some networks hold old records for up to 48 hours. During that time, some visitors still reach the old server, which is exactly why you keep it active. Do not cancel the old plan for at least a week.
Post-move checklist
| Check | What to look for |
|---|---|
| Website | Home, key pages and images load on mobile and desktop |
| SSL | Padlock shows, HTTP redirects to HTTPS, no certificate warnings |
| Forms and checkout | Test submissions arrive and test orders complete |
| Sending and receiving both work, old messages are present | |
| Email authentication | SPF, DKIM and DMARC records are correct for the new server |
| Cron jobs | Scheduled tasks are set up and running once, not twice |
| Search engines | Indexing is allowed and Search Console shows no new errors |
| Speed | PageSpeed Insights results are equal or better than before |
| Backups | Automatic backups are running on the new host |
Common migration mistakes to avoid
- Cancelling the old host too early, before every visitor and email has moved over.
- Forgetting email, so messages keep landing on the old server where nobody reads them.
- Losing TXT records such as SPF, DKIM and site verification codes when changing nameservers.
- Skipping the test step and discovering a database error after DNS has already switched.
- Leaving “discourage search engines” switched on after testing a WordPress copy.
- Running cron jobs on both servers, which can send duplicate emails or invoices.
Finally, update email apps on phones and computers with the new server settings, and raise your TTL back to a normal value once everything is stable.
How HostRiser helps
When you move to HostRiser, our team migrates your website for free, including files, databases and email. It usually takes 1-2 business days and is done with zero downtime: we copy and test everything first, then tell you exactly when and how to point your domain to ns1.hostriser.com and ns2.hostriser.com. Every plan also comes with daily backups, free SSL and a 30-day money-back guarantee. Learn more on our free migration page.
Frequently asked questions
How long does it take to migrate a website to a new host?
Copying a typical small business site takes from under an hour to a few hours of work. DNS changes then usually take effect within a few hours, though full worldwide propagation can take up to 48 hours.
Will my website go down during a migration?
Not if you do it in the right order. Keep the old host running, copy and test everything on the new host first, and only then switch DNS, so visitors always reach a working copy.
Will moving hosts hurt my SEO?
A careful migration that keeps the same domain, URLs and content has no lasting SEO impact. Problems come from downtime, broken links or accidentally blocking search engines, which the post-move checks catch.
Do I need to move my domain name too?
No. Your domain can stay with its current registrar. You only change where it points, usually by updating the nameservers or DNS records to your new host.
When can I cancel my old hosting?
Wait at least a week after switching DNS. Confirm the site, email and forms all work on the new host and that no new emails are arriving at the old server before you cancel.
Ready for a host that renews at the price you signed up at? Compare our hosting plans and let us handle the move.
Last updated October 12, 2026
