A website migration checklist keeps a hosting move organized from the first backup to the final DNS switch. Moving to a new host involves more than copying files, because databases, email accounts, DNS records, SSL certificates, and application settings must also arrive intact. Without preparation, a move can cause broken pages, missing messages, unexpected downtime, or technical SEO problems.
This guide shows how to prepare your site, transfer its data, test the new server, and switch DNS safely. Whether you run a WordPress site, an online store, or a custom application, these steps help you reduce disruption and confirm everything works before you retire the old hosting account.
Table of Contents
- What Is a Website Migration Checklist, and Why Is It Important?
- Website Migration Checklist: What to Prepare Before Moving
- How to Back Up Your Website Before Moving Hosts
- How to Transfer Website Files and Databases
- How to Migrate Email Accounts and DNS Records
- How to Test Your Website on the New Hosting Server
- How to Switch DNS and Reduce Website Downtime
- How to Protect SEO During a Website Migration
- How to Verify the Migration and Retire Your Old Hosting
- Frequently Asked Questions
- Summary:
What Is a Website Migration Checklist, and Why Is It Important?
Website migration is the process of moving a website from one hosting environment to another. It may involve transferring files and databases, moving email accounts, changing DNS settings, upgrading server resources, or changing the website’s domain or URL structure. A website migration checklist turns that process into clear, verifiable steps.
Following a website migration checklist keeps the website accessible while protecting its data and functionality. It also lets you check application compatibility, SSL configuration, backups, and hosting performance before visitors reach the new server.
Not every migration has the same scope. Moving to a new host while keeping the same domain and URLs is different from changing the domain name or redesigning the site. A hosting-only move mainly involves infrastructure and DNS, while a URL-changing migration also needs careful redirects, canonical URL checks, and extra search engine monitoring.
Website Migration Checklist: What to Prepare Before Moving
Your website migration checklist should start with the current environment. Before you move your website, document it and identify everything that must keep working after the transfer.
Review your existing hosting setup
Record your current hosting provider, control panel, PHP version, database version, installed applications, scheduled tasks, and important server settings. Compare the requirements of your CMS, plugins, themes, and custom code with the new environment.
Choose a compatible hosting plan
Confirm that the new plan has enough storage, memory, processing power, database support, and any required software features. If you run WordPress, review the available HostElevate web hosting plans and compare their features with your site’s actual requirements.
List your website components
Your website migration checklist should include:
- Website files, uploads, images, and downloadable documents
- Databases and application configuration files
- Email accounts, messages, aliases, and forwarders
- Domains, subdomains, DNS records, and SSL certificates
- Scheduled tasks, forms, integrations, and third-party services
- Backups, access details, and recovery procedures
Plan the migration window
Add a migration window to your website migration checklist and choose a time when the change can be monitored and tested. If your site handles frequent orders or user submissions, plan how new data created during the transfer will be synchronized so nothing is lost when traffic switches to the new server.
How to Back Up Your Website Before Moving Hosts
A complete backup is the most important part of any website migration checklist. It gives you a recovery option if the transfer fails or the new environment does not work as expected.
Back up website files
Download or create an archive of the website’s files, including application code, themes, plugins, uploads, and configuration files. For WordPress, this usually means the WordPress installation and its wp-content directory.
Export the database
Create a database backup with your control panel or database tool. WordPress sites commonly use MySQL or MariaDB. Make sure the export matches the website files you are transferring.
Preserve email data
If email is hosted on the current server, check how mailboxes, messages, aliases, forwarders, and filters will be transferred. A website file backup does not necessarily include all email data.
Verify the backups
Confirm that the files exist, the database export is readable, and the backup is stored away from the hosting account you are migrating. Where possible, test a restore in a safe environment, and mark it as complete on your website migration checklist before relying on the backup.
Keep the existing hosting account and its data intact until the new website and email services have been verified against your website migration checklist.
How to Transfer Website Files and Databases
Once your backups are ready, this stage of the website migration checklist is to transfer the website to the new hosting account. The exact process depends on your control panel, CMS, and hosting provider.
Transfer the website files
Use a supported account transfer tool, a full hosting backup, SFTP, or another secure method. Preserve file permissions and directory structure where the application requires them.
Create or import the database
Create the required database and database user on the new server, then import the backup. Update the application’s configuration with the new database name, username, password, and host where necessary.
Update application settings
Some applications store their domain, file paths, or server settings in configuration files or databases. Review these values and change only what the new environment requires. For WordPress, confirm that the site URL and home URL are correct, and avoid an unnecessary search-and-replace across serialized data.
Check file permissions and dependencies
Verify that the application can read its files and write to the required directories. Confirm that the PHP version, extensions, and database compatibility are supported.
If you use WordPress, HostElevate WordPress hosting is a relevant option to compare when you evaluate a hosting environment for WordPress-specific requirements.
How to Migrate Email Accounts and DNS Records
Email deserves its own section in a website migration checklist because website files and email messages are usually stored and managed differently.
Inventory existing email accounts
List every mailbox, alias, forwarder, autoresponder, and important email setting. Confirm whether your old hosting provider manages email or whether a separate service handles it.
Transfer mailboxes and messages
Create the matching mailboxes on the new service and migrate existing messages with a supported transfer method. If the old server keeps receiving mail during the transition, plan a final synchronization to capture messages that arrive after the first copy.
Review DNS records
Record the existing A, AAAA, CNAME, MX, and TXT records your services rely on. The records you need depend on your setup. If email is hosted separately, changing your website’s IP address should not redirect mail to the wrong provider.
Preserve email authentication
Review SPF, DKIM, and DMARC records if your sending infrastructure changes. Make sure the new sending service is authorized and that DKIM signing and DMARC alignment work as expected.
Check domain management
If you need a domain for a new project or want to review domain options, visit HostElevate domain registration. You generally do not need to transfer your domain registration to the new hosting company just to change where the website is hosted.
How to Test Your Website on the New Hosting Server
Do not switch DNS immediately after copying files. First test the new website while the old site remains available. Testing uncovers missing files, database errors, incompatible software, and configuration problems before visitors reach the new server. Use this website migration checklist to cover the main areas:
- Homepage and important pages: Confirm that key pages load correctly and do not return unexpected errors.
- Images and downloads: Verify that media files, documents, and other assets are available.
- Forms and user accounts: Test contact forms, login flows, password resets, and other essential interactions.
- Online transactions: If your website accepts orders or payments, test checkout safely in test mode where available.
- SSL and HTTPS: Confirm that the new environment has a valid certificate and that HTTPS works without warnings or mixed-content issues. HostElevate offers SSL certificates if you need one.
- Application logs: Review web server, PHP, and application logs for errors.
- Performance and compatibility: Check page loading, database operations, scheduled tasks, and integrations.
For a WordPress website, also check the dashboard, plugin functionality, theme layout, permalinks, and caching behavior. Avoid tests that create real orders or send unwanted messages to customers. Only proceed when the important parts of the new site work as expected.
How to Switch DNS and Reduce Website Downtime
Treat the DNS switch as a late item on your website migration checklist. Once the new environment passes testing, point your domain to the new hosting server. This is the stage at which traffic begins moving to the new environment.
Confirm the correct DNS provider
Make changes at the provider that manages your authoritative DNS records. This might be your registrar, hosting provider, or a dedicated DNS service. Editing records in the wrong control panel may not affect public DNS.
Review TTL values
The Time to Live (TTL) determines how long DNS responses may be cached. If you plan to reduce the TTL before a migration, do so well in advance. Lowering it right before the switch does not instantly clear caches that already hold the previous value.
Update the required records
Change the relevant website records to the new server’s values. If you are changing nameservers rather than individual records, confirm that the complete DNS zone is configured at the destination before making the change.
Monitor the transition
DNS resolvers refresh at different times, so some visitors can reach the old server while others reach the new one. Keep both environments available where possible and manage any data created during the transition.
For more background, read our guide tohttps://hostelevate.com/blog/dns-propagation-how-long/ . The key is to verify the authoritative records and test the website from more than one network instead of assuming the change is complete everywhere at once.
How to Protect SEO During a Website Migration
SEO checks belong on every website migration checklist. A hosting-only migration that keeps the same domain, URL structure, content, and indexing settings is generally simpler than one that changes URLs. Even so, server configuration problems can affect crawling, indexing, and user experience, so include these items in your website migration checklist.
Keep URLs consistent when possible
If you are only changing hosting providers, avoid unnecessary changes to page URLs, titles, content, or internal links during the same migration. A stable site structure makes problems easier to identify and resolve.
Check crawling and indexing settings
Review the new site’s robots.txt, meta robots directives, and HTTP headers. Make sure temporary staging restrictions or noindex settings are removed when the production website is ready to be crawled.
Verify canonical URLs and redirects
Check that canonical tags point to the correct preferred URLs. If URLs or the domain are changing, prepare a URL mapping and set up permanent server-side redirects, usually 301 or 308, to the closest matching destination. Avoid redirect chains and redirects to unrelated pages.
Update and inspect the sitemap
Confirm that the XML sitemap lists the correct canonical production URLs. If the URL structure has changed, update the sitemap and internal links to match.
Monitor Google Search Console
After the move, review indexing reports, crawl errors, and search performance. Google notes that crawl activity may fluctuate temporarily after a hosting change, so investigate sustained errors, inaccessible pages, or unexpected indexing changes instead of treating every short-term fluctuation as a problem.
For official guidance, read Google’s documentation on site moves without URL changes. If you are also changing URLs, use Google’s site move with URL changes guide.
How to Verify the Migration and Retire Your Old Hosting
A successful DNS switch does not automatically mean every item on your website migration checklist is complete. Perform a final review before you cancel the previous hosting service.
Confirm website availability
Test the domain, important pages, forms, and critical application functions from different networks or devices. Check that the site resolves to the intended destination and that HTTPS works properly.
Confirm email delivery
Send and receive test messages with the relevant mailboxes. Check MX records, SPF, DKIM, and DMARC where applicable, and confirm that messages sent during the transition have not been missed.
Review backups and monitoring
Create a fresh backup of the new environment. Monitor server logs, application errors, uptime, performance, and traffic, and check that scheduled tasks and automated notifications are running correctly.
Keep the old hosting active temporarily
Add this to your website migration checklist: do not cancel the old account right after changing DNS. Keep it until you have confirmed that the new site is stable, email is working, and any remaining data has been synchronized. The right retention period depends on your site and provider, and no single time fits every migration.
If you prefer help with the process, the HostElevate website migration service states that its team moves website files, databases, and email, tests the new environment, and coordinates the DNS switch. Ask whether the team follows a website migration checklist and confirm the scope for your specific setup before you arrange a migration.
Frequently Asked Questions
How long does a website migration take?
It depends on the site’s size, data volume, email needs, and the testing required before the DNS switch.
Will moving to a new host affect my Google rankings?
A hosting-only move can keep URLs unchanged, but downtime or indexing errors can temporarily affect search performance.
What should a website migration checklist include?
It should cover backups, files, databases, email, DNS, testing, SEO checks, and a final review.
Should I transfer my domain to the new hosting provider?
No, you can usually keep your domain with its current registrar and just update the required DNS records.
When should I cancel my old hosting plan?
Wait until the new website, email, and essential services are verified and all data is synchronized.
Summary:
A reliable website migration checklist starts with preparation, verified backups, and a clear plan for transferring files, databases, email, and DNS settings. Test the new hosting environment before switching traffic, then monitor the website and email while DNS updates reach different resolvers.
To protect search visibility, keep URLs consistent when possible, verify indexing settings, check canonical tags and redirects, and monitor Google Search Console after the move. Keep the old hosting account available until the new environment is stable and every essential service is confirmed. Following this website migration checklist helps you move your website to a new host in a controlled, verifiable way.
