Website Migration Checklist + Hosting Comparison: Move to a New Host Without Downtime
site migrationhosting comparisondowntime preventionbackup and restoreWordPress migration

Website Migration Checklist + Hosting Comparison: Move to a New Host Without Downtime

WWebhosts.top Editorial Team
2026-11-11
6 min read

Use this practical website migration checklist to compare hosts, test a new server, cut over DNS safely, and preserve a reliable rollback plan.

Moving a website to a new host does not have to mean downtime or lost data. This reusable website migration checklist covers the audit, backup, staging, DNS cutover, testing, and rollback steps needed to change hosts safely, plus a practical framework for comparing migration support before you choose a plan.

Overview

A successful migration is less about moving files once and more about keeping two working environments available until the new host has been verified. The safest approach is to prepare the destination, copy the site, test it on a temporary address, and only then change the traffic direction.

Start by separating the website from related services. Your domain registration, DNS, website files, database, email, SSL certificate, scheduled tasks, analytics, and third-party integrations may be managed in different places. Moving web hosting does not automatically move email or transfer the domain. If business mail is involved, review your mailboxes, MX records, authentication records, and retention requirements before changing DNS. The business email hosting comparison can help you assess those dependencies.

Plan the move during a period of lower activity, but do not treat timing as a substitute for testing. Keep the old hosting account active until the new site is confirmed and you have passed the period in which delayed DNS requests could still reach the old server.

Checklist by scenario

Before any migration

  • Record the current host, server IP address, DNS provider, registrar, CMS version, PHP or runtime version, database engine, and storage usage.
  • List every domain and subdomain, including staging, API, image, checkout, and redirect domains.
  • Inventory cron jobs, webhooks, payment integrations, CDN settings, firewall rules, analytics, form notifications, and external API keys.
  • Check renewal dates and cancellation terms. Do not cancel the old hosting account before the migration and rollback window is complete.
  • Measure current performance and confirm that uptime monitoring is active. A baseline makes it easier to identify a post-migration problem; see this website uptime monitoring guide.
  • Lower DNS record TTL in advance if your DNS provider permits it. A lower TTL may help changes be recognized sooner, but it cannot eliminate resolver caching.

Backup and export

  • Create a complete backup of website files, databases, media, configuration files, and deployment scripts.
  • Download a copy outside the current host and confirm that the archive can be opened.
  • Export databases separately when possible, and record their names, users, character sets, and connection details.
  • Back up email only if email is part of the move, using a method appropriate to the mailbox system.
  • Document the backup timestamp and identify which content may change after the backup, such as orders, comments, registrations, or support tickets.

Destination setup and staging

  • Create the destination account with matching or compatible runtime versions and enough storage, memory, CPU, and database capacity.
  • Install the CMS, upload the files, import the database, and update configuration values for the new database and file paths.
  • Use a temporary URL, hosts-file override, staging domain, or password-protected preview to test the site before DNS changes.
  • Check login, navigation, search, forms, media, redirects, structured data, checkout flows, and transactional email.
  • For WordPress, review plugins, themes, uploads, permalink settings, scheduled actions, caching, and the site URL. A separate WordPress staging guide covers safer testing practices.

Cutover and rollback

  • Choose a cutover window and freeze nonessential content changes.
  • Take a final database backup immediately before switching traffic, especially for stores and membership sites.
  • Update the relevant A, AAAA, CNAME, or nameserver records according to the new host’s instructions. Keep email records unchanged unless email is also moving.
  • Confirm SSL, canonical URLs, redirects, robots.txt, sitemap access, and application logs on the new host.
  • Keep the old site available as a rollback target. Write down the previous DNS values and the exact steps for restoring them.
  • Monitor both hosts, error logs, uptime, forms, orders, and traffic after the change.

Migration feature comparison template

Provider features and limits change by plan, CMS, site size, and support channel. Complete this table from each provider’s current plan documentation or a written pre-sales response rather than assuming that “free migration” covers every site.

Item to compareProvider AProvider BWhat to verify
Migration costConfirmConfirmWhether the offer applies to your plan, CMS, and site size
Automated importConfirmConfirmSupported CMSs, databases, domains, and retry options
Manual migration helpConfirmConfirmFiles, databases, email, DNS, and configuration included
Staging environmentConfirmConfirmCreation, cloning, password protection, and production push options
Backups and retentionConfirmConfirmFrequency, retention, off-site copies, and restoration process
Resource limitsConfirmConfirmStorage, bandwidth, CPU, memory, inodes, and database limits
Support channelsConfirmConfirmChat, ticket, phone, escalation, and coverage hours
Typical timeframeAskAskExpected handling time and dependencies that may delay completion

For a broader hosting comparison, consider whether shared, VPS, or cloud infrastructure matches the site’s traffic and operational requirements. The guide to shared, VPS, and cloud hosting provides a useful starting point.

What to double-check

DNS is a common source of confusing migration results. Use a DNS propagation checker and test from more than one network, but remember that different resolvers may retain old answers for different periods. Confirm that the root domain, www version, subdomains, mail records, SPF, DKIM, DMARC, and verification records all point where intended. More DNS guidance is available in how to connect a domain to hosting.

Check application behavior, not just whether the homepage loads. Submit forms, place a test order if appropriate, inspect logged-in pages, test image uploads, confirm scheduled tasks, and review error logs. Compare page titles, canonicals, redirects, sitemap URLs, and indexability settings so the move does not create an avoidable SEO problem.

Review security settings on the new host: SSL coverage, administrator access, firewall rules, file permissions, malware scanning, automatic updates, and backup restoration. A backup that cannot be restored is not a complete recovery plan.

Common mistakes

  • Changing nameservers too early: Test the destination first and document the old DNS configuration.
  • Forgetting changing data: A static brochure site is easier to copy than a store or community site. Use a final database sync or maintenance window when necessary.
  • Moving the domain instead of the website: A domain transfer and a hosting migration are separate processes. See the domain transfer guide if the registrar is changing too.
  • Assuming free migration means complete migration: Ask specifically about email, large databases, custom applications, multisite installs, and unsupported plugins.
  • Canceling the old host immediately: Preserve the old environment until monitoring shows stable traffic and all critical functions work.
  • Ignoring renewal economics: Compare the new plan’s renewal cost, add-ons, backups, email, and resource limits rather than judging only the introductory offer. Review domain renewal costs separately.

When to revisit

Use this checklist whenever you plan a host change, outgrow a shared plan, move from one CMS to another, or compare renewal costs with alternatives. Recheck provider migration features before signing up because included migrations, supported platforms, size limits, backup retention, staging tools, and support procedures can change with a plan update.

It is also worth revisiting after a failed cutover, a security incident, a major application upgrade, or a seasonal traffic cycle. At the start of each migration, refresh your inventory, create a new external backup, confirm the rollback DNS values, and record the destination host’s current limits and support route. Then schedule the move, test the staging copy, and proceed only when the checklist is complete.

Related Topics

#site migration#hosting comparison#downtime prevention#backup and restore#WordPress migration
W

Webhosts.top Editorial Team

Hosting and Domains 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.