If you run client accounts in GoHighLevel, you’ve probably built a snapshot or two and quietly assumed it doubled as a backup. It doesn’t. A snapshot saves the way an account is built — your workflows, funnels, pipelines, and custom fields — but it leaves behind the data those things hold. Your contacts, conversations, and opportunities never come along for the ride. So the day someone deletes the wrong list or overwrites a field on a few thousand records, the snapshot you were counting on turns out to be empty where it matters.
Do HighLevel snapshots include contacts?
No. Contacts aren’t part of a snapshot, and neither are conversations, opportunities, notes, tasks, appointment history, or call logs. A snapshot is a template of how an account is set up, the kind of thing you reuse when you onboard a new client. HighLevel deliberately keeps live data out of it, so one client’s records can’t end up inside another account when you deploy that template somewhere else. That’s exactly what you want when you’re cloning an account. It’s also why a snapshot is the wrong thing to reach for the moment you actually need to recover something.
This mix-up is easy to make and expensive to learn. Plenty of agencies only find out their “backup” was never a backup on the day they go looking for data that’s already gone.
What a snapshot saves, and what it leaves out
A snapshot captures the building blocks of an account. It skips everything you’d need to recover from data loss.
| A snapshot DOES include (structure) | A snapshot does NOT include (your data) |
|---|---|
| Workflows and automations | Contacts |
| Funnels and websites (pages, CSS, forms) | Conversations (SMS, email, chat history) |
| Pipelines and pipeline stages | Opportunities and deals |
| Calendars and calendar settings | Notes, tasks, and activity history |
| Custom fields (the fields, not each contact’s values) | Appointments and appointment history |
| Email and SMS templates | Call logs and recordings |
| Tags, triggers, campaigns | Reputation and review data |
| Forms and surveys | Integrations, phone numbers, billing, user accounts |
The way HighLevel itself puts it: structure transfers, data and credentials don’t. That’s a good rule for cloning an account, and no help at all when a record disappears.
Why snapshots get mistaken for backups
Part of it is the word. In most software a snapshot means a point-in-time copy of everything, the way you’d snapshot a server or a disk. In HighLevel it means a reusable template, which is close to the opposite. Same word, very different job.
The rest is just how the product is laid out. Snapshots are the most visible “save this account” feature most agency owners ever touch, so they quietly become the mental model for keeping an account safe, even though they were built for onboarding and resale rather than recovery. And because nobody tests a backup until they need one, the gap stays invisible right up until the moment it costs you.
What happens when you rely on a snapshot for recovery
Picture the usual way this goes wrong. A team member deletes a few thousand contacts, or runs a bulk edit that overwrites a custom field, or drags an opportunity to the wrong stage and loses the history behind it. You go to your snapshot to put things back, and there’s nothing there to put back, because the data was never in it.
At that point you’re left with HighLevel’s own recovery, and it has real limits:
- Deleted contacts can be restored for 60 days. After that they’re gone for good, and there’s no way to get them back.
- Native restore only covers deletions. It can’t undo an overwritten field, a bad bulk update, or a botched import, because those records were never deleted, just changed. There’s no version history to roll back to.
- Any associated data that was deleted separately doesn’t come back with the contact. (HIPAA-enabled accounts can’t restore deleted contacts at all.)
- If you cancel your subscription, you’ve got about 90 days to reactivate before everything is permanently deleted.
A snapshot does nothing for any of that. It can rebuild the shell of the account, but it can’t give you back what was inside.
How to actually back up your HighLevel data
You’ve got a few real options, and they’re not equally safe.
The simplest is a manual CSV export. From the Contacts page, an admin can export contacts to CSV on desktop. That gets you the contact fields, but not conversations, notes, tasks, opportunities, or custom objects, and it’s a one-time copy you have to remember to run. Fine as an occasional safety check, but not a strategy you can lean on.
The next step up is rolling your own automation against the HighLevel API, usually with something like n8n, Make, or a Google Sheets sync. This can pull more than a CSV does, but it’s fragile. You’re dealing with API rate limits, jobs that break quietly, no real way to push data back into HighLevel in one move, and ongoing upkeep that lands on you. You end up maintaining infrastructure instead of running your business.
The version that actually holds up is a purpose-built backup. It listens to HighLevel’s webhooks and saves a new version of every contact, opportunity, task, note, and custom field the instant it changes, then lets you restore any earlier version in a single click, straight back into HighLevel. It covers the data a snapshot ignores, and it turns recovery into a click instead of a project.
That’s what we built GHLArmor to do. It’s the first backup approved by the HighLevel Marketplace, it keeps real-time versioned backups of your contacts, opportunities, tasks, notes, and custom fields, and it restores any previous version in one click.
Frequently asked questions
Do HighLevel snapshots back up contacts? No. A snapshot copies account structure such as workflows, funnels, pipelines, and custom fields. Contacts, conversations, opportunities, and history aren’t included.
Can I restore a deleted contact from a snapshot? No. There’s no contact data in a snapshot. Your only native route is HighLevel’s restore-deleted-contacts feature, which works for 60 days. After that the contact is gone for good, and native restore only reverses deletions, not edits or overwrites.
What do HighLevel snapshots actually save? Workflows, funnels, websites, pipelines, calendars, custom fields, email and SMS templates, tags, triggers, campaigns, forms, and surveys. The setup of an account, not the data inside it.
Is there a way to back up HighLevel contacts and conversations automatically? Yes. A backup tool that listens to HighLevel webhooks saves every change to your contacts, conversations, opportunities, and custom fields and lets you restore any earlier version in one click. A manual CSV export or a DIY API script only covers part of your data.
What happens to my HighLevel data if I cancel? You’ve got roughly 90 days to reactivate before the data is permanently deleted. After that, support can’t retrieve it.