Live Chat
Help Center
Inventory before moving
Record the current domain settings, DNS records, mailboxes, databases, cron jobs, redirects, SSL configuration and software versions. Create a list of third-party services such as payment gateways, analytics and transactional email that may depend on the old server.
Create verified backups
Download full copies of website files and databases before changing anything. Test that archives open and database exports contain expected tables. Preserve the old hosting account until the migrated site and email have been verified.
Prepare the destination
Create the domain, database users and mailboxes on the new platform. Match required runtime versions and extensions. Import files and databases, then update configuration values without changing the public DNS yet.
Test privately
Use a hosts-file preview or temporary URL to test key pages. Check forms, login, search, checkout, redirects, images and scheduled tasks. Review browser console and server logs. Testing before DNS changes prevents visitors from becoming the test team.
Switch DNS carefully
Lower DNS TTL ahead of a planned move when possible. Update only the required records and keep a copy of the previous values. DNS changes can propagate at different speeds, so both old and new environments should remain operational during the transition.
Verify after launch
Test from multiple networks, confirm HTTPS, send and receive email, inspect analytics and monitor errors. Take a fresh backup of the new environment. Cancel old hosting only after propagation is complete and every business-critical function is confirmed.
A step-by-step cutover plan you can print
48–72 hours before a planned move
- List web, email and DNS providers separately; they may not be the same company.
- Export current DNS records (A, AAAA, CNAME, MX, TXT and any service verification records).
- Back up files and databases; verify the archives are readable and record their dates.
- Identify forms, payment callbacks, login sessions, scheduled jobs and third-party integrations.
- If suitable, lower DNS TTL in advance. This only helps records that resolvers subsequently refresh.
On migration day
- Set up the destination with compatible runtime, database versions and HTTPS.
- Copy files and import data while the original service remains available.
- Preview the destination using a safe temporary hostname or a local hosts-file entry.
- Check at least five core URLs, then test a form submission, a login, images and any checkout flow.
- Freeze or synchronize changing data before final cutover, especially orders and user-created content.
- Change only the DNS records that need to move. Do not replace mail-related records when email remains elsewhere.
After DNS changes
Test the website from another network and confirm the HTTPS certificate, redirects and form delivery. Send and receive mail externally. Check logs for missing assets, 404s and failed application requests. Keep old hosting active until DNS transitions and critical transactions have been checked.
Rollback decision
Write down in advance what counts as a failed cutover—for example, checkout failures or missing email. Keep the previous DNS values and working old server until the handover is signed off. Rolling DNS back does not automatically recover orders created on the new server, so reconcile changing data carefully.