Domain, website and email changes are often treated as one task, but they are separate systems that happen to share DNS. The safest migration starts by documenting what already exists before changing nameservers, hosting or mail records.
1. Inventory the current setup
Record the registrar, authoritative DNS provider, website host and email provider. Export or screenshot the entire DNS zone. Identify which addresses people actually use and which records support other tools such as verification, forms or third-party services.
2. Protect the mail path first
Before changing DNS, confirm the existing MX records and email-authentication records such as SPF, DKIM and DMARC. If the website is moving but email is not, those mail records normally need to be preserved in the new DNS zone.
3. Separate registration, DNS, hosting and email
The domain can stay registered with one provider while DNS is managed elsewhere, the website is hosted on another platform and email remains with a dedicated mail provider. Understanding that separation makes migrations much easier to plan.
4. Build and test before switching the public domain
Publish the new website to a temporary deployment URL first. Test pages, forms, mobile layout, legal links and conversion flows before changing the custom domain. This reduces pressure during the DNS cutover.
5. Compare the DNS zone before changing nameservers
Automatic DNS scans are useful but should not be treated as a perfect backup. Compare every important record with the exported zone and add anything that is missing before delegating the domain to new nameservers.
6. Test both the website and email after the change
- Open the root and www domain on desktop and mobile.
- Submit the website enquiry form and confirm delivery.
- Send inbound and outbound test email.
- Check that business aliases and recovery addresses still work.
- Verify SSL and redirect behaviour.
7. Keep a rollback record
Save the old DNS export, previous deployment and key configuration notes. A migration is easier to troubleshoot when the previous known-good state is documented.
Where Not Out Labs fits
We can support domain, hosting, business email, website and migration work as part of our business technology support. The exact scope depends on who currently controls the domain and which systems need to move.