How do I move a website to a new host without creating avoidable downtime?

Business Tech & Tools

How do I move a website to a new host without creating avoidable downtime?

The short answer

Build and test a complete copy at the new host before changing public DNS. Keep the URLs the same, lower the relevant DNS TTL ahead of time, schedule a short content freeze, switch the traffic, test the live customer path, and keep the old host available until the new copy is stable.

The safest migration is a controlled handoff between two working sites, not canceling one host and hoping the backup imports into the other.

Inventory what is actually moving

A WordPress site usually includes both files and a database. It may also depend on:

  • DNS records.
  • HTTPS certificates.
  • email accounts or mail records.
  • forms and email-delivery services.
  • scheduled tasks.
  • payment, shipping, course, or membership integrations.
  • server redirects and security rules.
  • analytics and verification files.
  • subdomains and staging sites.

WordPress’s migration guidance says to begin a server move by backing up the WordPress directory, images, plugins, other files, and the database. See WordPress’s official migration documentation.

Prepare before migration day

  1. Record current hosting, DNS, PHP, database, SSL, and email settings.
  2. Create a fresh independent backup of files and database.
  3. Confirm you know how that backup would be restored.
  4. Copy the site to the new host.
  5. Test it through the host’s preview method or another safe local method.
  6. Fix version, permission, path, cache, and plugin problems before the switch.
  7. Lower the relevant DNS TTL early enough for the old value to expire.
  8. Choose a quiet period and tell anyone who publishes or processes orders.

Google suggests lowering DNS TTL to a conservative low value, such as a few hours, at least a week before a hosting move. See Google Search Central’s hosting-move guidance.

Build a test sheet for the new host

Test more than whether the homepage opens.

Area Test
Pages and media Important URLs, images, downloads, search, navigation
Forms Submission, business receipt, visitor confirmation, reply-to address
Sales Product, cart, checkout, payment mode, receipt, refund workflow if used
Accounts Login, password reset, purchase access, logout
Operations Scheduled posts, backups, cron tasks, outgoing email
Search robots directives, canonicals, sitemap, redirects, status codes
Security HTTPS on root and www, admin access, least-privilege accounts

Use test transactions or the platform’s test mode where appropriate. Do not place a real charge and assume that every post-purchase step worked because checkout displayed a success screen.

Control changing data

For a brochure site, a short publishing freeze may be enough. For a store, forum, course, or membership site, the database can change every minute.

Decide in advance how you will handle orders, form entries, comments, account changes, and enrollments created between the first copy and the final switch. Options include a brief maintenance window, a final database synchronization, or a migration tool designed for changing data. This is where experienced technical help may be worth more than a do-it-yourself shortcut.

Switch and verify

At the agreed time:

  1. Complete the final content or database sync.
  2. Change only the necessary DNS record or nameserver setting.
  3. Confirm authoritative DNS shows the intended value.
  4. Test from more than one network.
  5. Confirm the certificate and redirects.
  6. Submit forms and complete the critical customer path.
  7. Watch server logs, uptime, orders, email, and error reports.
  8. Restore the TTL after the move is stable.

If the domain and page URLs do not change, this is a hosting move, not a redesign. Avoid changing navigation, plugins, URLs, theme, and host in one event. Fewer moving parts make a rollback possible.

Keep the old host until you are certain

Do not cancel immediately. Keep the old site intact and prevent accidental new activity there if necessary. Retain it through the period in which you are checking DNS caches, missing files, mail delivery, scheduled tasks, and customer reports.

Define rollback before the switch: which DNS value you will restore, which database copy is authoritative, and who makes the decision. A rollback plan written during an outage is usually too late.

Sources and further reading

A free next step

Not sure which business fits you yet?

The free Freedom Path Assessment can help you compare your strengths, schedule, income goals, and preferred way of working before you commit to a business direction.

Take the Freedom Path Assessment Free

Related Questions

Related WAHMN resource

If you want to turn this website task into a service or build a stronger process for your own site, this system walks through the work in more depth. See Website & Landing Page Build System.

← All questions