Website Migration Checklist & Step-by-Step Workflow: Move to a New Host with Zero‑Downtime
site migrationhosting migrationwebsite migration checklistDNS TTLstagingrollback plan

Website Migration Checklist & Step-by-Step Workflow: Move to a New Host with Zero‑Downtime

WWebhosting.live Editorial Team
2026-11-11
8 min read

Use this practical website migration checklist to stage, test, cut over, monitor, and roll back a host move with minimal downtime.

Moving a website to a new host does not have to mean taking it offline. This repeatable migration workflow covers preparation, backups, staging, DNS changes, verification, monitoring, and rollback so you can reduce disruption and identify problems before visitors do. Use the included checklists before every hosting migration, then revisit the provider details as plans, dashboards, software versions, and limits change.

Overview

A successful website migration is a controlled change, not simply a file upload. The safest approach is to run the existing site and the new copy in parallel, test the new environment privately, and change DNS only after the destination is ready.

“Zero downtime” is a practical target rather than a promise. DNS caches, third-party services, application sessions, and last-minute database changes can create a short period in which different visitors reach different servers. You can reduce that risk by lowering DNS TTL in advance, keeping the old host available during propagation, and planning a final synchronization for sites that receive new orders, registrations, comments, or other user-generated data.

The workflow has six stages:

  1. Inventory the current site and choose the destination plan.
  2. Back up files, databases, email, DNS records, and configuration.
  3. Build and test a staging copy on the new host.
  4. Prepare DNS and complete a final content synchronization.
  5. Cut over, verify the live site, and monitor both hosts.
  6. Keep a rollback path until the migration is confirmed.

For a broader performance review after the move, use a consistent test method rather than relying only on how the site feels in one browser session. The web hosting performance test guide explains which response-time, speed, and uptime signals to compare.

What to track

1. Build an inventory before buying or configuring the new host

Record every component that must work after the cutover:

  • Domain names, subdomains, parked domains, and redirects.
  • Website files, uploads, themes, plugins, scheduled tasks, and deployment scripts.
  • Database names, users, versions, character sets, and connection settings.
  • PHP, Node.js, Python, Ruby, or other runtime versions used by the application.
  • Email accounts, forwarding rules, mailboxes, and transactional email services.
  • DNS records for the website, mail, verification services, APIs, and CDNs.
  • SSL certificates, private keys, environment variables, cron jobs, webhooks, and external integrations.

Check the new provider’s documented software versions, storage, database support, bandwidth or transfer limits, import tools, backup options, and access method. Do not assume that a one-click migration tool copies email, DNS, cron jobs, or third-party configuration. Confirm each item explicitly.

2. Create and verify backups

Make at least one complete backup before changing anything. Keep an independent copy outside the current hosting account. A useful backup set includes the document root, uploads, database export, configuration files, DNS zone information, and a record of current PHP or application settings.

Test the backup by opening the archive and, where possible, restoring it to a temporary location. A backup that was never checked may not be usable during an emergency. Also note the exact time of the backup; this becomes important if you need to compare the final synchronization with the original site.

3. Lower DNS TTL and prepare the destination

Before the planned cutover, lower the TTL for the relevant DNS records to a short, practical value supported by your DNS provider. A commonly used planning range is several minutes to around an hour, but the right value depends on the provider, record type, and how much advance notice you have. Lowering TTL does not force every resolver to forget an old answer immediately, so keep the old host online.

Create the site on the new host and copy the files and database. Use a temporary staging URL, hosts-file override, provider preview URL, or another private testing method. Avoid indexing the staging copy: restrict access and prevent search engines from treating it as a public duplicate.

4. Test the staging copy like a visitor and administrator

Check the home page, key landing pages, forms, authentication, search, uploads, payments or checkout where relevant, redirects, media, and any API integrations. Confirm that the application can write to required directories and that scheduled jobs run with the intended frequency. Review logs for PHP errors, database connection failures, missing files, permission errors, and blocked requests.

For WordPress and similar applications, clear or rebuild caches only after confirming the site works without them. Verify the site URL, HTTPS behavior, permalink rules, administrator login, and background tasks. For stores or other frequently changing sites, identify which data must be synchronized immediately before DNS changes.

Copyable pre-migration checklist

[ ] Inventory domains, files, databases, email, DNS, jobs, and integrations
[ ] Confirm destination runtime, database, storage, transfer, and import limits
[ ] Export and independently store files, databases, DNS records, and configuration
[ ] Verify the backup can be opened or restored
[ ] Create the site and staging access on the new host
[ ] Copy files and database; test pages, forms, logins, email, and integrations
[ ] Lower relevant DNS TTL and record the date and previous values
[ ] Freeze deployments and announce the cutover window
[ ] Plan a final database or content synchronization
[ ] Confirm support contacts and rollback access

Cadence and checkpoints

Cutover day workflow

  1. Freeze changes. Pause deployments and tell contributors not to publish content during the final synchronization.
  2. Capture the final state. Take a fresh database export and copy files that changed since the staging build. For a busy application, use the host’s documented migration or replication method if available.
  3. Apply the final changes. Import the latest database and confirm that the destination has the correct configuration, credentials, permissions, and SSL setup.
  4. Perform smoke tests. Test the homepage, representative content, login, forms, checkout or transactions, uploads, redirects, and critical API connections on the destination.
  5. Change DNS. Update the relevant A, AAAA, CNAME, or provider-specific record. Change only what is necessary; do not overwrite unrelated mail or verification records.
  6. Watch both environments. Check DNS responses from multiple networks and monitor application logs, uptime, error rates, email delivery, and important user journeys.

Keep the old hosting account active during the normal DNS transition period and longer if the site has complex caching or international traffic. Do not cancel it immediately after seeing the new IP address from one connection.

Provider comparison and cutover template

Current host: ____________________   New host: ____________________
Migration date/time (UTC): ____________________
DNS provider: ____________________
Records changing: A / AAAA / CNAME / other: ____________________
Previous TTL: __________   New TTL: __________   Lowered on: __________
Staging URL or test method: ____________________
Destination PHP/runtime version: ____________________
Destination database version: ____________________
Storage and transfer limits confirmed on: __________
Import or migration limit confirmed on: __________
Final backup timestamp: __________
Final sync completed: yes / no
Verification: pages [ ] forms [ ] login [ ] checkout [ ] email [ ] SSL [ ] redirects [ ] logs [ ]
Support contact and ticket number: ____________________
Rollback decision time: ____________________

Recheck this template whenever the provider changes its control panel, migration API, supported runtime versions, import limits, or account policies. Screenshots and step names are especially likely to become inaccurate after dashboard changes.

How to interpret changes

A migration is not complete merely because DNS resolves to the new server. Compare the destination against a baseline from the old host. Look for broken redirects, slower server response, missing media, failed background jobs, database warnings, certificate problems, and changes in email delivery. A small change in page speed may be caused by caching or test location; repeated errors across several tests deserve investigation.

Separate DNS propagation from application faults. If some networks still reach the old host while others reach the new one, that may be expected during transition. If all networks reach the new host but forms fail, logs show database errors, or users cannot authenticate, the issue is more likely in the application or destination configuration.

Check uptime and service commitments separately from observed availability. A hosting SLA may define exclusions, measurement methods, and credits that do not match your own monitoring. Review the web hosting SLA guide before treating an uptime promise as a complete risk assessment.

If the site becomes unavailable, use the website outage response checklist to distinguish a DNS issue, host outage, certificate error, application failure, or resource limit.

Rollback checklist

[ ] Define rollback triggers before cutover: failed checkout, data loss, severe errors, or unavailable admin
[ ] Keep the old host online and preserve its files and database
[ ] Record the previous DNS values and TTL
[ ] Stop writes or capture a final export before switching back
[ ] Restore the previous A, AAAA, or CNAME records if rollback is required
[ ] Confirm DNS responses and test the old environment
[ ] Reconcile new orders, comments, accounts, or other data created during cutover
[ ] Document the failure, preserve logs, and schedule a new migration attempt

Rollback is safest when it is a planned decision with a named owner and a clear deadline. Switching DNS back without reconciling new data can create duplicate or lost transactions, so involve the application owner before restoring the old destination.

When to revisit

Use this article as a migration tracker, not a one-time document. Review the checklist quarterly for major hosting providers and before any planned move. Refresh it immediately after a provider changes its control panel, dashboard workflow, migration API, supported PHP or database versions, bandwidth or import limits, backup behavior, or DNS instructions. Recheck support links, contact methods, and pricing before major hosting-buying seasons or renewal decisions.

At minimum, refresh recommended TTL guidance and provider-specific requirements annually. Re-test the migration path when the site changes architecture, adds a CDN, introduces a transactional workflow, moves email, or begins using a new runtime. A small personal or brochure site may need a simple file-and-database checklist; a store or application with continuous writes needs a tested synchronization and rollback procedure.

Before your next migration, copy the pre-migration checklist into a project ticket, complete the provider comparison template, assign a cutover owner, and schedule verification at several intervals after DNS changes. Keep the rollback checklist open during the cutover. This preparation turns a stressful hosting change into a reversible, observable deployment.

For related hosting decisions, compare the operational trade-offs in shared hosting versus VPS hosting, review options for small business websites, and calculate renewal costs with the three-year hosting pricing guide.

Related Topics

#site migration#hosting migration#website migration checklist#DNS TTL#staging#rollback plan
W

Webhosting.live Editorial Team

Hosting Guides Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.