Atera allows you to export most operational data via reports (CSV) or the public API (JSON).
Reports are ideal for quick, manual exports, while the API provides full access to large datasets, automation, and scheduled export workflows.

Some data types—such as tickets and contacts—do not have a built-in bulk export option in the web interface. These can be exported only through the API, which is the recommended method for complete data coverage.
 

Overview

Q: How can I export customer data from Atera?
A: You can export customer data using either reports or the API:

• Reports: Run the Customer Health ( or any other cusotmer-facing report) report under Reports > Operational and export as CSV.

• Analytical Reports: Access customer and ticket metrics in Customer Overview or Tickets Overview dashboards under Reports > Analytical.
  (Presets available on Growth/Expert; custom dashboards on higher plans.)

• API: Retrieve your API key from Admin > Data Management > API, then call the endpoint GET /api/v3/customers.

Q: Is there an “Export All Data” function in Atera?
A: No. Data must be exported per entity (customers, devices, tickets, etc.) via reports or the API.

Q: Which data formats are supported for export?
A:

• Reports: Export as CSV.

• Analytical Reports: Export as PDF or Excel from dashboards. ((Presets available on Growth/Expert; custom dashboards on higher plans.)

• API: Returns JSON, which can be converted to CSV/Excel.

Reports vs. API

Q: When should I use reports vs. the API?
A:

• Reports: For quick, ad-hoc exports within the UI.

• Analytical Reports: For visual summaries, trend analysis, and limited exports in PDF/Excel formats. (Presets for Growth/Expert; custom for higher plans.)

• API: For bulk, automated, or recurring exports, especially for entities without direct UI export.

Q: Can I schedule exports?
A: Not via the Atera UI. However, you can schedule automated exports using the API and your own scripts (e.g., PowerShell, Python, or cron jobs).

Customers, Contacts & Users

Q: Can I export customers and users?
A: Yes—use Operational reports (CSV) or the API for complete export.

Analytical Reports can show customer-level summaries, user activity, and ticket distribution. (Growth/Expert presets, custom on higher plans.)

Q: How do I export user or contact information?
A:

• Reports: Pull from Customer Health or similar reports.

• Analytical Reports: Retrieve summarized user/contact data (e.g., ticket volume per contact). (Available depending on plan.)

• API: Use GET /api/v3/contacts to export all contacts in JSON. 

Q: Can I export customer location or sub-account data?
A: Yes, using either reports, analytical dashboards (where available), or the API. You can include additional attributes using custom fields.

Devices & Assets

Q: How do I export device lists per customer?
A: Run the Auditor report under Reports > Operational, then export as CSV.
You can also use Analytical Reports to view device status, performance metrics, and agent installation summaries. (Presets for Growth/Expert; custom for higher plans.)

Q: Can I export all device data (including customer names and device status)?
A:

• Reports: Use Analytical reports (up to ~5,000 rows per batch).

• Atera's analytical reports

• API: Retrieve your API key, then call endpoints like GET /api/v3/agents or GET /api/v3/devices.
  These endpoints return detailed device data (including customer and status). Use pagination for large exports and convert the results to CSV or Excel for reporting.

• GET Agents API

Q: Can I export custom asset types and metadata?
A: Yes. If custom fields exist, they appear in API results and in mapped reports. For full exports, use the CustomValues API endpoints.

• Custom Values
   

Tickets & Alerts

Q: How do I export tickets from Atera?
A:

• Reports: Use Timesheet, Ticketing Summary, or Customer Tickets Overview, then click Export (CSV or Excel).

• Analytical Reports: Access Tickets Overview, Technician Performance, or Response Time dashboards for visual metrics and exportable summaries.
  (Presets for Growth/Expert; custom dashboards on higher plans.)

• API: Use GET /api/v3/tickets for complete ticket data.

Q: How do I export alerts and their resolution statuses?
A:

• Reports: Use Alerts or Automation Feedback reports.

  - Ticket alerts

  - Site Health

  - System at-a-glance

  - Customer Health

• Analytical Reports: Access alert trends and performance insights via Site Health or System Overview dashboards. (Plan-dependent.)

• API: Use the GET /api/v3/alerts endpoint to export all alerts and statuses in JSON format. Convert to CSV/Excel if needed.

       - GET Alerts API

Billing & Accounting

Q: Can I export billing or accounting data (QuickBooks, Xero, etc.)?
A: Yes—invoices and billing batches can be exported or synced directly to QuickBooks Online/Desktop or Xero.

Q: Will exported invoices include ticket details?
A: Yes—if invoices were generated at the ticket or time-entry level, all related details are included.

Q: Can I export product, expense, or time-entry reports?
A: Yes—these can be exported as CSV via Billing > Reports or the Timesheet report.

Custom Fields

Q: Are custom fields included in exports?
Reports: Custom fields appear as additional columns in Auditor or Device exports.

• Analytical Reports: Displayed as columns or filters in dashboards (depending on plan).

• API: Use CustomValues endpoints to retrieve all custom field data.

   

Limits, Filters & Data Scope

Q: Are there limits to exports?
A:

• Reports: Typically limited to ~500–5,000 rows per export.

• API: Supports pagination, allowing export of much larger datasets.

Q: Can I export by date, status, or customer?
A: Yes—filter within reports or use API parameters for targeted exports.

Q: Are deleted records included?
A: No—only active records are included in exports.

Security & Unsupported Items

Q: Will exports include passwords or sensitive credentials?
A: No—passwords and sensitive data are never exportable via UI or API.

Q: Are attachments included in bulk exports?
A: No—attachments must be downloaded individually.

Q: Can I export automation settings, thresholds, or monitoring profiles?
A: No—these are not currently exportable. You’ll need to document or recreate them manually.

API-Only Export Workflows

Some data—especially tickets, contacts, and custom objects—does not have a “bulk export” option in the Atera console.

These must be retrieved through the API.