This is a preview card so the review deck can be styled and tested before real feedback exists. The kit went into a fresh sub-account, the load sheet listed every custom value in order, and the build was finished before lunch.
Sub-Account Transfer & Handover
A transfer is one button and a long list of things that do not travel with it. We work the list first, so the client does not lose their phone number on a Friday.
What you get back
- A pre-transfer audit of everything that does not move with the account
- Phone numbers checked for portability and released or ported deliberately, never by accident
- Integrations, domains and sending authentication re-pointed or documented for the receiving side
- Agency-level assets the sub-account depends on identified and either duplicated or replaced
- The transfer executed with the relationship number confirmed on both sides
- A handover pack: what moved, what did not, what the receiving agency must rebuild
How it runs
- 01
Find the dependencies
A sub-account usually leans on things that live above it — an agency-level integration, a shared domain, a workflow that references an agency snapshot. Those do not travel. We list them before anybody clicks transfer.
- 02
Decide about the numbers
Phone numbers are the part clients care about and the part that is hardest to undo. We confirm portability, agree in writing whether each number ports, transfers or is released, and sequence it so no number goes dark mid-transfer.
- 03
Re-point the outside world
Sending domain authentication, custom domains, webhooks and third-party integrations all point at something. Each one is re-pointed or handed over with the exact settings written down.
- 04
Execute
The transfer itself, with the relationship number confirmed by both agencies before and after. Five minutes of work that only goes badly when the four steps above were skipped.
- 05
Hand over honestly
The pack says what did not survive the move. A receiving agency told the truth on day one is a receiving agency that does not spend a fortnight discovering it.
One button, and a lot of preparation
The transfer control itself is trivial. Everything expensive about a transfer happens because somebody used it before working out what the sub-account was quietly depending on.
The number is the thing
Clients forgive a rebuilt workflow. They do not forgive a phone number that stopped receiving calls, printed as it is on a van, a sign and four years of invoices. Portability is confirmed and the sequence agreed in writing before anything moves.
Both directions
Sending an account out is about leaving cleanly. Receiving one is about finding out fast what did not arrive. The audit is the same work; the report is written for whichever side you are on.
Related work
If the account arriving is in poor condition, sub-account audit and rescue picks up where the handover pack stops.
Reviews
Reviews of this service
These are sample entries. SubaccountKit is new, so rather than invent testimonials we are showing clearly-labelled placeholders while the deck waits for real customers. Nothing here is published as review or rating markup either — search engines see no ratings from this site until the words are real.
Placeholder copy standing in for a real review. The point being illustrated here is the follow-up ladder stopping the moment someone books, which is the thing most sequences get wrong.
A preview entry, not a customer quote. It exists so the deck renders with a realistic length of text and the shuffle animation can be judged honestly before launch.
Sample text. Deliberately four stars rather than five, so the star row is tested at more than one value and the layout is proven before real reviews arrive.
Another preview card. Real reviews will replace every entry in this file, and the same change that swaps them in also switches the review structured data on.
Questions
Agency-level assets the sub-account referenced, some integration authorisations, conversation history in certain configurations, and anything bound to the sending agency's own domains. The exact list depends on the account, which is why the audit comes first.
They can hold it directly if they take on their own GoHighLevel plan. That changes the billing relationship and some of the white-label surface, and we will set out what changes before anyone commits.
Yes, and it is often the more valuable side. We audit what arrived against what should have arrived, and give you a list of what to rebuild before the client notices it is missing.
Related services
Next step
Get sub-account work scoped this week
Send what you are trying to ship. You get a scope and a fixed number back, or an honest reason why this is not the right engagement.
No call required to buy a kit · replies within one business day