How MSPs Can Run Manual Device Inventory Reviews with Portal Exports

Automated onboarding and offboarding tasks are typically a boon for enterprise IT or MSPs operating at scale. However, constant device turnover and enrollment can leave a few blind spots that may require spontaneous intervention.

For that, MSPs can do manual device inventory using built-in portal exports. This guide explains how to adopt this workflow and how it helps IT stacks become more sustainable and compliant.

Core components and actionable steps for device inventory

This guide focuses on leveraging exports from portals like NinjaOne, Intune, or Entra ID, which MSPs can use to analyze and detect missing, duplicate, or stale endpoints.

Here’s an overview of the core components of a device inventory process:

Before starting a manual review, MSPs should line up these essentials:

📌 Prerequisites:

• Secure storage for exported inventories (e.g., SharePoint, IT Glue, NinjaOne Docs)
• Access to client management portals (NinjaOne, Intune, Entra ID, or other RMM tools)
• Clear criteria for “inactive,” “duplicate,” or “retired” devices
• Basic Excel/Sheets skills for comparison and reporting
• Defined audit frequency (monthly/quarterly, depending on client turnover)

👉 Reminder: Some prerequisites may vary depending on preferences and other active software integrations.

A. Define review frequency and scope

Monthly reviews are best for clients with frequent hires, departures, or remote staff. A quarterly review is the more efficient option for those with stable environments with minimal churn.

The scope generally tracks the following parameters:

• Total device count
• New vs. missing devices
• OS versions
• Last check-in dates
• Compliance signals (e.g., patch levels)

An unrefined or infrequent device inventory can often overlook stale devices and leave them lingering. Thus, an adjusted audit cadence according to the client risk profile is a good first step in eliminating vulnerabilities.

B. Capture portal snapshots

Exports from NinjaOne, Intune, or Entra form the backbone of the review. On that note, standardize fields like device name, assigned user, OS version, and last active date, and save them with consistent naming conventions.

• Export device lists from NinjaOne or Intune’s Devices report.
• Standardize export fields: Device Name, Assigned User, OS Version, Last Active, Compliance Status.
• Save with consistent filenames (e.g., ClientName_Inventory_YYYYMMDD.csv).

Different portals export inconsistent fields. To streamline the data, use a clean export structure to ensure later comparisons are accurate and repeatable.

C. Compare snapshots manually

Import two snapshots into Excel or Sheets, then apply formulas to detect missing devices, OS version changes, or inactivity. Highlight mismatches for follow-up.

• Import two exports into Excel or Google Sheets.
• Apply formulas to detect changes: =IF(COUNTIF(Current!A:A,Previous!A2)=0,”Missing”,”Present”)
• Highlight mismatches for review: missing devices, OS version changes, or long gaps in activity.

Manual comparisons can be error-prone, so a consistent comparison template is essential to reduce errors and speed up the review cycle.

D. Identify and act on discrepancies

Discrepancies reveal whether devices are added, missing, stale, or duplicated. Before remediation, each finding should be validated against HR or PSA records.

Here are some discrepancies to look out for:

• Unexpected new devices → Verify if onboarding was authorized.
• Missing or stale devices → Confirm if they were retired or lost.
• OS mismatches → Validate compliance with patch management policies.
• Duplicate records → Correct asset naming or consolidate entries.

Acting quickly on these findings prevents a recurring gap in security. For a more thorough review, cross-check against HR or PSA records before remediation.

E. Summarize and share findings

Trend charts add clarity, and sharing results during QBRs reinforces governance. Build a simple report for stakeholders showing device changes and compliance gaps:

Transparent reporting solves inventory issues and builds client trust. It also showcases the MSP’s commitment to proactive IT management.

When put together, these components transform a manual review into a repeatable governance process that strengthens accountability.

Automation touchpoint example

While manual reviews provide control, selective automation can reduce effort and ensure consistency. Here’s a workflow example and integration ideas for MSPs.

Manual device inventory audit workflow:

1. Export the device list from NinjaOne/Intune/Entra at the end of the month.
2. Save with a timestamped filename in a secure shared repo.
3. Compare the current vs. the last snapshot in Excel.
4. Flag and document discrepancies.
5. Create PSA tickets for remediation (e.g., decommission stale assets).
6. Present findings during QBRs for transparency.

NinjaOne integration ideas:

• Device inventory exports on schedule
• Custom fields to track status (active, inactive, retired)
• Report scheduling for monthly/quarterly reviews
• PSA integration to sync flagged devices into ConnectWise/Autotask
• QBR dashboards to showcase asset hygiene

Pairing manual oversight with selective automation creates a hybrid system that is both efficient and auditable.

Importance of manual device inventory

Being adept with manual inventory and automation is a big advantage for MSPs in the competitive IT management market. In particular, mastery of manual audits puts any MSP in a stronger position to layer in automation and RMM integrations that support long-term scalability and compliance.

Related topics:

• Mobile Device Management Strategy: Steps & Tips
• IT Asset Inventory: Definition, Management, & Best Practices
• What Is Inventory Management?