How to export Atera device inventory and reports
Run Atera's Auditor report for a customer or site, then use its Export menu for Excel or PDF. Use the account's documented API for other record exports, and RMMBackup Beta when you need dated copies of supported records to review later.
Export Atera Auditor inventory to Excel or PDF, check customer scope and retired devices, and choose reports or API collection for other records.
On this page
Choose the output you need
Use Auditor for a customer/site inventory, an available Analytical dashboard for summaries, or the public API for record collection. Atera's Data Export FAQ says there is no single Export All Data function and identifies the API for bulk contacts. Analytical presets and custom dashboards depend on plan.
You need technician access to the selected report and customer/site. Check the format offered by that report's Export menu: the general FAQ describes Auditor CSV, while the detailed Auditor instructions specify Excel/PDF. Use the detailed workflow below and confirm CSV availability in your account if CSV is required.
Export an Auditor device inventory to Excel or PDF
For a platform move, compare Atera import and export methods before preparing a destination file; an Auditor report and an asset importer have different scopes.
- Open Reports > Monitoring > Auditor as shown in the Auditor guide.
- Select the Customer (MSP) or Site (IT Department).
- Set Exclude retired devices and Hide excluded patches as needed.
- Choose Generate and inspect the result.
- In the top-right Export menu, select Excel or PDF.
- Save the original with its customer/site and date.
Auditor includes device inventory, hardware, disk and selected software/patch information. Its software summary is not an inventory of every application; MS Project is excluded, and Linux port/patch details are unavailable. Download the export-validation checklist to record scope and omissions.
Validate the Auditor export
Our suggested checks:
- Open the Excel workbook or PDF and confirm it is readable; retain the original format.
- Compare the device count with the generated report for that customer/site.
- Check the retired-device option and sample a known workstation and server where present.
- Verify hardware values and customer context. Check whether stable identifiers are included before joining to another file.
- Repeat for each required customer/site and keep files separate. The Operational Reports FAQ limits Auditor to one customer at a time.
For Analytical exports, the Data Export FAQ describes approximately 5,000 rows per batch. Do not apply that number as a universal Auditor or API limit. Compare totals and check for truncation in the particular export you use.
Export a Windows 11 hardware-readiness report
For upgrade planning, use Atera's Windows 11 Readiness and Compatibility Assessment. It describes uploading the hardware-readiness script, assigning it through an IT Automation profile, and opening the resulting Patch & Automation Feedback report. Compare devices with returned results against all assigned devices; an endpoint that did not run is not a compatibility pass.
The detailed export steps list Excel/PDF, while the overview mentions CSV. Use the format offered in your report and confirm CSV availability if required. This is a script-result report, separate from Auditor inventory. The profile route is documented for all Atera customers; the script-based custom-field alternative depends on plan. RMMBackup Beta's inventory/custom-value coverage does not establish script execution or automatic capture of this readiness report.
API-based collection
The API guide explains access to the account's API reference. Use that reference to choose fields and follow pagination for each resource. The RMMBackup list below shows the data its Atera integration backs up.
Open Admin > Data management > API, then API documentation, following Atera's API guide. Use a token with read access to the required domains and compatible IP restrictions. Confirm resource paths, filters and pagination in that account's reference before collecting; the general FAQ is not an endpoint specification. Keep original JSON before deriving tables. Compare entity counts and customer IDs with the UI. A failed page makes the run incomplete, not a smaller successful inventory.
RMMBackup Beta backs up supported Customers, Contacts, Agents, Devices, Alerts, and CustomValues records, along with available hardware details for each managed agent.
These ZIPs contain captured records and original API responses, rather than an Auditor workbook or PDF. Check collection status before relying on a file; incomplete captures do not establish deletions or a new comparison baseline. Earlier records are useful during an outage or after deletion only if captured successfully beforehand and still accessible under your plan.
Troubleshoot coverage gaps
- Missing contacts are expected from a device report; use the documented Contacts API for a bulk JSON export.
- A low device count usually means the report or role is scoped. Recheck the selected customer and account visibility.
- If a desired Analytical export is absent, confirm the plan; do not assume every dashboard exports the same format.
- For large API collections, verify every page and preserve the raw responses before converting them.
Keep dated configuration notes alongside native exports. The configuration inventory template helps record settings that the Auditor CSV does not contain.
Plan the next step
For a move, review Atera import options or the Atera-to-Syncro migration guide, 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.