Transfer and Manage External Domains Through Domain Dashboard

Modified on: Thu, 10 Jul, 2025 at 10:54 PM

This guide walks you through how to transfer your existing domains from registrars like GoDaddy or Namecheap into HighLevel using the Domain Transfer-In feature. By the end of this article, you’ll understand how to configure the feature, perform a successful domain transfer, and manage your DNS settings—all from one place. Whether you’re centralizing your workflows or improving DNS security, this guide ensures you follow each step with clarity and confidence.


TABLE OF CONTENTS


What is Domain Transfer-In


Domain Transfer-In is a built-in HighLevel feature that allows users to move domain ownership and management from third-party registrars (such as GoDaddy, Namecheap, etc.) into the HighLevel platform. This simplifies your workflow by letting you purchase, transfer, renew, and manage DNS records without ever leaving your sub-account. The Domains page acts as your centralized dashboard for all domain activity, improving visibility and control.


When you initiate a domain transfer, HighLevel guides you through a 5-step process—starting with domain entry and ending with approval from your current registrar. The system automatically checks transfer eligibility, allows DNS record import or review, and ensures a secure finalization using an EPP (authorization) code. Once complete, the transferred domain integrates instantly with your websites, funnels, client portals, and email systems—all within HighLevel.


Key Benefits of Domain Transfer-In Feature in HighLevel


  • Centralized Control: Manage purchases, renewals, DNS settings, and product connections directly from your sub-account’s Domains dashboard.

  • Zero Downtime with DNS Verification: Preserve critical services like email and websites by reviewing or importing DNS records during the transfer process.

  • Transparent Pricing with Built-in Renewals: Transfer fees are fixed and clearly shown upfront. You also gain an additional year added to your existing domain’s renewal period.

  • Secure Management Without External Logins: No need to log into GoDaddy or Namecheap post-transfer—manage all domain settings directly within HighLevel.

  • Instant Product Integration: Transferred domains instantly connect to funnels, websites, blogs, email tools, and client portals without manual mapping.


How to Configure Domain Transfer-In


Follow these detailed steps to enable and complete a domain transfer into HighLevel. This guide also includes important prerequisites to ensure a smooth experience.



Step 1: Enable Domain Purchase (Agency Settings)


  • Switch to Agency View by clicking the location dropdown at the top-left corner of your screen and selecting Agency.



  • Navigate to Settings → Company → Domain Purchase. Toggle the setting ON to activate domain purchasing functionality across the platform.




Step 2: Enable Domain Purchase for Sub-Accounts



  • Go to Settings → Domain Purchase



  • Enable domain purchasing individually for each sub-account that will use the Domain Transfer-In feature.




Step 3: Enable Domain Transfer-In in Labs


  • Go to Settings → Labs → Sub-Account



  • Locate Domain Transfer-In and click Manage



  • Choose the sub-accounts where this feature should be active.




Before starting the transfer, ensure:

You must be an Admin of the sub-account.

The domain should be at least 60 days old and not in a locked or pending status.

You must have access to your registrar account (e.g., GoDaddy or Namecheap).

Your HighLevel Wallet must have sufficient funds for the transfer fee.

You should be able to unlock the domain, disable DNSSEC, and turn off Whois Privacy at your registrar.

It’s recommended to export your current DNS zone file for backup or import.




Step 4: Initiate Domain Transfer


  • Go to the Domains page within the relevant sub-account.




  • If the domain already exists as external, click Transfer-In.



  • Otherwise, click Purchase/Transfer Domain → Transfer Domain.




Step 5: Complete the Eligibility Check


  • The system will verify whether the domain is eligible for transfer. You’ll also see the transfer fee and domain expiration details here.




Step 6: Review or Upload DNS Records


  • Choose to auto-scan DNS records or upload a zone file from your registrar. Double-check all entries—especially for email, website, and CNAME records—to avoid service disruptions.




Step 7: Finalize the Transfer


  • At your current registrar:

    • Unlock the domain

    • Disable DNSSEC

    • Turn off Whois Privacy

    • Copy the EPP (authorization) code

  • Paste the EPP code into HighLevel and confirm the transfer.

  • The transfer fee is deducted from your HighLevel Wallet.





Step 8: Approve the Transfer at Registrar End


  • Your registrar may send you an approval email or require you to manually approve the transfer in their dashboard. Once approved, the domain becomes internal and fully manageable within your HIghLevel account.


Frequently Asked Questions


Q: Will my website or email go down during the transfer?

No, as long as DNS records are reviewed and correctly configured during the transfer process, there should be no downtime.


Q: How do I get my domain’s authorization (EPP) code?

Log into your current domain registrar’s dashboard. The EPP code is usually available in the domain management section.


Q: Can I transfer any domain extension (TLD) to HighLevel?

HighLevel supports most common TLDs like .com, .net, .org. However, some country-specific domains like .in, .co.uk, and .tv are not supported.


Q: What happens if I make a mistake with my DNS records?

You can review and edit DNS records during the transfer process. If needed, you can also make changes post-transfer under DNS settings (for internal domains).

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