Move a domain you already own into lemlist so it can be fully managed from your account. This is useful when you want to centralize domain management and handle your domain directly inside lemlist instead of keeping it at another registrar.
Learning Objective
By the end of this tutorial, you’ll know how to start a domain transfer in lemlist, search for your existing domain, and submit the authorization code needed to move it under lemlist management.
Why This Matters
Transferring a domain into lemlist gives you one place to manage the domain instead of splitting control between lemlist and an outside registrar. This can simplify setup and ongoing administration, especially if you want your domain operations handled directly inside the platform.
Prerequisites
You already own the domain at another registrar.
You have access to your current registrar account.
You can retrieve the domain’s authorization code, also called the Auth code or EPP code.
Core Lesson — Step-by-Step Workflow
Phase 1: Open the Domains area
Go to your domain settings.
In lemlist, click your profile in the bottom-left corner, then select Settings. After that, open Buy domains & emails and click Buy/add domain.
This is where lemlist lets you search for domains to buy, add externally, or transfer in from another registrar.
Phase 2: Search for the domain you want to transfer
Enter your domain name and look for the Transfer option.
Type the domain you already own into the search field. If the domain is eligible for transfer, you’ll see a Transfer button instead of Buy.
This is the key difference: domains available for purchase will show a buy option, while an existing domain you already own can show a transfer option.
Transfer vs. external domain
External domain: You keep the domain at your current registrar and only update nameservers to use it with lemlist.
Domain transfer: The domain itself is moved into lemlist and becomes fully managed inside the platform.
Phase 3: Authorize the transfer
Click Transfer and enter your Auth code.
Once you click Transfer, lemlist opens a transfer authorization window. Confirm the domain name and paste the Auth code provided by your current registrar, then continue to the next step.
This code proves that you own the domain and authorizes the transfer request.
Phase 4: Decide whether transfer is the right option
If you want lemlist to fully manage the domain, continue with the transfer flow. If you prefer to keep the domain at your existing registrar, use the external domain option instead.
To add an external domain, click Add external domain. This option keeps the domain at your current registrar and asks you to verify ownership and update nameservers rather than transferring the registration itself.
When you choose the external domain route, lemlist explains that you’ll keep the domain with another registrar and connect it by verifying ownership and updating nameservers.
Practical Application
A good use case for domain transfer is when your team wants everything managed in one place. For example, if you bought a domain at another registrar but now want lemlist to handle it directly, transfering it in can reduce back-and-forth between tools and make administration easier.
Use domain transfer when:
You want the domain fully managed inside lemlist.
You no longer want to maintain the domain at a separate registrar.
You have access to the domain’s Auth/EPP code.
Use external domain instead when:
You want to keep the domain at your current registrar.
You only want to connect the domain to lemlist services.
You’re comfortable updating nameservers yourself.
Troubleshooting & Pitfalls
Issue: You see “Buy” instead of “Transfer”
Root cause: The domain may not be recognized as transferable in the search results, or you may be searching for a different variation of the domain.
Fix:
Double-check the exact domain spelling and extension, such as
.comor.net.Make sure you entered the domain you already own, not an alternative suggestion.
If needed, verify with your registrar that the domain is eligible for transfer.
Issue: You don’t have the Auth/EPP code
Root cause: The code is issued by your current registrar, not by lemlist.
Fix:
Log in to your current registrar account.
Locate the transfer or domain management section.
Request or copy the authorization code, then return to lemlist and paste it into the transfer window.
Issue: You want to use the domain with lemlist but not transfer it
Root cause: You may only need to connect the domain, not move registrar ownership.
Fix:
Go to Buy domains & emails.
Choose Add external domain instead of starting a transfer.
Follow the ownership verification and nameserver update instructions.
Issue: The transfer cannot move forward
Root cause: The authorization code may be incorrect or outdated.
Fix:
Re-copy the Auth code directly from your current registrar.
Check for extra spaces before or after the code.
If it still fails, generate a new code from your registrar and try again.