What I check before moving a WordPress website to a new host.

Before copying anything, I confirm access to the current WordPress site, files, database, DNS provider, registrar, destination hosting, SSL controls, email provider, analytics, and any external integration. A migration should not begin with one missing account that can stop the launch.

I record WordPress and PHP versions, active themes and plugins, database size, uploads, scheduled tasks, redirects, forms, user roles, ecommerce or membership data, error logs, storage use, and the important public URLs. I also test the current business journeys so the destination can be compared against a known state.

Changing a website address record should not accidentally replace Google Workspace, Microsoft 365, or another email provider. I document A, AAAA, CNAME, MX, TXT, SPF, DKIM, DMARC, verification, and subdomain records before touching DNS, then change only what the migration requires.

The destination receives an independent copy of files and the database. Search indexing is blocked, caches are controlled, and production email, payment, webhooks, or customer notifications are prevented from firing during tests. The original site remains available until the destination passes review.

I check pages, menus, media, forms, login and password reset, account routes, ecommerce, scheduled jobs, API callbacks, redirects, sitemap output, canonical tags, analytics, mobile layout, and administrative editing. Testing uses safe recipients and avoids fake activity that could confuse customers.

For a changing website, the first copy is not the final copy. I define whether content, orders, users, inquiries, stock, bookings, or form entries can change during the move. The launch plan includes a final export, temporary freeze, selective reconciliation, or another documented method appropriate to the workload.

At launch I confirm the destination backup, lower DNS risk where possible, complete the final sync, change the required records, issue or verify SSL, clear caches, and repeat the priority tests from external networks. The old environment is retained until the new path is stable and the rollback condition has passed.