How to Migrate Your Website to a New Host (Step by Step)

Migration is a sequence, not a leap. Do the backup, the copy, the DNS prework and the verification in order, and you can move a live site with minutes of disruption instead of hours.

The fear of migration keeps people on bad hosts for years. In practice it is a checklist: back up everything, copy it to the new server, verify it there, then flip DNS. Follow the order below and you get a smooth move with minimal or zero downtime for your website hosting.

Before you start: prepare DNS

Lower your DNS TTL from the default (often 3600 seconds or more) to 300 seconds at least 24-48 hours before you plan to switch. This does not change where traffic goes yet, but it means when you do change the record, resolvers worldwide pick it up in minutes instead of a day. Note your current TTL and records first: A, AAAA, MX, CNAME, TXT (especially SPF, DKIM, DMARC) - you will recreate them.

Step 1: complete backup

Take two backups: a full account backup from your current host (files plus database plus email) and an off-site copy you control. Verify the archive opens and the database SQL file is complete. A backup you have not checked is not a backup.

Step 2: copy files and database

• Files: transfer via SFTP or the panel's file manager to public_html on the new host. Exclude caches and temporary files; they will regenerate.
• Database: export with phpMyAdmin or mysqldump, then import into a fresh database on the new server. Create a dedicated DB user and grant only the privileges it needs.
• Configuration: update the database name, user and password in your application config (for example wp-config.php, .env, or your framework's settings file).

Step 3: test on the new server before switching

Preview using a hosts-file entry on your computer or a temporary URL, and browse the site as a logged-in user. Test the homepage, one deep article, a form submission, the checkout or login flow, and your admin panel. Fix broken paths, missing cron jobs and redirect rules now, while production is still serving traffic from the old host.

Step 4: email cutover

If mail lives with your host, migrate it deliberately: create mailboxes on the new provider, move mail over IMAP (server-to-server copy), verify from webmail, then update MX records. Do this separately from the website DNS change so you can troubleshoot either one in isolation.

Step 5: switch DNS and verify

Point the A record at the new server IP. With a low TTL, propagation typically completes within 5-30 minutes. Watch server logs on the new host: you should see traffic arriving. Keep the old host alive for at least 48-72 hours as a fallback, and confirm cron jobs, SSL renewal and backups are all running on the new environment.

Post-migration checklist

• SSL certificate issued and HTTPS forces correctly.
• Forms, checkout, login and any API integrations tested.
• Search console still verified; no spike in crawl errors.
• Backups scheduled on the new host with an off-site copy.
• Raise DNS TTL back to a normal value once you are confident.
• Cancel the old plan only after a week of clean operation.

If the whole process sounds like more than you want to handle, most hosts - including us - will migrate a standard site for you as part of onboarding. Ask before you buy and confirm what is included.