How to Move Your Website to a New Host Without Downtime
Switching hosting providers does not have to mean broken pages or lost email. Follow this step-by-step plan for copying files, databases and email, testing safely and switching DNS with no downtime.
Updated November 18, 2026 · 4 min read
Moving a website to a new host is one of those jobs that sounds risky but is very manageable with a plan. The secret to zero downtime is simple: build and test the site on the new server while the old one keeps running, then point your domain at the new server only when everything works.
- Keep the old hosting active until the move is finished and checked.
- Lower your DNS TTL a day or two before the switch so changes spread quickly.
- Test the new server before switching, and do not forget email, SSL and scheduled tasks.
Step 1: Take stock of what you are moving
Make a list of everything your current host provides. It is often more than just the website:
- Website files and any databases (for WordPress, the database holds all posts, pages and settings)
- Email accounts and their messages, if your email is hosted with the same company
- Subdomains, redirects and custom server settings, such as .htaccess rules
- SSL certificates
- Scheduled tasks (cron jobs), such as backups or automated imports
- DNS records for services like email providers, verification records and other tools
Step 2: Take a full backup
Before you touch anything, take a complete backup of files and databases from the old host and store it on your own computer or cloud storage. If you use WordPress, a migration or backup plugin can package everything into one file, or your control panel may offer a full account backup.
Step 3: Lower the DNS TTL
DNS records include a TTL (time to live), which tells other servers how long to remember the record before checking again. If it is set to 24 hours, some visitors may keep going to the old server for a day after you switch. A day or two before the move, lower the TTL on your main records (usually the A or CNAME records for the domain and www) to something short, such as 300 seconds. Wait for the old TTL to expire before switching.
Also readSPF, DKIM and DMARC Explained: Set Up Business Email That Reaches the InboxStep 4: Copy the site to the new host
- Create the hosting account and add your domain on the new server.
- Upload the website files.
- Create a new database and user, import your database backup and update the site’s configuration file with the new database details.
- Copy any custom server settings and recreate cron jobs.
Many hosts offer a free migration service or a tool that copies a whole cPanel account in one go. It is worth asking.
Step 5: Test before anyone else sees it
You can preview the new server before changing DNS by editing the hosts file on your own computer, which tells only your computer to use the new server’s IP address for your domain. Some hosts also give you a temporary preview address.
Check that:
- The homepage, key pages and images load correctly
- Forms send messages and checkouts work, using test payments
- You can log in to the admin area
- Pretty links and redirects work
- There are no errors in the server’s error log
Remove the hosts file entry when you have finished testing.
Step 6: Plan the email move
Email is where most migrations go wrong. If your email is hosted with your old provider, create the same mailboxes on the new host or a dedicated email service, and copy existing messages using the provider’s import tool or an IMAP migration tool. Check the MX record and the SPF, DKIM and DMARC records that tell other mail servers your messages are genuine. If your email is with a separate service such as Microsoft 365 or Google Workspace, make sure those records are copied exactly to your new DNS.
Step 7: Switch DNS
Choose a quiet time. Pause content changes on the old site so nothing is lost, then update the DNS records (or the domain’s nameservers, if your new host will manage DNS) to point to the new server. Because you lowered the TTL, most visitors will reach the new server within minutes. A few may take longer, which is fine because the old site is still running.
Step 8: SSL and final checks
Issue an SSL certificate on the new host as soon as the domain points there. Many hosts do this automatically with free certificates. Then check the site over HTTPS in a private browser window, confirm email sends and receives, submit your sitemap in Google Search Console and watch for errors for a few days.
A quick migration checklist
| Before | During | After |
|---|---|---|
| Inventory and full backup | Copy files and database | Issue SSL |
| Lower DNS TTL | Test via hosts file | Check email and forms |
| Plan email move | Switch DNS at quiet time | Monitor, then cancel old host |
With the old site running until the new one is proven, a hosting move can be completely invisible to your visitors.
This article is independent, general information and is not legal, financial or security consulting advice. Product features and prices change often, so check the vendor's current documentation before you buy or change your systems.





