A domain transfer should start with a checklist, not with cancelling your old account. Your domain registration, website hosting, DNS and business email may be managed in different places. Before moving anything, identify which of those services you actually want to change.
This guide is for business owners preparing to move an existing domain between registrars. It is a planning checklist, not a promise of uninterrupted service or a fixed completion time. Country-code domains and individual registrars can have different requirements.
1. Decide what is moving
Write a one-sentence scope for the job: “Move the registration, keep the current website and email providers.” If you also want new hosting or a new mail service, give each change its own preparation and verification steps. A successful registrar transfer does not prove that your files or mailboxes have moved.
| Service | Record before starting | Verify afterward |
|---|---|---|
| Domain registration | Current registrar, expiry date and authorized account owner | The domain appears in the intended registrar account with the expected expiry details |
| DNS | Nameservers and the provider holding the DNS zone | Nameservers and important records match the agreed plan |
| Website | Hosting account, current backup and critical customer journeys | HTTPS pages and important forms still work |
| Business email | Mail provider, active mailboxes and email-related DNS records | A test message can be received, sent and replied to |
For a separate hosting move, use our website migration preparation guide. Do not assume that a registrar transfer includes the migration services described there.
2. Check eligibility before changing account details
For domains covered by ICANN’s transfer policy, a recent registration or previous transfer can prevent a move during the relevant 60-day period. A change of registrant can also trigger a 60-day transfer lock. Ask the current registrar which restriction applies before changing the registered owner’s details. Check the current ICANN Transfer Policy and the rules for your particular extension.
Record the expiry date now. If the domain is near expiry, ask the registrar how to keep the registration active while resolving eligibility or approval problems. Do not build a business-critical plan around an assumed grace period. A deadline written in your own calendar is more useful than an unfinished transfer request sitting in an inbox.
Choose who will watch the request and who will handle website or email issues. For a small team, these may be the same person, but make the responsibility explicit. Keep an alternate way to contact that person if the domain’s own email service becomes unavailable.
3. Prepare the authorization code securely
Your current registrar supplies the authorization code, often called an Auth-Code or EPP code. Follow its transfer-unlock and approval process. ICANN’s registrant transfer FAQ explains the code and common reasons a transfer may be refused.
Treat the code as private. Enter it only in the intended provider’s secure transfer form; do not put it in a public support comment, screenshot or shared planning document. Confirm that the domain spelling is correct before submission. Save the non-secret order or support reference so you can ask about the exact request without sending the code again.
4. Record DNS and email dependencies
Export or securely record the existing DNS zone before making changes. Include the main website and important subdomains, not just the address visible in the browser. A and AAAA records point names to IP addresses; CNAME records alias names. MX records route incoming mail, while SPF, DKIM and DMARC help receiving systems evaluate mail sent for your domain. See Cloudflare’s DNS record reference for the different record types.
- Confirm whether the current DNS service remains available after the registration moves.
- List business-critical subdomains, verification records and email services that a basic record scan might miss.
- Keep the existing DNS and hosting subscriptions active until the agreed checks pass.
- If DNS is also moving, compare the new zone against the saved inventory before changing nameservers.
DNSSEC needs a separate migration plan. Do not remove its settings automatically just because you are changing registrar. If you are also replacing nameservers, follow the old and new DNS providers’ instructions for the signing keys and parent DS record. Cloudflare’s nameserver-change guide explains why an incompatible DNSSEC configuration can make a domain unreachable.
5. Submit the transfer and track the exact request
MyLightHost provides a domain-transfer form with fields for the domain name and authorization code. Review the current price, supported extension and renewal terms shown for your domain before placing an order. Do not assume that every extension follows the same transfer or renewal rules.
Follow the confirmation instructions from the providers involved. If the request is rejected, record the stated reason and resolve that issue before submitting again. Avoid changing the registrar, nameservers, hosting and email all at once simply to see whether a failed request starts working.
Keep a short change log: the request reference, submission time, expected next update, responsible person and any provider response. Use it to distinguish “submitted,” “awaiting confirmation,” “rejected” and “completed.” A payment receipt alone is not proof that the registration has finished moving.
6. Verify the business services before closing the job
- Confirm the domain is in the correct destination account. Review the displayed expiry and renewal settings; investigate unexpected differences.
- Compare the nameservers and important DNS records with the agreed plan.
- Open the website over HTTPS on desktop and mobile. Test a contact form or another low-risk customer journey without creating a real purchase.
- Send an agreed test email in both directions and reply to it. Check any delivery failure instead of assuming that a working website proves email health.
- Review the transfer lock and account protection with the authorized account owner. Never leave the authorization code in the change log.
If something fails, pause further changes and compare the failing service with its recorded pre-move configuration. Contact the responsible provider with the domain and non-secret request reference. Do not cancel the old service until you know which dependencies still rely on it.
Ready to plan your move?
Use this checklist to gather the information first, then review a domain transfer to MyLightHost. If you are choosing a new address instead of moving an existing one, start with our domain-extension guide or browse the domain services.
Sources checked on 11 September 2026. Recheck the current registrar and extension-specific requirements when you are ready to transfer.