Datto RMM data export: inventories, reports and API reads
Use Datto RMM CSV and PDF exports for targeted reporting, or use RMMBackup Beta to keep repeatable snapshots of supported account, site, device, inventory, patch, alert, and activity records.
Export Datto RMM inventories and reports, or keep repeatable snapshots of supported account, site, device, patch, alert, and activity data.
On this page
Keep configuration packages alongside reports
Compare Datto RMM package and report exports before choosing a file: policy/component portability and device-history exports are separate tasks.
Datto RMM provides native component and monitoring-policy packages as well as report exports. Use the Datto RMM import guide for .cpt and .pcy handling, policy exclusions and target checks. These packages serve a different purpose from the component metadata retained by RMMBackup; neither package format establishes device-history migration.
Available export methods
Use native exports for spreadsheet-ready tables and reports for presentation. The API can collect documented account, site, and device data programmatically.
Device and asset lists
In the report workflow, choose the required export, then configure device or site targets and available criteria. Generate the file and verify that its targets match the inventory you intended to preserve. A report with no useful targets is not proof of an empty estate.
Reports and file formats
Datto RMM documents PDF reports and CSV exports. Keep the original CSV before opening it in Excel. The available columns and criteria depend on the selected export, so retain those choices with the file.
Export patch details with multiple statuses
In Analytics > Reports, add Patch Details export, choose device/site targets, select any or all of Approved, Not approved and Installed, and choose columns. The Reports reference documents these options for Windows patch data. Use this multi-status CSV before building a merge from separate approved/installed files.
Our suggested check is to compare targets, device counts and representative patch states with the report. Record the selected statuses and generation time. If a join is still needed, inspect native device and patch identifiers in both files; a KB label alone may not distinguish the patch variants needed by the task. Current patch status is not a complete ledger of historical installation events.
Export job stdout as usable CSV
Open Automation > Jobs, select the job and choose the required run in Job History. In its Devices table, select the endpoints, then choose Export Selected StdOut/StdErr. The Job results reference documents stdout/stderr selection, Output only (no job summary information) and a custom file extension. A .csv extension leaves the contents unchanged.
The table's Export Selected Rows to CSV exports displayed row information; it is separate from script output. For stdout to form a usable table, the script must emit consistent delimited records. Our illustrative schema is device_id,component_id,execution_time,status,value, not a guaranteed Datto layout. Check headers, delimiter, quotes, commas/newlines in values and device identity before combining results. Multiple components with output can produce multiple downloads; inspect every file. Datto documents output truncation above 1,048,576 characters, so check for truncation before treating a result as complete.
RMMBackup Beta job discovery is limited to identifiable jobs. Use the native output download when you need script stdout; a captured job record does not establish complete output capture.
Why are nested values or UDFs missing from an API CSV?
Native report-column choices and a PowerShell wrapper's output are different. In the community DattoRMM.Core module, device/site, antivirus, patch and user-defined-field values can be nested objects. Direct CSV serialization can leave class names instead of the values you need.
The project's CSV export documentation describes Export-RMMObjectCsv transforms and explicit UDF selection with -Udf or -IncludeUdf; default transforms exclude UDFs. Check the installed version and help, then sample populated, blank and multiline values. Preserve device/site IDs and original JSON before flattening. These wrapper defaults do not establish missing columns in Datto's native reports.
API-based collection
RMMBackup traverses the documented account, site, device, audit, patch, alert, activity, filter, and component-metadata reads selected for the connection. Paginated responses provide pageDetails; the collector follows nextPageUrl until it is null and rejects a next-page URL outside the chosen official platform host. Activity retrieval starts at the Unix epoch instead of accepting Datto's 15-minute default, so it captures all history the API still exposes.
The snapshot ZIP includes the original captured records and source responses. Component coverage includes descriptive information, but not script or package contents. Job history is limited to jobs the connection can identify. Review the Datto RMM integration for supported backup data and Beta qualifications.
Exporting all available data and identifying gaps
Check every selected collection's completion state before relying on a snapshot. A failed page or detail scope produces a partial collection, does not create a deletion baseline, and does not turn missing results into deletions. "All sites" means all sites visible to the configured API identity; Datto permissions can hide additional sites or devices.
Additional official references
Plan the next step
For a move, review Datto RMM configuration imports, 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.