A domain transfer and a DNS change are not the same thing. Before transferring the registrar, document the current DNS and confirm where the website and email are actually hosted.
Separate the registrar from the DNS provider
The company where a domain is registered may not be the company hosting its DNS. Before moving anything, identify the registrar, authoritative nameservers, website host, email provider and any third-party DNS services.
1. Confirm ownership and transfer access
Make sure the business has access to the registrar account and the email address used for transfer approvals. Check whether the domain has a transfer lock or other restriction and record renewal dates before starting.
2. Export or document the DNS
Record A, AAAA, CNAME, MX, TXT and any important verification records. Pay particular attention to email authentication records. A domain transfer should not become an accidental DNS rebuild.
3. Check the website and email dependencies
Write down where the website points, where email is handled and which services rely on DNS. This can include payment systems, Microsoft 365, Google Workspace, marketing tools, verification records and subdomains.
4. Plan the transfer separately from DNS changes
If the DNS provider will remain the same, keep that arrangement clear. If DNS will also move, recreate and test the zone before switching nameservers. Avoid making registrar, DNS and hosting changes simultaneously unless there is a strong reason.
5. Verify after the move
Check the website, HTTPS, email sending and receiving, important subdomains and verification services. Keep the old information and a rollback plan available until the new arrangement is confirmed.
The safest principle
A domain move should be boring. The less you change at the same time, the easier it is to identify a problem and reverse it if necessary.