FastHostNow

Plan a move

An example move plan

This is a worked example. Put in your own switch time and setup on the left.

01 The switch
02 DNS

Shown next to each record at the company that runs your DNS. 14400 is a common shared-hosting default.

03 What moves
Also on the site

Nothing is stored when you build a plan. Nothing here contacts your hosts or DNS.

Move · Example: bakery.example.com

OLDcurrent host
NEWnew host
Switch
Sat Oct 24
11:00 PM EDT
Method
A record
TTL now
4 hours
Steps
15

Lower TTL by

Sat 6:00 PM

Keep old host until

Sat Nov 7

No risk flags

  1. Now · Tue Oct 13, 8:23 PM
  2. The days before
  3. T-7d Sat Oct 17 11:00 PM

    Write down everything the site uses

    • Export or copy down EVERY DNS record (A, AAAA, CNAME, MX, TXT incl. SPF/DKIM/DMARC, SRV, CAA). A new host's default zone often replaces them.
    • Note the database name(s) and the config file that holds the database login (wp-config.php).
    • List all 4 mailboxes, forwarders and autoresponders; decide how each person gets their new password.
    • Note which address the site's forms send from and how (PHP mail or SMTP login).
    • Download a full backup from the old host and keep it off both servers.
  4. T-6d Sun Oct 18 11:00 PM

    Set up the new host

    • Add the domain to the new hosting account (do not change DNS yet).
    • Match the PHP version the site runs on today.
    • Create the empty database and its user.
    • Create the 4 mailboxes on the new host with the same names.
    • Write down the new server's IP address: you need it for the test and the switch.
  5. T-3d Wed Oct 21 11:00 PM

    First full copy to the new host

    • Copy all site files to the new host.
    • Export the database and import it on the new host; update the database login in the config file.
    • The domain stays the same, so no search-and-replace of URLs is needed.
  6. T-2d Thu Oct 22 11:00 PM

    First copy of the mailboxes

    • Copy each mailbox old -> new over IMAP (the new host's mail import tool, or imapsync).
    • People keep using the old mailboxes until the switch.
  7. T-2d Thu Oct 22 11:00 PM

    Lower the TTL to 300 seconds

    • At the DNS host you use TODAY, set the TTL of the records you will change (the domain, www, mail) to 300 seconds.
    • Why: resolvers keep the old answer for up to the old TTL (4 hours). Lowered in time, the switch reaches almost everyone within about 5 minutes.
    • Latest safe moment: the deadline shown. Earlier is fine.

    Deadline Sat Oct 24, 6:00 PM EDT

  8. The day before
  9. T-1d Fri Oct 23 11:00 PM

    Test the new copy from your own computer

    • Point only your computer at the new server with a hosts-file line: NEW-IP yourdomain and NEW-IP www.yourdomain.
    • Windows: C:\Windows\System32\drivers\etc\hosts (Notepad as administrator). Mac/Linux: /etc/hosts (sudo).
    • Click through the site: home, a few pages, login, a form.
    • Remove the line afterwards. The certificate warning during this test is expected until the new host can issue its certificate.
  10. Switch
  11. T-1h Sat Oct 24 10:00 PM

    Freeze changes

    • No new posts, comments, uploads or settings changes on the old site from now on: they would not be in the final copy.
  12. T-30m Sat Oct 24 10:30 PM

    Final copy of the database and changed files

    • Export the database again and import it on the new host, replacing the first copy.
    • Copy files changed since the first copy (uploads, images).
  13. T-0 Sat Oct 24 11:00 PM

    Switch

    • At your DNS host: change the A record(s) for the domain and www (and any AAAA) to the new IP.
    • Change the mail records (MX target / mail host) to the new host.
  14. Right after
  15. T+15m Sat Oct 24 11:15 PM

    Check the site on the new host

    • From a phone on mobile data (not your Wi-Fi): load the site and a few pages.
    • Check the padlock: the certificate must be valid for the domain and www.
    • Free certificates can only be issued once the domain points at the new host. If HTTPS fails, run the host's certificate check (AutoSSL / Let's Encrypt) now.
    • Log in to the site's admin.
    • Send a form and confirm the email arrives (check spam too).
    • Send a message to one mailbox from an outside address and read it on the new host.
  16. T+1h Sun Oct 25 12:00 AM

    Rollback decision point

    • Badly broken? Point the record(s) back to the old IP: with a 300-second TTL most visitors are back on the old site within minutes.
    • Only roll back before new content lands on the new server, or copy it back first.
  17. T+6h Sun Oct 25 5:00 AM

    Stragglers have moved

    • A few resolvers ignore short TTLs. After about 6 hours the old server should see almost no visitors: check its access log.
  18. Wrap up
  19. T+2d Mon Oct 26 11:00 PM

    Raise the TTL again

    • Set the records back to a normal TTL (3600 is a common choice). Short TTLs are only needed around a change.
  20. T+3d Tue Oct 27 11:00 PM

    Final mailbox catch-up

    • Copy each mailbox old -> new once more: mail delivered to the old server by stale records lands there.
    • After this, nobody needs the old mailboxes.
  21. T+14d Sat Nov 7 11:00 PM

    Cancel the old hosting

    • Download one last full backup from the old host first.
    • Check the old access log and mailboxes show nothing new for several days.
    • Then cancel. Kept 14 days because mail moved.

Rules of thumb, not guarantees: your hosts' own steps win where they differ. Times are in Eastern (New York) time.