The challenge
The agency needed to move leads between sub-accounts and control which accounts could send and receive them.
What we built
- Custom GHL app that copies contact fields and tags to a chosen sub-account
- Per-account access: Send + Receive, Receive Only, or Disabled
- Searchable destination picker, plus rollout troubleshooting of auth vs. feature access
Result
Client confirmed transfers working across the enabled accounts.
The full story
The situation
An insurance agency ran several GoHighLevel sub-accounts and needed to pass leads between them. Moving a contact by hand meant re-typing details and losing tags, and there was no control over which accounts could send or receive.
What we built
We built a custom lead transfer app inside GoHighLevel. A user selects one or more leads, picks a permitted destination sub-account from a searchable list, and the app copies the supported contact fields and tags across.
Access control
- Send + Receive: the account can both send and receive leads
- Receive Only: the account can only receive leads
- Disabled: the account is left out of transfers
The tricky part
During rollout the Lead Transfer button could appear in an account while the separate authorisation screen still said “Not Authorized”. Feature access and account authorisation turned out to be two separate settings. We checked the source account, the receiving accounts and the authorisation status separately until the full path worked.
Where it stands
The client confirmed transfers were working, and the button appears in every account where access was enabled. Conversations, notes and opportunities are outside the transfer scope by design.
