A migration checklist turns a risky “copy and switch” job into a sequence of decisions. It is useful for a host change, domain change or a move from a static site to WordPress. The checklist should name the site owner, technical contact, launch window and rollback decision-maker.
Before the move
- Inventory pages, URLs, files, database, plugins and integrations.
- Confirm the destination meets the site’s technical requirements.
- Back up files and database and verify that the archive is accessible.
- Identify domain, DNS, email, SSL and CDN account owners.
- For shops, plan how to handle orders or account changes during cutover.
During preparation
Copy the site to staging, check representative pages, forms and administrator access, and note any PHP or plugin compatibility issue. Map URLs that will change and prepare redirects. Keep content frozen only when needed and communicate the timing to the team.
After switching
Check SSL, redirects, forms, images, sitemap, robots settings, checkout and email delivery. Test from a normal browser and mobile device. Monitor logs and customer reports, and keep the old host until the new site is stable. DNS propagation is not instantaneous for every resolver, so plan a transition period.
Document what moved, what remains with a provider and where the backup is stored. This checklist does not remove every risk, but it makes ownership and verification explicit—two things that prevent many avoidable migration surprises.
Written by Code Papa, an independent WordPress developer based in the UAE with 15 years of experience.