NinjaOne deleted device records: history versus recommissioning

At a glance

For NinjaOne (formerly NinjaRMM), first distinguish deletion from decommissioning. Previously exported records can help reconstruct historical information; they do not recreate a deleted device. RMMBackup Beta can preserve earlier successfully captured device records and deletion evidence without recreating devices in NinjaOne.

Find NinjaOne deletion evidence and earlier inventory copies while distinguishing deleted records from decommissioned devices.

Published Updated

On this page

Check the device state

NinjaOne's ITAM documentation describes recommissioning a device that still exists in a decommissioned state. This is not evidence that a permanently deleted record can be restored. Confirm the current state and account context before choosing a vendor workflow.

Check the saved record before deletion

NinjaOne's device removal instructions state that deletion removes access to the device's associated data and cannot be undone. Before confirming deletion, our suggested checklist is:

  1. Save device ID, name, serial where available, organization and location.
  2. Export required inventory and custom fields; list any missing or inaccessible values.
  3. Save required activity and script-run evidence separately from current inventory.
  4. Record capture time, source account and field permissions.
  5. Open the saved files or snapshot and compare the required values with the device before deleting it. Check capture success and plan access to the copy you intend to retain.

RMMBackup's NinjaOne collector requests showSecureValues=false. Do not rely on it for rotated administrator passwords, secure organization-field values or BitLocker secrets. Only values actually saved before deletion can support a later review.

Find deletion evidence

The Activities dashboard can show references to deleted devices; NinjaOne marks deleted device or organization names in red and says those records are no longer accessible. Filter the relevant activities and export the visible evidence as CSV where available.

Retrieve an earlier inventory

Locate a device-search export or other preserved copy created before deletion. Match native ID, organization, and capture time. Separate fields verified in that file from details you no longer have. For example, an old hostname can identify a prior label without proving today's device state.

Coverage and limitations

Recommissioning, reinstallation, and file recovery are separate operations. This guide does not assert a deleted-record restore endpoint or a retention window for every resource. Contact NinjaOne for incident-specific recovery options. RMMBackup Beta keeps earlier device versions after complete successful device inventories, but it does not recreate devices in NinjaOne.

Additional official references

Official source

NinjaOne ITAM lifecycle management

Related NinjaOne (formerly NinjaRMM) integration

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