RMM data export: devices, reports, CSV and APIs

At a glance

Use a built-in export when you need a specific list or report, and RMMBackup when you need repeatable snapshots over time. Whichever method you choose, verify the included fields, filters, permissions, and record counts.

Choose the right RMM export for device inventories and reports, check file formats, and identify missing data.

Published Updated

On this page

Choose an export method

Want to download supported platform records? Start a free RMM data export and check the included platforms and Free plan limits.

Use the vendor import and export tools comparison to choose between native reports, configuration packages and technical exports before following a vendor guide.

Method Useful for Check before relying on it
Device or asset list Inventory and ownership IDs, selected columns, filters and custom fields
Report export A defined question or date range Summary versus record-level data and file format
Documentation export Client handoffs and reference material Included articles, attachments, passwords and relationships
Configuration package Reusing supported settings or scripts Destination package format, targets and documented exclusions
Official API collection Repeatable reads of documented resources Permissions, pagination, rate limits and nested details
Historical snapshot ZIP Data already captured independently Capture date and successful collection status

CSV is a table format that Excel can open; opening CSV in Excel does not make it a native Excel workbook. PDF reports favor presentation, while JSON preserves nesting. Use only the formats the selected vendor export actually offers.

Export device inventories and reports

  1. Define the customer account, resource, date range, and fields you need.
  2. Include native IDs and customer or site relationships where available.
  3. Record the selected filters and columns with the output.
  4. Compare row counts and sample records with the source view.
  5. Preserve the original file and perform spreadsheet edits on a copy.

An illustrative inventory checklist might require device ID, hostname, customer, serial number, and capture time. Missing fields belong in a gap list; do not infer them from similarly named devices.

Collect through the official API

Choose documented read operations and follow their pagination until complete. Keep original responses and log which resources succeeded. Do not include API keys in filenames, notes, or response archives. A failed page is not an empty collection.

Identify gaps in an all-data export

A report may omit nested details, configuration, or deleted records. Check configuration coverage separately. Data deleted before collection may require an older copy; see historical device information. Decide how long copies remain available through your retention plan.

Download an existing RMMBackup snapshot

For a supported provider capture, open Activity or a snapshot, request the ZIP, wait for Ready, and download it. Check manifest.json, captured JSON records, and original-api-responses/. If a prepared download expires, request it again from the retained snapshot. This downloads a past capture rather than querying the live vendor.

Review current coverage. Snapshot ZIPs do not restore records into a vendor or recover endpoint files.

Prepare an export for migration

Check for an official source-specific importer before transforming files. Keep the original export unchanged; map a copy only when the selected destination workflow requires a template. Check the data import guide for accepted records and validation, then use the RMM migration checklist to track confirmed transfers, exclusions and unresolved history.

Available vendor backup guides

  • Back up Syncro data: separate native CSV and database exports from recurring snapshots.
  • Back up Action1 data: compare report CSV or HTML with scoped API collections.
  • Back up N-able N-sight data: combine inventory and report exports with XML API captures.
  • Back up Hudu data: distinguish native CSV, PDF, and weekly exports from GET-only snapshots.
  • Back up Atera data: compare operational and analytical reports with supported RMM API records.
  • Back up SuperOps data: separate module Data Reports from documented GraphQL captures.
  • Back up Domotz data: preserve documented Public API resources without triggering scans, captures, or device actions.
  • Back up Level RMM data: preserve documented v2 inventory and configuration while recording public API gaps.
  • Back up OptiTune data: preserve documented inventory, groups, metadata, task definitions, alerting configuration, and opt-in stored files without invoking actions.
  • Export Automox data: preserve documented organizations, endpoint inventory, policy and Worklet configuration, patch state, execution history, audit activity, and webhook definitions without invoking actions.

Provider guides

Choose a platform-specific export guide below for exact native steps and file formats. These export pages remain focused on obtaining data outside the source platform; the backup guides above cover recurring RMMBackup behavior, setup, history, and product limits.

Export by dataset