Checklists
Website Migration Checklist
A step-by-step checklist for moving a website to new hosting or a new platform without losing data, email, search visibility or customer trust.
- Published
- Updated
- Reading time
- 4 min read
Moving a website to a new host, server or platform is one of the riskiest routine changes a business makes. Problems rarely come from copying the files; they come from the details around them: DNS records nobody documented, email that silently stops, scheduled tasks left behind, or redirects missed for old URLs that still bring in enquiries.
This checklist is written for hosting and server migrations, and most of it also applies when you change platform or domain. Work through each phase in order. The aim is a migration that is planned, reversible and verified, rather than one that is simply hoped to have worked.
Phase 1: Plan and inventory
Most migration failures are caused by something nobody knew existed.
- Define the scope. Is this a hosting move only, a platform change, a domain change or a combination? Each adds risk, so avoid combining them unless you need to.
- Inventory everything the site depends on: CMS and version, PHP or runtime version, database, extensions, cron jobs, caching, CDN, payment gateways, APIs and third-party scripts.
- Export all DNS records from the current DNS provider, not just the website records. MX, SPF, DKIM, DMARC and verification records are easily lost. Our glossary explains DNS if you need a refresher.
- Find out where email is hosted. If mailboxes live on the old web server, they need their own migration plan.
- Check domain registration and access. Confirm who controls the registrar account, when the domain expires and whether DNSSEC is enabled.
- Confirm the new environment meets requirements: supported PHP and database versions, required extensions, memory limits and disk space.
- Agree a migration window and freeze. Choose a low-traffic period and pause content changes or orders during the final copy.
- Write a rollback plan. Decide in advance what would trigger a rollback and how you would point traffic back to the old server.
If you would rather hand the planning and execution to specialists, our website migration service follows this same structure.
Phase 2: Back up and prepare
- Take a full backup of files and database and store it off both servers.
- Verify the backup restores. A migration is effectively a restore onto new hardware, so test the process first. Our backup restore test checklist covers the steps.
- Lower DNS TTL values to a few minutes, at least a day before the cut-over, so the change propagates quickly and can be reversed quickly.
- Keep the old hosting active until the new environment has been stable for an agreed period. Do not cancel it on migration day.
Phase 3: Build and copy
- Set up the new environment with matching or newer, supported software versions.
- Copy files and import the database, checking character encoding and table prefixes.
- Update configuration such as database credentials, file paths and environment variables.
- Recreate cron jobs and background workers on the new server, and disable duplicates on the old one at cut-over.
- Recreate redirects and server rules from the old configuration (.htaccess or Nginx), including HTTPS and www or non-www rules.
- Install an SSL/TLS certificate on the new server, or plan for it to be issued immediately after DNS changes.
Phase 4: Test before cut-over
Test the site on the new server before any visitor is sent there, using a temporary URL or a hosts-file override.
- Browse key pages and templates on desktop and mobile, checking for missing images, broken styles and mixed-content warnings.
- Test every critical journey: contact and quote forms, search, account login, basket and checkout with the payment gateway in test mode.
- Confirm transactional email sends from the new server and arrives without landing in spam.
- Check integrations and APIs, including any that whitelist the old server's IP address.
- Compare performance with the old server for key pages, so you know whether the new environment is an improvement.
- Check search engine settings: the live site must not be set to discourage indexing, and robots.txt must not block crawlers.
Phase 5: Cut-over
- Announce the window to internal teams and pause content edits.
- Run a final sync of the database and any uploaded files changed since the first copy.
- Update DNS records for the website, leaving email records untouched unless email is also moving.
- Issue or confirm the SSL certificate as soon as the domain resolves to the new server. Our domain, DNS and SSL management service handles this step routinely.
- Monitor propagation from several locations and confirm the new server is receiving traffic.
Phase 6: Verify after launch
- Repeat the critical-journey tests on the live domain.
- Check for 404 errors in server logs and crawl tools, and add redirects for any old URLs that still receive traffic.
- Confirm cron jobs, backups and monitoring are running on the new server, not the old one.
- Review Search Console for crawl errors, and submit an updated sitemap if URLs changed. An SEO health audit can catch issues that are easy to miss.
- Watch error logs and performance closely for the first week.
- Restore DNS TTLs to normal values once the site is stable.
Phase 7: Decommission safely
- Take a final backup of the old server and keep it for an agreed period.
- Remove credentials and access for the old environment from your password vault and integrations.
- Cancel the old hosting only after the stability period has passed and nothing is still pointing at it.
- Update your documentation with the new hosting details, access contacts and renewal dates.
Planning a migration?
If you are preparing to move a website or application and want an experienced team to plan and carry it out, get a quote and we will scope the work with you.