Website Migration Checklist: What to Do Before You Switch Hosts

We've handled hundreds of website migrations and the ones that go badly almost always share the same root cause: someone skipped the preparation step. A migration that takes two hours with proper planning can turn into a two-day fire drill without it.

Use this checklist before you move anything.

Before You Start: Document Everything

The first step is building a complete picture of what you're moving.

• Record your current server specs — PHP version, MySQL version, any custom PHP extensions
• Export a full list of your DNS records — A, CNAME, MX, TXT, SRV. Screenshot every single one.
• Note your current TTL values — you'll need to lower these before migration (see below)
• List all domains and subdomains on the account
• Identify any cron jobs running on the server and their schedules
• Note any custom .htaccess rules or nginx configs you've set up

Back Up Everything

This is non-negotiable. Before touching anything:

• Full file backup — everything in your web root, including hidden files like .env
• Full database dump — every database the site uses
• Email backup (if you're also migrating email)
• SSL certificates — export your private key if you're using a custom cert

Store backups in at least two places: your local machine and a cloud storage service.

Lower Your DNS TTL Early

Log in to your domain registrar and lower your TTL to 300 seconds at least 24 hours before the migration date. This ensures that when you update your DNS records, the changes propagate quickly.

• Set TTL to 300 seconds on all A and CNAME records
• Wait 24+ hours (this is the time the old, high TTL needs to expire everywhere)

Set Up the New Server First

Never cut over DNS before your site is confirmed working on the new server.

• Set up your new hosting environment
• Transfer all files to the new server
• Import your database
• Update your application's config to point to the new database
• Test the site using the server's IP address or a temporary preview URL
• Verify all forms, payment flows, and integrations work
• Install and verify your SSL certificate

The Cutover

Only once everything checks out on the new server:

• Update your A records to point to the new server IP
• Monitor DNS propagation (use dnschecker.org or similar)
• Test the live site once DNS has propagated to your location
• Set up any cron jobs that were running on the old server

After Migration

• Keep the old server running for at least 48 hours as a safety net
• Restore your TTL to 3,600 seconds (or higher) once you're confident
• Update any hardcoded server IPs in your application config or third-party services
• Cancel the old hosting plan only after the 48-hour window

A migration done with this checklist in hand takes longer to plan but is almost always smooth. If you'd rather not deal with any of this yourself, our team offers a full managed migration service — we handle every step from start to finish.