How to export NinjaOne device inventory and custom fields
Use NinjaOne's Devices page to export an inventory CSV. Choose the custom-field export when you need those values; the all-device-details export omits them. Keep dated RMMBackup Beta snapshots when you also need to review earlier supported records.
Choose NinjaOne device CSV columns, export custom fields separately, and check device IDs, filters and downloaded values before using the files.
On this page
Export a native NinjaOne device CSV
Use the NinjaOne tools comparison to distinguish device CSVs, Activities exports, organization creation and documentation imports.
You need a technician role that can view the intended organizations and devices. In NinjaOne, open Devices, apply the organization, location, device, or saved-group filters you need, and review the filtered result. Then use the page's export action and choose one of the modes in NinjaOne's Devices search documentation:
| Native CSV option | What NinjaOne documents |
|---|---|
| Export visible columns | The columns currently visible in the table; table settings control the selection |
| Export with all device details | All device-detail columns, but no custom fields |
| Export with custom fields | Device ID, name, role, type, organization, location, tags, and custom fields with last-update data |
Save the original CSV with the filter scope and date. Use a role with access to the intended devices and fields; check your account's available export controls before promising a handover file. The illustrative device CSV contains fictional data and is not NinjaOne's guaranteed schema.
Export NinjaOne custom fields
From the same filtered Devices search, choose Export with custom fields. This produces device identifiers and organization/location context alongside custom fields and their update data, rather than adding those fields to an all-details CSV. See the official export-mode definitions.
Our suggested check is to export inventory and custom fields close together, then match rows by device ID while keeping organization context. Do not join on hostname alone. Check a populated value, an empty value and a multiline value against the console; keep empty values distinct from missing columns. If a required field is unavailable, confirm its visibility with your administrator before treating it as absent from the device.
Verify the native CSV
- Compare the CSV row count with the entire filtered Devices result, including devices beyond the first screen.
- Confirm that representative device IDs, organizations, and locations match.
- For a visible-column export, confirm the intended columns were visible before export.
- For an all-details export, record that custom fields are omitted.
- For a custom-field export, spot-check a value and its last-update data against the device.
- Keep the completed export-validation checklist with the unedited CSV.
If devices are missing, clear or record filters and confirm the technician's organization/device access. If columns are missing, choose the appropriate export mode rather than merging unlike schemas without notes.
Export the Windows build rather than only the edition
In Devices > Table Settings > Columns, add OS Name, OS Build Number and OS Release ID, then save the table settings and choose Export visible columns. NinjaOne's High Risk Software Audit guide names these columns; the export modes above determine which columns go into the file.
A Windows edition/name alone does not identify the build. Open the downloaded CSV and compare the build and release values for a known device with its current inventory before using it for upgrade planning. Keep a blank or stale value distinct from a different edition; the column label alone does not prove a current result.
For script execution results, use the separate global Activities investigation, not a device inventory CSV.
Separate native CSVs from RMMBackup snapshots
Native device CSVs are targeted spreadsheets of the current filtered search. RMMBackup Beta uses documented read operations to keep dated snapshots across the supported RMM and documentation sources below. Its ZIP contains a contents summary, JSON records, archived source responses, and permitted attachments; it is not a NinjaOne CSV or an import/restore package.
Export supported Public API resources
The Beta integration captures:
- organizations, locations, detailed devices, and their native relationships;
- hardware, operating systems, disks, volumes, processors, networking, logged-on-user inventory, installed software, and Windows services;
- custom-field definitions and readable scoped values without requesting secure values;
- policy names/assignments, device roles, overrides, groups/memberships, scheduled task definitions, notification channels, and automation script metadata;
- active alerts and jobs, retrievable activities, and OS/software patch status and install history;
- knowledge base folders and article content, document/checklist templates and values, organization documentation, ITAM asset relationships, and permitted attachments.
Script metadata is not script source. Policy identities and assignments are not a claim that every internal policy setting is exposed. Licensing, organization access and field permissions determine which details can be saved.
Verify a RMMBackup snapshot
RMMBackup follows each endpoint family's documented paging model: numeric after paging, report cursors, relationship nextCursor paging, or activity ID history bounds. A repeated or unusable cursor fails the collection rather than producing a successful truncated capture. Endpoints whose official contract documents one unpaged response are preserved as that response; their absence is not used for deletion detection.
Check collection status before relying on the ZIP. Compare organization/device counts, sample parent IDs, policy assignments, custom values, article bodies, document values, and attachment checksums. A partial collection retains successful records but does not advance its comparison/deletion baseline.
The native Devices CSV and an API snapshot can legitimately have different counts and fields. Compare matching source scope and stable IDs; do not use CSV column parity as proof that every API collection succeeded.
Excluded data and actions
Ticketing, PSA, billing, invoices, agreements, and service-desk workflows are excluded. RMMBackup does not back up endpoint file systems or NinjaOne Backup recovery images. It never runs scripts, starts jobs, installs patches/software, resets alerts, controls devices, registers webhooks, or writes records back to NinjaOne.
Continue with the NinjaOne integration page, backup setup guide, and API credential guide.
Plan the next step
For a move, review NinjaOne import and deployment guide, 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
Is there one NinjaOne export for the complete account?
No. Native exports and documented API resources have different scopes, fields, pagination, permissions, and retention limits.
Does a RMMBackup NinjaOne ZIP restore into NinjaOne?
No. It is a read-only reference artifact for browsing, comparison, and download.
Official source
NinjaOne Public API 2.0 reference
Official resource paths, parameters, and response schemas for NinjaOne's Public API.
Related NinjaOne (formerly NinjaRMM) integration
Review current NinjaOne (formerly NinjaRMM) backup coverage and availability.