How to Migrate Your Website to a New Host Without Downtime (or a Bill)

Most people stay on a host they've outgrown for one reason: they're afraid the move will break their site. It won't — if you do it in the right order.

The golden rule: copy first, switch last

The mistake that causes downtime is changing your domain's DNS *before* the site works on the new host. Do it the other way around:

1. Copy your files and database to the new host while the old site keeps running.
2. Test the copy on the new host using a temporary URL or your hosts file, so you can see it before the public does.
3. Only then change your DNS to point at the new host.

Because the copy already works when you flip DNS, visitors never hit a broken site. The worst case is that someone sees the old, still-running site for a few minutes while DNS propagates.

What actually needs to move

• Files — your whole web root (for WordPress, the wp-content folder is the part that's truly yours).
• Database — export from the old host, import to the new one.
• Config — for WordPress, update the site URL if it changes; for custom apps, environment variables and any cron jobs.
• Email — remember email is often separate from web hosting; moving your website does not move your mailboxes unless you plan for it.

Why you shouldn't pay for this

Migration is mechanical. A good host *wants* you to move in, so they do the copy-test-cutover for you at no charge — because the alternative is you staying put out of fear. On Nxeon, migration is free: we bring the files, the database, and the configuration across, verify the site actually serves on the new box, and help you cut the domain over cleanly.

Your pre-flight checklist

• [ ] Full backup of the current site (belt and braces)
• [ ] Files + database copied to the new host
• [ ] Site tested on the new host before touching DNS
• [ ] SSL confirmed on the new host (it should issue automatically once DNS points over)
• [ ] Email plan sorted separately
• [ ] Lower your DNS TTL a day before, so the cutover is fast

Do it in that order and a migration is boring — which is exactly what you want from one.