A safe website migration copies the application, tests it at the destination and moves traffic only after you have a recovery path. Domain registration, website hosting and email can move separately. You do not always need to change nameservers.
1. Inventory the services before copying
List domains, website files, databases, software versions, scheduled jobs, certificates, forms, payment integrations and mail services. Export or record the current DNS zone, including A, AAAA, CNAME, MX, TXT and any other records in use. Confirm who controls DNS and the domain registration.
2. Back up and agree the scope
Take complete copies of files and databases, and verify that you can open or restore them. Keep a copy outside the source hosting account. Identify email and any other data that need a separate migration. Agree migration charges, work included, timing and a rollback plan before starting.
For an online shop or another frequently updated application, plan a short write freeze or a final data synchronisation so new orders and changes do not remain only on the old server. Do not blindly overwrite a database after the new site starts accepting writes.
3. Prepare and test the destination
Match the required software versions and extensions, create the database, copy the files and update the application configuration. Keep configuration files and credentials private. Use an approved preview method that preserves the real hostname, such as a temporary hosts-file mapping, where appropriate; a raw IP address may show the wrong site or break HTTPS.
Test representative pages, logins, uploads, search, forms, redirects and integrations. Prevent tests from sending real customer notifications or charging live payment methods. Arrange certificate validation before the final cutover.
4. Change only the necessary DNS records
If DNS stays with the current provider, moving the website may require only its web records. Leave MX and mail authentication records intact when email is staying put. If nameservers must change, recreate and verify the full required zone first; include DNSSEC coordination if it is enabled.
A lower DNS TTL can shorten caching during a planned move, but only after the previous TTL has elapsed. Different resolvers can retain the old answer for different periods. Monitor both destinations rather than promising a fixed completion time.
5. Verify before retiring the old service
Check HTTPS, forms, application logs, scheduled jobs and inbound and outbound mail. Confirm new data is being written only to the intended destination. Keep the old service and backups available for the agreed verification period. Cancel it only after all required website and email data have been verified and any rollback decision is settled.
Request migration help with your software, approximate data size and desired timing. Compare hosting plans before committing to the destination.
Reviewed 3 October 2026. Reference: cPanel backup and restore capabilities. A full account restore can require provider assistance.