How to Transfer Your Domain Name to a New Registrar [2025]

Introduction

Transferring a domain name to a new registrar is a common procedure for domain owners. It involves moving your domain’s management from your current registrar to a different registrar of your choice. This process is regulated by ICANN (the Internet Corporation for Assigned Names and Numbers) to ensure security and fairness. In this comprehensive guide, we will walk you through how to transfer your domain name to a new registrar step by step. We will also explain why you might want to transfer, what you need to prepare beforehand, and how to handle common issues that can arise during a domain transfer. By following this formal, professional guide, you can ensure your domain transfer goes smoothly with minimal downtime or complications.

Table of Contents

• Why Transfer a Domain Name?
• Prerequisites Before Transferring
• Step-by-Step Guide
  • Unlock Your Domain
  • Disable WHOIS Protection
  • Obtain the Authorization Code (EPP Code)
  • Verify Admin Contact Information
  • Initiate the Transfer with the New Registrar
  • Approve the Transfer Request
  • Wait for Transfer Completion
• Common Issues and Troubleshooting
• Best Practices for a Smooth Transfer
• External Resources and References

Why Transfer a Domain Name?

Domain name transfers happen for several reasons. Understanding why people transfer domains can help you decide if a transfer is right for you:

• Better Pricing or Service: Sometimes a new registrar offers more competitive pricing for renewals or better customer service and support. Over time, these factors can motivate a move to a registrar that better meets your needs.
• Feature Set: Registrars offer different features. You might find a new registrar with a more user-friendly control panel, additional DNS management tools, enhanced security features (like two-factor authentication), or bundled services (such as email or hosting) that your current registrar lacks.
• Consolidation: Many domain owners prefer to manage all their domain names in one place for convenience. If you have domains spread across multiple registrars, you may transfer some so that all domains are under a single registrar account.
• Ownership Change: If you purchased a domain from someone else or as part of a project acquisition, the domain might be at a registrar you don’t normally use. Transferring it to your preferred registrar can simplify management.
• Dissatisfaction with Current Registrar: If you’ve experienced problems – for example, poor support, unexpected fees, or limited features – you might transfer your domain as a solution. Moving to a new registrar can provide a fresh start under terms you find more favorable.

It’s important to note that transferring a domain does not affect the domain’s ownership or the functioning of your website/email attached to the domain. A well-executed transfer is seamless to end-users; your domain continues to resolve as usual. The process is essentially administrative – changing which company manages your domain registration. However, during the transfer window, you need to be attentive to emails and confirmations to avoid any interruption.

Prerequisites Before Transferring

Before initiating a domain transfer, there are several prerequisites and preparations to address:

• Domain Eligibility: Verify that your domain name is eligible for transfer. Under ICANN rules, domains cannot be transferred within 60 days of initial registration or within 60 days of a previous transfer. Additionally, if you recently updated the registrant contact information (such as the owner’s name, organization or email), a 60-day transfer lock may apply (unless you opted out of that lock during the update). Ensure your domain is older than 60 days and not currently under any transfer lock.
• Good Standing: The domain should not be in a “redemption” or “pending delete” status. Generally, it should be active (not expired) or only recently renewed. It’s often recommended to transfer a domain at least a couple of weeks before its expiration date to avoid complications. If the domain is close to expiring, you may either renew it first or ensure the transfer completes before expiration. (Most transfers will add an additional year to the domain’s expiration upon completion, but an expired domain might not transfer normally.)
• Access to Administrative Email: Ensure that the administrative contact email address listed in the domain’s WHOIS record is current and accessible. During a transfer, approval emails are typically sent to the domain’s administrative contact (for many TLDs, especially legacy gTLDs like .com, .net, etc.). If that email is outdated or incorrect, you will not receive the authorization message. Before initiating transfer, update the admin email through your current registrar if needed (this might trigger the 60-day lock if it changes the registrant information, so ideally it’s correct from the start). In the era of GDPR, many registrars privacy-mask WHOIS data; in such cases, be sure you know which email will receive transfer confirmations – it may be the registrant email on file in your account profile.
• Registrar-Specific Requirements: Check if your current registrar has any special procedures or fees for transfers. While most do not charge you to leave, you should familiarize yourself with their domain control panel to find the settings we’ll need (unlocking, auth code, etc.). Similarly, set up an account with the new registrar where you intend to transfer, and ensure you are ready to pay the transfer fee (which covers a one-year renewal in most cases).
• DNS Considerations: A transfer generally does not modify DNS settings. The nameservers associated with your domain will remain the same through the transfer, so ideally your website/email should not experience downtime purely due to the transfer. However, it’s good practice to note your current DNS settings. If you plan to change nameservers or DNS hosting after the transfer (for example, using the new registrar’s DNS), do so after the transfer completes to avoid mixing changes with the transfer process. Keeping DNS unchanged during the move ensures continuity.

By taking care of these prerequisites, you set the stage for a smooth transfer process. Essentially, you are making sure the domain is transferable (unlocked and past any age locks), that you can respond to approval requests, and that switching registrars won’t inadvertently disrupt your services.

Step-by-Step Guide

Below is the step-by-step process to transfer your domain name to a new registrar. Each step is critical to a successful transfer. We’ll describe what to do and what to expect at every stage:

Step 1: Unlock Your Domain

By default, most domains are set in a “Registrar Lock” or “Transfer Lock” status to prevent unauthorized transfers. The first step is to remove this lock:

Log in to your current registrar’s control panel for your domain. Navigate to the domain management section and look for an option related to “Transfer Lock” or “Domain Lock.” It might be a simple toggle or checkbox. The interface wording varies; common labels include “Unlock Domain”, “Registrar Lock: ON/OFF”, or “Allow Transfer”. If the domain is locked, switch it to the unlocked status.

After unlocking, the registrar will usually display a confirmation that the domain is now unlocked for transfer. Technically, this changes the domain status from something like CLIENT TRANSFER PROHIBITED to OK or ACTIVE in the registry records, indicating it can be transferred. Some registrars also send an email notification confirming that the lock was removed (as a security measure to alert the domain owner).

Note: If you cannot find the unlock setting, contact your registrar’s support. In a few cases, domains may be automatically unlocked by the registrar when you request a transfer, but generally you must do this manually. A domain must be unlocked, otherwise any transfer request initiated by the gaining (new) registrar will be rejected by the current registrar’s system immediately.

Step 2: Disable WHOIS Protection

If you have WHOIS privacy protection (also known as private registration) enabled on the domain, you should disable it before initiating the transfer. WHOIS privacy replaces your public contact info with proxy details to shield your identity. While that is useful day-to-day, it can interfere with the transfer process because approval emails may be sent to the proxy service email instead of to you.

In your domain settings, locate the WHOIS Privacy/Protection option and turn it off (often labeled as “Disable Privacy” or “Reveal WHOIS Information”). Disabling privacy will unmask the domain’s registrant and admin contact information to the public WHOIS. More importantly, it ensures that the transfer authorization email goes to your actual email address and not to a privacy proxy.

After turning privacy off, confirm that the registrant/admin email listed for the domain is indeed yours (as noted in prerequisites). You can do a quick WHOIS lookup to verify that your email is now showing. If it still shows the privacy service, there might be a delay or the registrar might only reveal it to the gaining registrar behind the scenes – in any case, make sure you have access to the listed email.

Note: Some modern registrars (post-GDPR) no longer require turning off privacy because they have mechanisms to forward transfer emails even if WHOIS is masked. However, to be safe, it’s recommended to disable it unless your registrar explicitly advises otherwise. This step prevents missed communications. You can usually re-enable privacy after the transfer at the new registrar if you prefer.

Step 3: Obtain the Authorization Code (EPP Code)

The authorization code (also known as an EPP code, transfer key, or Auth-Code) is a unique code for your domain. It acts like a password that you must provide to the new registrar to authorize the transfer. This code is crucial for security – it proves that you (the domain owner) consent to the transfer.

Request or retrieve your domain’s EPP/authorization code from your current registrar. In many registrar dashboards, there will be a button or link such as “Get Auth Code” or “Transfer Out Code.” Upon clicking, the code might be displayed to you directly on screen, or it might be emailed to the registrant/admin email address on file (for security, some registrars prefer email delivery). In some cases, you may have to open a support ticket or send an email request to get the code, but this practice is less common now – most allow self-service retrieval.

The auth code is typically a string of letters, numbers, and special characters. It might look something like K34#8$1YZ (each registrar’s format can differ). Treat this code as sensitive information – do not share it except with the new registrar during the transfer process. If anyone else obtains this code, they could initiate a transfer of your domain without your permission.

Note: Registrars are required by ICANN to provide this code within five calendar days of your request (often it’s instantaneous). If you’re unable to get the code via the account interface, contact the support team of your current registrar. Ensure you copy the code exactly as provided, including any special characters or case sensitivity. You will need to provide this code to the new registrar in the next steps.

Step 4: Verify Admin Contact Information

Now that the domain is unlocked and you have the auth code, double-check that the administrative contact information on the domain is correct – especially the email address. As mentioned, the transfer approval request (known as the Form of Authorization, or FOA) will be sent to this email for many domain transfers.

Perform a WHOIS lookup on your domain to see the current admin/registrant email. You can use the registrar’s WHOIS tool or a public WHOIS lookup service. If WHOIS privacy is off, you should see your email listed. If privacy is on (and your registrar forwards emails), ensure that you can receive forwarded mail from the privacy service.

Update the contact information if necessary: If you find any errors in the contact details (e.g., old email address, outdated phone number, etc.), update them in your current registrar’s account before initiating the transfer. Be mindful: as noted earlier, changing the registrant’s organization or email on some domains can trigger a 60-day transfer lock (per ICANN’s Transfer Policy) unless you explicitly opt out of that lock at the time of change. If you must correct something and a lock would apply, you might opt out of the lock (if the registrar provides that option) or delay the transfer until the lock period passes.

Also, check your email spam/junk folder settings to be sure that emails from registrars aren’t filtered out. During the transfer, you will receive emails from both your current (losing) registrar and the new (gaining) registrar – make sure you can receive those. It may help to add both registrars’ domains to your email whitelist or contacts.

Note: Verifying contact info is not just about the transfer emails; it’s also a good practice to keep WHOIS data accurate as required by ICANN policy. Inaccurate WHOIS data can, in extreme cases, lead to a domain registration being suspended. So this step ensures both a smooth transfer and compliance with rules.

Step 5: Initiate the Transfer with the New Registrar

With your domain prepared on the current registrar’s side, the next step is to go to your new registrar (the one you want to transfer into) and initiate the transfer request. The exact process can vary slightly by registrar, but generally:

Log in to your account at the new registrar (or create an account if you haven’t done so already). Look for an option like “Transfer a Domain” or “Transfer Domains.” This will usually prompt you to enter the domain name you wish to transfer.

Enter your domain name (e.g., yourdomain.com) and follow the prompts. You will be asked to provide the Authorization/EPP code that you obtained from the current registrar. Input the code exactly as given. The new registrar’s system may immediately validate the code and domain status. For example, it might check: Is the domain unlocked? Does the auth code match? If there’s an issue (wrong code or domain lock still on), you will get an error and you’ll need to resolve that before proceeding.

Once validated, you will need to pay the transfer fee to the new registrar. Typically, the cost of a transfer includes a one-year renewal of your domain (the added year will be tacked onto your current expiration date upon completion). Complete the checkout or payment process as required.

After initiating, the new registrar will formally submit a transfer request to the registry for your domain. At this point, the status of your domain at the registry will likely switch to “pendingTransfer,” indicating a transfer is in progress.

Note: Initiating a transfer does not automatically cancel anything at your old registrar – it just sets the process in motion. You will now move to the approval phase. The responsibility shifts somewhat: the new registrar coordinates the transfer with the registry, and the current registrar will be alerted of the request, which brings us to the approval step.

Step 6: Approve the Transfer Request

Once the transfer is initiated, typically two important emails are sent out:

1. From the New Registrar (Gaining Registrar): An email often titled something like “Please Confirm Domain Transfer for yourdomain.com.” This is the Form of Authorization (FOA) where you, as the domain owner, must explicitly approve the incoming transfer. Follow the instructions in that email – usually, it contains a link you need to click to approve, or a code to paste on a confirmation page. By approving, you’re informing the new registrar that you authorize them to proceed with the transfer.
2. From the Current Registrar (Losing Registrar): An email notifying you that a transfer request was received for your domain. Depending on the registrar, this email may give you a chance to explicitly confirm or decline the transfer. In many cases, if you want the transfer to proceed, you do not need to take action on this email (the transfer will auto-complete after a certain number of days if you do nothing). However, if you want to expedite the process, some registrars allow you to approve the transfer immediately in their system, which can speed up the completion. Conversely, if this was unauthorized, you could cancel the transfer in this step. Since you do want to transfer, either actively approve it if that option is given (for speed) or simply allow it to happen.

Monitor your email (the admin contact email) closely after initiating the transfer. When you get the new registrar’s approval email, act on it as soon as possible. Without your approval, the transfer will not proceed. If you do not see the email within an hour or two, check spam folders. If still nothing, contact the new registrar – they can resend the FOA email.

Additionally, some registrars have an internal dashboard where you can see pending outgoing transfers. It’s worth logging into your account at the old registrar after initiating the transfer. If they have a section for “pending transfers” or “transfer out,” you might find a button to ACKNOWLEDGE or APPROVE the transfer immediately. Clicking that (after you’ve confirmed via the new registrar’s email) can cut down the waiting time significantly. Not all registrars offer this, but many do, as a courtesy to not hold your domain longer than necessary.

Note: If for some reason you change your mind, the losing registrar’s email often also gives a way to cancel the transfer (by explicitly denying it). If you do nothing, transfers typically complete automatically. The default ICANN transfer process gives the losing registrar up to five days to release the domain if no action is taken. Our goal, having approved everything, is that the transfer will be finalized, usually sooner.

Step 7: Wait for Transfer Completion

After you have approved the transfer with the new registrar (and possibly confirmed with the old registrar), the transfer process is essentially in motion and you must wait for the registry and registrars to complete the handover. In many cases, if you’ve done all approvals, the transfer can complete within a few hours to a couple of days. However, ICANN policy allows up to five days for the losing registrar to release the domain.

During this waiting period, your domain should continue to function normally. You can continue to use your website and email without interruption. The DNS settings remain intact through the transfer – they are not altered automatically. The only thing changing is the registrar of record for the domain in the registry’s database.

Keep an eye on status updates: The new registrar may provide a status indicator (e.g., “Transfer in progress” in your account panel). Similarly, the old registrar might show the domain as “pending transfer.” You usually won’t need to intervene further. If you approved via the emails, it’s largely an automated process from here.

Within a few days (often sooner), you should receive a confirmation email from the new registrar informing you that the transfer is complete. The domain will now appear in your account at the new registrar. The expiration date should have extended by one year (except in rare cases or certain country-code TLDs where a year might not be added).

It’s a good practice, once the transfer is done, to verify the domain’s details at the new registrar. Make sure your contact information carried over correctly (sometimes the Whois may show the old info until you update it, depending on the transfer method). Also, if you want WHOIS privacy at the new registrar and it wasn’t automatically re-enabled, you can turn it on now. Lastly, confirm that the domain is once again locked at the new registrar (most will auto-lock it upon intake, but double-check the security settings so the domain isn’t inadvertently left unlocked after transfer).

The transfer process is now complete: you have successfully moved your domain to a new registrar!

Common Issues and Troubleshooting

Even with careful preparation, you might encounter some hiccups during a domain transfer. Below are common issues and how to address them:

• Incorrect Authorization Code: If the auth/EPP code you entered at the new registrar is rejected, double-check the code. Copy-paste it directly from the source to avoid typos. Ensure no extra spaces are included. If it still fails, request a new code from the current registrar – sometimes codes can be regenerated if suspected to be compromised. Remember, some auth codes are case-sensitive.
• Domain is Locked or Not Eligible: If the new registrar informs you that the domain is locked or not allowed to transfer, verify the status. Did you definitely unlock it at the old registrar? Log back into the old registrar and confirm the domain’s lock status is off. If it is unlocked but you still see issues, confirm the domain isn’t in that 60-day no-transfer window after registration or contact changes. If it is, you’ll have to wait until that period elapses. In rare cases, certain TLDs have specific transfer rules – verify if your domain extension has any special requirements.
• Did Not Receive Confirmation Emails: If you haven’t gotten the transfer approval emails, check your spam folder and any email forwarding/privacy settings. If you suspect the email went to a privacy service, you may need to contact your current registrar’s support to get assistance. As a workaround, some registrars allow approving transfers via the account portal (as mentioned before). If the new registrar’s FOA email is missing, ask their support to resend it. If absolutely unable to receive it, you might change the admin email to a different address (note: this could trigger a new 60-day lock unless it’s just a typo correction and not considered a registrant change – policies can vary here).
• Transfer Still “Pending” After Several Days: Domain transfers should typically complete within 5 days maximum if you’ve done all approvals. If it’s been that long and the status is still pending, reach out to both registrars. It’s possible the losing registrar is waiting the full allowed time. Some registrars don’t auto-approve outgoing transfers quickly; in that case, contacting them might allow you to manually expedite it. Ensure that the domain wasn’t accidentally re-locked or the transfer wasn’t canceled due to a missed email. Support can usually tell exactly where it’s stuck.
• Domain Expiration During Transfer: If your domain happened to expire during the transfer process (which ideally should be avoided), what happens can depend on timing. Generally, if a transfer is initiated while a domain is still active (even if expiration passes during the process), the transfer should still complete and the domain will renew for the additional year. However, if the domain was already expired or in redemption, transfers may be rejected. In such cases, you might have to renew at the old registrar first (paying a redemption fee if applicable), then transfer. Always better to handle renewals vs. transfers in a careful sequence to avoid this scenario.
• TLD-Specific Issues: Some country-code top-level domains (ccTLDs) have unique transfer processes (for example, .UK uses a “TAG” system instead of an auth code, .EU requires initiating at the gaining registrar without a code, etc.). If you are transferring a ccTLD, ensure you’ve followed that registry’s specific process. Troubleshoot by reading the documentation for that TLD or contacting the registrars, because the steps above are general and apply mostly to generic TLDs like .com, .net, .org, etc.

If any issue arises, do not panic. Domain transfers can always be re-attempted if they fail (you won’t “lose” your domain simply because a transfer failed – it will remain with the original registrar if not completed). You may need to start over if a transfer fails due to an error, but identify the cause (incorrect code, still locked, etc.) and fix that first. Keep communication lines open with both your new and old registrar’s support teams; they can often provide insight or speed things along if something gets stuck.

Best Practices for a Smooth Transfer

To ensure your domain transfer goes as smoothly as possible, consider these best practices and tips:

• Time Your Transfer Wisely: Avoid initiating a transfer last-minute before a domain’s expiration or during critical business periods. It’s best to transfer at least a couple of weeks before expiration. If your domain expires in a few days, it might be safer to renew it first (to avoid service disruption) and then transfer. Also, be mindful of any ongoing website launches or email campaigns – transfer during a calm period, since you’ll be busy with approval emails and monitoring the process.
• Maintain Access to Both Registrars: Keep your accounts active at both the losing and gaining registrar until the process is fully complete. Do not terminate your old registrar account or assume everything is done immediately. Likewise, do not let your new registrar account lapse. After completion, verify the domain in the new account and also verify it’s gone from the old account.
• Save Documentation: Save copies of relevant information: the auth code (until used), screenshots of the domain’s unlocked status, and any emails related to the transfer. Having a paper trail is helpful in case you need to escalate an issue with ICANN or the registrars. For instance, if the current registrar does not provide the auth code or is stalling the transfer without cause, you have evidence of your requests and their responses, which can be used in a complaint to ICANN if necessary.
• Update DNS After Transfer (if Needed): As noted, your nameservers remain the same through a transfer. If you intend to switch to using your new registrar’s DNS or any other DNS changes, wait until the transfer finishes to make those changes. Doing so beforehand can sometimes complicate matters (for example, if you pointed to the old registrar’s DNS and then leave, you’d want to repoint to new DNS after). Essentially, handle one thing at a time: first transfer, then adjust DNS if required.
• Re-enable Domain Lock and Privacy: After the transfer, remember to turn the registrar lock back on at your new registrar to protect against any unwanted transfers moving forward. Transfers require that lock off, but once done, you want your domain secured again. Similarly, if you had WHOIS privacy and want it on, re-enable it at the new registrar (if it didn’t come along or wasn’t automatic). This returns your domain to a secure state post-transfer.
• Know Support Channels: Each registrar has support available (ticket, phone, chat). Don’t hesitate to use them if you have uncertainties. For example, if the transfer isn’t visible in your new account after a day, ask the new registrar to confirm it’s in progress. If the old registrar hasn’t sent any email, ask if the domain is properly unlocked and if there are any reasons on their end that would block a transfer.
• Multiple Domains Strategy: If you plan to transfer several domains, it might be wise to transfer one first as a test run (especially if the domains are critical). Once you see the process works as expected, you can initiate bulk transfers for the rest. This way, you minimize risk and learn the nuances of the particular registrar’s system with a low-stakes domain before doing all of them.

By following these best practices, you reduce the chances of unexpected problems and make the transfer experience efficient. In summary, preparation, timing, and communication are key. When in doubt, refer to your registrars’ help articles or reach out to their support – domain transfers are a routine task for them, and they can guide you through any registrar-specific details.

External Resources and References

For further reading and official information on domain transfers, you may consult the following authoritative resources:

• ICANN – FAQs for Registrants: Transferring Your Domain Name
• ICANN – Inter-Registrar Transfer Policy (Official policy outlining rules and procedures for domain transfers)
• ICANN WHOIS Lookup Tool (To check your domain’s current registrar, status, and contact information before and after transfer)
• ICANN – About Authorization Codes (Information on what EPP/authorization codes are and how they function in domain transfers)

These resources provide additional guidance and clarify policies directly from ICANN and other reliable entities. Always ensure you follow the latest policies, as domain transfer rules can evolve over time.