GoHighLevel Sub-Account Transfer & Ownership (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 22 September 2026 · 10 min read
Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend. Full disclosure.
A GoHighLevel sub-account transfer moves an entire location from one agency to another, and it is the single most misunderstood offboarding step in this platform. Most Australian agencies only learn what does not move on the day the client is already gone.
This guide walks the in-app flow, what HighLevel carries across, what it quietly deletes, and the checklist we run before pressing Confirm. Whether you call it a HighLevel location transfer or a client handover, the mechanics and the surprises are identical.
Quick Facts
| Where it lives | Agency View > Sub-Accounts > Manage Client > Actions > Transfer Sub-Account |
| Who can do it | Agency Owner by default; the Owner may grant it to specific Agency Admins |
| What you need | The receiving agency's Relationship Number — 7 digits, X-XXX-XXX format |
| Who approves | The receiving agency, from Sub-Accounts > Sub-Account Transfers |
| Partial transfers | Not supported — no merging, no moving selected data only |
| Eject option | Converts the location into its own agency on the $97/month Starter plan; releasing agency earns 40% affiliate commission on renewals |
| Source | HighLevel Sub-Account Transfer Guide and pricing page, both current 2026 |
What a GoHighLevel sub-account transfer actually moves
A transfer moves the whole location from the releasing agency to the receiving agency. HighLevel's documentation is blunt: it does not merge sub-accounts and it does not move selected data only.
Contacts, conversations, appointments, opportunities and history stay attached to the location. Funnels, websites, calendars and automations travel with it.
The catch is that every automation arrives in Draft. HighLevel sets all transferred Workflows to Draft on arrival, so an unattended handover means nobody's nurture, no appointment reminders and no review requests until someone republishes them one by one.
Transfer, eject or snapshot — three different tools
Agencies conflate these constantly, and the wrong choice costs a rebuild.
| Method | Moves live data? | Use it when |
|---|---|---|
| Transfer to an existing agency | Yes — contacts, conversations, history | The client is moving to an agency that already has a HighLevel account |
| Eject to a new agency | Yes — the location becomes the new agency | The client wants to run HighLevel themselves |
| Snapshot | No — structure and assets only | You are cloning a build into a fresh location |
A snapshot is a template, not a handover. Hand one to the incoming agency and the client loses every conversation thread, opportunity and record of history — and you still own the original location.
Before you do anything irreversible, take a full sub-account backup first so you have an exportable record of contacts and assets independent of the platform.
The official HighLevel location transfer flow, step by step
The flow is short. The preparation around it is not.
- Switch to Agency View and open Sub-Accounts, then Manage Client on the location you are releasing.
- Choose Actions > Transfer Sub-Account, then pick "Transfer to an Existing Agency" or "Eject to a New Agency".
- Enter the receiving agency's Relationship Number and confirm with your password.
- Track the request under Sub-Accounts > Sub-Account Transfers > Send, where you can also cancel it from the three-dot menu.
- The receiving agency approves from their Transfer Requests tab, and the location moves the moment they do.
The Relationship Number is an agency identifier, not a Location ID. It sits in Agency View under Settings > Company > Company Data, and only Agency Owners and Admins can see it — so ask the receiving agency's owner rather than guessing from a sub-account URL.
There is no platform-side waiting period — timing depends entirely on how fast the other agency approves. By default only the Agency Owner can request or approve a transfer, which is worth keeping that way; review your agency user roles and sub-account permissions before you hand that capability to anyone else.
What transfers vs what you have to rebuild
Send this to the incoming agency before anyone approves anything.
| Asset | Transfers? | Practitioner note |
|---|---|---|
| Contacts, conversations, appointments, opportunities | Yes | History stays intact |
| Funnels, websites, calendars | Yes | External calendar integrations disconnect |
| Workflows and enrolled contacts | Yes, but Draft | Enrolment survives; republish every automation |
| Sub-account users | Conditional | Only User Type "Account" users tied to that one location |
| Sub-account API keys | Yes | Unchanged after the move |
| Smart Lists | No | Screenshot the filter logic first |
| Auth connections (Google, Facebook, Instagram, QuickBooks) | No — deleted | Google and Facebook settings cleared entirely |
| Sub-account Stripe fields | No — cleared | Re-test every payment link and invoice |
| Mailgun / SMTP | No — removed | Location inherits the receiving agency's provider |
| Domains and white-label app subdomain | No | Re-add and re-verify every custom domain |
| SaaS Mode settings | No | Disabled automatically before transfer |
| Paid add-ons (WordPress, Yext, WhatsApp, dedicated IP) | No | Cancel them or the transfer is blocked |
Sources: HighLevel's Sub-Account Transfer Guide and Eject Sub-Account to a New Agency, 2026.
Phone numbers, LeadConnector and email after a location transfer
This is where most handovers break, and the rule is provider-dependent.
| Scenario | What happens to the numbers |
|---|---|
| Both agencies and the sub-account on LC Phone | Numbers transfer automatically, eligible A2P registration stays, future usage bills to the receiving agency |
| Either agency on their own Twilio | Nothing transfers — both agencies and the Twilio account owner arrange the move directly with Twilio |
If you run a bring-your-own Twilio setup, start the number conversation two weeks before the transfer, not on the day. A client's main business line living in your Twilio project is the one asset that can hold an offboarding hostage, and nobody enjoys that conversation.
For Australian agencies there is a wrinkle worth naming. A2P 10DLC is a United States registration regime, so that guarantee applies to US numbers; locally what matters is who holds the number with the carrier and whether your consent and sender-identification obligations under the Spam Act, administered by the ACMA, follow the client to their new provider.
Email is equally provider-dependent. On LC Email, an agency-assigned dedicated domain is removed while a sub-account-owned dedicated domain travels with the location, any dedicated IP is unassigned and its subscription removed, and the email verification setting is preserved.
On Mailgun or SMTP, those configurations are stripped and the location inherits whatever the receiving agency uses by default. Plan for a deliverability dip and re-warm accordingly.
Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.
Handing ownership to the client: the eject path
When a client wants the keys rather than a new agency, Eject to a New Agency is the right tool. You nominate one sub-account user as the new Agency Owner and they receive an email invitation to sign up.
Signup defaults to the $97/month Starter plan — three sub-accounts, unlimited contacts and unlimited users on HighLevel's 2026 pricing page. The releasing agency earns 40% affiliate commission on the new agency's renewals.
The ejected location transfers into the new agency automatically once the nominee completes payment and setup. Until they do, nothing moves — so if your client drags their feet on the signup, the handover simply stalls in the Eject tab.
If the location is HIPAA-enabled, the new agency must buy the HIPAA add-on during signup — priced at $297/month on HighLevel's 2026 pricing page. Raise that early rather than letting it surface at checkout.
The offboarding checklist an Australian agency should run
We run this before the transfer request goes out, not after.
- Export everything. Contacts, custom fields, custom values, pipeline data and a written record of every Smart List filter.
- Screenshot the integrations. Google Business Profile, Meta, calendar connections and marketplace apps, since every auth connection is deleted.
- Cancel paid add-ons. WordPress hosting, Yext, WhatsApp and dedicated IPs, or the transfer will not proceed.
- Disable SaaS Mode deliberately. It switches off automatically anyway; doing it yourself lets you cancel the client's SaaS subscription cleanly.
- Document the workflow inventory. Names, folders, triggers and publish state, because everything lands in Draft.
- Settle the phone position in writing. Who owns the numbers, who pays porting costs, and when the client's line stops routing through your account.
- Agree a data-handling line. Under the Australian Privacy Act the client's database is personal information you hold on their behalf — confirm what you retain and for how long.
Payments deserve their own pass. Stripe fields are cleared on transfer, so the incoming agency must rebuild the Stripe connection and payment recovery flows before an invoice or order form works again.
If you are receiving, resist the urge to push your standard snapshot over the top. Understand how snapshot updates push changes into a live location first, or you will overwrite the client's working assets on day one.
Give yourself a seven-day stabilisation window after any handover. Republish Workflows in batches, test one form and one calendar booking end to end, then tell the client it is complete.
And if the reason for the transfer was a client threatening to leave, the transfer is the symptom rather than the disease — our notes on SaaS Mode churn cover the retention side of that equation.
Common mistakes to avoid
- Sending a snapshot instead of a transfer, then discovering the client lost every conversation, opportunity and appointment record.
- Assuming Workflows keep running — they arrive in Draft, and an unpublished nurture sequence is silent failure nobody notices for a fortnight.
- Entering a Location ID where the Relationship Number belongs; the dialog wants the seven-digit agency identifier.
- Leaving WhatsApp, Yext, WordPress hosting or a dedicated IP active, which blocks the transfer until cancelled.
- Forgetting the client's numbers sit in your Twilio project, turning a clean exit into a hostage negotiation.
- Transferring before you have exported contacts and documented Smart Lists, custom values and integrations offline.
If you want a clean, documented sub-account handover — done once, with nothing left broken on either side — book a strategy call with the HL Growth Partner team.
Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.
Frequently asked questions
Who has to approve a GoHighLevel sub-account transfer?
The receiving agency approves the request from Agency View > Sub-Accounts > Sub-Account Transfers > Transfer Requests. By default only the Agency Owner can request or approve a transfer, though the Owner can grant that permission to specific Agency Admins. The releasing agency can cancel a pending request from the three-dot menu on the Send tab.
Do phone numbers transfer with the sub-account?
Only if the releasing agency, the receiving agency and the sub-account are all on LC Phone, in which case numbers move automatically and eligible A2P registration stays with them. If either agency uses its own Twilio account, no numbers transfer and the two agencies must coordinate the move with Twilio directly. Settle this in writing before you submit the transfer request.
Will my Workflows keep running after the transfer?
No. HighLevel transfers all automations but sets them to Draft in the receiving agency. Enrolled contacts and their workflow enrolment data survive the move, so once you republish each Workflow the sequences resume rather than restarting from scratch.
Can I transfer only part of a sub-account, or merge two locations?
Neither is supported. A transfer moves the complete sub-account and its supported data as one unit, and it will not combine that data with an existing location. If you need selected assets only, build a snapshot instead and accept that contact data stays behind.
Is a snapshot the same as a sub-account transfer?
No. A snapshot copies structure and assets such as funnels, Workflows and custom values into a different location, while a transfer moves the live location itself including contacts, conversations and history. Use a snapshot for cloning a build and a transfer for changing who owns the account.
What happens to Mailgun or LC Email settings during a transfer?
Mailgun and SMTP configurations are removed and the sub-account adopts the receiving agency's default email provider. On LC Email, an agency-assigned dedicated domain is removed while a sub-account-owned dedicated domain transfers, and any dedicated IP is unassigned with its subscription cancelled. Expect to re-verify sending domains and re-warm before heavy sends.
How long does a GoHighLevel sub-account transfer take?
The location moves as soon as the receiving agency approves the request, so the practical timeline is set by how quickly they act. Delays usually come from eligibility blockers such as a missing HIPAA add-on or active paid subscriptions that must be cancelled first. Both agencies can watch the status on the Sub-Account Transfers page, where a request shows as pending, completed, rejected, cancelled or blocked.
Related Articles on HL Growth Partner
Before you start a transfer
- GoHighLevel Sub-Account Backup & Restore
- Agency Security, 2FA, Roles & Access
- Agency Wallet & Auto-Recharge Settings
Rebuilding the stack after a handover
- White Label Setup Guide for Agencies
- Custom Menu Links: Agency Setup
- Contact Import & CSV Field Mapping
