WordPress migration · Technical and SEO workflow
WordPress Hosting Migration Checklist
Use this checklist to move the complete WordPress system—not only the visible pages. It covers recoverable backups, files, database, email, DNS, SSL, redirects, canonicals, analytics, Search Console, testing, final synchronization, and rollback.
A safe WordPress migration is complete only when the destination serves the same URLs and content over HTTPS, dynamic features work, email and DNS are correct, search-engine directives remain intentional, analytics and conversions fire, a clean backup exists, and the source account is retained long enough for rollback.
Use the checklist with the actual migration method
A provider plugin, full-cPanel transfer, staff-assisted service, or manual migration may complete some items, but the website owner remains responsible for verifying the final site, domain, email, analytics, search visibility, licenses, third-party services, backups, and cancellation timing.
Interactive browser-saved checklist
WordPress Migration Checklist
Completion is stored only in this browser. Print or save a PDF before clearing browser data.
WordPress-specific risks that generic migration lists miss
Serialized data and URL changes
Use a WordPress-aware search-and-replace method when the domain or protocol changes. A plain text replacement can corrupt serialized values.
Caches and generated files
Clear page, object, browser, CDN, and server caches after migration. Rebuild generated CSS, image variants, and optimization files when the site uses them.
Licenses and server binding
Premium themes, plugins, firewalls, SMTP services, backups, and CDNs may bind licenses or API access to a domain, server IP, path, or account.
Scheduled events
WordPress cron, server cron, queue workers, backups, feeds, imports, subscriptions, and ecommerce tasks can stop when cron jobs or external triggers are not recreated.
SEO migration guardrails
| SEO element | Required check | Common migration failure |
|---|---|---|
| URLs and status codes | Keep the same canonical URLs for a same-domain host change; test every redirect and priority template. | 404s, redirect chains, temporary URLs, or changed permalink structures. |
| Indexing directives | Confirm production pages are indexable and temporary/staging copies are not. | Destination remains noindexed or staging becomes indexable. |
| Canonicals | Verify final HTTPS production URLs on every template. | Canonicals point to staging, HTTP, old hostnames, or duplicate variants. |
| Internal links and media | Crawl for broken links, HTTP assets, old paths, and missing images. | Mixed content, missing files, or internal links to temporary domains. |
| Sitemap and robots | Load the final robots file and XML sitemap; compare their URLs with the live site. | Blocked CSS/JS, stale sitemap hosts, missing pages, or redirected sitemap URLs. |
| Structured data | Compare rendered JSON-LD before and after migration. | Plugin conflicts, missing images, wrong URLs, or disabled schema output. |
| Analytics and Search Console | Confirm tags, conversions, ownership, sitemap, and critical URL inspection. | Lost tracking, duplicate tags, missing events, or unmonitored errors. |
Dynamic-site cutover plan
For WooCommerce, memberships, courses, communities, bookings, donations, lead portals, or frequently updated sites, choose a defined write freeze or final synchronization method. Record the last order, user, comment, booking, inventory update, and database export before DNS changes. Test payment callbacks, webhooks, emails, scheduled tasks, and account sessions at the destination.
What to retain after migration
- Original and final backups with dates.
- DNS before-and-after record.
- Migration ticket, scope, quote, and provider correspondence.
- Final crawl and test results.
- Search Console and analytics screenshots for the transition period.
- Cancellation confirmation and final invoice.
- A written rollback and incident note if anything failed.
Frequently asked questions
Should I install WordPress before migrating?
It depends on the method. Some automated tools require a destination WordPress installation or setup flow; full-account or manual transfers may require an empty document root and separately created database. Follow the selected method’s official instructions.
Should I change nameservers before copying the site?
Usually no. Prepare and test the destination first. Change public DNS only after the destination, SSL, email plan, and rollback path are ready.
Do I need to tell Google about a same-domain host change?
There is no change-of-address action for a same-domain host move. Preserve URLs and content, keep the site available, verify the sitemap and canonicals, inspect critical URLs, and monitor crawling, errors, performance, and indexing.
Claim-level official citations
Verify the migration details at the provider source.
These pages support the material policy and workflow claims in this guide. Open the exact source again before starting a transfer because eligibility, pricing, limits, and procedures can change.
Research method and verification record
Files, database, email, DNS, SSL, redirects, canonicals, analytics, Search Console, and post-launch validation
Prepared by Nathan Lackey. Provider-controlled claims were checked against official documentation on August 3, 2026. The page distinguishes sourced policy facts, workflow guidance, editorial cautions, and reader-entered tool results.
Page-specific update history
Updates require a verified migration-policy or editorial change.
- August 4, 2026: Initial guide, original decision tool, official-source records, contextual internal links, and mobile comparison layout published.
- Provider verification: The comparison date and article source records are maintained independently from unrelated site rebuilds.
- Future revisions: Record the previous value, new value, official source, editor, and verification date after a substantive policy, price, scope, or workflow change.
Continue the migration research path
Use the next guide before changing DNS or canceling hosting.
Move through the remaining migration guides in the most useful order: choose the right route, execute the transfer, and confirm whether a switch is actually necessary.
How to Switch Web Hosts Without Downtime
Build the migration sequence and keep the old site available until validation is complete.
Free Website Migration Policies Compared
Match free, conditional, automated, and paid migration routes to the exact website.
When Should You Change Web Hosts?
Decide whether to optimize, upgrade, or switch using documented evidence.