You found GoHighLevel's Copy Workflow option, went to move an automation into another account, and hit a wall — the item is greyed out, the account you want is not in the list, or the copy landed as a draft that will not run. None of that is a bug. Here is what is really blocking you, and a route that moves a workflow into any account without the gates.
GoHighLevel does have a native "copy workflow to another sub-account" feature in some versions, so people reasonably expect to move an automation anywhere they manage. In practice it is deliberately narrow, hedged in by permissions and matching rules you only discover by tripping over them. Name the gates it enforces, and the greyed-out menu and the mysterious draft both stop being mysteries.
First check whether the option is greyed out or absent, because they usually mean different things. A control that is visible but disabled is typically a permissions problem: your user does not hold the role GoHighLevel requires for a cross-account copy. If it is missing altogether, that is more often a version or plan difference — the native copy has rolled out unevenly, and plenty of accounts simply do not have it exposed.
Either way, it is not a fault you can clear by refreshing or re-logging — it reflects a deliberate decision about who may move a workflow, and to where.
When the native copy does appear and is clickable, three constraints govern whether it will actually work for the move you have in mind:
Stack those together and the native copy cleanly serves one scenario: an agency admin moving a workflow between two same-agency sub-accounts whose fields already line up. A real case, but a thin slice of what people need.
Suppose you clear every gate and the copy runs. The workflow still arrives switched off, as a draft — GoHighLevel never publishes a copied workflow live. That is a sensible safety step, and an admission that its references may not resolve in the new account.
The trouble is what the native draft does not tell you. It is on you to open every step and confirm each tag, pipeline stage, assigned user and custom field still points at the right record — or at any record at all. It saves you from an automation firing against nothing, but hands you a manual audit with no map of what to fix, and a blanked-out reference is easy to miss until a live contact runs through it.
ExportGHL Workflows is a Chrome side-panel extension backed by a server proxy, and it sidesteps the native gates by not using GoHighLevel's internal copy at all. It works with any account you can open in your browser — your own, your agency's, or a client's — with no agency-admin requirement and no same-agency restriction. The move runs in three steps:
Clearing the permission gates is only half the problem; the other half is making the workflow actually run in its new home — the work the native copy leaves to you. On a cross-account deploy, cross-account remap runs automatically: it reads every account-scoped reference in the workflow — pipelines, stages, tags, users, custom fields and email templates — looks up each one's name in the source, and rewrites the id to the matching record in the destination. The custom-field-type mismatch that trips the native copy becomes a name match it reconciles for you rather than a hard failure.
Anything it genuinely cannot match — a tag never created in the destination, a user who is not a member — is flagged, and the workflow is deployed as a draft rather than published broken. Same safety instinct as the native draft, with a crucial difference: you are shown exactly which references need attention instead of being left to find them. The id rewriting is covered in the cross-account id remap guide, and the full move in copy a workflow between accounts.
Because the workflow lives in your library after the first save, moving it again is just another deploy. Manage ten client accounts and want the same onboarding automation in each? Save it once and deploy it into each in turn, with remap wiring every copy to that account's own records — a repeatable deploy, not a throwaway copy. If you only need the same workflow again inside one account, the native route and clone a workflow cover that for free.
You can move your first workflow end to end on the free trial with no card, seeing remap and draft-flagging on your own accounts before spending anything. After that it is pay-as-you-go credits that never expire, or a one-time Toolkit licence with no subscription — see pricing.
No agency-admin gate, no same-agency wall. Save it once and deploy it into any account you can open, with references remapped for you.
Start free
ExportGHL