A snapshot is a template of a sub-account's configuration that an agency can load into other sub-accounts. It copies the build, not the data. Snapshots carry things like workflows, pipelines, funnels and websites, forms and surveys, calendars, email and SMS templates, custom fields, custom values and tags. They don't carry contacts, conversation history, opportunities, phone numbers or A2P registration, or connected integrations such as Google, Facebook and Stripe.
In practice
Agencies build a master sub-account for a niche, save it as a snapshot from the agency view, then load it when creating a new client or import it into an existing one. Snapshots can also be shared with other agencies by link. When you improve the master, you can push selected assets from an updated snapshot to sub-accounts that already use it (as of October 2026).
Two things go wrong often. First, pushing updates over a client that has been customized can overwrite their changes, so many agencies push only to untouched accounts and apply changes by hand elsewhere. Second, sub-accounts drift: someone adds a field in one client, deletes one in another, and six months later no two accounts match the snapshot.
Where it shows up in RGS Tools
Field Finder's sub-account compare puts your snapshot's source sub-account next to a client's and lists every field that exists in one but not the other, plus keys whose type changed. That shows drift before a template or integration breaks. Because snapshots don't move contacts or files, Backup & Insights's copy to another sub-account covers pushing contacts and their documents into a different sub-account.