From 17+ years of hands-on engineering · 8 min read
What to Prepare for Website Hosting or Migration
A website migration involves more than copying files. The domain, database, email records, certificates, scheduled tasks, storage and outside integrations may all depend on the current hosting. A written inventory and tested backup make the move safer and reduce last-minute surprises.
In this guide
Collect account access before scheduling the move
Confirm who owns the domain registration, DNS, current hosting, new hosting, website administration, email service, analytics and any content-delivery or security service. Do not assume the same company controls all of them.
Use named accounts and secure credential sharing rather than sending passwords in ordinary messages. If a former supplier controls an account, resolve access while the existing site is still working.
- Domain registrar and DNS
- Current and new hosting
- Website and database access
- Email provider and DNS records
- Analytics, forms and external services
Make an inventory of everything that must continue
List the website files, databases, uploads, redirects, SSL certificate, scheduled tasks, background jobs and environment settings. Record subdomains and any API callbacks that point to the old server. A small forgotten task can affect invoices, bookings or form notifications after the visible pages appear correct.
Email deserves separate attention. A website hosting change should not silently replace or remove mail records. Record current MX, SPF, DKIM and verification entries before editing DNS.
Create backups and test the new environment
Take a fresh backup close to migration time, but also confirm that it can be restored. A downloaded archive is not useful if it is incomplete or the new server cannot run the application. Build and test the site on a temporary address without changing the public domain.
Check software versions, storage permissions, forms, payments, logins, image uploads, search and important integrations. Confirm that the new host can send required email and that monitoring and backups are configured there too.
Plan the DNS change and data freeze
DNS changes can take time to reach every visitor. Lowering the relevant record lifetime in advance may help, but it is not an instant switch. For a site that accepts orders, accounts or form submissions, decide how data created during the change will be handled.
Choose a quieter period, define who makes the final change and keep the old host available during verification. Avoid unrelated website updates at the same time.
Verify the business journey after the switch
Check more than the homepage. Submit forms, sign in, complete a purchase or booking where safe, inspect email delivery and verify redirects. Watch error logs and uptime from outside the new server. Search-engine crawling should continue through the same page addresses or deliberate permanent redirects.
Keep a short rollback plan with the previous DNS values and current backup. Once the new environment has remained stable and required data is confirmed, the old hosting can be closed according to the agreed retention plan.