Website migration checklist
A website migration moves your site from an old hosting account to a new one. Alongside files, you need to check the database, email, SSL and DNS settings.
Follow this order: Record the old setup, take backups, test the new copy, then direct visitors to the new server. Keep the old service active until you have verified the replacement.
This is the general checklist. For WordPress-specific steps, use the WordPress migration guide linked below as well.
Verify the new copy before directing visitors to it.
- Prepare the copy
Preserve files, database and current DNS settings.
- Test the new environment
Check content and application tasks on the restricted copy.
- Direct visitors
Update the required DNS records after the final data transfer.
- Verify the live site
Check HTTPS, the website and email through your normal connection.
Keep the old service until the replacement is verified. Plan how to prevent new orders on both servers at once.
Record the existing setup
Where? In the old hosting panel and at your current DNS provider.
- List the domains you are moving.
- Record the PHP version, required extensions, storage usage and database names. PHP is the software that runs your application on the server.
- List scheduled tasks, which run automatically, and connections to external services.
- Save a copy of the DNS records. Preserve email MX, SPF, DKIM and DMARC records in particular; email may be staying with another provider.
A domain transfer is separate: Hosting migration moves the site to another server; a domain transfer changes the registrar. You do not need to do both to move a website.
Back up and plan the transfer
- Take a current copy of the website files.
- Back up the database too. It stores records such as posts, users and orders; copying files alone does not move those records.
- Keep backups outside website folders that visitors can download from.
- For a site accepting orders or comments, plan a maintenance window for the final transfer. Decide how to prevent new records being created on both servers at once.
- Decide when to take the final backup and which environment will accept new records. A maintenance page may not stop payment notifications or writes through an API.
If you need assistance, include the source panel, data size and preferred time in a support request. Share access details only through the secure method recommended by support.
Test before changing DNS
Where? In the new hosting account. Visitors still use the old site at this stage.
- Protect web access to the new copy with authentication or IP restrictions.
noindexaffects search visibility; it does not protect customer data from access. - Transfer the files and database to the new service. Point the application's connection settings at the new database.
- Before opening the new copy, restrict real customer notifications, payment/API actions and scheduled tasks for testing. If you cannot identify these controls, get technical help before running it.
- Use a preview method available with the service. Alternatively, a temporary hosts entry on your own computer can point only that computer at the new server; other visitors are unaffected.
- Check sign-in, forms, images, internal links and tasks under controlled test conditions. Do not create real payments or duplicate customer notifications.
Expected result: The new copy opens with the correct data. This does not prove that public DNS or automated certificate validation works; check those separately after switching.
You can test the copy without moving every visitor.
- Your own computer
A temporary hosts entry can direct you to the new server.
- Other visitors
They use the existing destination while public DNS stays unchanged.
Remove the hosts entry after testing. Apply separate access restrictions to protect the test copy.
Switch DNS and verify
- If the old site's data changed during testing, complete the planned final transfer.
- At the authoritative DNS provider, update the required A/AAAA records: the server addresses for your website. If changing nameservers, first copy email and verification records into the new DNS zone.
- Remove any temporary hosts entry from your computer. Open the site using your normal connection.
- Test HTTPS, sign-in and forms. Check incoming and outgoing email separately.
- Review test access restrictions and any
noindexsetting before launch. Do not accidentally leave the public site restricted. - Monitor traffic and error logs on both environments. DNS caches, which hold previously learned addresses, may update at different times.
If something fails: Use the saved DNS values and backups to plan a rollback. Pointing DNS at the old server does not move orders created on the new one. Decide how to preserve those records first.