HighLevel backup
HighLevel keeps its platform running, but it does not keep a history of a client account that you can restore from: a bad import, a workflow that overwrote thousands of contacts, a deleted pipeline or a lost conversation history cannot be undone from HighLevel's side. Caryvane backs up each client account (contacts, notes, tasks, opportunities, conversations, calendars, invoices, payments and more) into the customer's own storage every night, keeping every version.
Deleted contacts can be restored inside HighLevel for a limited time, the contact record only. HighLevel's own database backups protect its platform, not one client account, and are not available to you. Snapshots copy a client account's setup (funnels, workflows, pipelines), not its contacts or conversations.
1. Connect your company #
One sign-in covers as many client accounts as you choose. Nothing is installed at the customer, and nobody creates an app in HighLevel.
- Connectors → choose the customer → in the HighLevel card, Connect HighLevel. A new tab opens HighLevel's consent page for Caryvane's app.
- Sign in as an admin of your company's HighLevel account, choose the company, and choose the client accounts to back up (or all of them). A single client account can also install the app on its own.
- Back in the console, refresh the card. Each chosen client account is listed.
- If you connected for a company that serves several of your customers, use ⋮ → Give to another customer on each client account to put it with the customer it belongs to. Its backup then goes to that customer's storage and is billed to them. Do this before choosing storage.
- On each client account, Choose storage: a cloud storage target of the customer's, a folder, and how long to keep history (seven years by default). The first backup starts at once.
- With many client accounts, use Back up all waiting client accounts instead: one storage, folder and retention for all of them, each in its own folder with its own job. Tick Start client accounts that arrive on a later sign-in automatically and the ones added later start on their own the next time HighLevel is connected. Stop starting new ones turns that off; client accounts already backing up carry on.
The destination must be object storage that encrypts at rest (Amazon S3, Wasabi, Backblaze B2, Azure Blob, DigitalOcean Spaces, Cloudflare R2, Linode or Vultr). Contacts, conversations and payments are personal data; an SFTP server, network share or local folder is refused. Other S3 storage (OVH, Scaleway, MinIO and so on) is accepted when its bucket has default encryption switched on: Caryvane asks the bucket when you save, and if it does not, the message says how to switch it on.
Each client account gets its own folder, named after it, inside the folder you chose. Caryvane keeps your company's sign-in encrypted on its server; the backup workers only ever receive a short-lived token for one client account.
2. What is captured #
- Contacts, with their notes and tasks; tags, custom fields and custom values.
- Opportunities and pipelines with their stages.
- Custom objects: each schema and its records.
- Conversations, and their messages: SMS, email, calls, WhatsApp, Facebook and Instagram, as HighLevel's message export gives them.
- Calendars and appointments, from three years back to a year ahead.
- Invoices, orders, transactions, subscriptions and products.
- Form and survey submissions, email templates, users, and the media library (each file's content, once).
Every night each list is read in full and a record is written only when it changed, so a quiet night costs almost nothing in storage. Conversations and messages are read from where the last run stopped. Every version of every record is kept as its own file for the retention period; a record deleted in HighLevel is marked as gone, never removed. If HighLevel ever answers with far fewer records than were there the night before, nothing is marked deleted on that evidence: the run says so and the next run decides.
HighLevel allows each app a fixed number of requests per client account per day. A very large first capture can reach it; the run then stops as Partial and carries on from where it got to the next night.
3. What HighLevel does not give any backup product #
HighLevel's API does not expose the design of funnels and websites, and for most accounts not the steps of workflows. No backup product can capture them. Keep a HighLevel snapshot for those designs, and Caryvane for the data.
4. Getting data back #
On the HighLevel card, Browse backup on a client account opens its backup. Pick a date to see every record as it stood then; records since deleted in HighLevel are marked. Open a record to see each captured version, compare two versions field by field, and download any of them.
- Restore over the original sets the live record back to the chosen version. If HighLevel no longer has it, it is re-created. A re-created contact gets a new id in HighLevel, so restore it first and its notes and tasks after it.
- Restore as a copy creates a second record beside the live one, which is left alone. It is offered for notes, tasks, opportunities, custom object records and products; HighLevel would match a copy of a contact, custom value, custom field or tag to the original.
- What can be restored: contacts, notes, tasks, opportunities, custom values, custom fields, tags, custom object records, products and media files. A media file is uploaded again as a new file, because HighLevel cannot replace a file in place. A product's prices are not changed.
- Export takes the client account as at a date as a ZIP of HighLevel's own JSON, or its contacts as a CSV for HighLevel's Contacts → Import.
Every restore is listed with what was done and who asked for it, and appears in the access report. Conversation history, payments, invoices and form submissions cannot be written back into HighLevel by any means; the backup keeps them as a complete, dated record you can download.
A client account connected before restore was available needs to be reconnected once, with Reconnect on its row, to give Caryvane permission to write.
5. What it costs #
Each client account is backed up by its own job in Caryvane's cloud, and is billed like any other cloud job: one cloud credit for each day its backup runs, plus the data transferred. However often it runs in a day, a day is one credit. Disconnecting a client account stops its job, so it uses no more credits; what was backed up stays for its retention period. Ask us for the current rates.
Notes #
- If the app is uninstalled from a client account in HighLevel, Caryvane stops that client account's backup at once and its row says why; what was backed up is kept. Install the app and connect again to resume. If your company's sign-in is revoked instead, the client account shows Reconnect needed; connect HighLevel again and backups resume with no gap in history.
- Disconnecting in Caryvane stops the backup, so it uses no more cloud credits; to remove the app from HighLevel as well, uninstall it there.
- HighLevel tells Caryvane when a note is added, changed or deleted, and that contact's notes are backed up on the next run. Every contact's notes are also checked in full over the course of a week, which catches anything HighLevel did not report.
- HighLevel backups run on Caryvane's cloud workers, from Caryvane's published addresses (see IP addresses and firewalls).