Deleted device history: finding earlier RMM records

At a glance

Previously captured exports or snapshots may let you inspect a device after its live record disappears. The record must have been captured successfully before deletion, and reviewing it is not the same as restoring the endpoint or undeleting it in the RMM.

Review RMM device records captured before deletion, distinguish decommissioning from removal, and separate historical access from restoring a device.

Published Updated

On this page

Establish what was deleted

Check the correct customer, site, permissions, and filters before assuming deletion. Record the native device ID, known names, and approximate deletion time. Offline, decommissioned, queued for deletion, and permanently removed can mean different things in different products.

Some vendors expose an explicit deletion feed or a retained archived state. Others only stop returning a record. RMMBackup treats provider and collection behavior separately: a missing record is not called a confirmed vendor deletion when permissions, filters, account scope, or an incomplete collection could explain the absence.

Find a copy that predates deletion

  1. Review the vendor's documented activity or lifecycle view.
  2. Locate a prior inventory export or independent snapshot.
  3. Match the native ID and account before relying on a hostname match.
  4. Check capture time and collection completeness.
  5. Preserve the original evidence and record the remaining gaps.

For example, a saved inventory can establish a device's prior customer assignment only if that field was captured. It cannot reconstruct details that were never collected. See export planning.

Separate viewing history from restoring management

The vendor tools comparison separates record imports, configuration transfers and historical exports. Use it to plan earlier copies; an import listing is not evidence of undelete support.

Native import documentation does not establish native undelete behavior. Check the vendor's lifecycle or recovery instructions separately for the exact product and record type. A successful agent installation or configuration import is not proof that the previous device identity or its history has returned.

Vendor-specific reinstall, re-enrollment, or recommissioning processes can create a new identity or depend on retained lifecycle state. Follow current official instructions; do not assume that a CSV import restores old history. Endpoint file and image recovery require their own backups.

If you are moving platforms, use the RMM migration checklist and check the destination import separately. A destination import can create a current record without transferring the source device's earlier versions or native identity.

Use RMMBackup history within its coverage

For supported provider records captured before deletion, open the older snapshot or record history and inspect the preserved native data. Check collection status: failed collections do not establish deletions or new baselines. Some providers deliberately disable deletion inference when permission or company scope can make a record disappear. RMMBackup does not restore the device into the source platform.

What remains available depends on both prior capture and backup retention. Configuration copies may help explain a device's former settings but are not evidence of a complete device restore.

See the Deleted Device History use case for the customer outcome and product workflow.

Available vendor backup guides

Use the guide for the source platform before assuming historical access works the same everywhere: Syncro, Action1, N-able N-sight, Hudu, Atera, SuperOps, Domotz, Level, or OptiTune. Each guide identifies whether deletion detection is supported, disabled, or collection-specific and links to the relevant vendor evidence.

Provider guides

Use the platform guides below to distinguish a retired record from permanent deletion and find the right next step. Restoring a vendor record and recovering endpoint files are separate tasks.