If you run an agency, you have probably built the same automation more than once: a lead follow-up sequence, an appointment reminder, a missed call text back, a review request after a job is marked complete. You build it once, it works, and then you need it in five, twenty or fifty client accounts. The instinct is to copy it. The problem is that almost nothing about a client automation is portable on its own, and the parts that silently fail are rarely the parts you checked.
This guide covers what breaks when you move an automation between accounts, how GoHighLevel, Zapier, HubSpot, Make and n8n handle that move today, a checklist for building automations so they survive the copy, a test plan for after you move one, and a troubleshooting table for "it's copied but it's not working" symptoms.
What usually breaks when you copy an automation to a new account
Every platform calls this something different (snapshot, template, blueprint, export), but the failure modes are nearly identical because the underlying problem is the same: an automation is not a standalone object. It points at other things inside the account it was built in, and most of those pointers do not resolve in a new account.
Hard-coded internal IDs. A step that says "move to pipeline stage X" or "assign to user Y" is usually storing an internal ID, not the label on screen. That ID exists only in the source account, so in the new account it either points at nothing or at something unrelated that happens to share the number.
Connected integrations and credentials. Email accounts, calendars, payment processors, phone connections and third-party logins are authenticated per account. A copied automation almost never carries working credentials with it; every platform below treats re-authentication as a separate manual step by design, since API keys and OAuth tokens are too sensitive to copy automatically.
Phone numbers and sender identities. A step that sends from "the main business line" is really sending from one specific number or verified sender. In the new account that number does not exist yet, and an unverified sender can fail outright or land in spam.
Custom fields and tags that do not exist yet. If a workflow reads a field called "Appointment Date" or filters on a tag called "VIP," that field or tag has to exist under the exact same name in the destination account. A missing field usually does not throw an error, it just evaluates as empty, and the step silently fails.
Pipelines and stages. The same applies to any step referencing a specific pipeline or stage. If the new account's stage names differ, or the pipeline does not exist yet, the step has nowhere to put the contact.
Calendars and booking links. A reminder tied to one calendar needs the equivalent calendar built, and usually reconnected to a real provider, in the destination account.
Templates that need separate approval. Email and SMS templates usually copy as plain text, but WhatsApp templates do not: every WhatsApp message template requires approval from Meta, tied to the sending WhatsApp Business Account rather than the text itself. Copying the words does not carry over the approved status; it has to go through Meta's review again.
Time zones. A reminder scheduled for "9:00 AM" is evaluated against whatever time zone the account, contact or step is set to. If the source account's default time zone differs from the client's real business hours, a working copy fires at the wrong hour elsewhere.
Opt-in and compliance differences. Different clients, different jurisdictions, different consent records. An automation built around the assumption that every contact has already opted in to SMS or WhatsApp breaks compliance the moment it lands in an account with different intake forms or no consent capture at all. This is a review step, not a technical one, and the one most often skipped in a fast rollout.
How the major platforms actually handle it
This section describes what each vendor documents today. Platforms change this regularly, so treat the mechanism as current as of the check date below and re-verify before you rely on it for a large rollout.
GoHighLevel snapshots
A snapshot in GoHighLevel is a packaged copy of a sub-account's configuration, not its live data. HighLevel's Snapshots Overview article lists what a snapshot can carry: calendars, custom fields, custom objects, custom values, pipelines, tags, trigger links, smart lists, email and text templates, funnels and websites, forms, surveys, campaigns, dashboards, custom reports, membership products, documents and contracts, and WhatsApp templates, among others. Contacts, conversations, opportunities and notes are not included.
The flow has three steps that are easy to conflate: share a snapshot, import it into your agency's snapshot library, then load it into a specific sub-account. Importing adds it to your library without touching any client account. Loading applies selected pieces to one sub-account, with a conflict check for anything in the destination that already shares a name.
Connected accounts and credentials, a client's own email connection, phone number or payment processor, are not part of what a snapshot carries, so those get set up per client after loading. WhatsApp templates can be carried, but Meta's approval is tied to the sending WhatsApp Business Account, so a template loaded into a new sub-account typically needs its own approval before it can send.
Zapier: copying Zaps between accounts
Zapier's documented method is "copy assets to another account," from the Assets page: select the Zap workflows, choose "copy to another account," pick the destination and a folder, then confirm. This also works for Tables, Forms, Interfaces, Chatbots and Agents. Several things do not carry over: app connections need re-authenticating, global variables are replaced with their current values rather than staying linked, run history does not transfer, and copied Zaps arrive turned off. A Zap's dependencies, such as a Zapier Table it reads from, are not copied automatically.
Zapier's older method, sharing a Zap as a public template link, is being retired: shared Zap templates will be deprecated on 15 December 2026, after which existing links stop working, though Zaps already built from one keep running. If you hand out template links to onboard clients, move to asset-copying or guided templates before that date.
HubSpot: copying workflows between portals
For a long time HubSpot had no native way to move a workflow between portals; the only paths were to rebuild it by hand or use the API, which only supports certain workflow types. HubSpot's knowledge base now documents a native asset-copying feature inside multi-account management, copying marketing emails, forms, segments and workflows between accounts in the same organization. It requires an Enterprise subscription on the primary account, Professional or Enterprise on the connected accounts, Super Admin permissions on both sides, and does not work with sandbox or trial accounts. A copied form carries its fields but not collected data; a copied segment carries the definition, not its records. If your clients each run a fully separate portal outside that structure, you are back to the API or a manual rebuild.
Make: blueprint export and import
Make calls a portable version of a scenario a blueprint. From the scenario builder's menu you export a blueprint as JSON, or copy it to the clipboard; to bring it into another account, create a new scenario and import that file. A blueprint retains the scenario's modules and mapped values but excludes credentials such as logins and API keys, so it can be shared without leaking secrets. Every connection needs re-pointing at a real connection in the destination account, and Make's own guidance is to use "Run once" to test rather than assume it works.
n8n: workflow JSON export and import
n8n workflows export as JSON from the Workflow menu, the CLI, or the API, and import the same way into another instance. The JSON carries credential names and IDs, not the secrets themselves, by design, so every imported workflow needs its credentials reconnected manually. For moving many workflows and credentials between self-hosted instances at once, n8n recommends its CLI's dedicated export and import commands, and warns that a decrypted credentials export contains plaintext API keys and should never be committed to version control.
Template-ready automation checklist
Build the automation so the next copy is a configuration exercise, not a rebuild.
| Check | Why it matters |
|---|---|
| Document every pipeline stage, calendar and user assignment the automation touches, so you can re-map each one on copy | These are account-specific IDs that do not resolve in a new account |
| Confirm every custom field and tag the automation reads or writes is created in the destination account first, under the exact name | A missing field usually fails silently instead of throwing an error |
| List every sender identity used (phone number, email address, WhatsApp number) separately from the automation | Senders are per-account and often need separate verification or approval |
| Note the time zone the automation assumes versus the setting it actually depends on | A reminder firing at the right hour in one account can fire at the wrong hour in another |
| Write down which integrations and credentials the automation calls | No platform here copies live credentials automatically |
| Name steps and the automation consistently, so a client copy is obviously derived from the template | Makes later version updates and audits possible |
| Keep a short written description of the trigger, logic and exit conditions next to the build | Whoever loads the tenth copy did not build the first one |
| Flag compliance-sensitive steps (SMS, WhatsApp, calling) for a per-client consent and registration check | Opt-in rules and number registration differ by client, not by automation |
Post-copy test plan
A copy that "looks right" in the builder is not the same as a copy that works. Run through this with a real test contact before calling a rollout finished.
- Create one test contact in the destination account with none of the dependent data pre-filled, so you can watch each field and tag get set as it should.
- Trigger the automation the way a real contact would, not through a manual "run now" option, since manual runs can skip filter checks that only apply to the real trigger event.
- Walk every branch: the goal-met branch, the no-reply branch, the opted-out branch, and any error or fallback path.
- Confirm the sender identity on every outbound step belongs to this client, not the account you built the template in. Sending from the wrong client's number is the most common mistake in a fast rollout.
- Check timing against the client's real time zone, not the time zone the builder happened to show during testing.
- Confirm every integration step actually ran by checking the connected service itself (the calendar event appeared, the payment was created) rather than trusting a green status in the automation's own history.
- Re-run the test after re-publishing, if the platform requires a separate publish step. A saved draft is not a live automation.
Troubleshooting: symptoms after copying an automation
| Symptom | Likely cause | Fix |
|---|---|---|
| GoHighLevel workflow not triggering after a snapshot load | Loaded in draft status and never published, or auto-reverted to draft after hitting an error threshold | Confirm it shows Published, not Draft, then republish if you edited since loading |
| Contact never enters the workflow | Trigger filters reference a tag, form or stage that does not exist, or was renamed, in the destination account | Re-point each filter at the equivalent object in this account; a stale reference fails silently rather than erroring |
| Workflow runs but a step does nothing | The step reads a custom field or tag not yet created in the destination account | Create the field or tag with the exact expected name, then re-test with a fresh contact |
| Message sends from the wrong number or address | The sender was not re-pointed after copy and is still using a default or leftover value | Explicitly set the sender on every outbound step to this client's verified identity |
| WhatsApp step fails to send | The template copied as text has not been separately approved on this client's WhatsApp Business Account | Submit for approval on the new account and wait for approved status before enabling |
| Integration step errors out | The connected account was never reconnected, since credentials are never copied automatically by any platform here | Open the step and create a fresh connection authenticated as this client |
| Reminder fires at the wrong local time | The automation inherited the template's time zone rather than the client's real business hours | Set the time zone explicitly for this client and re-test |
| Contact re-enters repeatedly, or never re-enters | Re-entry settings copied as-is do not match how this client expects repeat contacts handled | Review and set re-entry rules intentionally per client |
| Zap copied into the new account does nothing | Copied Zaps arrive turned off with connections not carried over | Reconnect each app step to the destination account's login, then turn it on |
| HubSpot workflow copy option is missing | Accounts are not in the same multi-account organization, or one is sandbox/trial, or lacks the required tier | Confirm both are Professional or Enterprise in the same setup, or fall back to the API or manual rebuild |
Migrating off GoHighLevel: a related but different problem
Copying a template into a new client account and migrating away from a platform are not the same job, even though both involve moving automations elsewhere. If you are planning to migrate from GoHighLevel entirely, the automation side is usually the hardest part to move cleanly, because trigger types, actions and condition logic differ across platforms. A GoHighLevel workflow does not translate step-for-step into another tool's builder; it has to be rebuilt against that tool's own trigger and action set, using the original as a specification rather than an export you drop in. Budget for rebuilding and testing each automation, not just for exporting contacts and pipeline data, which generally moves more directly.
Where Inflowave fits
Inflowave does not offer cross-account copying, snapshots, or any equivalent import/export feature between client workspaces; each client stays in its own separate workspace. What it does provide is a library of ready-to-clone workflow templates, including missed-call text-back, appointment reminders and Instagram DM lead capture, that you can use as a starting point inside a client's own workspace rather than building each automation from a blank canvas.
Frequently Asked Questions
Can I copy a workflow to another account without losing the trigger filters?
The filters usually copy as configuration, but what they reference, a tag, a form, a pipeline stage, may not exist in the destination account. The filter does not throw an error when its reference is missing; it simply never matches, so the workflow looks copied correctly but never fires. Re-check each filter against the destination account's actual tags, forms and stages before relying on it.
Do GoHighLevel snapshots copy connected phone numbers and integrations?
No. HighLevel's documentation lists the configuration and content a snapshot carries, such as workflows, pipelines, templates and calendars, but connected integrations, phone numbers and other credentials are account-specific and are set up separately in each sub-account after loading.
Can I share a Zap with another Zapier account the way I used to?
Shared Zap template links are being retired: per Zapier's help center, you can no longer create new shared Zap templates, and existing links stop working on 15 December 2026, although Zaps already built from a template keep running. The supported method now is "copy to another account" on the Assets page.
Why can't I copy a HubSpot workflow to a different portal?
Historically HubSpot had no native cross-portal copy feature. HubSpot now offers one, but only between accounts in the same multi-account management organization, on Professional or Enterprise subscriptions, with Super Admin access, and not with sandbox or trial accounts. If your clients each run a fully separate portal outside that structure, there is still no native path, and the options are the API or a manual rebuild.
Does a Make blueprint or n8n workflow export include my API keys?
No, in both tools' own documentation. Make's blueprint excludes credentials such as login details and API keys. n8n's exported workflow JSON includes credential names and IDs but not the underlying secrets, so a workflow can be shared without leaking authentication. Every connection needs re-authenticating in the destination account after import.
Why did my WhatsApp template work in one client account but not another after I copied it?
WhatsApp message templates require approval on the specific WhatsApp Business Account sending them, per Meta's documentation. Copying the template text does not carry over that approval; the new account has to submit the same template and get it approved before it can send.
What's the single most common cause of "it copied fine but nothing happens"?
A reference inside the automation, a tag, custom field, pipeline stage, calendar or sender, that does not exist yet in the destination account. The automation fails that check silently rather than raising a visible error. Test with a fresh contact and watch the whole path, not just whether the copy completed.
Sources
Checked 12 October 2026 unless noted.
- HighLevel, Snapshots Overview: help.gohighlevel.com/support/solutions/articles/48000982511-snapshots-overview
- HighLevel, Create Snapshots: help.gohighlevel.com/support/solutions/articles/48000982512-create-snapshots
- HighLevel, How to Import Snapshots: help.gohighlevel.com/support/solutions/articles/48000982581
- Zapier Help Center, Move Zap workflows between accounts: help.zapier.com/hc/en-us/articles/8496275081357-Move-Zap-workflows-between-accounts
- Zapier Help Center, Share a template of your Zap (deprecation notice): help.zapier.com/hc/en-us/articles/8496292155405-Share-a-template-of-your-Zap
- HubSpot Knowledge Base, Copy assets to another HubSpot account: knowledge.hubspot.com/account-management/copy-assets-to-another-hubspot-account
- HubSpot Community, Copy/move a workflow from one portal to another: community.hubspot.com/t5/APIs-Integrations/Copy-move-a-workflow-from-one-portal-to-another/td-p/454855
- Make Help Center, Scenario blueprints: help.make.com/blueprints
- n8n Documentation, Export and import: docs.n8n.io/build/manage-workflows/export-and-import
- Meta for Developers, WhatsApp template fundamentals (template approval status): developers.facebook.com/documentation/business-messaging/whatsapp/templates/overview
