How to export and back up Gorelo RMM data
Keep a separate copy of supported Gorelo devices, assets, customer details and monitoring records. This guide distinguishes native portability guidance from RMMBackup snapshots you can browse, compare and download.
Export documented Gorelo managed agents, custom assets, client context, uptime checks, alerts, and supported deletion records.
On this page
Verify the native export or import you need
The Gorelo portability comparison helps you choose between client/contact transfers and a separate copy of RMM device history.
Gorelo's CRM overview describes CSV/API transfers for clients, contacts and products. Ask Gorelo for the template and matching rules for the records you plan to move. Use its platform-switching guide to plan the transition, and preserve device history separately from CRM transfers.
For supported RMM records, define the required devices, client context and monitoring fields, then use the documented reads below. Preserve source IDs and a sample of relationships with every export.
Define the RMM export boundary
This integration deliberately excludes PSA, billing, project, form, document, technician, and API-key inventory. Its export scope is managed agent assets, custom assets and hardware types, clients, locations, contacts, uptime checks, alerts, and explicit deletion entries for clients, contacts, and custom assets.
The managed-agent detail response contains the public API's hardware, operating-system, network, warranty, user, security-posture, and custom-field information. It does not provide separate complete collections for installed software, patch details, policies, scripts, monitoring rules, or activity history.
Capture complete cursor pages and parent details
Gorelo cursor endpoints accept up to 200 records per page. RMMBackup follows the opaque NextCursor, rejects repeated identifiers and cursor loops, and requires the final response to say HasMore is false. It follows every discovered managed agent and client to the documented detail endpoint, and then requests locations for every client.
Original response envelopes are archived alongside normalized record files. Normalization adds only stable IDs, searchable names, and relationship aliases; the vendor fields remain preserved.
Respect permissions and throttling
Gorelo uses X-API-Key. Missing or invalid credentials return 401, insufficient endpoint scope returns 403, and throttling returns 429. The public documentation does not publish a fixed numeric request allowance. RMMBackup uses a conservative application-side pace of 50 requests per minute, honors Retry-After when supplied, and otherwise uses bounded retry delays for throttling, transient server errors, timeouts, and connection failures. The pacing value is not a claimed Gorelo limit and can be reduced for an individual connection.
Validation checks each selected category without requiring it to contain records. An empty response proves that request and response handling works; it does not prove populated-record mapping for that category.
Verify the downloaded snapshot
Compare the managed-agent and custom-asset counts with Gorelo, sample client and location relationships, and inspect representative detailed device fields. Review each collection's complete, partial, failed, or unavailable state before relying on the snapshot.
In the ZIP, check the manifest, provider-native record JSON, and archived gorelo/... responses. A second successful backup should keep unchanged record identities stable while recording substantive field changes. Routine device timestamps configured as volatile do not create meaningful-change noise, but their original values remain in preserved records.
Handle deletion evidence carefully
The deletion endpoint is queried only for record types 1 Client, 2 Contact, and 7 Custom asset, matching the RMM/context scope. Gorelo documents that a restored record leaves this feed and reappears in its normal list. Managed agents instead expose lifecycle status IDs, including pending and completed device/client deletion states.
The current OpenAPI list operation accepts agent status filters 1, 2, 3, 4, and 6 and explicitly excludes deleted and client-inactivated devices. Gorelo's help page separately documents additional agent deletion states, so the published sources do not provide one reliable list-based managed-agent deletion contract. RMMBackup preserves returned status evidence but does not treat ordinary list absence as proof of deletion. This avoids false deletion events after permission or visibility changes and incomplete retrieval.
Plan the next step
For a move, review destination import options, then use the RMM migration checklist. Check the selected native tool before transforming files; an export is not automatically a destination import package. The migration use case explains how successfully captured records remain useful as a separate reference within your plan's accessible history.
Frequently asked questions
Is there one public Gorelo endpoint for a complete account export?
No. The official public API exposes separate resource endpoints, and several product areas have no documented read operation.
Can a RMMBackup Gorelo ZIP restore data into Gorelo?
No. It is an independently retained read-only snapshot for browsing, comparison, and download.
Official source
Gorelo Public API OpenAPI specification
Official machine-readable contract for Gorelo's public API endpoints, parameters, permissions, and response schemas.