Moving a website to a new host does not have to mean broken pages, missing files, interrupted email, or lost search visibility. This reusable website migration checklist walks through planning, backups, staging, DNS, SSL, redirects, testing, launch, and rollback so you can move deliberately and verify each important dependency.
Overview
A hosting migration changes where your website files, database, and server configuration live. It may also change PHP or runtime versions, database behavior, caching, firewall rules, mail settings, and the IP address returned by DNS. The safest approach is to separate the work into preparation, copying, testing, DNS cutover, and post-launch verification.
This guide assumes that your domain name will remain the same while the website moves to a different hosting account. If you are also changing the domain, redesigning the site, or changing URL structures, treat the project as a broader SEO migration. Keep a tested backup and do not cancel the old hosting account until the new site has passed its checks and the rollback window has ended.
Before you begin, record the current hosting provider, domain registrar, DNS host, CMS version, runtime version, database type, SSL setup, email provider, analytics tools, and third-party integrations. The website migration plan can complement this checklist when you need a more detailed project sequence.
Checklist by scenario
For any website migration
- Assign ownership. Identify who can access the registrar, DNS provider, current host, new host, CMS, database, email platform, analytics, and search-monitoring tools.
- Create a migration inventory. List the production domain, subdomains, URL patterns, databases, upload directories, cron jobs, server-side scripts, forms, APIs, webhooks, redirects, robots.txt rules, XML sitemaps, and scheduled tasks.
- Measure the current site. Save a crawl or URL list, important status codes, page titles, canonical URLs, top landing pages, current redirects, and baseline performance observations. This gives you something to compare after launch.
- Check compatibility. Compare the old and new PHP or application runtime, database engine and version, web server behavior, extensions, file permissions, image-processing support, and storage limits. Resolve incompatibilities before copying the live site.
- Take and test backups. Keep a complete copy of site files, the database, configuration files, DNS records, and email-related records. A backup is more useful when you have confirmed that it can be opened or restored; see this backup and restore workflow for a repeatable test.
- Prepare DNS. Record every relevant A, AAAA, CNAME, MX, TXT, and verification record. Lowering the DNS TTL ahead of the cutover may help changes be recognized sooner, but existing caches can still honor the previous value for a period of time.
- Build a staging copy. Restrict access with authentication or another suitable method. Do not allow a private staging copy to be indexed, and remove those restrictions only after the production site is ready.
- Copy files and database. Transfer the complete application, uploads, themes, plugins, configuration, and database. Update connection details and environment-specific settings without exposing credentials.
- Validate before cutover. Test navigation, search, forms, account flows, checkout or booking functions, media, downloads, integrations, scheduled jobs, and administrative access on the new host.
- Cut over DNS and monitor. Change only the records required for the website unless your email or other services are moving too. Monitor both the old and new environments while DNS changes are being recognized.
For WordPress or another database-backed CMS
- Put the site into a controlled maintenance state, or briefly pause content changes, while taking the final database export.
- Copy the uploads directory and confirm that file names, permissions, and generated media are intact.
- Update the database credentials, site URL settings, environment variables, and any host-specific configuration.
- Verify the selected PHP version and required extensions against the CMS, theme, and plugins. Update or replace incompatible components before launch rather than discovering the problem during cutover.
- Check permalinks, rewrite rules, cache settings, cron behavior, login, forms, and image generation. A WordPress migration is not complete merely because the homepage loads.
For an email or DNS move at the same time
Separate website DNS changes from email changes whenever possible. If mail is staying with its current provider, preserve the existing MX records and email-related TXT records. If mail is moving, document the new provider's MX, SPF, DKIM, and DMARC requirements and test inbound and outbound delivery before closing the old service. The guide to SPF, DKIM, and DMARC setup is useful for this part of the inventory.
What to double-check
Use a written verification table instead of relying on a quick visual review. Include representative URLs from every important template and directory:
| Area | Check | Expected result |
|---|---|---|
| Homepage and navigation | Open desktop and mobile versions; follow primary menus | Pages load over HTTPS without unexpected redirects |
| URL inventory | Test key pages, posts, categories, files, and media | Important URLs return the intended status and content |
| Redirects | Compare the old redirect list with the new server rules | Legacy URLs resolve to the correct relevant destinations |
| SEO signals | Inspect canonical tags, robots.txt, sitemap, titles, and metadata | Production directives are present and staging blocks are gone |
| SSL | Test the certificate, HTTPS redirect, mixed content, and asset URLs | No certificate warning or insecure critical asset remains |
| Forms and transactions | Submit contact, login, checkout, booking, or download flows | Submission succeeds and notifications reach the intended inbox |
| Send and receive test messages from more than one mailbox | Website mail and normal domain email continue to work | |
| Monitoring | Review analytics, search tools, uptime checks, and error logs | Tracking is active and new errors are investigated |
Use a DNS propagation checker or query records from different networks, but do not treat one result as proof that every resolver has updated. Keep the previous host available until traffic, forms, email, and logs look stable. For background on nameservers and records, read how to connect a domain to web hosting.
Common mistakes
- Changing nameservers without copying all records. This can remove email, verification, subdomain, or third-party service records. Export or document the complete DNS zone first.
- Forgetting the final database changes. If the site remains editable during migration, a database export taken too early can overwrite new orders, comments, accounts, or form submissions.
- Testing only the homepage. Broken uploads, search, checkout, APIs, redirects, and administrator functions often appear on deeper paths.
- Leaving staging controls in production. Remove password protection, temporary noindex directives, test banners, and development credentials only after confirming the live environment.
- Replacing every redirect with a homepage redirect. Map old URLs to the closest equivalent destination. Preserve existing valid paths where possible and document intentional removals.
- Canceling the old host immediately. DNS changes are not a signal that every dependency has been verified. Retain a rollback option until the site has been monitored through normal traffic and key workflows.
- Ignoring server logs and resource limits. A site can appear functional while requests fail because of memory limits, timeouts, permissions, missing extensions, or scheduled-job errors.
When to revisit
Revisit this checklist before every host change, major redesign, domain change, platform upgrade, or seasonal traffic period. It is also useful after a migration when auditing redirects, indexing, forms, email, and performance. Hosting control panels, CMS export methods, runtime support, SSL procedures, DNS recommendations, and search-engine guidance can change, so review the relevant steps before using an old project document.
Go-live sign-off
- Confirm that a current, restorable backup exists.
- Confirm that the new host has passed the compatibility and staging tests.
- Confirm that DNS, SSL, email, analytics, redirects, robots.txt, and sitemap settings are documented.
- Confirm that critical URLs, forms, transactions, integrations, and administrator access work in production.
- Confirm that the old host remains available for rollback and that monitoring owners know what to watch.
- Record the cutover time, DNS changes, test results, open issues, and the date for the final post-migration review.
Once the migration is stable, compare the new site with your saved baseline rather than assuming success from availability alone. This final review turns a hosting move into a controlled website launch and provides a reliable record for the next migration.