To transfer a GoHighLevel sub-account to another agency: (1) Go to Agency Level → Sub-Accounts, (2) select Manage Client on the sub-account, (3) click Actions → Transfer Sub-Account, (4) enter the receiving agency's Relationship Number, (5) confirm with your password.
The sub-account is sent as a request and only transfers once the receiving agency approves. Most core assets transfer contacts, conversations, workflows in Live state, calendars, funnels, memberships. External auth connections (Google, Facebook, Stripe, Instagram) are deleted and must be reconnected. White-label sub-accounts and multi-location agency sub-accounts cannot be transferred at all.
1. What Is a GoHighLevel Sub-Account Transfer?
Definition: A GoHighLevel sub-account transfer is the movement of a sub-account from one agency (the Releasing Agency) to another agency (the Receiving Agency). It is not a merge, and it is not partial the entire sub-account moves as one unit, or it does not move at all. Confirmed from GHL's official Sub-Account Transfer Guide.
Detail: The transfer feature exists because GoHighLevel is designed around the agency-client relationship, but ownership of that relationship changes over time. A client may want to take direct ownership of their setup under their own agency account. An agency may sell or hand off a client to another provider. Two agencies may consolidate. In each case, the sub-account itself with all its contacts, funnels, workflows, and history needs to move without being rebuilt from scratch.
Example: An agency managing a dental client for 3 years decides to focus on legal instead. They find a specialist dental GHL agency willing to take on the client. Rather than the client losing 3 years of contact history, workflow data, and appointment records, the sub-account is transferred to the new agency. The client keeps their phone number, workflows continue running in Live state, and the new agency picks up management from day one.
For a full comparison of transfer vs a complete platform migration from another CRM: GHL migration services →
2. What Are the Prerequisites Before You Can Transfer?
Definition: Before initiating a sub-account transfer, both agencies must meet specific eligibility conditions and the sender must have one critical piece of information from the receiver.
Detail: Confirmed from GHL's official documentation, the prerequisites are:
- The Receiving Agency's Relationship Number: This is the unique identifier for the receiving agency. Without it, the transfer cannot proceed. It is a specific numeric string that must be provided by the receiving agency to the sending agency before the transfer form is filled out.
- Neither agency is a multi-location agency: Multi-location agencies cannot transfer sub-accounts using this feature. Confirmed from GHL's documentation.
- The sub-account is not under white-label branding: White-label sub-accounts cannot be transferred. SaaS Mode is auto-disabled before any transfer takes place.
- Active subscriptions on the sub-account are cancelled: If the sub-account has active subscriptions (ad publishing plans, membership subscriptions, etc.), you must cancel them first. Cancellation reason: "Transferring to another agency."
- You have full agency ownership permission: Only the agency owner or a user with agency-level permission can initiate a transfer.
The receiving agency owner logs into their GHL dashboard. In the top-right area, they click the question mark (?) help icon. The Relationship Number is displayed at the top of the help section. They copy this number and send it securely to the releasing agency (email or Slack never on a public form). Confirmed from third-party GHL training documentation, matches GHL's official Sub-Account Transfer Guide.
3. What Is the Difference Between Transfer and Eject?
Definition: GoHighLevel offers two related but distinct options when moving a sub-account out of your agency: Transfer to an Existing Agency (moves the sub-account to another already-active GHL agency account) and Eject to a New Agency (converts the sub-account itself into a brand-new standalone agency account).
Detail: Both options are accessed the same way Sub-Accounts → Manage Client → Actions → Transfer Sub-Account but at the next step, you choose which path to take.
| Feature | Transfer to Existing Agency | Eject to New Agency |
|---|---|---|
| Requirement | Receiving agency's Relationship Number | Nominated user email |
| Result | Sub-account moves to another existing agency | Sub-account becomes its own standalone agency account |
| Cost to receiver | Depends on receiving agency's plan | Nominated user gets a $97/month signup link |
| Affiliate commission | None | Sending agency receives 40% affiliate commission on all future renewals from the new agency |
| Typical use case | Selling client to another agency, client consolidation | Client wants to run their own agency account independently |
| Approval | Receiving agency must accept the request | Nominee must sign up for the new agency plan |
The 40% affiliate commission on future renewals from ejected sub-accounts is a legitimate ongoing revenue stream. If you eject a client to a new $97/month agency and they stay on GoHighLevel for two years, that is approximately $931 in affiliate commission back to you over that period without any ongoing work. Confirmed from GHL's official Eject documentation. This is why some agencies deliberately use the Eject path when handing clients off rather than the standard Transfer.
4. What Are the Exact Step-by-Step Transfer Instructions?
Definition: The exact procedure to send a sub-account to an existing agency, confirmed from GHL's official Sub-Account Transfer Guide (article 155000002031, modified February 18, 2026).
Detail (Sender side Releasing Agency): Complete these steps in order.
- Step 1 Confirm eligibility: Verify the sub-account is not white-label, your agency is not multi-location, and all active subscriptions on the sub-account are cancelled with the reason "Transferring to another agency."
- Step 2 Get the Relationship Number: Ask the receiving agency owner to send you their agency Relationship Number. They find it by clicking the question mark help icon in their dashboard.
- Step 3 Navigate to the sub-account: Log in to your Agency Level dashboard. Go to Sub-Accounts. Find the sub-account you want to transfer. Click Manage Client on that sub-account.
- Step 4 Initiate the transfer: In the top-right corner, click Actions. Select Transfer Sub-Account from the dropdown.
- Step 5 Choose Transfer to Existing Agency: You will see two options. Select Transfer to an Existing Agency (not Eject to a New Agency).
- Step 6 Enter the Relationship Number: Input the Receiving Agency's Relationship Number. Double-check the number one wrong digit sends the sub-account to the wrong agency, and you will need HighLevel support to recover it.
- Step 7 Review and confirm: Review the transfer guidelines that appear on screen. Check the box confirming you understand what will and will not transfer. Enter your account password. Click Confirm.
- Step 8 Wait for receiving agency to approve: The transfer is now a request, not a completed transfer. The receiving agency will see the request in their dashboard and must accept it before the sub-account moves. You can track the status under the Sent tab on the Sub-Account Transfers screen.
Detail (Receiver side Receiving Agency): Log in to Agency Level. Navigate to Sub-Accounts → Sub-Account Transfers → Received tab. Review the incoming transfer request. Accept the transfer. The sub-account now appears as a new sub-account in your dashboard.
Example: A UK-based GHL agency transfers a real estate client to a US-based agency who specialises in that vertical. Sender confirms the client's sub-account has no active ad publishing subscription (cancelled Stripe subscription for their previous Facebook Ads add-on with reason "Transferring to another agency"). US agency provides their Relationship Number via secure email. Sender completes Steps 3-7, transfer request sent. US agency logs in the next morning, accepts. Sub-account appears in US agency dashboard within minutes with all contacts, workflows, funnels, and calendars intact.
5. What Data Transfers and What Does Not?
Definition: Not everything moves with the sub-account. GoHighLevel's official documentation lists exactly what transfers, what stays behind, and what is deleted during the transfer process.
- All contacts and their conversation history
- Appointments, opportunities, and pipeline records
- Workflows and campaigns (all automations transfer in Live state they continue running)
- Contacts already enrolled in workflows remain enrolled workflow enrollment data is preserved
- Funnels, websites, and landing pages URLs stay the same
- GHL calendars and calendar configurations
- Memberships and course access
- Sub-account-level API keys (they remain the same after transfer)
- Users who have User Type "Account" AND are assigned only to that sub-account (users on multiple sub-accounts do NOT transfer)
- All external auth connections: Google, Facebook, Instagram, QuickBooks, Clio, DrChrono, Yext, and similar. All disconnect.
- External calendar integrations: Google Calendar, Outlook, or other external calendars disconnect from GHL calendars.
- Any SaaS settings: SaaS Mode is auto-disabled before the transfer starts.
- Agency-assigned dedicated email domains: If the original agency assigned a dedicated sending domain to the sub-account, it is removed during transfer. Sub-account-owned dedicated domains DO transfer.
- Dedicated IP for email (if any): Even if the domain transfers, the dedicated IP subscription is unassigned. Receiving agency must re-provision if needed.
Stripe, Authorize.Net, and other payment gateway connections are external auth connections. They will be DISCONNECTED during transfer. The receiving agency must reconnect Stripe (or the client's payment gateway) after the transfer. Any active Stripe subscriptions running from the sub-account must be cancelled BEFORE the transfer with reason "Transferring to another agency" or the transfer will error. This is the single most common transfer failure.
For related guidance on transitions and integration reconnection: GHL migration mistakes →
6. How Are Phone Numbers Handled During the Transfer?
Definition: Phone number continuity depends on which phone infrastructure both agencies are using: LeadConnector (LC) or Twilio.
| Scenario | Phone Numbers Transfer? | A2P Registration Continues? | Future Charges Billed To |
|---|---|---|---|
| Both agencies on LeadConnector | Yes, automatically | Yes, no re-registration needed | Receiving agency |
| Sender on LC, Receiver on Twilio | No coordinate with Twilio manually | N/A Twilio handles separately | Depends on Twilio setup |
| Sender on Twilio, Receiver on LC | No coordinate with Twilio manually | Receiving agency will need to re-register | Receiving agency once numbers ported |
| Both agencies on Twilio | No coordinate with Twilio manually | Twilio handles separately | Depends on Twilio setup |
For A2P registration specifics when transferring agencies: A2P registration for agencies →
For Canadian A2P edge cases: A2P 10DLC Canadian numbers →
7. What Are the Restrictions That Prevent a Transfer?
Definition: GoHighLevel enforces four hard restrictions that prevent a sub-account transfer from being initiated at all. If any of these apply to your situation, the Transfer Sub-Account option will either not appear or will fail on submission.
- Multi-location agency restriction: If either the sending or receiving agency is set up as a multi-location agency, the sub-account cannot be transferred. Multi-location is a separate structural setup that the transfer feature does not support.
- White-label sub-account restriction: Sub-accounts operating under white-label / SaaS Mode branding cannot be transferred. SaaS Mode is auto-disabled before any transfer takes place, but the underlying restriction remains for white-label sub-accounts.
- Active subscription restriction: Sub-accounts with active subscriptions must have those cancelled first, with the reason "Transferring to another agency." If not cancelled, the transfer will error and cannot complete.
- Partial transfer restriction: You cannot transfer only some data from a sub-account. It is an all-or-nothing transfer. You also cannot merge a sub-account into an existing sub-account at the receiving agency transferred sub-accounts always arrive as new, separate sub-accounts.
8. How Does Bulk Transfer Work for Multiple Sub-Accounts?
Definition: Bulk Location Transfer is a feature introduced in 2025 that allows agencies to transfer multiple sub-accounts to another agency at once, rather than one at a time. Confirmed from GHL's official Bulk Transfer documentation (article 155000004570, modified December 11, 2025).
- Access: Agency Level → Sub-Accounts → Sub-Account Transfers → Bulk Transfer Subaccount button.
- Selection: Two options select specific sub-accounts from a list, or use Select All. Maximum 1,000 sub-accounts per bulk transfer request.
- Relationship Number: Same as single transfer input the receiving agency's Relationship Number.
- Confirmation: Enter your password. Confirm to send the bulk transfer request.
- Tracking: Under the Sent tab → Bulk Request sub-tab, click View Details to check the status of each sub-account in the transfer. Status values include Pending (awaiting acceptance), Rejected, and Completed (receiving agency accepted).
An agency is being acquired by another agency. Instead of transferring their 47 client sub-accounts one at a time (which would take hours), they use Bulk Transfer. They select all 47 sub-accounts, enter the acquiring agency's Relationship Number once, and submit as a single request. The acquiring agency receives 47 transfer requests in their Received tab, reviews them, and accepts them in a batch. All 47 sub-accounts appear in the new agency's dashboard within an hour.
For agencies considering a comparable full CRM migration rather than a sub-account transfer: HubSpot to GoHighLevel migration guide →
GHL Scale Up handles sub-account transfers for agencies both sender-side (pre-transfer audit, integration mapping, phone number handoff) and receiver-side (post-transfer integration reconnection, workflow validation, client onboarding).
See real GoHighLevel results and case studies from agency transitions: real GoHighLevel results and case studies →
For a specific situation, book a free strategy call at ghlscaleup.com/contact →
9. Frequently Asked Questions
How long does a GoHighLevel sub-account transfer take?
Once initiated by the sending agency, the transfer request appears in the receiving agency's dashboard within minutes. Once accepted by the receiving agency, the sub-account moves to their dashboard almost immediately, with all contacts, workflows, funnels, and calendars intact. The end-to-end timeline typically takes hours from initiation to full completion but the delay is usually the receiving agency's response time, not GHL's processing time. Bulk transfers of 1,000 sub-accounts have similar processing speed once accepted.
What happens to phone numbers when I transfer a GoHighLevel sub-account?
It depends on the phone infrastructure. If both the sending and receiving agencies are on LeadConnector (LC), all phone numbers transfer automatically with the sub-account and existing A2P 10DLC registrations remain valid no re-registration is required. All future phone usage charges are billed to the receiving agency. If either agency is on Twilio instead of LC, phone numbers do NOT transfer through GoHighLevel you must coordinate directly with Twilio and the previous account owner to port the numbers manually.
Do I lose my A2P 10DLC registration when transferring a sub-account?
Not if both agencies are on LeadConnector. Confirmed from GHL's official documentation: sub-accounts do not need to re-register phone numbers that are already A2P registered when transferring between LC-based agencies. The brand and campaign registrations continue seamlessly, and SMS delivery is not interrupted. If either agency is on Twilio, the A2P registration situation must be handled through Twilio directly HighLevel does not manage that path.
Does Stripe transfer when I move a GoHighLevel sub-account?
No. Stripe (and other external payment gateway connections) are external auth connections, which are all disconnected during the transfer. The receiving agency must reconnect Stripe or the client's payment gateway after the transfer. Any active Stripe subscriptions must be CANCELLED before the transfer with the reason 'Transferring to another agency' if left active, the transfer will error. This is the single most common transfer failure.
Can I transfer a white-label GoHighLevel sub-account?
No. White-label sub-accounts operating under SaaS Mode cannot be transferred using the standard Transfer Sub-Account feature. SaaS Mode is auto-disabled before any transfer takes place, but the underlying restriction on white-label transfers remains. There are two workarounds: (1) disable SaaS Mode on the sub-account first (which changes the client's branding view), or (2) use the Eject to New Agency path instead, which converts the sub-account to its own standalone agency account.
What is the difference between Transfer and Eject in GoHighLevel?
Transfer moves a sub-account to another EXISTING agency account (you need their Relationship Number, and they must accept the request). Eject converts the sub-account itself into a brand-new standalone agency account (you nominate a user, they receive a $97/month signup link via email, and once they sign up they become the agency owner of the newly independent account). Eject also generates a 40% affiliate commission to the sending agency on all future renewals from the ejected agency confirmed from GHL's official Eject documentation.
How do I find my GoHighLevel agency Relationship Number?
Log in to your agency dashboard. Click the question mark (?) help icon in the top-right area of the interface. The Relationship Number is displayed at the top of the help section. Copy this number and send it securely to the sending agency (via email or private channel never on a public form). The Relationship Number is required for both single sub-account transfers and bulk transfers of up to 1,000 sub-accounts at a time.
Related Articles
Ready to transfer a GHL sub-account without breaking anything?
GHL Scale Up manages sub-account transfers end-to-end. Pre-transfer audit, integration mapping, phone number and A2P handoff, post-transfer reconnection, and client validation so nothing breaks in the handover.
Book Your Free Strategy Call
All procedures in this guide are verified against GoHighLevel's official support portal documentation as of July 2026 (articles 155000002031, 155000004570, and 155000003465). GoHighLevel policies and interface details are set by HighLevel and can change always verify current steps in your Sub-Account Transfers dashboard before initiating.
ghlscaleup.com