A WordPress website migration is easier to control when you treat it as a sequence of checks instead of a single “move the site” task. Before changing hosting or DNS, make sure you have a usable backup, know which services depend on the domain, record the current WordPress setup, and decide exactly what will and will not change during the move. This WordPress website migration checklist gives you a practical order for doing that work and checking the site afterward.
The short version: what to check before a WordPress migration
- Create and verify a complete backup. You need a recovery copy of the database, uploads, themes, plugins, and important configuration.
- Record the current setup. Note the WordPress version, PHP version, active theme, active plugins, important forms, redirects, analytics tools, and any special integrations.
- Identify everything connected to the domain. Website hosting, DNS, SSL, email, subdomains, verification records, and third-party services may not all move together.
- Reduce unnecessary changes. Avoid combining a hosting migration with a redesign, major plugin replacement, and large content rewrite unless there is a specific reason.
- Test the destination before switching traffic. Confirm the site loads, the admin area works, forms can be tested, and important pages render correctly.
- Switch DNS carefully. Change only the records that actually need to change, and protect email-related records.
- Run a post-migration check. Test the live site on desktop and mobile, confirm SSL, forms, navigation, redirects, analytics, and WordPress administration.
1. Make a backup you can actually restore
A backup is your recovery path if the migration fails, the database imports incorrectly, a plugin behaves differently on the new server, or an important file is missed. Do not assume that “backup completed” means the backup is useful. Confirm what is included, where the backup is stored, and how you would restore it.
If you are unsure what a usable recovery check looks like, start with how to test a WordPress backup before you need it. A migration is not the best time to discover that the only backup is incomplete or inaccessible.
At minimum, confirm the backup includes
- The WordPress database.
- The wp-content/uploads media library.
- The active theme and any child theme.
- Installed plugins.
- Important configuration files when applicable.
- Any custom code or server-level settings that are not stored in WordPress.
Keep a copy somewhere other than the server you are leaving. If the old account is closed or becomes inaccessible, a backup stored only on that account may not help.
2. Record the site before you move it
A simple inventory makes troubleshooting much faster because it gives you a “before” reference. You do not need a complicated technical report. You need enough information to recognize what changed.
Record these items
- WordPress version.
- PHP version and any important server requirements.
- Active theme and child theme.
- Active plugins.
- Permalink structure.
- Important user roles and administrator access.
- Contact forms and where they send notifications.
- Analytics, Search Console, tag-manager, or verification code connections.
- Redirects that are managed inside WordPress or a plugin.
- Scheduled tasks, ecommerce functions, membership tools, or other features that depend on the server.
Take a few screenshots of important pages and the WordPress dashboard. They can help you spot layout or configuration differences after the move.
3. Separate the website move from DNS and email
One of the easiest migration mistakes is assuming the domain, DNS, website hosting, and email are the same service. They can be handled by different companies and can change independently.
Before editing DNS, identify which records control the website and which records support email or other services. The website commonly depends on A, AAAA, or CNAME records. Email can depend on MX records plus TXT or CNAME records for SPF, DKIM, verification, and other settings.
Do not copy only the website record and discard everything else. If the domain already has working email, preserve the records that support it unless the email service is intentionally changing too.
Questions to answer before the DNS switch
- Where is the domain registered?
- Who currently hosts DNS?
- Which record points the main domain to the website?
- Does www use a separate record?
- Where is email hosted?
- Are there important subdomains?
- Are there verification or security records that must stay in place?
4. Review WordPress before the migration
It is useful to know whether WordPress is healthy before moving it, but that does not mean you should update everything five minutes before changing servers. Every additional change creates another possible cause if something stops working.
If updates are needed, use a deliberate process such as the WordPress plugin update checklist. For a migration, the key is to know whether you are moving the existing working site as-is or intentionally changing software at the same time.
Good reasons to delay a nonessential update
- The site is currently stable and the migration is imminent.
- The update changes a major plugin or theme component.
- You cannot test the update separately before the move.
- You would have difficulty identifying whether a problem came from the update or the new hosting environment.
Security-critical fixes are different. If an update addresses an urgent security problem, weigh that risk separately rather than following a blanket “never update before migration” rule.
5. Decide what will change during the move
The safest migration plan keeps the number of simultaneous changes as small as practical. If the goal is only to move hosting, consider preserving the same domain, WordPress version, theme, content, URLs, and plugin configuration through the initial launch.
After the site is stable on the new host, you can make redesign, cleanup, or plugin changes with a clearer baseline.
Changes that deserve their own plan
- Changing the domain name.
- Changing URL structure.
- Moving from one page builder to another.
- Changing ecommerce, membership, or form systems.
- Replacing a large number of plugins.
- Changing email providers.
- Changing important redirects.
6. Test the new copy before switching live traffic
Whenever the hosting setup allows it, test the migrated copy before the public domain points to it. The goal is to catch obvious problems while the old site is still available.
Check these areas on the new server
- Homepage and major service pages.
- Navigation menus.
- Images and downloadable files.
- WordPress login and administrator screens.
- Contact forms.
- Mobile layout.
- Search or filtering features if the site uses them.
- Ecommerce cart, checkout, account, and payment-flow configuration when applicable.
- Redirects and custom 404 behavior.
Temporary URLs can behave differently from the real domain, especially with SSL, cookies, caching, or plugins that store absolute URLs. A temporary test is useful, but the final live-domain test still matters.
7. Switch DNS carefully
When the destination site is ready, change the website-related DNS records according to the new host’s instructions. Avoid deleting unrelated DNS records simply to “start clean.”
DNS changes can take time to be seen consistently because resolvers may cache older information. During that transition, different visitors may temporarily reach different servers. Keeping both the old and new copies working during the transition reduces unnecessary risk.
During the DNS transition
- Keep the old hosting account active until the new site is confirmed.
- Avoid making important content changes on two different copies of the site.
- Confirm SSL works on the new host.
- Check the main domain and www version.
- Confirm email still sends and receives.
8. Run a post-migration website check
Once the domain is reaching the new server, perform a fresh review as a normal visitor and as a WordPress administrator. A migration can look successful while still leaving small problems behind.
A good ongoing maintenance process makes this easier. The website maintenance service overview explains the value of checking updates, backups, forms, navigation, and other customer-facing functions on a predictable schedule.
Post-migration checklist
- Confirm HTTPS loads without browser warnings.
- Check that the preferred domain version redirects correctly.
- Test navigation and key internal links.
- Open important pages on desktop and mobile.
- Submit forms and verify notifications arrive.
- Check images, PDFs, and other media.
- Confirm redirects still work.
- Check that analytics and verification tools are still connected.
- Open the WordPress dashboard and save or update a test item if appropriate.
- Review error logs or host diagnostics if the new environment exposes problems.
What should you fix first after a migration?
Prioritize problems by how much they affect access, customers, and recovery.
- Site unavailable or unsafe. Fix DNS, SSL, database, server, or fatal WordPress errors first.
- Business-critical functions. Fix forms, checkout, account access, appointment tools, or other lead and transaction functions next.
- Broken navigation or missing content. Repair important URLs, redirects, images, and page rendering.
- Performance or caching differences. Address slow pages, cache configuration, and environment-specific performance issues after the site is stable.
- Cosmetic details. Small spacing or styling issues can usually wait until the core site is functioning correctly.
If the cause of a migration problem is unclear, a structured WordPress troubleshooting process can help separate hosting, plugin, theme, database, cache, and configuration problems instead of changing several things at once.
When is a DIY migration reasonable?
A do-it-yourself migration can be reasonable for a small, straightforward WordPress site when you have reliable backups, understand where the domain and DNS are managed, know how email is configured, and can test the destination before switching traffic.
Professional help becomes more useful when the site handles ecommerce, memberships, large databases, custom code, frequent orders or form submissions, complex DNS, multiple subdomains, or a domain change. The cost of a mistake is usually higher when the site has more moving parts or cannot tolerate a long interruption.
Frequently asked questions about WordPress migrations
Will a WordPress website migration cause downtime?
Not necessarily. A well-prepared move can reduce interruption by keeping the old site available while the new copy is prepared and by switching DNS only after testing. Some transition risk remains because DNS caching and server differences are outside WordPress itself.
Can a migration hurt SEO?
A hosting-only migration that keeps the same domain and URLs is different from a redesign or domain change. SEO problems are more likely when URLs change, redirects are missing, pages become unavailable, robots settings change, or important content is altered accidentally. Preserve the existing URL structure unless there is a clear reason to change it.
Can changing website hosting break business email?
It can if DNS records for email are changed or removed. Before moving the website, identify the MX and related email records and preserve them unless the email provider is intentionally changing too.
If you are planning a WordPress move and the DNS, backups, plugins, or testing steps are unclear, 651 Web Design can help you organize the migration into a smaller set of verifiable steps before the live switch.
