How to export N-able N-sight inventory, reports and API data

At a glance

Use N-sight inventory and report exports when you need a targeted file, or use RMMBackup to keep repeatable snapshots of supported clients, sites, devices, inventory, monitoring, alerts, settings, and history.

Export N-sight device lists to Excel or hardware and software inventory to XML/SQL, retrieve offline downloads, and validate client scope and software status.

Published Updated

On this page

Choose a device list or detailed inventory dump

The N-able N-sight tools comparison identifies the inventory-dump scope and download deadline; it does not apply N-central workflows to N-sight.

Use Device Inventory for a filtered device worksheet, Asset Tracking for detailed hardware/software inventory, and a dated report for added/removed-device events. Inventory files and event reports answer different questions. Keep scripts and configuration exports separately. N-central and Passportal instructions do not establish N-sight capabilities.

Use a login with access to the intended clients and relevant dashboard. Before downloading, check that the source view includes the clients you expect; a narrow view cannot establish account-wide coverage.

Export a device or asset list

  1. Open Dashboards > Device Inventory in N-sight.
  2. Filter the list for the client or devices you need, then select useful columns.
  3. Select the export icon. Choose all column data or only your selected columns.
  4. Open the downloaded Excel worksheet and compare its scope with the filtered view.

These steps follow N-able's Device Inventory export instructions. For an offboarding inventory, our suggested check is to include identifiers and client/site context, then compare counts per client rather than relying only on a total.

Preserve detailed hardware and software inventory

  1. Open the Asset Tracking Dashboard.
  2. Choose Reports > XML Data Dump or SQL Data Dump.
  3. Choose All Clients or the particular client you need.
  4. Use Download for immediate generation, or Offline Mode for background generation.
  5. For offline output, retrieve the emailed link or return to the Data Dump dialog using the requesting account. The dialog link remains available for 24 hours.

The hardware and software dump instructions describe XML/SQL inventory output. In Excel, open the XML file and follow its schema prompts. The software Deleted status distinguishes installed (0) from uninstalled (5); it is not a declaration that the device was deleted. These inventory dumps do not establish a backup of monitoring policies or every account setting.

Our suggested check is to retain the original dump, inspect client/device relationships and sample both hardware and software entries. Count devices separately from software rows. Use the status field when checking installed software; including uninstalled entries changes the meaning of a total. Record missing or stale inventory rather than treating a file that opens successfully as proof of current agent data.

Export reports separately

In All Devices > Reports > Added and Removed Devices Report, select the date range and optional Username, Action and Event filters, then use CSV Export. Choose the displayed columns before exporting and retain the range and filters with the file. The official report instructions distinguish browser generation from CSV download. This is evidence of device events, not the full inventory of every removed device.

The verified paths here produce Excel, XML, SQL and report-specific CSV. A browser printout saved as PDF is a different artifact; do not assume every N-sight report has a native PDF or JSON export.

Collect through the official API

N-sight's Data Extraction API setup guidance identifies Settings > General Settings > API and account-region-specific service URLs. Reusing an existing authorized key avoids breaking integrations through regeneration. Consult the official service definition for each resource before collecting it; API access alone does not establish complete account coverage.

For a repeatable capture, keep native response files with the collection name, account, retrieval time and completion status. Keep the API key out of filenames, request logs and export notes. A missing response is a failed capture, not an empty resource.

Validate your export set

Keep a small manifest such as client, source_view, filters, captured_at, row_count, filename. Retain originals separately from working spreadsheets. Compare at least one device's identifiers and inventory against the console, and record any fields that the chosen report omits. For Device Inventory, check all filtered devices, not just the first displayed screen, and confirm whether you chose all columns or selected columns. For an offline dump, download before the link expires and verify that the file is readable. Capture configuration separately before using the files as a handover package.

Plan the next step

For a move, review destination import options, 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.

Official source

Export Device Inventory

Related N-able N-sight integration

Review current N-able N-sight backup coverage and availability.