Changing hosting providers can improve reliability or simplify operations, but a rushed move can interrupt sales, break forms and disrupt search access. A safe migration is a planned infrastructure change, not just a copy of website files. This checklist covers moves where the public domain and page URLs remain the same. If you also change URL paths or domains, consult Google's separate URL migration guidance.
1. Inventory Your Website Before Moving
Record your registrar, DNS provider, current host, CMS or framework, database, SSL certificate, CDN, email service, cron jobs, payment provider, CRM and integrations. Identify who controls each account and who can authorize DNS changes. Document essential customer journeys: contact forms, login, checkout, order emails, downloads and password resets.
Export important URLs and record their current HTTP status codes, canonical tags and redirects. Capture recent traffic and indexing reports from Search Console. This baseline will help distinguish migration issues from existing problems.
2. Create and Test a Recoverable Backup
Back up application files, media, databases, redirects and relevant configuration. Keep a protected copy outside the original hosting account. A backup is only useful if you can restore it: perform a test restoration in an isolated environment and verify content and database records. The WordPress backup handbook explains the importance of protecting both files and database content.
Plan for changing data
Stores and membership sites can receive new orders or registrations while files are being copied. Schedule a final database synchronization near cutover, or briefly pause writes if needed. Agree on the rollback point and decide who will execute it. Never expose backup archives or application secrets publicly.
3. Build the New Hosting Environment First
Configure the correct application runtime, database version, extensions, environment variables, storage permissions, caching, background workers and HTTPS certificate. Copy your website to the new environment before changing live DNS. Use an access-controlled staging hostname or a local hosts-file override to test it.
Do not allow an unrestricted staging duplicate to appear in search results. Google recommends testing the new infrastructure before a hosting move and preventing temporary test sites from being indexed. Review Google Search Central's changing-hosting guide.
Test complete customer journeys
Visit key pages and inspect images, CSS and downloads. Submit forms, test authentication, verify outbound emails, inspect API integrations and confirm scheduled tasks work. For ecommerce, use the payment provider's test mode. Review application and server logs for missing assets, permission errors and database failures. A working homepage does not prove the whole website works.
4. Prepare DNS and Protect Email
Determine whether the website uses A, AAAA or CNAME records, and record existing values before making changes. Preserve MX, SPF, DKIM and DMARC records unless an email migration is separately planned. Website hosting and email hosting are not necessarily provided by the same company.
Google recommends lowering relevant DNS time-to-live values ahead of the move so old records can expire sooner. Make the adjustment sufficiently early for the previous TTL to elapse. Propagation is not instantaneous everywhere, so keep the old host available during the transition.
Schedule cutover during a quieter period, appoint a technical owner and define a communication plan for anyone managing orders or customer inquiries.
5. Switch Hosting Without Unnecessary URL Changes
Once staging checks and final data synchronization are complete, update the necessary DNS records. Preserve page URLs, internal links, canonical tags, redirects and XML sitemaps. A hosting change alone does not require a domain change or a new URL structure.
Remove staging-only noindex rules and crawler restrictions from the production copy. Verify the new server presents the right TLS certificate and that HTTP-to-HTTPS redirects behave correctly. Avoid accepting independent writes on both old and new databases unless replication is explicitly designed.
Do not combine hosting migration with an unrelated redesign or CMS replacement if those changes can be separated. Google's site-move documentation recommends changing one major element at a time where practical.
6. Check SEO and Conversion Paths After Cutover
Immediately inspect important pages, checking expected 200 responses, correct 404 responses for missing content, redirect chains, robots.txt, canonical URLs, structured data and sitemap accessibility. Retest forms, checkout, logins and email notifications.
Use Search Console and server logs
Inspect representative URLs in Google Search Console to confirm Googlebot can reach the new host. Monitor indexing, organic landing pages, server errors and crawl behavior over the following days. Google notes that temporary crawl-rate changes can occur after a hosting migration; investigate persistent errors rather than treating every fluctuation as a ranking problem.
7. Troubleshoot Common Hosting Migration Problems
- Broken images: confirm media files were copied and permissions allow access.
- Unexpected 404 pages: review application routing and web-server rewrite rules.
- Redirect loops: inspect HTTPS settings across CDN, reverse proxy and application.
- Missing leads: check form handlers, outbound email and CRM integration logs.
- Search indexing issues: remove accidental production noindex directives and crawl blocks.
- Missing recent orders: verify final data synchronization before enabling writes.
8. Monitor and Retire the Old Host Safely
Compare uptime, server errors, sales and form submissions with the pre-migration baseline. Keep both environments available until traffic is consistently served by the new host. Google's guidance recommends checking logs on both systems and shutting down the old infrastructure only when users and Googlebot are no longer depending on it.
After confirmation, archive required records, rotate obsolete credentials, update operational documentation and cancel unused hosting according to your retention policy.
Printable Website Hosting Migration Checklist
- Inventory DNS, hosting, email, database and integrations.
- Record important URLs, redirects and Search Console baseline.
- Back up files, database and configuration; test restoration.
- Configure and privately test the new hosting environment.
- Plan data synchronization, rollback and responsible owners.
- Lower applicable DNS TTL values ahead of time.
- Preserve email records and public URLs.
- Switch DNS, verify HTTPS and complete customer journeys.
- Monitor logs, indexing, conversions and uptime.
- Retire the old host only after verification.
When to Get Help With a Hosting Migration
A small static site may be simple to move. An ecommerce store or custom application with live transactions and several integrations needs a more deliberate migration plan. Ask any provider who owns backups, DNS, rollback, testing and post-launch monitoring.
Explore DesDevSol's domain and hosting services for infrastructure planning, or its website maintenance and security solution for ongoing support. Share your platform, existing hosting setup and critical integrations to discuss a suitable migration plan.