How to back up Level RMM data

At a glance

RMMBackup keeps a separate, read-only history of supported Level devices, groups, tags, custom fields, alerts, updates, and activity. Use the guide below to connect Level, choose what to protect, and verify your first snapshot.

Back up documented Level devices, groups, tags, custom fields, automations, alerts, updates, activities, and discoverable automation-run details.

Published Updated

On this page

Choose a Level backup method

Method Best use Important limitation
Level public API script Retrieve selected documented resources as JSON You must implement cursor completeness, retries, secure storage, scoped custom-field traversal, and history yourself
RMMBackup Repeat selected read-only collections into separate Level snapshots and download captured ZIPs Coverage is limited to resources exposed by Level's public API
Manual report or screen export Answer a narrow operational question It is not evidence of a recurring, independently retained provider snapshot

Review the Level integration and official developer reference before treating the API as a complete account export.

What RMMBackup backs up from Level

RMMBackup captures expanded device inventory and security data, group hierarchy, tags, custom-field definitions and organization/group/device values, non-archived automation summaries, automation webhook definitions, alerts, updates, activities, and automation-run details whose IDs appear in activity references.

Resource area Relationship retained Public API limitation
Devices and groups Native device and group IDs plus parent/child hierarchy Only resources visible to the organization key are returned
Custom data Field ID plus organization, group, or device assignment Every discovered assignment scope must complete
Automations Automation, group, device, and discoverable run IDs Definitions, scripts, archived automations, and a complete run list are absent
Alerts, updates, and activity Device and referenced-object IDs Source retention can make older entries unavailable

The current public API does not expose script bodies, monitors or monitoring policies, full automation definitions, archived automations, or a list of every automation run. Activity references to those object types do not replace the missing source definitions. See the Level export guide for the precise boundary.

Set up recurring Level backups

  1. Create a dedicated read-only key by following the Level API credential guide.
  2. In Settings > Integrations, select Level and paste the key.
  3. Select the documented collections needed by the MSP and save the connection.
  4. Validate the connection before enabling backups.
  5. Start a manual Level backup and review every collection status.
  6. Compare representative devices, group relationships, custom values, and automation summaries with Level, then inspect the downloaded ZIP.

After the first successful backup, RMMBackup applies the existing tenant plan and scheduling rules. Manual backups remain scoped to this Level connection.

Free allows one accepted manual backup attempt per rolling 24 hours across the MSP account, keeps the latest fully successful snapshot accessible, and does not schedule automatic backups. Full Access allows two accepted manual attempts per rolling 24 hours for this vendor, keeps ongoing accessible history, and adds a daily automatic schedule after the first fully successful backup. Full Access is free during open beta; contact support to activate it. See pricing.

Understand partial captures and deleted devices

Level list requests are complete only when every cursor page succeeds and ends with has_more set to false. Authentication errors, permission failures, throttling exhaustion, timeouts, malformed pages, and failed custom-field scopes produce failed or partial collection results rather than empty captures.

Device deletion detection advances only after a complete successful Devices collection. Historical alerts, updates, activities, automation runs, and custom-field values do not infer deletion because source retention and scope changes can make absence ambiguous.

Before a migration, capture and verify a complete Level snapshot while the key still sees every required device and group. Keep separate supported exports for configuration the API omits and follow the RMM migration checklist and deleted-device guidance.

Review and download Level backup history

RMMBackup preserves Level identifiers, relationships, original records, and source responses for browsing, comparison, and backup ZIP downloads.

Frequently asked questions

Does RMMBackup run Level scripts or automations?

No. The Level adapter uses documented GET operations only. It never invokes webhook triggers or other action and write endpoints.

Is this a complete backup of all Level configuration?

No. Level's current public v2 API does not expose script contents, monitor or policy definitions, archived automations, or full automation definitions.

Official source

Level developer API reference

Official Level reference for public v2 resource paths and response schemas.

Related Level integration

Review current Level backup coverage and availability.