Sub-account Compare

What it does

Sub-account Compare loads two sub-accounts side by side and tells you how their fields differ. You get four counts at the top: fields in both, fields only in the first, fields only in the second, and fields with the same key but a different type. Below that are two lists, "Missing from A" and "Missing from B", and a "Same key, different type" list showing the change, like Single line → Dropdown.

Every row has a copy button for its merge tag or key, and the whole comparison exports to CSV.

Why it matters

Agencies build sub-accounts from snapshots, then the sub-accounts drift. Someone adds a field to the client account during a call. The template gets three new fields in March that older clients never received. A field gets deleted and recreated as a dropdown with the same key. Workflows and forms that depend on those fields break in ways that are hard to trace.

GoHighLevel doesn't have a native field diff. Loading a snapshot again can add missing items, but it won't give you a report first, and it won't flag a type change. The manual method is to export or screenshot each sub-account's field list and compare them in a spreadsheet, which takes long enough that nobody does it until something's already broken. Comparing custom fields between sub-accounts walks through that spreadsheet approach if you want to try it by hand.

How it works

1. Open Field Finder and switch to Compare at the top.
2. Choose the first sub-account (it defaults to the one you're viewing) and the one to compare it with.
3. Press Compare. Field Finder loads both sub-accounts' fields and custom values.
4. Read the four tiles for the summary, then the two "Missing from" lists for detail.
5. Check the "Same key, different type" list. These are the ones most likely to break a form or workflow.
6. Press the CSV button to download the comparison. Each row has a status ("Only in A", "Only in B" or "Different type"), the object, name, key, and the type in each sub-account.

Good to know

• Matched by key, not name. A field renamed from "Revenue" to "Monthly Revenue" with the same key counts as present in both. Two fields with the same name but different keys count as different.
• Objects are kept separate. A contact field and an opportunity field with the same key aren't treated as a match.
• Both must be connected. You can compare any two sub-accounts connected to your account. With an agency-level install, that's every sub-account.
• Fixing the gaps. Copy the missing names from the CSV and paste them into the Bulk Field Creator in Sub-Account Manager to recreate them in the target account.
• Pick two different accounts. Comparing a sub-account with itself is blocked.