TickYouOff
Back
🔄

Website Migration Checklist

Hard 20 items · 2 hours
testuser's avatar
testuser Published 1 month ago

A practical, step-by-step checklist to move a website to a new hosting provider with minimal downtime. It walks through backups, database export/import, SFTP transfer, DNS and MX changes, SSL, redirects, and smoke tests. Ideal for site owners, developers, and IT teams planning a controlled migration.

Progress
0 / 20
  1. Create a full backup of site files and assets — Backup the webroot, media, and any uploaded files; store off-server with timestamped copy.
  2. Export the latest database dump and verify integrity — Use mysqldump/phpMyAdmin and confirm the dump imports locally before migrating.
  3. Inventory current server settings and services — Record PHP version, extensions, PHP-FPM/nginx/apache configs, crons, and mail settings.
  4. Prepare a rollback plan and verify backups are accessible — Document rollback steps, restore point, and key contacts in case you need to revert.
  5. Set up the new hosting environment (DB, users, PHP, services) — Create DB/user, match PHP version/extensions, and configure cron jobs and permissions.
  6. Upload site files to the new host via SFTP and set permissions — Transfer files securely, maintain owner/group, and set web-safe permissions for folders/files.
  7. Import the database on the new host and update configuration files — Import dump, update DB credentials and connection strings, and test DB connections.
  8. Test the new site via a temporary URL or hosts file before changing DNS — Use a hosts file override or preview URL to confirm pages, login, and dynamic features.
  9. Reissue or install the SSL certificate and confirm HTTPS — Install cert on new server, verify chain, and check for mixed-content warnings.
  10. Lower DNS TTL ahead of the cutover — Set TTL to 300–600 seconds 48–72 hours before switching to speed propagation.
  11. Update MX and email DNS records or execute your email migration plan — Ensure MX, SPF, DKIM, and DMARC are ready; schedule mail cutover to avoid loss.
  12. Update domain A/AAAA records to point to the new host — Change the records during the planned window and monitor propagation.
  13. Set up 301 redirects and URL mappings for changed pages — Implement server-level 301s or rewrite rules to preserve SEO and user bookmarks.
  14. Run pre-launch smoke tests — Quickly verify core functionality before public traffic switches.
  15. Load the homepage and log into admin/user accounts — Confirm site loads quickly and admin access works without errors.
  16. Submit contact, order, and key forms and verify notifications — Check form submissions, transactional emails, and webhook endpoints.
  17. Verify HTTPS, certificate details, and redirect behavior — Confirm valid cert, no mixed content, and canonical URLs redirect correctly.
  18. Monitor DNS propagation and check the live site from multiple locations — Use propagation checkers and spot-check geographic access and latency.
  19. Run a crawler to find broken links and fix or map redirects — Use tools like Screaming Frog to detect 4xx/5xx and update routes or redirects.
  20. Submit updated sitemap and check Google Search Console for errors — Upload sitemap, request reindexing if needed, and monitor coverage reports.
Sign in to save
📝 My Notes