How to rebrand a GHL snapshot under your agency’s name

Rebranding a snapshot badly is worse than not rebranding it at all. A client who receives an automated email six weeks after launch, signed by a company they have never heard of, learns two things at once: that you outsourced, and that you did not check.

This is the order we work in. It is deliberately front-loaded — the first four steps remove roughly eighty per cent of the leakage.

1. Map the custom values before you touch anything

Open Settings → Custom Values and read every one. In a well-built snapshot this is your control panel: business name, offer name, price points, booking link, address, support email, review link. Change them here and they propagate everywhere they are referenced.

In a badly built snapshot this list is nearly empty, which tells you the real work is going to be manual. Budget accordingly.

2. Replace sender identities

Every email template, every workflow email action and every internal notification has a from-name and a from-address. Workflow-level overrides beat account defaults, so changing the account default does not fix them.

• Account-level: Settings → Email Services → sender name and address.
• Template-level: each saved email template can carry its own.
• Workflow-level: each Send Email action can override both.
• Reply-to: frequently forgotten and frequently pointed at the builder.

3. Hunt hard-coded links in SMS and email bodies

This is the one that catches people. Custom values do not help if the builder typed a full URL into an SMS body. Search every workflow for `http` and read what comes back.

4. Fix funnel and website metadata

Every funnel page has a title, a description, a favicon and an Open Graph image. Snapshot exports carry all four. A client who shares their new landing page in a group chat and sees somebody else’s logo in the preview card will ask a question you do not want.

5. Strip foreign tracking

Check page-level head tracking code, funnel-level tracking, and any UTM parameters baked into links. Builders leave their own pixel IDs and GTM containers in place more often than you would believe. Beyond the branding problem, it means your client’s traffic data is being reported to a third party.

6. Reassign internal notifications

Every "notify the team" action needs to point at your team or the client’s. Look specifically at pipeline stage-change notifications and form-submission alerts, which are usually configured last and reviewed never.

7. Rebuild the visual layer properly

Logo, favicon, colour system, button styles, email header images and typography. Do this against a real brand kit, not by tinting the existing design. A recoloured template still looks like the template.

8. Do a copy voice pass

The sequences should sound like your agency wrote them. That means your offer names, your guarantee language, your price framing and your tone. This is the step that separates a rebrand from a repaint, and it is the step most agencies skip.

9. Rename the assets themselves

Workflow names, funnel names, pipeline names and tag names all appear in the client’s interface. "TGS_Dental_Recall_v3" is a builder’s filename, not a product.

10. Re-export as your own snapshot

Once the rebuild is clean, create a fresh snapshot from that sub-account inside your own agency. That new snapshot is now your product. Every future client installs from it, so the rebrand work happens once rather than per client.

11. Run the QA sweep

Import your new snapshot into a throwaway sub-account and go through it as if you were the client. Submit every form. Trigger every workflow. Read every email that arrives. Fourteen checks, an hour of work, and it is the hour that protects the relationship.

How long it should take

A thorough first rebrand of a substantial snapshot is a full day of focused work, sometimes two. Every subsequent client install is minutes, because you are installing your own snapshot rather than rebranding theirs again. If you would rather not spend the day, our rebranding service does the same eleven steps with a fourteen-point QA log and a 72-hour target turnaround.