A client is leaving or taking their account in-house, and you want to give them the automations you built — not a login to your account and not a snapshot of everything. Here is the clean handoff.
When a client leaves, takes their marketing in-house, or spins their sub-account out into their own agency, you are usually happy for them to keep the automations you built — the nurture sequences, the booking reminders, the pipeline logic. What you do not want is to hand over your entire GoHighLevel account, or ship them a snapshot of everything to move a handful of workflows. GoHighLevel gives you no clean way to pass over just the workflows, so this guide does it properly: save the ones that belong to the client, deploy them into their account as new workflows, and remap the references to the client's own objects.
The handoff tends to come up at a few predictable moments: a client offboards and wants to take their marketing in-house; you are selling or transferring a sub-account; or an arrangement ends and you would rather part on good terms than hold their automations hostage. In each case the value is the build — the workflows you designed — not the shell of your account.
So the goal is narrow: the client ends up with working copies of a chosen set of workflows inside an account they control, while your own account and your other clients' work stay exactly as they were. That is a different job from a full account migration, and it needs a different tool.
It is worth being clear about what GoHighLevel can and cannot do here, because the native tools almost fit and then stop short:
For a handoff, a snapshot is too much — you would be exporting your entire operational template just to give someone three workflows. What you want is surgical: the specific automations and nothing else.
ExportGHL works on a simple model: you save a workflow once, then deploy it where you need it. For a handoff, open each workflow that belongs to the client in your source account and save it to your private cloud library. The full build is captured — every trigger, every action in order, the waits, the branches and the settings — so the saved copy faithfully records how the automation runs.
Save only the ones that are genuinely theirs. This is where the handoff stays clean: you choose a deliberate set, not the whole account. Internal workflows, cross-client utilities and anything you reuse elsewhere stay unsaved and never leave.
With the workflows saved, open the destination — the client's sub-account, or their own agency if they have added you — and go to its Workflows area. Deploy each saved workflow from your library and ExportGHL rebuilds it there as a new workflow.
Deploy never overwrites or edits anything already in the destination unless you deliberately choose to update an existing workflow, so there is no danger of disturbing automations the client already has. If you saved several, you deploy them one after another — save once, deploy as many times as the handoff needs, into as many accounts as it involves.
A workflow is full of references that only mean something in the account it was built in: pipelines and stages, tags, users, custom fields, calendars and templates are all stored as account-scoped ids, not names. Drop a raw workflow into the client's account and those ids point at nothing, so steps fail quietly — tags never land, opportunities never move, and the workflow looks fine in the editor while broken at runtime.
Cross-account remap is what makes the handoff actually work, and it runs automatically on a cross-account deploy. It matches every reference by name against the client's account and rewrites the ids to theirs, so the "Booked" pipeline stage, the "warm-lead" tag and the custom fields all resolve to the client's own records. Anything it cannot match is flagged, and if a workflow still has unmapped references it is imported as a draft — never published broken. You can read more about how that matching works in the cross-account id remap guide, and the mechanics are the same whether you are doing a handoff or an ordinary copy between accounts.
If you are handing over the front end as well, the same clean-handoff thinking applies to the website — see handing off a GoHighLevel website to a client. Moving your first workflow is free, with no card, so you can run a full handoff end to end before deciding how to pay. See pricing for the credit and licence options.
Save the automations that belong to them, deploy them into their account remapped, and leave the rest of your account untouched. Your first move is free.
Start free
ExportGHL