Moving a WordPress website to new hosting does not have to mean downtime, broken links, missing files, or lost search visibility. This reusable migration checklist explains how to inventory the current site, create and verify backups, copy files and the database, test the new environment, plan the DNS cutover, protect email, and complete post-migration SEO checks.
Overview
A WordPress hosting migration usually involves four separate systems: the website files, the WordPress database, the domain’s DNS records, and any related services such as email, analytics, forms, backups, and SSL. Treating the move as a staged project is safer than changing everything at once.
The goal is not simply to make the homepage load on a new server. A successful migration should preserve the site’s URLs, content, media, metadata, user accounts, settings, tracking, forms, and search-engine signals. Before choosing a new provider, compare storage, performance resources, security features, support, backups, and control-panel access. The web hosting comparison checklist can help organize that decision.
For most sites, the lowest-risk sequence is:
- Inventory the existing installation and connected services.
- Prepare the new hosting account without changing DNS.
- Create and verify a complete backup.
- Copy the WordPress files and database.
- Test the new site using a temporary address or hosts-file method.
- Lower DNS timing in advance if appropriate, then make the cutover.
- Monitor the live site and complete SEO, security, email, and backup checks.
Exact control-panel labels vary between hosts. The underlying tasks remain similar whether the migration uses a hosting-panel tool, a WordPress migration plugin, or a manual file and database transfer.
Checklist by scenario
Before any migration
- Record the current site: Save the WordPress version, active theme, plugins, PHP version, database type and version if available, media directory size, and known customizations.
- List important URLs: Export or record the XML sitemap, key landing pages, category pages, attachment URLs if they matter, and any redirects. Confirm the site uses the intended HTTPS and www or non-www format.
- Inventory DNS: Document A, AAAA, CNAME, MX, TXT, SPF, DKIM, DMARC, verification, subdomain, and nameserver records. Use the DNS records guide if you need to identify what each record does.
- Check domain control: Confirm that you can access the registrar and DNS provider. A hosting move does not necessarily require a domain transfer.
- Freeze risky changes: Avoid publishing major content, changing themes, or updating complex plugins during the copy and cutover window.
- Check access: Keep administrator credentials, hosting-panel access, SFTP or FTP details, database credentials, and a way to contact the new host available.
Backup and transfer
- Create two backup types: Make a full hosting backup if available, plus a separate WordPress backup containing both the database and
wp-content. Store at least one copy away from the old host. - Verify the backup: Check that the archive opens, the database file exists, uploads are present, and the backup date is recent. A backup that has never been tested should not be treated as a recovery plan; use the backup and restore plan for a repeatable test process.
- Prepare the destination: Create the site, database, database user, SFTP account, PHP version, SSL setup, staging or temporary URL, and required email settings on the new host.
- Review compatibility: Match the current PHP and database environment first when practical. After the site is stable, plan PHP, WordPress, theme, and plugin updates separately. Do not combine an uncertain platform upgrade with the migration unless you have a tested rollback.
- Copy files: Transfer WordPress core files,
wp-content, the configuration file, custom server rules, and any files used by security, caching, or verification tools. Exclude temporary caches when the migration method recommends doing so. - Import the database: Create the destination database and import the SQL backup. Update the destination configuration with the correct database name, username, password, and host.
- Check URLs carefully: If the temporary address differs from the live domain, use a migration method that safely handles serialized WordPress data. Avoid a simple unqualified search-and-replace that can corrupt serialized values.
Moving with a migration plugin
A migration plugin can simplify packaging and importing, especially for owners who do not use command-line tools. Confirm that the plugin supports the source and destination environments, check package size limits, and follow its restore instructions. Keep the original site online until the imported copy has been tested. If the plugin reports skipped files, database errors, or storage limits, resolve those issues before changing DNS rather than assuming the migration is complete.
Moving manually
A manual migration gives more control. Export the database, transfer the files over SFTP or another secure method, create the database on the new host, import the SQL file, update configuration values, and test rewrite rules. Manual work is useful for large or customized sites, but it requires a clear rollback plan and careful handling of credentials.
DNS cutover and low-downtime moves
- Keep the old hosting account active during testing and for a reasonable observation period after the switch.
- If your DNS provider allows it, reduce the relevant DNS record TTL before the planned cutover. This may help resolvers refresh sooner, but it cannot control every cached result.
- Put the site into maintenance mode only for the shortest necessary period, if needed. For sites receiving orders, registrations, comments, or form submissions, pause or record those transactions so they are not split between servers.
- Update the A or AAAA record, or change nameservers only when you understand which DNS records will move with them.
- Do not change MX records casually. Website hosting and email hosting may be separate services. Confirm mail delivery before and after the DNS change.
For a domain-to-hosting refresher, see how to connect a domain to web hosting.
What to double-check
Technical and content checks
- Open the homepage, several posts, pages, categories, search results, author pages, and a sample of older content.
- Test images, downloadable files, embedded media, menus, widgets, comments, forms, login, password reset, and ecommerce or membership functions where relevant.
- Confirm permalink settings and rewrite rules. A saved permalink setting can refresh rewrite configuration, but review server-specific rules rather than changing them blindly.
- Check that the live site points to the correct database and is not still using a temporary URL.
- Confirm file permissions, scheduled tasks, caching, object caching, and cron behavior where the site depends on them.
- Verify that the new server has a valid SSL certificate and that HTTP requests redirect to the intended HTTPS version. Use the SSL certificate troubleshooting guide for certificate warnings.
SEO and measurement checks
- Compare a sample of old and new URLs. The path, protocol, hostname, trailing-slash preference, and important query behavior should be intentional.
- Check titles, meta descriptions, canonical tags, robots directives, XML sitemaps, structured data, and pagination where used.
- Make sure the production site is not blocked by a staging “noindex” setting or robots rule.
- Test analytics, tag management, consent tools, Search Console verification, advertising pixels, and conversion tracking.
- Review server logs or crawl reports for spikes in 404, 500, redirect-chain, or timeout responses.
- Use one-to-one 301 redirects only when URLs genuinely change. Do not redirect every missing page to the homepage; restore the original URL or provide the closest relevant destination.
Post-cutover sign-off
Record the migration date, new host, DNS change, tested URLs, outstanding issues, backup location, and rollback decision. A simple sign-off can state: “Homepage, representative content, media, forms, login, HTTPS, redirects, analytics, sitemap, robots rules, email, backups, and uptime checks verified.” Keep the old site available until this list is complete.
Common mistakes
- Changing DNS before testing: This turns ordinary migration errors into a live outage. Test the destination first.
- Relying on one backup: A failed archive or incomplete database can leave no safe rollback. Keep independent copies and verify them.
- Forgetting email: Replacing nameservers without copying MX and authentication records can interrupt business mail.
- Updating everything at once: Migrating, changing PHP, replacing a theme, and updating plugins makes the cause of a failure difficult to identify.
- Leaving staging controls active: A copied site may retain password protection, noindex directives, temporary URLs, or development analytics.
- Using an unsafe URL replacement: Serialized WordPress data can be damaged by tools that do not understand its structure.
- Removing the old host too soon: DNS caches, missed files, and delayed troubleshooting are easier to manage when rollback remains possible.
- Ignoring performance differences: Check real page loads, resource limits, caching, and error logs after launch. A migration is not complete merely because the homepage opens.
When to revisit
Use this checklist before every WordPress hosting migration, domain or DNS change, major seasonal campaign, or redesign that changes URLs. Revisit it after the new host changes its control panel, PHP options, backup process, SSL workflow, or staging tools. WordPress, themes, plugins, and migration utilities also change over time, so confirm compatibility before repeating a familiar process.
For practical follow-up, schedule checks at the end of the cutover, the next day, and after the first full backup on the new host. Review uptime, forms, email, analytics, Search Console coverage, redirects, error logs, and resource usage. Then remove the old hosting account only after you have a verified backup, a documented rollback decision, and confidence that the new WordPress environment is stable. Ongoing monthly checks can be added to the WordPress maintenance checklist.