Domains purchased through lemlist can be transferred to another registrar once they become eligible. This guide explains the eligibility requirements, the end-to-end transfer workflow, and what to plan for so your DNS and email services continue working smoothly.
Learning objective
By the end of this tutorial, you’ll know how to confirm your domain is eligible for transfer, unlock it in lemlist, retrieve the authorization (AUTH/EPP) code, and complete the transfer with a new registrar without unexpected downtime.
Why this matters
Moving your domain to a registrar you already use can simplify billing, centralize DNS management, and give you broader registrar tooling. Knowing the lock rules and DNS/email implications helps you avoid transfer failures and service interruptions.
Prerequisites
You have access to the lemlist workspace that owns the domain.
You have chosen a new registrar (for example: Cloudflare, OVH, GoDaddy, Namecheap, etc.).
Your domain is past the required lock period (details below).
Eligibility for domain transfer
ICANN-mandated 60-day lock period
Most domains are subject to a mandatory 60-day transfer lock after:
Initial registration (right after you purchase the domain), or
Changes to registrant details such as name, organization, or email address.
During this period, transfers are not allowed. If you try to transfer early, the transfer will fail or be rejected.
After the lock period
Once the 60 days have passed, you can transfer your domain by unlocking it and generating an AUTH code (also called EPP code or transfer code) in lemlist, then submitting that code to your new registrar.
Core lesson — Step-by-step transfer workflow
Phase 1: Prepare for the transfer
Check timing and plan your DNS/email cutover.
Transfers can take time (often hours to several days depending on the registrar and TLD). If the domain is actively used for sending or receiving email, plan the migration so you can update DNS at the right time and monitor deliverability.Verify your domain contact email is accurate and accessible.
Most registrars send transfer approval or confirmation emails to the domain’s registrant/admin contact. If you can’t access that inbox, the transfer can stall.
Phase 2: Unlock the domain and retrieve the AUTH/EPP code in lemlist
Open your domain management settings in lemlist.
Log in to lemlist and navigate to the section where your purchased domains are managed.Disable “Registrar Protection” (unlock the domain).
In the domain’s settings, turn off Registrar Protection. This is required to allow transfers.Generate and copy the Authorization (AUTH/EPP) code.
Once the domain is unlocked, generate the transfer code from the same settings area. Store it securely—your new registrar will require it.
Tip: Treat the AUTH/EPP code like a password. Anyone with this code (and access to approval emails, depending on the registrar) may be able to initiate a transfer.
Phase 3: Start the transfer at your new registrar
Begin a “Transfer domain” order with the new registrar.
In your new registrar’s dashboard, choose the option to transfer an existing domain.Enter your domain name and paste the AUTH/EPP code.
Follow the registrar’s prompts. Some registrars also require you to confirm contact details or choose DNS hosting during checkout.Approve transfer emails (if requested).
Watch for confirmation emails related to the transfer and approve them promptly to prevent delays.Wait for completion, then verify ownership and DNS resolution.
After the transfer completes, verify the domain appears in your new registrar and confirm your DNS records are correct.
Important considerations (read before transferring)
DNS and email settings do not automatically carry over
Any DNS configuration you set while the domain is managed through lemlist will not automatically move to the new registrar. Plan to recreate required records, such as:
A / AAAA records (website hosting)
CNAME records (tracking, subdomains, verification)
MX records (mail routing)
TXT records (SPF, DKIM, DMARC, domain verification)
Interim option during the 60-day lock: use custom nameservers
If you need to control where the domain points before the lock period ends, lemlist allows you to set up custom nameservers. This can give you temporary control over DNS hosting without transferring the domain.
Platform limitation: domains are primarily intended for sending from lemlist
Domains purchased via lemlist are designed mainly for email sending use cases within the platform. Full external-registrar-level management is limited, and you won’t get direct access to the upstream registrar while the domain is managed in lemlist.
Practical application example
Scenario: You bought a domain in lemlist to send outbound emails, and now you want to centralize all domains in Cloudflare.
Wait until the domain passes the 60-day ICANN lock.
Unlock the domain in lemlist by disabling Registrar Protection.
Copy the AUTH/EPP code and start a “Transfer Domain” in Cloudflare.
After transfer completes, recreate DNS records in Cloudflare (especially SPF/DKIM/DMARC if you’ll keep sending email).
Troubleshooting & pitfalls
Issue: “Transfer not allowed” or “Domain is locked”
Root cause: The domain is still within the 60-day ICANN lock period, or Registrar Protection is still enabled.
Fix:
Confirm at least 60 days have passed since purchase or registrant detail changes.
Disable Registrar Protection in the domain settings in lemlist.
Try the transfer again once both conditions are met.
Issue: You never receive the transfer approval email
Root cause: The registrant/admin email is incorrect, inaccessible, or messages are being filtered.
Fix:
Verify the contact email on the domain is correct before initiating the transfer.
Check spam/quarantine folders.
Ask your new registrar if manual approval steps are available.
Issue: Email sending/receiving stops after the transfer
Root cause: DNS records (MX/SPF/DKIM/DMARC) weren’t recreated or nameservers changed unexpectedly.
Fix:
Recreate required DNS records at the new DNS host.
Confirm MX records for inbound mail and SPF/DKIM/DMARC for sending.
Allow time for DNS propagation after changes.
FAQs
Can I transfer my domain immediately after purchasing it?
No. Domains are locked for 60 days after purchase due to ICANN regulations. You can only initiate a transfer after this period ends.
What happens to my email services during the transfer?
If you purchased Google Workspace email addresses with the domain, the Workspace subscription cannot be transferred. You’ll need to set up a new Google Workspace account through your new provider/registrar (or directly with Google), then reconfigure DNS accordingly.
Can I manage my domain directly at the external registrar?
No. Domains purchased through lemlist are managed within the lemlist platform, and direct access to the upstream registrar is not available while the domain is held there.