Getting existing HighLevel workflows ready to copy to another brand

Why a working account isn't a ready snapshot

A snapshot copies the configuration assets you select from a source account, and workflows and calendars are among them. It copies each one exactly as it stands. If a text in a workflow names the business, every contact in the new brand's account gets the old business name.

This is where existing accounts catch people out. In our builds we've seen workflows with the business name typed straight into the message copy, step after step. None of it shows up as an error. The workflow runs, and the wrong name goes out under the new brand.

A snapshot copies how an account is built. It can't tell which words belong to the old brand.

Find the old brand inside each workflow

Open every workflow you plan to copy and read each action that sends words to a person, whether that's a contact or someone on the team. Make a list of anything true for this one business and wrong for the next.

• The business name in texts, emails and internal notifications
• Sign-offs that carry a person's name or title
• Links to this brand's website, booking page or review page
• Phone numbers, addresses and opening hours written out in a message
• Any value shown in red. HighLevel marks a dynamic value that is invalid or outdated that way, so fix or remove it here rather than copy it

Swap typed text for Custom Values

A Custom Value holds a piece of business text in one place, and a workflow field that supports Custom Values reads it from there. When the next brand loads the snapshot, it changes the value once instead of editing every step.

Work down your list. Replace each typed detail with a Custom Value, inserted through the picker rather than typed by hand. Then read the step again. HighLevel shows a value it recognizes as a chip, so a chip tells you the field picked it up, and nothing on the step should be red.

Details that change from contact to contact, such as a first name, stay as contact fields. The aim is simple: the only brand-specific text left in the account should sit in Custom Values, where a new brand can see it and change it.

Build the snapshot and load it

Once the source account reads cleanly, the snapshot itself is the short part. For a sub-account that already exists, the steps run like this.

1. In the prepared source account, create the snapshot and select the assets the new brand needs, including every workflow you cleaned up.
2. In the agency view, open Sub-Accounts, then Manage Client on the destination, then Actions and Load Snapshot.
3. Choose the snapshot under Pick a Snapshot, select the assets to bring in and click Proceed.
4. Where an asset already exists in the destination, choose Override to replace it or Skip to keep the one that's there. An override can't be undone through the snapshot load, so decide asset by asset.
5. Confirm the load.
6. In the destination, reconnect the integrations it relies on and assign its Voice AI phone numbers.
7. Fill in the new brand's Custom Values, then send a test contact down every trigger and every branch before real contacts arrive.

What a snapshot leaves behind

HighLevel's snapshot overview says contacts, appointments and conversations don't transfer, and neither do connected integrations or Voice AI phone number assignments. Calendars themselves can be copied; the bookings on them stay in the old account. HighLevel has changed this list before, so check its current page before you plan around it.

A snapshot also carries no proof that the copy works. A workflow that leans on a connected integration has nothing to talk to until someone reconnects it in the new account. That's why the test contact in the last step matters more than the load.

Changing the source after the snapshot exists

Edits you make in the source account don't flow into a snapshot that already exists. Use Refresh to capture the source changes you select, then Push Update to send them to the accounts that use that snapshot.

Take care with workflow steps when you push. Deleting a step in a snapshot workflow can remove contacts who are waiting on that step in the accounts you update. Check who is sitting on a step before you delete it.