NinjaOne configuration backup: custom fields and policy context
NinjaOne custom fields, applied policies, and overrides can provide valuable context when reviewing earlier device settings. RMMBackup Beta preserves the supported configuration details available to the connection.
Preserve NinjaOne custom-field values and policy context without assuming a full policy export or account restore.
On this page
Back up supported custom-field values
The NinjaOne tools comparison distinguishes custom-field exports and documentation templates from a whole-policy transfer.
From the Devices search page, filter the devices and select Export with custom fields. NinjaOne also documents an export button on a dashboard's Custom tab. Check field permissions before treating a missing value as empty.
Record policy context separately
NinjaOne's device settings view includes assigned policy and applied override information. Record the visible policy identity, device scope, override context, and capture time before a planned change. Preserve a dated original rather than continually editing one configuration worksheet.
Save script source, metadata and policy context separately
A script text file preserves code; an import-ready artifact also needs the destination's accepted structure. Our suggested preservation checklist includes source text, original script/category IDs, language and execution context, parameters/variables, custom-field references, policy assignments and capture time. Inspect what the chosen tool actually saves and what the destination accepts before describing JSON as import-ready.
For example, record that a device uses a child policy, its parent policy identity and any device override separately. A direct assignment or policy name alone does not establish all inherited effective settings. The dashboard settings reference explains where to inspect assigned policy and device overrides.
Third-party option: SHADOW advertises script/policy/custom-field exports, JSON import and Git comparisons. It is an independent, closed-source browser extension. Its author explains that it uses internal NinjaOne APIs and does not publish the implementation. Treat those advertised features as the author's claims and check compatibility/support before use; this is not an official public-API migration procedure.
RMMBackup Beta captures automation script metadata, not script source or an import-ready script package. Keep separately obtained source and dependencies alongside the supported configuration records.
Troubleshoot custom-field script access
Check field scope (device, organization or documentation), configured script access and execution context before treating a missing value as an export failure. NinjaOne's CLI custom-field guidance describes protected CLI access and separate secure-field restrictions. Use the documented system/automation context rather than weakening folder permissions. These scripting permissions do not make secure values available in an RMMBackup capture.
Compare before and after a change
Compare the same device and organization using stable IDs. Separate changes to a custom-field value from changes to its definition or permission. Record which values came from an export and which were documented manually.
Coverage and limitations
The official sources here establish these specific views and exports, not a universal policy export/import workflow. Do not infer the latter from a policy name in a CSV. RMMBackup Beta captures documented policy identities, assignments, roles, overrides, scheduled-task definitions, notification channels, custom-field definitions, and readable values; it does not claim every internal policy setting and does not restore data.
Additional official references
Official source
Related NinjaOne (formerly NinjaRMM) integration
Review current NinjaOne (formerly NinjaRMM) backup coverage and availability.