How to back up Gorelo RMM data

At a glance

RMMBackup keeps a separate, read-only history of the RMM and asset-context data exposed by Gorelo's public API. Connect a dedicated API key, choose the categories your MSP needs, validate access, and inspect the first successfully captured snapshot.

Back up documented Gorelo managed agents, custom assets, clients, locations, contacts, uptime checks, alerts, and supported deletion records.

Published Updated

On this page

Create and scope the API key

In Gorelo, open Settings > Integrations, configure the API integration, and choose Generate New Key. Give the key read access to Clients, Contacts, Assets, Alerts, Uptime, and the deletion records needed for clients, contacts, and custom assets. Gorelo returns 403 Forbidden when a key lacks an endpoint's scope.

Copy the key when Gorelo shows it. RMMBackup stores customer credentials through its encrypted provider credential store and never displays the stored value again. The integration uses the official US API endpoint, https://api.usw.gorelo.io/, and sends the key only in the X-API-Key header.

Method Best use Important limitation
Gorelo public API script Retrieve selected documented resources as JSON You must implement complete cursors, detail traversal, throttling, partial captures, safe storage, and history
RMMBackup Repeat selected RMM collections into separate Gorelo snapshots and download captured ZIPs Includes the supported data listed below
Manual report or screen export Answer a narrow operational question It does not provide repeatable provider-scoped snapshot history

Follow the Gorelo API credential guide for the key creation and safe rotation workflow.

Choose what Gorelo data to back up

All supported categories start enabled, and you can change the selection in Settings > Integrations > Gorelo.

Category Data preserved Important limitation
Clients and locations Client detail, domains, API-visible custom fields, and every returned location Client deletion can also make child contacts disappear from normal lists
Contacts Contact identity, status, client/location relationships, and communication fields The integration does not collect ticket conversations or other PSA records
Managed agent assets Device status, hardware and OS summary, IP data, warranty, users, security posture, and API-visible custom fields The API does not expose separate full software, patch, policy, or script collections
Custom assets and hardware types Custom asset identity, assignments, serial, warranty, IP address, and hardware-type definitions Custom assets are distinct from managed agent devices
Uptime checks Target, type, status, cadence, retries, region, tags, and maintenance configuration This is check configuration, not a complete uptime-results history
Alerts Alert status, severity, message, device/client/check relationships, and timestamps Ticket, contract, and billing records referenced by some alerts are not collected
Deletion records Explicit client, contact, and custom-asset deletion entries Gorelo's deletion endpoint does not document managed agent deletions

For managed agents, the backup includes the hardware, OS and security details returned with the device record. Policy definitions, script source and separate software or patch inventories are outside the current Gorelo backup.

Validate and run the first backup

  1. In Settings > Integrations, choose Gorelo and leave the region set to United States.
  2. Enter the API key, choose the categories, and save the connection.
  3. Validate the connection. RMMBackup checks each selected endpoint and accepts valid empty collections.
  4. Enable the validated connection and start a manual backup.
  5. Review every collection status, compare the managed-agent count with Gorelo, and inspect representative device details and customer relationships.
  6. Download the snapshot ZIP and review its manifest and preserved gorelo/... source responses.

After the first successful backup, normal plan, retention, and scheduling rules apply. Free allows one accepted manual attempt per rolling 24 hours across the MSP account, retains access to the latest fully successful snapshot, and has no automatic schedule. Full Access allows two accepted manual attempts per rolling 24 hours for this vendor, ongoing accessible history, and a daily schedule after the first fully successful backup. Full Access is free during open beta; contact support to activate it.

Understand partial captures and deletion safety

Cursor-based collections complete only when every page succeeds and Gorelo returns a final page with HasMore false. Detail and per-client location traversal must also finish. A timeout, exhausted retry, permission failure, malformed response, missing detail, or broken cursor produces a failed or partial collection; it is never converted into an empty successful inventory.

RMMBackup requests every status filter accepted by the current managed-agent list contract, including pending-delete and pending-client-inactive records. Gorelo's separate help page also documents deleted and client-deleted agent states, but the current OpenAPI operation says deleted and client-inactivated devices are excluded from the list. The integration therefore does not claim reliable managed-agent deletion detection. It captures the explicit deletion feed for clients, contacts, and custom assets, and ordinary absence from a later list is not classified as deletion because access or visibility may have changed.

Review the Gorelo RMM export guide for export options and the data included in your download.

Before changing platforms, follow the RMM migration checklist. For records that disappear from the source, use the deleted-device guidance together with Gorelo's explicit deletion and lifecycle evidence.

Frequently asked questions

Does RMMBackup run Gorelo scripts, scans, or remote sessions?

No. The Gorelo adapter uses documented GET operations only and never invokes actions or write endpoints.

Does this back up every part of a Gorelo account?

No. It intentionally covers RMM and asset context only, and the saved data is limited to the categories listed in this guide.

Official source

Gorelo API guide

Official Gorelo instructions for API keys, the US base URL, authentication, permissions, and agent status IDs.

Related Gorelo integration

Review current Gorelo backup coverage and availability.