How to back up NinjaOne RMM and documentation data
RMMBackup keeps a separate, read-only history of supported NinjaOne devices, inventory, policies, activity, knowledge base content, and organization documentation. Use the guide below to prepare the connection, choose what to protect, and verify your first snapshot.
Configure read-only NinjaOne Beta backups for devices, inventory, policies, activities, knowledge base content, organization documents, and attachments.
On this page
Create a least-privilege connection
Follow the NinjaOne API credential guide. A NinjaOne system administrator creates an API Services (machine-to-machine) application, enables Client Credentials, and grants the read-only Monitoring scope. Select the same regional instance used to sign in.
RMMBackup stores the client ID and secret through its encrypted provider credential store. Access tokens are short-lived, reused until near expiry, and never written to logs, snapshots, or ZIP exports.
Choose backup sources
All supported sources are selected by default. You can select organizations, locations, devices, hardware/OS/network/storage inventory, software, services, custom fields, policies, groups, automation script metadata, alerts, activities, jobs, patch data, document templates, organization documents, knowledge base articles, checklists, and asset relationships separately.
| Source area | Examples preserved |
|---|---|
| Tenant structure | Organizations, locations, policies, groups, and custom fields |
| Endpoint state | Devices, operating systems, hardware, disks, volumes, software, services, and patch results |
| Operations | Alerts, activities, job history, and automation-script metadata |
| Documentation | Templates, organization documents, knowledge base articles, checklists, relationships, and permitted attachments |
The connected identity determines visibility. "All organizations" means all organizations accessible to that API identity; it does not imply access to hidden organizations.
Documentation fields and attachments can depend on NinjaOne licensing and account permissions. RMMBackup preserves the original values and attachments available to the connection. If an attachment cannot be captured, the affected collection is marked partial.
Run and verify the first backup
- Open Settings > Integrations, choose NinjaOne Beta, and select the region.
- Enter the OAuth client ID and client secret.
- Save and validate the connection. Validation checks authentication, organization/device reads, and documentation access when documentation sources are selected.
- Review source selection and start a manual backup.
- Confirm each collection completed, compare representative records with NinjaOne, and inspect the snapshot ZIP.
| Verification check | Expected result |
|---|---|
| Connection | The selected NinjaOne region and OAuth application validate successfully |
| Collection status | Each selected source is complete, or clearly marked partial or failed |
| Snapshot scope | Records belong to the intended MSP tenant and NinjaOne provider connection |
| Export | The ZIP contains a contents summary, original captured records, and source response archives |
After the first successful backup, RMMBackup applies the account's existing scheduling and entitlement rules. Manual backups remain scoped to the selected NinjaOne connection.
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 NinjaOne, 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.
Understand history and deletion safety
The first successful activity and patch-history capture traverses all history that the documented API still returns. Current snapshots remain complete rather than delta-only: resources without a documented safe incremental contract are fully scanned again. This avoids incomplete ZIP exports and false deletions when older mutable records change.
Device deletion detection advances only after a complete successful Devices inventory. Authentication failures, missing permissions, throttling exhaustion, malformed pagination, partial detail retrieval, or changed API visibility do not create a successful empty device baseline.
Review and download NinjaOne backup history
RMMBackup preserves the supported NinjaOne RMM and documentation records listed above as read-only history for browsing, comparison, and backup ZIP downloads.
Frequently asked questions
Does RMMBackup run NinjaOne scripts, jobs, patches, or endpoint actions?
No. The adapter is read-only. It uses GET operations plus the OAuth token exchange and never executes or changes endpoint operations.
Does Automation Scripts include script source code?
No. NinjaOne's documented read endpoint returns script metadata, parameters, and variables, not the script body.
Does this back up files from managed computers or NinjaOne Backup recovery images?
No. It captures supported RMM and documentation data, including permitted documentation attachments, but not endpoint file systems or recovery images.
Official source
NinjaOne Public API documentation
Official NinjaOne overview for its Public API and resource reference.
Related NinjaOne (formerly NinjaRMM) integration
Review current NinjaOne (formerly NinjaRMM) backup coverage and availability.