Editorial guide · Updated September 2026 · Review current provider documentation before purchasing.
A step-by-step checklist for moving a WordPress site with less disruption. The guidance below explains what to inspect and how to verify the details for your own website.
Inventory your setup
Record domains, DNS, SSL, email, cron jobs, redirects, plugins and any hard-coded URLs.
Create and verify backups
Save files and database independently; verify that the backups are readable and that you can restore them.
Prepare the destination
Check PHP compatibility, storage, credentials, SSL and required extensions before transferring data.
Test before DNS changes
Use a staging URL or hosts-file method where appropriate; verify forms, logins, images, redirects and checkout.
Switch and monitor
Lower DNS TTL in advance where useful, change records, monitor errors and keep the old account until the new site is stable.
Check the current plans and terms directly. We may earn a commission if you buy through our link, at no additional cost to you.
See WPX plans ↗Before the move
Confirm access to the domain registrar, DNS provider, old hosting control panel and WordPress administrator account. Export a database and files backup and verify that you can restore them. Inventory PHP version, cron jobs, redirects, email services and paid plugin licenses. Identify a low-traffic maintenance window if the site accepts transactions.
During and after the move
Restore into the new environment, inspect logs, test internal links and media, and run a representative user journey before DNS changes. For a store, decide how orders placed during the transition will be reconciled. After cutover, test HTTPS, forms, mail delivery, scheduled jobs, search-engine directives and backups. Keep a dated record of what changed.
Your practical evaluation worksheet
Use this worksheet while researching wordpress migration checklist. It is designed to turn a general hosting question into a decision you can verify for your own website, rather than relying on a generic rating or an unsupported promise.
- Define the outcome: write down the specific problem or decision that brought you to wordpress migration checklist, and identify one measurable sign of improvement.
- Collect a baseline: record your current provider, plan, billing term, site count, storage, audience location and any recent performance or reliability issues.
- Separate essentials from extras: identify the features your website cannot operate without, and do not count a feature until its limits and responsibilities are clear.
- Verify current documentation: consult the provider’s official plan page, knowledge base and contract for every detail that could affect the purchase.
- Test a representative journey: check a public page and any important form, login, membership or checkout flow before committing to a migration.
- Keep an exit plan: retain an independent backup, confirm how to export your data and note the renewal or cancellation date.
If you cannot answer a critical question from the published documentation, ask the provider in writing. The right decision is the one whose limits and responsibilities you understand before moving a live site.