Domain Transfer-In Process

Modified on: Tue, 16 Sep, 2025 at 3:03 PM

Transferring your domain into HighLevel lets you manage registration, renewal, DNS, and product connections (email, sites, client portals) all in one place. This overview of domain transfer explains the full transfer-in workflow, including eligibility, step-by-step instructions, and troubleshooting.


TABLE OF CONTENTS


Domain transfer-in may not be enabled on all accounts. If you do not see the option for domain transfer, please contact support to have it enabled.



Eligibility & Prerequisites


Before you start, confirm that your domain meets industry requirements and is ready for domain transfer:


  • Domain is older than 60 days (ICANN rule).

  • Domain is unlocked at your current registrar.

  • WHOIS privacy protection is turned off.

  • DNSSEC (if enabled) is disabled.

  • You have access to the EPP/Auth code from your registrar.

  • Your contact email is correct in WHOIS, since transfer approval emails will be sent there.

Transfer-In Workflow


Step 1: Start Transfer


In your location, navigate to Settings > Domains & URL Redirects > Domains Tab > Purchase/Transfer Domains Button > Transfer-In Domain Button.




Enter the domain name you want to transfer and click the Continue button.



Step 2: Eligibility Check


The system runs an eligibility check to confirm ICANN requirements. If the domain is eligible for transfer you can continue with the transfer process.


During the Eligibility Check, We verify whether your domain qualifies to be transferred into the platform. The system evaluates both registrar-level rules and technical readiness. If the domain is eligible for transfer you can continue with the transfer process. When a domain is eligible for transfer you can see the 

  • Domain Name
  • Current Domain Registrar
  • Current expiration and new expiration (extended by 1 year)
  • Applicable fee for the extension of expiry date.


A domain is not eligible for transfer when:

  • Its current registrar is not supported.
  • It has been previously purchased internally.
  • It’s TLD is not supported.
  • It has been purchased or transferred in last 60 days
  • It has an EPP status that does not allow for transfers (eg, pendingDelete, redemptionPeriod, serverHold etc)
  • The transfer would result in the term of the domain exceeding the maximum allowed term
  • Other (more obscure) reason

In these cases, the Continue button will be disabled, and a relevant error message will explain why the domain cannot be transferred at this time.


Step 3: Review and Save DNS Records


When you transfer your domain from your current registrar, such as GoDaddy, Namecheap, etc., it’s important to ensure that all DNS records configured with your current DNS provider are accurately transferred as well. This is crucial to keep your existing services like websites, email, and others working smoothly after the transfer. If the DNS records are not reviewed properly, your website might go down or your email may stop working. To avoid such issues, it is strongly recommended to carefully review and replicate your DNS records before completing the domain transfer.


Retrieving DNS records

Users can choose between two methods to retrieve your DNS records by A) uploading the DNS zone file from your current DNS provider or B) auto scanning the DNS records:


A) Upload DNS Zone File


This method is recommended if you want to import all DNS records from your current DNS provider without missing any of the existing records. This file contains all your domain’s DNS entries including A, CNAME, TXT, MX, and other record types.


Get the DNS Zone file from your current DNS provider:

  1. Login into your current DNS provider or where you purchased your domain originally.

    NOTE: Your domain registrar and DNS provider can be different if you’ve changed the nameservers where you bought your domain. For example, if you bought your domain on GoDaddy but pointed it to Cloudflare by updating the nameservers, then Cloudflare is now managing your DNS. In that case, you’ll need to log in to Cloudflare to access your DNS records (zone file).

  2. Go to DNS settings of the domain you want to transfer

  3. Locate the option to export DNS zone/records file

  4. In case you can’t find such option, reach out to your current DNS provider or registrar’s support to get it


Go to your registrar below to follow step by step process:

  • GoDaddy - Learn about how to upload zone files from GoDaddy HERE.

  • Cloudflare - Learn about how to upload zone files from Cloudflare HERE.

  • NameCheap - Currently, Namecheap does not offer a downloadable zone file, so you may need to recreate the records manually or reach out to support to access the records. Link to manually extract the records HERE.

  • IONOS


B) Auto Scan DNS Records


This method is convenient and requires no prior setup. In this method, your existing DNS records will be automatically scanned, but some of the existing records may not get detected in the scan. So, to avoid interruptions in your existing connected services like funnel, website etc post transfer, it is highly recommended to manually cross check the scanned records with your records at your current DNS provider or registrar and add/edit records if required.


NOTE: Your domain registrar and DNS provider can be different if you’ve updated the nameserver records at your registrar. For example, if you purchased your domain from GoDaddy but pointed it to Cloudflare by changing the nameservers, then Cloudflare becomes your DNS provider. In that case, you’ll need to log in to Cloudflare to view and compare your DNS records.


Reviewing DNS Records


Once records are retrieved, you can now review your DNS records. In the DNS table shown you can:

  • View all DNS entries in a table format, categorized by record type (e.g., A, CNAME, TXT, MX).
  • Add new records by clicking “Add Record”.
  • Edit or delete individual records as needed.
  • Search records using any field (name, type, value).

HighLevel Interface:


GoDaddy Interface: 


NOTE: It is highly recommended to manually cross-check the scanned DNS records with the records currently available at your DNS provider or registrar (where you originally purchased your domain). If any record is missed during the automatic scan, it could cause your website to go down or your email to stop working after the transfer. That’s why it’s important to carefully review and compare the scanned records with your existing ones, and make any necessary additions or changes to ensure nothing is left out.



Step 4: Finalize Transfer


The Finalize Transfer step is where you complete the authorization process to move your domain from your current registrar (like GoDaddy, Namecheap, IONOS, etc.) to HighLevel. This step ensures that your domain and related services continue working smoothly after the transfer.



What Happens During This Step


On the Finalize Transfer screen, you will:

  1. Log into your current registrar (where you originally registered the domain)

  2. Disable DNSSEC & Whois Privacy
    1. Before initiating a domain transfer, it is important to disable DNSSEC and remove Whois privacy protection from your current registrar. General Instructions (the details can vary):
      1. Log in to your current registrar account.
      2. Go to DNS or Domain Settings.
      3. Find the option for DNSSEC and disable it.
      4. If Whois Privacy Protection is enabled, turn it off.
      5. Save changes

    2. GoDaddy: Disabling DNSSEC and Removing Whois Privacy Note: It may take a few minutes for the DNSSEC record to be fully removed. You’ll see a confirmation on GoDaddy once the setting is updated.

    3. NameCheap: Disabling DNSSEC and Removing Whois Privacy

    4. IONOS: Disabling DNSSEC and Removing Whois Privacy

  3. Unlock your domain and request authorization code (EPP code)
    1. Before transferring your domain, it must be unlocked, and you’ll need an authorization code (also called an EPP or transfer code) from your current registrar. General Instructions (the details can vary):
      1. Log in to your current registrar account (e.g., GoDaddy, Namecheap, IONOS).
      2. Go to your domain management or domain settings section.
      3. Look for the Domain Lock or Registrar Lock option.
      4. Disable or turn off the lock to unlock the domain.
      5. Once unlocked, locate the option to get the authorization code (may be labeled EPP code, Transfer Code, or AuthInfo).
      6. The code may either be displayed on screen or sent to your registered email.

    2. GoDaddy: You can read in detail about transferring your domain out of GoDaddy HERE.

    3. Namecheap: You can read in detail about transferring your domain out of Namecheap HERE. Note: Make sure WhoisGuard is disabled before requesting the auth code.

    4. IONOS: You can read in detail about transferring your domain out of Ionos HERE.

  4. Submit the transfer and complete payment.When the Confirm and Finalize Transfer button is clicked, we will:
    1. Validate domain unlock status, auth code and for any other registry level statuses.
    2. If the domain is valid for transfer, charge the wallet for the fee.
    3. Submit the transfer request

Step 5: Approve In-Progress Transfer


Once you’ve submitted your domain transfer request, the final step is to approve the transfer at your current registrar. Until you do that, the transfer stays in a pending state and won’t complete.



Why Approval Is Required


Domain transfers require explicit confirmation from your current registrar (such as GoDaddy, Namecheap, or IONOS) to protect against unauthorized changes. You must manually approve the transfer either through your email inbox or your registrar’s dashboard.

If no action is taken, the transfer may auto-approve after 5–7 days, depending on the registrar’s policy.


How to Approve the Transfer at Your Registrar


Here’s how to approve the transfer depending on who your registrar is:

GoDaddy

  • Option 1: Email Approval
  • Option 2: Dashboard Approval

Namecheap: Transfer a domain out of Namecheap.


IONOS: Domain Transfer Out of Ionos

  • Sign in to IONOS
  • Go to Domains & SSL
  • Click on the domain you’re transferring
  • Look for a Pending Transfer prompt or email instructions
  • Approve the transfer when prompted



After Transfer Approval


Once you approve the transfer:

  • Your domain is moved under our registrar partner (Cloudflare)
  • You’ll see it listed under Internal Domains in your account
  • You can manage DNS, renewals, and billing right inside our platform
  • The Manage button becomes active so you can take further actions

If the Transfer Is Rejected



Your transfer can be rejected if:

  • You manually cancel it
  • Your registrar blocks it (e.g., 60-day lock)
  • You don’t approve it in time


When this happens:

  • The domain status shows as Rejected
  • The Transfer to Us button reappears so you can try again

Step 6: After the Transfer


Verify DNS records: make sure your domain points correctly to sites, funnels, or email.


Reconnect products:


  • Email sending domains

  • Website/funnel domains

  • Client portal or white-label login domains


Set up auto-renew (recommended).


Common Issues & Troubleshooting


Auth code rejected → Double-check with registrar, request a new code.


Transfer email not received → Verify WHOIS contact email; check spam/junk folders.


Domain locked → Ensure registrar lock is fully removed.


Transfer takes longer than 7 days → Some registrars delay releases; check status in your current registrar’s panel.


Website/email downtime → Verify DNS records were imported correctly.


See the Troubleshooting section in Connecting Your Domain on GHL - A Guide.


Frequently Asked Questions


Q: How much does transferring in a domain cost?

You’ll be charged for a 1-year renewal, added to your existing expiration date.


Q: Can I transfer in all domain extensions?

Most common TLDs (.com, .net, .org, etc.) are supported. Certain country-code TLDs may not be.


Q: What if I want to transfer out later?

You can unlock your domain and obtain an Auth code to transfer out to another registrar (see [Domain Transfer Out guide]).


Q: What if some DNS records are missing after auto-scan?

Always manually cross-check the scanned records with your current DNS provider. Auto-scanning might miss some records. You can edit, delete, or add records before finalizing the transfer.


Q: What if my nameservers are managed by someone else (e.g., Cloudflare), but the domain is with GoDaddy?

Then your DNS provider is Cloudflare even if your registrar is GoDaddy. When transferring the domain, your DNS setup will still be managed at Cloudflare unless you switch nameservers post-transfer.


Q: What if my registrar and DNS provider are different?

Then you'll need to log in to your DNS provider (e.g., Cloudflare) to export or review DNS records. The registrar only holds the domain, not the DNS settings.


Q: How long does it take after I finalize the transfer?

Once submitted, transfers typically complete within 1-5 days depending on your registrar. Some domains may complete faster if approved manually.


Q: I don’t see the option to unlock my domain. What should I do?

Some registrars hide this setting under “Security” or “Transfer Settings.” If it’s not visible, search their help center or contact their support.


Q: What if my auth code is wrong?

You’ll see an error. Double-check with your registrar and make sure the domain is also unlocked.


Q: Will transferring my domain cause downtime?

Not if DNS records are accurately reviewed and migrated before the transfer. Always cross-check.


Q: Can I transfer my domain back to another registrar later?

Yes but typically, you’ll need to wait 60 days after the last transfer, per ICANN rules.


Q: Will transferring my domain cause downtime?

Not if DNS records are accurately reviewed and migrated before the transfer. Always cross-check.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article