Website Migration Checklist: Move Hosting Providers Without Losing Traffic or Data
website migrationhosting transferbackupsdowntime preventionDNS managementSSL security

Website Migration Checklist: Move Hosting Providers Without Losing Traffic or Data

VVarious.cloud Editorial Team
2026-11-12
7 min read

Use this step-by-step website migration checklist to move hosts safely while protecting files, databases, DNS, email, SSL, SEO, and uptime.

Moving a website to a new host is safest when treated as a controlled release rather than a one-time file copy. This website migration checklist covers backups, staging, database and file transfers, DNS, email, SSL, redirects, monitoring, and rollback decisions so you can move hosting providers with minimal disruption to traffic, data, and visitors.

Overview

A reliable hosting migration has three goals: preserve the website, preserve its supporting services, and make the change observable. The website itself may include application files, databases, uploaded media, scheduled jobs, environment variables, and server configuration. Supporting services can include DNS, business email, payment callbacks, APIs, analytics, CDN settings, and SSL certificates.

Before starting, document the current environment. Record the domain names, DNS provider, hosting account, runtime versions, database engine and version, web server settings, cron jobs, SSL configuration, email records, and any external integrations. This inventory gives you a comparison point after the move and helps expose dependencies that are easy to overlook.

Choose a migration window only after you have tested the new environment. For many sites, the safest approach is to build and verify the new hosting account while the old site remains live. DNS is changed near the end, after the target website has passed functional checks. This approach can reduce downtime, but it does not remove the need for a rollback plan.

If you are also transferring the domain between registrars, treat that as a separate workstream. A domain transfer can involve ownership verification, transfer locks, authorization codes, and timing outside the hosting move itself. Keep the website migration and domain transfer separately documented where possible. See the domain transfer checklist if both changes are planned together.

What to track

1. Backups and recovery

Create at least one complete backup before changing production settings. For a database-driven site, this normally means a database export plus all application files and user-uploaded content. Preserve a copy outside both hosting accounts, label it with the date and environment, and confirm that the archive can be opened. A backup that has never been tested is only an assumption.

Keep the old hosting account available until the new site has been verified and the agreed rollback period has passed. Do not cancel the old service immediately after DNS changes; it may still contain recent uploads, orders, form submissions, or email-related data.

2. Staging and configuration

Build a staging copy on the new host and compare its runtime requirements with the production site. Check the supported PHP, Node.js, Python, database, or other application versions before changing versions. Copy environment variables and configuration carefully, but remove secrets from tickets, screenshots, and shared documents.

Prevent search engines from indexing a staging site. Use access controls or another suitable restriction, and make sure staging does not send real customer emails, process live payments, or write to production services unless that behavior is deliberately tested.

3. Files, database, and application behavior

Transfer the site files, import the database, and verify file ownership and permissions on the destination. Check writable directories, media uploads, cache paths, temporary directories, and symbolic links. For larger or frequently updated sites, schedule a final database and upload synchronization shortly before the DNS cutover.

Test representative pages rather than only the homepage: login and logout, search, contact forms, checkout or subscription flows, file downloads, image delivery, administrative actions, and any API connection. Confirm that scheduled tasks run and that logs are being written where expected.

4. DNS, email, and SSL

List every DNS record before migration, including A, AAAA, CNAME, MX, TXT, and verification records. Lowering the relevant DNS record time to live before the change may help some resolvers refresh sooner, but it does not guarantee instant propagation. Keep email records unchanged unless email is intentionally moving.

Test business email separately. Confirm that MX records, SPF, DKIM, and DMARC records remain present and correct after the DNS change. A website can appear healthy while email delivery is failing. The custom email setup guide provides a separate review path for these records.

Issue or install the SSL certificate on the new host before making the site public. Test both the preferred hostname and its alternate form, such as the www and non-www versions, and confirm that HTTP redirects to HTTPS. If certificates are automated, verify that renewal has been configured rather than assuming the initial issuance covers future renewals. For troubleshooting, use the SSL certificate checklist.

5. SEO and redirects

Hosting changes should not alter URLs without a reason. Crawl or export the current URL set, then compare important pages, canonical tags, robots directives, XML sitemaps, metadata, and structured data on the new host. If URLs must change, create one-to-one permanent redirects and update internal links. Avoid sending many unrelated URLs to the homepage; preserve the closest useful destination instead.

Keep analytics, consent tools, search verification, and monitoring code in place. After launch, inspect crawl errors and indexed pages rather than relying only on a successful homepage test.

Cadence and checkpoints

Use this runbook in five checkpoints:

  1. Preparation: inventory the environment, select the target plan, confirm compatibility, record DNS and email dependencies, and define success criteria.
  2. Backup: export the database, copy files, preserve an external recovery copy, and test restoration of a representative backup.
  3. Staging: deploy the site to the new host, configure the runtime, install SSL, test forms and integrations, and prevent indexing.
  4. Cutover: freeze or communicate changes if needed, perform the final synchronization, update DNS, and record the exact time of the change.
  5. Verification: test the public site, email, redirects, certificates, logs, jobs, analytics, and monitoring from more than one network where practical.

For the first day, monitor uptime, response errors, resource usage, database connections, application logs, form submissions, and transaction completion. Continue checking during the first several days because some issues appear only when scheduled jobs run or users access less common paths.

How to interpret changes

A DNS checker showing the new address does not prove that every visitor is reaching the new site. Compare DNS results with application logs, request timestamps, and real user tests. During propagation, different resolvers may temporarily return different answers.

A small change in response time may be acceptable if page behavior and error rates remain stable, but a rise in server errors, failed forms, slow database queries, or abandoned transactions requires investigation. Separate infrastructure problems from application problems: check host metrics and logs first, then review recent code, configuration, plugins, and database changes.

If critical data is missing, email is disrupted, payments fail, or errors cannot be contained, use the rollback decision defined before launch. Point DNS back only when the old site still has the required data and is safe to serve. Record what happened, preserve logs, and synchronize any data created during the incident before attempting another cutover.

When to revisit

Review this checklist before every hosting change, major runtime upgrade, domain move, or staging-to-production release. Perform a lighter migration audit monthly or quarterly, depending on how frequently the site changes. At minimum, confirm that backups restore, certificates renew, monitoring alerts work, DNS ownership is documented, and the current host still supports the application versions you rely on.

Revisit the runbook when the hosting control panel changes, a backup method is replaced, email providers change, a CDN is introduced, or the site adds payments, user accounts, APIs, or other stateful features. Editors and administrators should also refresh the procedure whenever supported runtime versions, SSL issuance steps, or search-engine guidance materially changes.

For a practical sign-off, have the owner confirm: backup available; staging tested; DNS and email records documented; SSL active; redirects and key URLs verified; monitoring enabled; and rollback conditions understood. Keep that sign-off with the migration record, along with timestamps, test results, and the person responsible for each decision. A hosting move is complete only when the site works for users, its data is recoverable, and the team knows what to do if the results change after launch.

Related Topics

#website migration#hosting transfer#backups#downtime prevention#DNS management#SSL security
V

Various.cloud Editorial Team

Technical 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.