There are plenty of reasons to transfer a domain to a new registrar: better pricing, improved DNS management, consolidating all your domains in one place, or escaping a registrar with poor support. Whatever your reason, the transfer process follows a standard procedure defined by ICANN — but there are nuances that can trip you up if you're not prepared.
This guide walks you through the complete transfer process, from pre-transfer preparation to post-transfer verification. We'll cover the common pitfalls that cause email disruptions, SEO problems, and unnecessary delays.
Before You Start: Transfer vs. Nameserver Change
First, make sure you actually need a domain transfer. There's an important distinction between two different operations:
- Domain transfer: Moves the domain registration from one registrar to another. The new registrar becomes the official owner on record. This is what we're covering in this guide.
- Nameserver change: Changes where your DNS records are hosted without moving the domain registration. If you just want to use a different hosting provider or DNS service, you may only need to update your nameservers — no transfer required.
If you're switching hosting providers but happy with your current registrar, a nameserver change is simpler and faster. If you want to move the domain itself to a new registrar, read on.
Pre-Transfer Checklist
Before initiating a transfer, complete these essential preparation steps:
1. Verify Your Domain Is Eligible
ICANN rules prevent transfers in certain situations:
- 60-day lock after registration: New domains cannot be transferred for 60 days after initial registration
- 60-day lock after previous transfer: You must wait 60 days between transfers
- 60-day lock after WHOIS changes: Some registrars lock domains for 60 days after changing the registrant contact information (this rule varies by registrar)
- Domain expiring within 15 days: Most registrars won't accept a transfer for domains that expire within the next two weeks
2. Document Your Current DNS Records
This is the most critical preparation step. Before transferring, export or screenshot every DNS record currently configured for your domain. This includes:
- A records (website IP addresses)
- CNAME records (aliases and third-party services)
- MX records (email routing)
- TXT records (SPF, DKIM, DMARC, domain verifications)
- NS records (current nameservers)
- Any SRV, CAA, or other specialty records
Serverlys Tip: Use our WHOIS lookup tool to verify your current domain registration details and nameservers before starting the transfer. Having a record of your current configuration prevents mistakes during the migration.
3. Lower Your DNS TTL
At least 48 hours before the transfer, lower the TTL (Time to Live) on all your DNS records to 300 seconds (5 minutes). This ensures that once DNS records change during the transfer, the updates propagate quickly instead of being cached for hours.
4. Back Up Your Website and Email
While a domain transfer shouldn't affect your website files or email data, having a fresh backup provides peace of mind. Download a full backup of your website and export any critical emails before proceeding.
The Transfer Process: Step by Step
Step 1: Unlock Your Domain
Most registrars apply a "registrar lock" (also called a transfer lock or client transfer prohibited status) to prevent unauthorized transfers. Log into your current registrar's dashboard and disable this lock. The exact location varies by registrar, but it's typically under domain settings or security settings.
Step 2: Get Your Authorization Code (EPP Code)
The authorization code (also called an EPP code, auth code, or transfer key) is a unique password that authorizes the transfer. Request this code from your current registrar. Some registrars display it immediately in the dashboard; others email it to the domain's registrant contact.
The auth code is typically valid for 5-14 days, so request it close to when you plan to initiate the transfer at the new registrar.
Step 3: Initiate the Transfer at the New Registrar
Go to your new registrar (like Serverlys) and start the domain transfer process. You'll need to:
- Enter the domain name you want to transfer
- Provide the authorization code
- Confirm or update the WHOIS contact information
- Pay the transfer fee (which typically includes one year of registration)
Step 4: Approve the Transfer
After initiating the transfer, the process requires approval from the domain owner. You'll receive an email at the registrant email address on file asking you to confirm the transfer. Click the approval link to proceed.
If you don't approve within 5 days, many transfers will still proceed automatically. However, actively approving speeds up the process significantly — from up to 7 days down to as little as a few hours.
Step 5: Wait for Completion
The standard transfer timeline looks like this:
| Phase | Duration | What Happens |
|---|---|---|
| Transfer initiated | Immediate | New registrar sends transfer request |
| Owner approval | Minutes to 5 days | You confirm via email link |
| Losing registrar review | 0-5 days | Old registrar can approve or let it auto-complete |
| DNS propagation | 1-48 hours | Nameserver changes propagate globally |
| Total typical time | 1-7 days | Most transfers complete within 3-5 days |
Protecting Your Email During Transfer
Email disruption is the biggest risk during a domain transfer. Here's how to prevent it:
If Your Email Is Hosted by the Old Registrar
This is the highest-risk scenario. If your email service is bundled with your domain registration (common with GoDaddy, Namecheap, etc.), transferring the domain may disconnect your email. Before transferring:
- Set up email with a new provider first (Google Workspace, Microsoft 365, Zoho, or your new hosting provider)
- Migrate your existing emails using IMAP migration tools
- Update MX records at the new registrar to point to your new email provider immediately after the transfer
- Keep the old email account active for at least 30 days to catch any straggling messages
If Your Email Is Hosted Separately
If you use Google Workspace, Microsoft 365, or another independent email provider, the transfer is lower risk. Your MX records just need to remain the same at the new registrar. As long as you correctly replicate your MX, SPF, DKIM, and DMARC records, email will continue flowing without interruption.
Serverlys Tip: When you transfer a domain to Serverlys, we automatically import your existing DNS records when possible, reducing the risk of email disruption. Our support team can also help verify your email configuration after the transfer completes.
Preserving SEO During a Domain Transfer
A registrar-to-registrar transfer of the same domain name should not affect your SEO rankings at all, because your domain name, URLs, and content remain unchanged. Google doesn't know or care which registrar manages your domain registration.
However, problems can arise if:
- Your DNS records change: If the A record points to a different server after the transfer, Google may temporarily see a different site or a 404 error. Ensure A records point to the correct hosting server.
- You change your domain name simultaneously: If you're rebranding and changing your domain name during the transfer, that's effectively a site migration — a much bigger operation that requires 301 redirects from every old URL to its new equivalent.
- Extended downtime: If misconfigured DNS causes your site to be unreachable for more than a few hours, Google may temporarily drop your pages from search results. They'll recover once the site is back, but prolonged downtime causes deeper damage.
SEO Checklist for Domain Transfers
- Verify your A record points to the correct server IP after transfer
- Confirm canonical URLs are unchanged
- Check that your sitemap is still accessible
- Verify Google Search Console still shows your site as verified
- Test all major pages to ensure they load correctly
- Monitor Google Search Console for crawl errors in the week after transfer
Common Transfer Problems and Solutions
Transfer Rejected by Losing Registrar
If your old registrar rejects the transfer, check for: an active transfer lock, an incorrect auth code, an expired domain, or a recent WHOIS change that triggered a 60-day lock. Contact the old registrar's support to identify the specific reason.
No Approval Email Received
The approval email goes to the registrant email address in the WHOIS record, not necessarily the email you use to log into the registrar. If you haven't received it, check spam folders, verify the WHOIS email is correct, and if necessary, update the registrant email before retrying the transfer.
Website Down After Transfer
If your website goes down after the transfer completes, the most likely cause is DNS records not being replicated at the new registrar. Log into the new registrar's DNS panel and verify all records match your pre-transfer documentation. Pay special attention to A records and CNAME records.
Domain Stuck in "Pending Transfer"
Transfers can take up to 7 days, but if a transfer has been pending for more than 5 days, contact both the gaining and losing registrars. The losing registrar may need to explicitly release the domain, or there may be a technical issue delaying the process.
"The most common transfer mistakes aren't technical — they're preparation mistakes. Documenting your DNS records, lowering TTL in advance, and having a clear plan for email continuity eliminates 90% of transfer problems."
After the Transfer: Verification Steps
- Verify DNS records: Compare every DNS record at the new registrar against your pre-transfer documentation
- Test your website: Load your site in multiple browsers and devices. Test key pages, forms, and functionality.
- Test email: Send and receive test emails to confirm MX records are working correctly
- Check WHOIS privacy: Enable WHOIS privacy at the new registrar if it was previously active
- Verify SSL certificate: Ensure your SSL certificate is still valid and working. Some certificates are tied to the hosting provider, not the registrar, so they typically remain unaffected.
- Update auto-renewal: Set up auto-renewal at the new registrar to prevent accidental expiration
- Raise TTL values: Once everything is confirmed working, raise your DNS TTL values back to normal (3600 seconds or higher)
Frequently Asked Questions
How long does a domain transfer take?
Most transfers complete within 3-5 days. The fastest transfers (with immediate approval from both sides) can complete in a few hours. The maximum is typically 7 days, after which the transfer auto-completes if not rejected.
Does a domain transfer cause downtime?
It shouldn't, if done correctly. The domain continues to resolve using the existing nameservers and DNS records during the transfer process. Downtime only occurs if DNS records are changed or misconfigured during the transfer.
Will I lose my remaining registration time?
No. When you transfer a domain, one year is added to the existing registration period. If your domain was set to expire in 8 months, after the transfer it will expire in 20 months (8 existing + 12 added).
Can I transfer a domain that's about to expire?
It's risky. Most registrars won't accept transfers for domains expiring within 15 days. Renew the domain at the current registrar first, then initiate the transfer. The renewal time will carry over.
How much does a domain transfer cost?
Transfer fees typically match the cost of one year of registration ($10-15 for .com domains). This fee includes a one-year extension of your registration. Some registrars like Serverlys offer free or discounted transfers for certain TLDs.