Migration
How to Migrate Website Hosting
Plan a website move with backups, destination testing, a cutover window and a rollback option.
A hosting migration combines data copying with a traffic cutover. Treat the website, email and domain registration as related but separate services. Keeping the old account temporarily available gives you a recovery option if testing exposes a problem.
Practical steps
- Inventory files, databases, mailboxes, DNS records, scheduled jobs and integrations. Ask the destination host to confirm compatibility, migration scope, cost and timing.
- Make independent backups and verify that they can be read. Protect exports containing credentials or customer data and use an approved secure transfer method.
- Prepare and test the destination without changing public DNS. Check forms, login flows, media, redirects, HTTPS and outgoing messages.
- Agree a final sync and a write-freeze period where necessary. Change the intended DNS records, monitor both destinations and retain the old host until caches and traffic settle.
Check the result
Check page content, database record counts, file uploads and mail delivery against the source. Review logs after cutover and confirm that new data is being written only to the intended destination.
Before you proceed
DNS changes do not copy files or mailboxes. A free transfer offer, if any, must have a confirmed scope; do not assume every migration or recovery task is included.