payless.host
How to Move a Website to a New Host Without Downtime
Updated Nov 22, 2026
Before you start
Moving a site between hosts means running it in two places at once for a short period, then switching the address over. The old host stays live until the new one is ready and tested. You will need access to both control panels, your domain registrar, and a way to edit a file on your computer.
Plan for the migration to take two to four days from start to finish, most of that waiting for systems to update rather than active work.
Step 1: Set up hosting at the new provider
Sign up with the new host and choose a plan that matches or exceeds what you have now. If your current site uses 5GB of storage and 20GB of monthly traffic, the new plan needs at least that. Shared hosting at DreamHost starts at 2.89 EUR/month and rises to 10.99 after twelve months, while HostGator begins at 3.75 USD/month and becomes 10.99 after thirty-six months.
Once the account is active, note the nameservers the new host provides — usually two addresses like ns1.example.com and ns2.example.com. You will need these in step five. Do not change anything at your domain registrar yet.
Step 2: Copy your site to the new host
Download your site files from the old host using FTP or the file manager in its control panel. This creates a local backup. Upload the same files to the new host's public_html or www folder.
Export your database from the old host through phpMyAdmin or a similar tool, choosing "Export" and saving the .sql file. Create a new database at the new host, then import that file into it.
Edit your site's configuration file — wp-config.php for WordPress, config.php for others — to use the new database name, username and password the new host assigned. Upload the edited file.
What can go wrong: File permissions may not transfer correctly, causing broken images or errors. In the new host's file manager, set folders to 755 and files to 644. A database import may fail if the new server runs an older version of MySQL; the error message will say which line failed, and you can edit the .sql file to remove incompatible commands.
Step 3: Test the site at the new host
The site now exists in two places, but your domain still points to the old host. To view the new version, edit your computer's hosts file. On Windows, this is C:\Windows\System32\drivers\etc\hosts. On Mac, it is /etc/hosts. Add a line with the new host's IP address and your domain name, separated by a space.
Save the file, then visit your domain in a browser. You are now seeing the new host's copy. Click through the site, test forms, check that images load. If something breaks, the old live site is unaffected — visitors still see that one.
What can go wrong: The hosts file edit may require administrator access. URLs may point to the old host if they were hardcoded; a search-and-replace in the database fixes this, but make a backup first. Email may stop working if the new host does not yet handle it; leave email DNS records pointing to the old host until the site migration is complete.
Step 4: Lower the TTL at your domain registrar
Log into your domain registrar and find the DNS settings. The TTL, or time to live, controls how long other servers remember your domain's address. Lower it from the default — often 86400 seconds — to 300. This means the address will update everywhere within five minutes once you change it, rather than a full day.
Wait twenty-four hours. Old TTL settings are still cached around the internet, and this wait ensures they all expire before you proceed.
Step 5: Point the domain to the new host
In the same DNS settings, replace the old nameservers with the ones the new host provided in step one. Save the change. Your domain now resolves to the new host, though it will take minutes to hours for the update to reach all DNS servers globally.
Remove the line you added to your hosts file in step three, so you see the same version of the site everyone else does.
What can go wrong: DNS propagation is not instant. For several hours, some visitors will see the old host and others the new one. Do not delete anything at the old host yet. If you find a problem, you can revert the nameservers and most visitors will never have seen the new version.
Step 6: Verify and wait
Visit your site from a device you have not used before, or use a phone on mobile data rather than your home connection. Both may still be using cached DNS. Test again after an hour, and again after six. Once the site loads consistently from the new host and everything works, wait another day before touching the old host.
Check email separately. If your domain handles email, confirm messages are arriving. If they are not, the MX records may need adjusting at your registrar to point to your email provider.
Step 7: Cancel the old hosting
Once the new site has been live for forty-eight hours with no issues, you can close the old hosting account. Download a final backup of files and database before you do. InterServer charges 2.50 USD for the first month, then 7.00, so timing the cancellation avoids paying for both hosts at the higher rate.
