How to back up Atera data
RMMBackup keeps a separate history of supported Atera customers, contacts, agents, hardware details, monitoring devices, custom values, and alerts. Use the guide below to connect Atera, choose what to protect, and verify your first snapshot.
Back up supported Atera customers, contacts, devices, hardware details, alerts, and custom values.
On this page
Choose an Atera backup method
| Method | Useful for | Important limitation |
|---|---|---|
| Native reports and dashboards | CSV from operational reports; PDF or Excel from supported analytical dashboards | Format, plan, filters, fields, and row limits vary; no single export-all action exists |
| API script | Retrieve supported JSON entities with pagination | Your script must handle tokens, permissions, IP restrictions, pagination, failures, storage, and verification |
| RMMBackup | Repeatable snapshots of supported Atera RMM data, with browsing and snapshot ZIPs | Coverage is limited to the supported data below |
Atera's Data Export FAQ distinguishes quick manual reports from bulk or recurring API collection. Native exports remain useful for independent verification even when RMMBackup is used.
See the Atera integration for the Atera data RMMBackup can back up.
What RMMBackup backs up from Atera
| RMMBackup collection | Captured Atera data | Boundary |
|---|---|---|
| Customers | Documented customer list fields | Limited to API-token visibility |
| Contacts | Documented contacts | Account permissions determine which contacts are available |
| Agents / Managed Devices | Windows, macOS, and Linux agent records with their original device details | Routine live-status updates are filtered from meaningful change alerts |
| Agent Hardware Details | Per-machine agent detail, including documented BIOS and battery fields | Derived from agent detail; deletion inference is disabled for this child collection |
| Monitoring Devices | SNMP, TCP, HTTP, and Generic devices | Separate from managed agents |
| Custom Field Values | Documented CustomValues records | Preserves the original values returned for accessible records |
| Alerts | Active and resolved alert records returned by the API | Source permissions and fields determine coverage |
The table above lists the Atera data currently backed up by RMMBackup. The connected account's permissions determine which records are available in each backup.
Set up recurring Atera backups
- Create and verify a RMMBackup account.
- Follow the Atera API token guide and grant custom Read access only for Customers, Contacts, Agents, Devices, Alerts, and Custom Values.
- In Settings > Integrations, choose Atera, enter the token, and select the collections you need.
- Save and validate the connection; a token can authenticate while lacking one collection's permission.
- Run a manual backup and inspect all collection statuses and representative records.
- Compare the device and customer counts with native Atera reports, then inspect the RMMBackup ZIP.
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.
Browse history and export captured data
RMMBackup lets you browse and compare accessible versions of Atera records and download a backup ZIP containing a contents summary, original records, and saved source responses. Use the Atera export guide to compare this history with Atera Auditor reports and dashboard exports.
If part of a backup fails, RMMBackup keeps the last complete version as the comparison baseline so incomplete results do not appear as deleted records. Atera history, browsing, and ZIP downloads remain separate from other integrations.
Preserve Atera data before switching providers
Export the Auditor report and any required operational or analytical reports, then complete and inspect a RMMBackup backup while the connection still works. Record report filters, row counts, and device/customer identifiers. Follow the migration checklist and Atera configuration guide to preserve the records you may need after the move.
Review records from deleted devices
If RMMBackup successfully captured an agent or monitoring device before it disappeared, an earlier accessible backup can still show the saved fields. See Atera deleted-device guidance and Atera retention notes to understand when earlier records remain available.
Frequently asked questions
Can Atera export all account data at once?
No. Atera's official Data Export FAQ says exports are performed per entity through reports, analytical dashboards, or API requests.
Can RMMBackup recover a device deleted before backup?
No. Atera native exports exclude deleted records, and RMMBackup can only show records it captured while they were returned by the API.