How to export and back up Level RMM data
Use Level's native exports for targeted device lists or reusable configuration, and RMMBackup for repeatable history of supported records. Check which fields each method includes before relying on it for a platform move.
Compare native Level CLI exports and automation specifications with RMMBackup history for supported devices, configuration, alerts and activity.
On this page
Choose a native CLI export or configuration specification
The Level tools comparison separates device-list CSV, CLI exports and automation imports from historical device-data transfer.
The official Level CLI Reference documents device, alert and run CSV exports, JSON lists, and YAML/JSON automation specifications. Check the active profile, command help and pagination before export, then compare IDs and counts with the intended scope.
These CLI capabilities are separate from Level's public v2 API contract and RMMBackup's implemented coverage below. A CLI automation specification is not the same artifact as a RMMBackup automation summary. Level also documents Resource Library imports; library items do not transfer old execution history.
Level also provides a native Device Listing CSV export: use Export to CSV for devices matching your active filters. The export includes all available columns, regardless of visible-column selection. Confirm group permissions and filters before comparing counts.
Define the Level export scope
One Level connection belongs to one MSP and one Level organization key. Record the intended organization and expected device/group counts before capture. Use Level's native IDs when reconciling records because names can change or be reused.
Export documented resources
Start with Devices and Groups, then capture Tags, Custom Fields, and Custom Field Values. Device requests include every documented inventory and security expansion. Custom values are queried at organization scope and once for each discovered group and device so assignment relationships remain explicit.
Automation exports include only non-archived summary fields exposed by GET /v2/automations plus webhook trigger definitions. Activity references can reveal automation-run IDs; RMMBackup follows those IDs to the run detail endpoint with steps enabled. There is no public list-runs endpoint, so this is not a guaranteed complete execution-history export.
Respect cursor and throttling behavior
Level list endpoints return up to 100 items and a has_more flag. RMMBackup sends the last native cursor as starting_after, rejects loops and incomplete pages, and archives each original response. Custom-field-value items are the exception: their documented schema has no separate value ID. If one assignment scope exceeds 100 values, RMMBackup uses the documented custom_field_id filter for every completely listed field instead of guessing an undocumented cursor.
Level documents HTTP 429 with Retry-After but does not publish a fixed numeric request limit in the cited public documentation. RMMBackup honors that response and applies bounded backoff rather than claiming an unsupported requests-per-minute value.
Verify the exported result
Check every selected collection status, compare expected device and group counts, inspect group IDs on devices, sample custom-field assignments, and review automation and activity boundaries. Open the ZIP and verify its manifest, native record files, and archived level/... response pages.
Script contents, monitors, monitoring policies, full automation definitions, archived automations, update policies, and full organization settings are not exposed by the current public v2 API and are not backed up. Keep any separate supported native exports needed for those gaps.
Keep offline, deleted and Hudu-archived states distinct
Level's Hudu integration synchronizes devices into documentation assets using mapped groups and companies. Its roadmap marks Hudu endpoint archiving for devices deleted from Level as completed. That deletion behavior does not establish what happens when a device is merely offline.
Before offboarding, check the integration's current settings and compare the Level device ID, connection/deletion state and corresponding Hudu asset/archive state. Keep a dated independent copy of required fields before changing lifecycle state. Synchronization keeps a connected system current; a successfully captured RMMBackup record preserves the values saved at that time. RMMBackup does not control Hudu archiving through the Level connection.
Keep Level data protected
Snapshot data can contain device inventory, activity details, automation output, and webhook trigger URLs. Limit access to authorized people, protect downloaded files, and rotate a Level webhook if its trigger URL is exposed. RMMBackup only preserves the captured URL for reference.
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 Level endpoint that exports the entire account?
No. The public API exposes separate resource lists, and some Level configuration visible in the product has no documented read endpoint.
Does a RMMBackup Level ZIP restore into Level?
No. It is an independently retained snapshot artifact for browsing, comparison, and download.
Official source
Level v2 REST API OpenAPI definition
Official machine-readable contract for Level's documented public v2 endpoints and schemas.