payless.host
How to Leave Your Web Host: A Step-by-Step Guide
Updated Nov 22, 2026
1. Back Up Everything Before You Touch Anything
Download a complete copy of your site before you make changes anywhere. Log into your current host's control panel and locate the file manager or FTP access. Download every file in your public_html or www folder to your computer. This takes minutes on a small site, hours on a large one with images and uploads.
If your control panel offers a backup tool, use it — it will package everything into a single archive. If not, use an FTP client like FileZilla. What can go wrong: forgetting hidden files (those starting with a dot) or skipping directories outside the main site folder. Check the downloaded folder size matches what the control panel reports.
2. Export Your Database
Most sites run on WordPress, Joomla or another system that stores content in a database separate from the files. Find phpMyAdmin or a database manager in your control panel. Select your database, click Export, choose SQL format, and download the file.
What can go wrong: exporting the wrong database if you have more than one, or hitting a size limit on very large databases. The export should complete with a .sql file on your computer. Open it in a text editor — it should contain readable SQL commands, not error messages.
3. Set Up the New Host and Upload Your Site
Sign up with the new provider and note the nameserver details they give you — you will need them later. Upload your files to the new host using their file manager or FTP. Create a new database through their control panel, then import the .sql file you exported earlier using their phpMyAdmin.
If you run WordPress or a similar platform, edit the configuration file (wp-config.php for WordPress) to match the new database name, username and password the new host assigned. What can go wrong: mismatched database credentials will break the site. The new host's error logs will show database connection failures if this happens.
4. Test on the New Host Before Changing DNS
Most control panels let you preview your site on the new server using a temporary URL before you move the domain. This might be an IP address or a subdomain the host provides. Visit it and check that pages load, images appear, and forms work.
What can go wrong: mixed content warnings if your site uses HTTPS, or broken links if the old site used absolute URLs. Test logging into your admin panel, submitting a contact form, and loading a few different page types. If something breaks, fix it now while the live site still runs on the old host.
5. Point Your Domain to the New Host
Log into wherever you registered your domain — often the old host, sometimes a separate registrar like Namecheap. Find the DNS or nameserver settings. Replace the old nameservers with the ones the new host gave you.
This change takes anywhere from an hour to forty-eight hours to complete worldwide, though most updates finish in under six hours. What can go wrong: typing a nameserver address incorrectly will point your domain nowhere, taking the site down. Double-check each character before saving.
6. Wait and Check That DNS Has Propagated
Visit your domain in a browser. If it loads the new site, DNS has updated. You can also use a DNS checker tool online to see whether different parts of the internet are seeing the new or old nameservers. Your own computer may cache the old address — try from a phone on mobile data to get a fresh lookup.
What can go wrong: impatience. Changing back and forth while propagation is underway creates confusion. Leave the nameservers alone once set and wait. Email may route to the old server briefly if you host it with the site — warn people not to expect instant delivery during the switch.
7. Test Everything Again on the Live Domain
Once DNS points to the new host, repeat the tests you ran on the temporary URL. Forms, logins, image uploads, payment gateways if you run a shop. What can go wrong: SSL certificates sometimes need reissuing on the new host. If your site shows a security warning, generate a new certificate through the new host's control panel.
Check that email works if you host it with the domain. Send a test message to yourself and verify it arrives.
8. Keep the Old Host Running for a Week
Do not cancel the old hosting account the moment DNS updates. Keep it active for at least seven days. If something breaks on the new host, you can switch the nameservers back while you fix it. The old site remains intact as a fallback.
What can go wrong: cancelling immediately and discovering a critical feature does not work on the new server. Most providers like HostGator or DreamHost will not restore a cancelled account.
9. Cancel the Old Hosting
Once the new site has run without problems for a week, log into the old host and cancel the service. Download one final backup before you do — some hosts delete files within hours of cancellation. Check whether the cancellation is immediate or at the end of your billing period. If you prepaid through InterServer or another provider, confirm whether any refund applies.
What can go wrong: forgetting to cancel, and paying for hosting you no longer use. Set a calendar reminder.
