NinjaOne data retention: activity windows and independent history

At a glance

NinjaOne (formerly NinjaRMM) documents a last-three-months limit for the Activities dashboard. That UI window is not a universal retention or recovery promise for all RMM data. RMMBackup Beta traverses the activity history that the Public API returns and preserves successful snapshots independently under the account's retention policy.

Understand NinjaOne activity visibility and plan independent inventory retention without applying endpoint backup rules to RMM records.

Published Updated

On this page

Use a resource-specific retention matrix

NinjaOne publishes a specific three-month maximum for the Activities dashboard. It does not publish one universal period covering every RMM resource in the cited documentation. Treat visibility, vendor retention, API availability, and your independent copy as separate facts.

Resource Documented UI visibility or export Public API availability used by RMMBackup What remains unknown from the cited source
Activities Dashboard filters reach back at most three months; the filtered list can be exported as CSV GET /v2/activities; RMMBackup requests all history the API returns Whether API history always matches the UI window or a longer guaranteed retention period
Current devices and inventory Devices search shows current visible devices; three device CSV modes are documented Detailed devices plus supported hardware, OS, storage, network, software, services, and related reads A universal vendor retention period after a device becomes inaccessible
Custom fields and configuration metadata Export scope varies; the custom-field device CSV has its own documented columns Supported custom-field definitions/values, policy identities and assignments, groups, tasks, notification channels, and script metadata Guaranteed historical versions in NinjaOne for each resource
Deleted device references Activities can show a deleted device or organization name in red and say it is no longer accessible Earlier RMMBackup records remain available only if successfully captured under the applicable plan A vendor-native hard-delete recovery window
NinjaOne Backup recovery data Governed by the separate NinjaOne Backup product and its settings Not part of RMMBackup's RMM snapshot coverage Endpoint-backup retention must be checked in that product's documentation and account

Use the retention-planning CSV to record a current official source, last-verified date, owner, and unresolved questions for every resource you depend on.

Preserve useful evidence before it ages out

The NinjaOne tools comparison distinguishes filtered Activities CSV from device inventory and destination imports; preserve each required history source separately.

Review the relevant organization and date range in Activities, then use its export action for the filtered list. Keep the filter context beside the CSV. Capture device inventories separately because events alone do not reconstruct all prior field values.

Verify the Activities CSV by comparing its filter summary, first and last visible dates, row count, and representative device/organization references with the dashboard. A three-month UI maximum is not proof that every day or event type is present; permissions and filters still matter.

Investigate a script run across devices

For example, to investigate a maintenance script that failed on several devices, open Dashboard > Activities at system level. Start with All, set the organization(s) and date range, then use Type and Filter to narrow the relevant automation events. The dashboard catalog documents these filters and Action > Export for a CSV of the filtered list.

Inspect a representative event's available details, then export the list. Check whether the saved row contains the result/error detail you need; a detail window showing output does not establish the same fields in CSV. Preserve the run time, organization/device identity and filter context with any separately saved detail. Confirm the actual type/status labels in your account rather than assuming a universal script-result schema.

The Activity Feed documentation limits the feed display to 1,000 entries and points to activity APIs for further history. That entry limit is separate from the Activities dashboard's three-month date boundary and from the records an API response actually returns. None establishes unlimited source retention.

RMMBackup Beta preserves successfully captured activity records for later review within your plan. Inspect a saved event before relying on a particular script result or output field.

Define independent copy retention

Decide which dated inventory, custom-field, and configuration copies your MSP needs. Maintain original files and record who can access them. Check an older copy periodically against its capture notes; a file without account scope or native IDs may be hard to use later.

Deletion and endpoint backup boundaries

A lifecycle record, an activity event, and an endpoint backup are different stores of information. Do not apply NinjaOne Device Backup revision settings to RMM account records. Confirm resource-specific retention and account-cancellation behavior with NinjaOne in writing when the public source does not answer it. Record the product, resource, interface, plan, and date covered by the answer.

RMMBackup snapshots retain successfully captured NinjaOne records independently under the account's current plan and retention behavior: Free exposes the latest fully successful snapshot, while Full Access keeps successful and partial snapshot history without age-based expiration during the current Beta offer.

Official source

NinjaOne dashboards reference

Related NinjaOne (formerly NinjaRMM) integration

Review current NinjaOne (formerly NinjaRMM) backup coverage and availability.