How to Move a WordPress Site to a New Host: A Safe Migration Checklist

Overview

A WordPress migration usually involves three separate jobs: moving the site files, moving the database, and directing the domain to the new server. Treating these as distinct steps makes the process easier to control. Your domain can continue pointing to the old host while you prepare and test the new copy.

Before starting, record the current environment. Note the WordPress version, active theme, important plugins, PHP version if visible in your hosting panel, database name, email configuration, scheduled tasks, and any custom DNS records. This information gives you a reference when the site behaves differently after the move.

Also decide whether you are migrating a simple brochure site, a content-heavy publication, an online store, or a membership site. A low-traffic informational site may tolerate a short maintenance window. A store or frequently updated site needs more careful timing because new orders, comments, form submissions, or user changes can occur while the files are being copied.

If you are still comparing providers, review storage, staging access, backups, SSL setup, server access, renewal pricing, and support before choosing new WordPress hosting. The best web hosting for small business comparison can help frame those requirements, while a developer hosting comparison is useful when you need SSH, Git, or more advanced deployment tools.

Checklist by scenario

For every WordPress migration

1. Choose a migration window. Prefer a period when publishing, sales, and form activity are low. Tell anyone who edits the site when content changes should pause.
2. Lower DNS cache time if appropriate. If you control the domain’s DNS, a lower TTL before the move may allow the change to be recognized sooner. DNS behavior varies by resolver, so do not assume every visitor will switch at the same moment.
3. Create a complete backup. Save both the WordPress files and the database. Download a copy outside the current host and confirm that the backup can be opened or restored. Keep the old hosting account active until testing and DNS propagation are complete.
4. Put the new hosting account in place. Create the domain or site container, database, database user, and required PHP settings. Do not change nameservers yet.
5. Copy the files. Transfer the WordPress directory, including wp-content, the active theme, plugins, uploads, and the wp-config.php file. Check hidden files such as .htaccess where applicable.
6. Import the database. Create a database on the new host and import the SQL backup. Confirm that the database user has the required permissions, then update the new wp-config.php values if the database name, username, password, or host has changed.
7. Test before DNS changes. Use the host’s staging address, temporary URL, hosts-file override, or another private preview method. The exact method depends on the provider. Test the front end and the WordPress dashboard before sending public traffic to the new server.
8. Change DNS or nameservers. Update only the records needed for the migration. If email remains with another provider, preserve its MX, SPF, DKIM, and related records. A nameserver change can affect the entire DNS zone, while an A record change may affect only the website.
9. Activate and test SSL. Install or enable the new host’s certificate after the domain resolves to the new server. Test both the non-secure and secure versions, confirm that the site redirects to HTTPS as intended, and look for mixed-content warnings.
10. Run a post-launch test. Check key pages, navigation, search, forms, images, downloadable files, login, comments, analytics, cookie tools, and contact notifications. Record issues rather than making many unrelated changes at once.

For a site with frequent content or transactions

Take an initial backup and copy the site to the new host before the final migration window. Then place the old site into maintenance mode or temporarily pause publishing and transactions, depending on the site’s needs. Take a final database backup immediately before the DNS change and import that newer database to the destination.

This two-stage approach reduces the gap between the first copy and the final copy. It is especially useful when orders, customer accounts, bookings, comments, or form submissions must not be missed. Confirm with the site’s operational team how to reconcile any activity that occurs during the transition.

For a domain and hosting move happening together

Moving the website and transferring the domain are separate operations. Prepare the new hosting account first, then migrate the site, and change the domain’s DNS when the destination is ready. If the domain transfer is also required, check registrar lock, authorization requirements, contact details, and DNS management before beginning. The domain transfer checklist covers that part of the process separately.

What to double-check

• URLs and serialized data: If the domain, protocol, or directory has changed, update URLs using a WordPress-aware method. Avoid a basic database-wide text replacement that could damage serialized settings.
• Permalinks: In the WordPress dashboard, visit the Permalinks screen and save the existing structure. This can refresh rewrite rules, but it does not replace a proper server configuration.
• Redirects: Test old post URLs, category pages, attachment links, and any deliberate redirects. Preserve useful redirects when changing domains, directories, or URL structures.
• DNS records: Check the A, AAAA, CNAME, MX, TXT, SPF, DKIM, and verification records relevant to your setup. Website migration should not accidentally interrupt business email or third-party services.
• File permissions and ownership: Confirm that WordPress can upload media, update settings where appropriate, and write to required directories without granting excessive access.
• Scheduled tasks: Review backups, publishing schedules, WooCommerce tasks, cron jobs, and integrations. A host change may require a new path, command, or scheduling method.
• Performance baseline: Compare representative pages before and after the move. The website speed and hosting performance checklist provides a practical testing framework rather than relying only on a single speed score.
• Search visibility: Confirm that the site is not blocked by a temporary “discourage search engines” setting, that the sitemap is available, and that canonical URLs point to the correct domain.

Common mistakes

Changing DNS before testing the destination is one of the easiest ways to create avoidable downtime. Keep the old site available until the new copy has passed a private review.

Backing up only the files leaves out posts, pages, settings, users, orders, and other database content. A usable WordPress backup requires both components.

Forgetting email records can make a successful website move look like a business outage. Document the existing mail setup before changing nameservers.

Using an unreliable temporary URL can produce misleading results. Some plugins, security rules, cookies, and HTTPS settings depend on the real domain. Test privately where possible, then perform a second review after DNS resolves publicly.

Deleting the old hosting account too soon removes your easiest rollback option. Keep the old environment, backups, and DNS notes until you have confirmed site behavior, email, forms, and scheduled tasks over an appropriate observation period.

Ignoring renewal and resource limits can create a later problem even if the migration succeeds. Compare the new plan’s long-term cost, backup policy, storage, database limits, and traffic allowances rather than evaluating only an introductory offer. Our guide to hosting renewal pricing covers the comparison points worth recording.

When to revisit

Use this checklist before every host change, major domain change, or redesign that alters URLs. Revisit it before seasonal campaigns, product launches, or other periods when downtime would be costly. It is also worth reviewing whenever your host changes its control panel, backup workflow, staging tools, PHP options, SSL process, or DNS interface.

After migration, schedule a short follow-up review. Confirm that backups are running on the new host, monitoring and analytics still work, email notifications arrive, and the site remains within its storage and resource limits. Recheck important pages after the next WordPress, theme, or plugin update because migration issues can remain hidden until a later change.

For a practical final pass, print or save this sequence: backup, copy, import, preview, test, document DNS, change DNS, enable SSL, verify redirects, monitor, and retain rollback files. Completing those steps in order turns a stressful hosting move into a controlled website maintenance task.