Moving Website to New Hosting: A Pre-Migration Checklist

When hosting migration checklist becomes a problem, the fastest fix is not always the first fix you find online. A safer approach is to confirm what changed, protect anything that still works and troubleshoot in a sequence that preserves recovery options.

Confirm the symptoms first

Write down exactly what is failing, when it started and who is affected. Save the exact error message. Test from another device or connection where appropriate.

If a live business service is affected, consider malware removal before making broad changes.

Check recent changes

Look for plugin or theme updates, password changes, DNS edits, hosting migrations, PHP upgrades, security rules or mailbox configuration changes. Use the timeline to narrow the investigation rather than assuming.

Protect recovery options

Before editing files, databases or DNS, confirm you have a usable backup or another recovery path. For security incidents, preserve relevant logs before cleanup.

Where compromise is suspected, Office 365 setup should consider credentials, vulnerable software and the original entry point, not just suspicious files.

Work from the outside in

Start with domain resolution, SSL, hosting response and account status. Then move into WordPress, plugins, the database and individual devices. This avoids troubleshooting the application when the fault sits elsewhere.

Change one thing at a time

Record important settings, make one controlled change and test again. Multiple simultaneous changes make it difficult to identify what fixed or worsened the issue.

For infrastructure changes such as website edits, keep a short record of old and new values so rollback remains possible.

Verify the complete service

A homepage loading does not prove a website is healthy. Test forms, logins, checkout, inbound and outbound email, mobile access, SSL and other functions the business relies on.

Prevent a repeat

Document the cause and recovery steps. Keep domain, hosting and email ownership clear, maintain backups and updates, and record DNS settings and important third-party services.

Related troubleshooting guides

Also see Domain Transfer Checklist and Website Form Spam for related checks and preventative steps.

Lower DNS TTL before the move

If you control the DNS zone, reducing the relevant TTL ahead of a planned migration can shorten the period in which visitors receive different server addresses. Record every existing DNS record before making changes, especially MX, SPF, DKIM and verification records used by business email and third-party services.

Build and test before switching traffic

Copy the website to the destination and test it before changing public DNS. Check important pages, forms, logins, redirects, SSL behaviour and any ecommerce or booking functions. A hosts-file preview or temporary staging method can let you test the destination while customers continue using the existing server.

Keep the old hosting available temporarily

Do not cancel the old account immediately after the DNS switch. Keeping it available gives you a rollback option and helps cover visitors whose DNS resolvers have not yet refreshed. Once traffic has settled on the new server and logs show normal operation, you can plan the old account’s closure.

Plan the final cutover

Choose a quieter period if the site receives transactions or frequent content changes. Take a fresh database copy immediately before cutover where necessary, then switch DNS and monitor both servers. Recheck contact forms and email notifications after the public domain resolves to the destination. Keep a written rollback threshold so the decision to revert is based on defined failures rather than pressure during the migration.

Practical takeaway

For hosting migration checklist, diagnose before repairing. Confirm the scope, protect recovery options, check recent changes, test systematically and verify the full service afterwards.

Related website and SEO resources

A hosting migration is also a good time to review the website and its search visibility. For website redevelopment see Branding Experts, and for search migration and technical SEO planning see SEO Edge.