Short answer: to move hosts without downtime, keep your old hosting running, copy your website files and databases to the new host, test the site there, lower your DNS TTL a day in advance, then switch DNS. Visitors move across gradually with no outage, and you can switch back if anything goes wrong. Or let SiloLobby do it: we migrate your website for free when you buy hosting.
Moving a website feels risky, but with the right order of steps it is routine. This guide gives you a safe migration plan used by professionals, a checklist for email, and the most common problems with their fixes.
The golden rule: overlap, do not cut over
Downtime happens when the old hosting is cancelled before the new site is ready, or when DNS is changed before the new site has been tested. Keep both running in parallel until you have confirmed everything works on the new host.
Before you start: gather what you need
- Login details for your old hosting (cPanel or FTP) and your domain's DNS.
- A list of email accounts and forwarders on the old host.
- Any cron jobs, special PHP settings or custom server configuration.
- A quiet time for the switch, such as a weekend morning.
Step 1: take a full backup
Download a complete copy of your website files and export your databases. If your old host uses cPanel, a full account backup includes both. Keep this backup safe: it is your safety net.
Step 2: set up the new hosting
Order hosting at SiloLobby. Do not change your domain's DNS yet; visitors still go to the old host.
Step 3: copy files and databases
- Upload your files to public_html (or your addon domain's folder) using cPanel File Manager or FTP. Uploading a ZIP and extracting it is fastest.
- Create a new database and database user.
- Import your database with phpMyAdmin.
- Update your application's configuration with the new database details (for WordPress, the wp-config.php file).
Step 4: recreate email accounts
Create the same email addresses on the new host, with the same passwords if possible, so mail has somewhere to land after the switch. Recreate forwarders and autoresponders too. If you want to keep old messages, you can copy them across with your email app (by adding both accounts) or ask our support team.
Step 5: test before switching
Preview your site on the new server before changing DNS. Our support team can show you how (for example with a temporary address or a hosts-file entry). Check:
- every main page loads correctly,
- images and styles appear,
- forms send messages,
- logins work,
- checkout and payments work (test mode where possible),
- there are no "database connection" errors.
Step 6: lower the TTL
A day before switching, lower the TTL on the DNS records you will change (usually the A record and www) to 300 seconds. When you switch, the change then spreads in minutes rather than hours.
Step 7: switch DNS
Change your nameservers or A record to point to the new host. See how to point your domain to your hosting for the difference between the two methods. If you change nameservers, make sure your email records (MX, SPF, DKIM) exist at the new DNS provider first.
Step 8: check, then clean up
For 24 to 48 hours, some visitors may still reach the old server. Do not make content changes on the old site during this time. After 48 hours:
- check the site and forms again,
- send and receive test emails,
- confirm the SSL padlock shows,
- check your old email account for any messages that arrived during the switch,
- then cancel the old hosting.
Migration checklist
- Full backup downloaded
- New hosting ordered
- Files uploaded
- Database imported and configuration updated
- Email accounts and forwarders recreated
- Site tested on the new server
- TTL lowered a day before
- DNS switched
- Email records confirmed
- SSL confirmed
- Old hosting cancelled after 48 hours
Common problems and fixes
| Problem | Likely cause | Fix |
|---|---|---|
| "Error establishing a database connection" | Wrong database details in configuration | Update the database name, user and password |
| Site shows but images are missing | Files not fully uploaded, or wrong paths | Re-upload; check file paths and permissions |
| Email not arriving | MX records not updated or missing | Check MX records point to the new mail server |
| Old site still showing | DNS caching | Wait, clear the browser cache, try another network |
| No padlock | SSL not issued yet | Wait a little after DNS updates, or contact support |
Let us do it for you
Free migration comes with SiloLobby hosting. Order your plan, open a support ticket with your old host's access details, and our team copies your site, databases and email accounts, tests them, and tells you when to switch.
Moving specific types of websites
WordPress
- Use a migration plugin, or copy wp-content and the database manually.
- Update wp-config.php with the new database details.
- If the domain stays the same, no search-and-replace is needed.
- Clear caches after the move.
Online stores
- Choose a quiet time and pause orders briefly during the final copy so no orders are lost.
- Test checkout and payment notifications (webhooks) on the new host.
- Confirm order emails are sent from the new server.
Custom apps
- Recreate environment variables and scheduled tasks (cron jobs).
- Match PHP, Node.js or database versions where possible.
- Check file permissions and upload folders.
Communicating with your team and customers
Most well-planned migrations are invisible to customers. Still:
- tell staff not to change website content during the switch,
- let your team know email may briefly arrive in two places,
- have a support contact ready in case something looks wrong.
After the migration: performance check
Once the new site is live, compare it with the old one:
- page load times on a phone using mobile data,
- server response time,
- any errors in the new server's logs.
Faster storage and caching on the new host often make a noticeable difference.
How long should you keep the old hosting?
Keep it for at least 48 hours after switching DNS, and up to a week if you are moving email. Some networks remember old DNS answers longer than expected, and the overlap gives you a safe fallback if anything was missed.
Free migration: what to send us
Open a support ticket with your old host's cPanel or FTP access, your database details if available, and a list of email accounts. We confirm when the copy is ready to test.
Summary
A no-downtime migration is about order: back up, set up the new host, copy and test, lower the TTL, switch DNS, and only then cancel the old hosting. Take your time, keep both running in parallel, and you will not lose visitors or email.