How to export and back up Action1 data
Use Action1 report exports when you need a targeted report, or use RMMBackup to keep repeatable snapshots of supported organizations, endpoints, software, updates, vulnerabilities, configuration, reports, and activity. This guide helps you verify what each option captures.
Export or back up Action1 organizations, endpoints, software, updates, vulnerabilities, configuration, reports, and operational history.
On this page
Export audit evidence and distinguish group imports
The Action1 tools comparison separates report exports from endpoint-group CSV imports, which organize devices already under management.
Action1's Audit Trail requires View Audit Trail permission and supports CSV export. Review the date, user and event filters: GET events are excluded by default. Save the filters with the file so another technician can understand its scope.
The endpoint-group CSV import expects an Endpoint Name column and endpoints that already have agents. It assigns membership rather than importing old device history. Regional migration is a separate internal account move; plan its documented manual configuration work before cutover.
Export automation history and failed-run details
Open History, or Automations > View History, to find a run. Filter by completion status or search for its name, then open the session or Actions > View Details. For one device, use its Automation History tab. Action1's Viewing Automation History describes session times, target endpoints and operation details. A session's overall status and an individual endpoint's result answer different questions.
For a failed run, save the organization, run identity, affected endpoint, execution time and visible operation/error detail. Keep the Audit Trail CSV separately: account audit events are not a substitute for endpoint execution results.
For a custom reporting file, the official API reference separates automation instances, endpoint results and result details. Action1's Halo connector reader demonstrates joining completed Warning instances to endpoint errors. Its selected statuses are an example, not an exhaustive definition of failure or cancellation.
A suggested reporting layout, to map against actual responses, is organization ID, instance ID, endpoint ID, execution time, run status, endpoint status and error/output detail. Confirm permissions, every page, timestamp meaning and the detail relationship against one known run before using it for audit evidence. This is a proposed derived table, not an existing flattened CSV or a promise of complete stdout.
RMMBackup captures supported automation instances, endpoint results and details as dated records. That saved history can support a later investigation; scheduled failure emails and custom reporting files require their own workflow. Report subscriptions below establish scheduled report delivery, not a failed-automation email service.
Export installed software and schedule report delivery
Open Real-Time Reports & Alerts > Built-in Reports > IT Asset Management > Software Inventory, then Installed Software. Expand an application to inspect affected endpoints and version details. The Software Inventory guide distinguishes the application summary/count from endpoint details. Use Tools to export CSV or HTML as described in Working with Reports.
For recurring email, select the intended organization in the report, then Tools > Subscribe, enable the subscription and set its schedule and recipient. Action1's Scheduled Reports instructions require View Reports permission and currently allow one recipient address belonging to an Action1 user. Save the settings and inspect a delivered report before depending on it.
Manual CSV, emailed subscriptions and delivery into SharePoint are separate workflows. Opening CSV in Excel does not create an XLSX attachment. Direct SharePoint delivery needs an additional integration; confirm the actual email format before designing that step.
Export vulnerabilities by endpoint
Use Vulnerability Management reports to drill into affected endpoints before exporting. A CVE summary is a different row layout from device/application details. Start with the endpoint or group you need and compare the downloaded IDs with that scope; do not assume a visible drill-down filter carries into every export.
Action1 also publishes the PSAction1 helper Export-Action1VulnerabilitiesEndpointsCsv. Its columns are CVEId, CVSSScore, Severity, RemediationStatus, EndpointId, EndpointName, ApplicationName, InstalledVersion and AvailableUpdate. Check the installed module's version and command help before use; vendor-published repository code is supplied as-is.
The helper emits application detail beneath affected endpoints/CVEs, so repeated endpoint/CVE pairs can be valid. It has no last-seen column or endpoint-selection parameter. Preserve organization context separately, inspect the endpoint IDs and select the required rows from a copy. A suggested join key starts with organization ID + endpoint ID + CVE, adding application/version for that row level. Obtain any needed last-seen value from a separately verified endpoint source and retain its timestamp meaning.
Validate scope and freshness before using the file
Compare a known software installation or CVE/device pair, row counts, selected organization and report time with the console. Check duplicate keys, blanks and every page before combining files. Keep originals and the module version alongside derived tables.
PSAction1's reporting documentation explains that re-query is asynchronous and offline endpoints refresh when they reconnect. An immediate export can therefore retain older values. Distinguish stale data from a missing page or failed request. RMMBackup saves available report data without initiating a re-query.
Save endpoint-group membership as JSON
Action1's Export-Action1EndpointGroupMembersJson accepts a group ID or name and optional member filters. Its JSON envelope includes schema, capture time, region, enterprise/organization/group IDs and member items. Check the installed command's help and the selected organization before exporting; retain that envelope with the file.
For a spreadsheet, inspect items and choose explicit columns on a copy, preserving endpoint IDs and organization/group context. Verify dynamic membership at capture time. A membership JSON file is distinct from a group-definition package, a group CSV import and a direct native group-to-CSV button.
Choose between report output and a backup snapshot
Use an Action1 report export when you need a specific report in its standard format. Use RMMBackup when you need repeatable snapshots of selected Action1 data, change comparison, and a complete ZIP of the captured snapshot.
These are complementary paths. A report is not proof that configuration, audit history, organization relationships, or every endpoint detail was included. An RMMBackup ZIP contains what its selected collections successfully captured; it is not an Action1 restore package.
Check organization and permission scope
Action1 credentials can see one or more organizations according to their role assignments. Record the intended organization scope, then compare it with the organizations discovered during RMMBackup validation.
Selected collections require their corresponding documented view or management permission even though RMMBackup performs only retrieval. A 403 for one collection is a scoped failure, not an empty successful capture. Review the Action1 API credential guide before relying on a backup.
Capture the data sets you need
Start with organizations and managed endpoints, then select the additional domains required by the recovery or audit plan:
- endpoint groups, installed software, missing updates, vulnerabilities, and remediation history;
- advanced settings, custom scripts and data sources, users, roles, deployment configuration, repositories, and schedules;
- report definitions, cached report rows and errors, automation history, audit events, diagnostic logs, and license metadata.
Report and log data can be cached, permission-limited, or retention-limited. Preserve capture timestamps and collection status with each export.
Verify the exported result
Open the snapshot and confirm each selected collection is complete or explicitly partial. Compare representative endpoints and organizations with Action1, inspect native JSON, and download the snapshot ZIP. Use the contents summary and original responses to check what was saved.
RMMBackup does not infer completeness from an empty response, does not run report requeries, and does not treat a failed collection as a deletion baseline. See the Action1 integration page and the general data export guide for the data you can save and download.
Plan the next step
For a move, review destination import options, 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.
Frequently asked questions
Does an Action1 report export contain every account record?
No. Report output is scoped to the selected report, organizations, fields, permissions, filters, and available history.
Does RMMBackup run Action1 automations or remote actions?
No. Provider-data collection is read-only; automation execution, remote sessions, endpoint changes, and report requeries are excluded.