Spiceworks

File Upload

Export software inventory from Spiceworks Inventory (Classic On-Prem and Cloud) as a CSV with the columns the SIM template needs.

Spiceworks maintains device and software details discovered by its scanner/agent:

Devices (Endpoints): Hostname, platform, and inventory attributes.
Installed Applications: Display name, version, and publisher per device.

Data can be exported from the Spiceworks UI (Cloud or Classic On-Prem). For Classic On-Prem, advanced users may alternatively query the SQLite inventory database.

Prerequisites

For UI export (Cloud or Classic On-Prem)

Admin (or equivalent) access to the Spiceworks console.
Recent inventory scans completed for all in-scope devices.
Permission to run reports and export to CSV.

For SQLite Method (Classic On-Prem only; optional)

File system access to the Spiceworks server hosting Classic Inventory.
Read access to the SQLite database file (commonly found under the Spiceworks install data directory).
A SQLite client (e.g., sqlite3, DB Browser for SQLite) or PowerShell with a SQLite provider/ADO.NET driver.

Export methods

The UI export is recommended for most users.

Option 1: Spiceworks UI export (recommended)

Cloud inventory

Sign in to Spiceworks (Cloud).
Navigate to Inventory → Software.
Optional: adjust filters to include all devices/sites as required.
Click Export → CSV.
Save the file (e.g., Spiceworks_SIM_Export.csv).
Confirm the export includes the following fields (names may vary slightly by tenant):

Device (device name/hostname)
Application (software name)
Version
Publisher

Classic On-Prem

Open Spiceworks (Classic) web console.
Go to Inventory → Software (or Reports and create a new Software report).
In the report columns, include:

Device Name
Application Name
Version
Publisher

Run the report, then choose Export → CSV.
Save as Spiceworks_SIM_Export.csv.

If extra columns are present (install date, category, etc.), they can be removed prior to SIM import.

Option 2: Classic On-Prem SQLite query (advanced, optional)

Use only if UI export is unsuitable or if you require automation. Schema names can vary by version; inspect the database to confirm table/column names in your environment.

Common schema pattern:

devices (one row per device; includes name/hostname and id)
software (catalog of software titles; includes id, display_name, publisher)
software_installations (link table mapping device to software; includes device_id, software_id, version)

Example SQL (adapt as needed)

-- Spiceworks Classic Inventory - SIM Export (adjust table/column names to match your DB)
SELECT
    d.name                AS "Device Name",
    s.display_name        AS "Software Name",
    si.version            AS "Software Version",
    COALESCE(s.publisher, '') AS "Software Publisher"
FROM software_installations si
JOIN devices d   ON d.id = si.device_id
JOIN software s  ON s.id = si.software_id
ORDER BY d.name, s.display_name;

Running the query with sqlite3 (example)

sqlite3 "C:\ProgramData\Spiceworks\data\inventory.sqlite" -header -csv ^
"SELECT d.name AS 'Device Name', s.display_name AS 'Software Name', si.version AS 'Software Version', COALESCE(s.publisher,'') AS 'Software Publisher'
 FROM software_installations si
 JOIN devices d ON d.id = si.device_id
 JOIN software s ON s.id = si.software_id
 ORDER BY d.name, s.display_name;" > C:\Exports\Spiceworks_SIM_Export.csv

Preparing for SIM import

The CSV header row must be exactly Device Name,Software Name,Software Version,Software Publisher.

Open the Licenseware SIM Template.
Paste the CSV data into the template.

Remove blank rows and any additional columns before saving.

Then upload it on the SIM - Template data source. See SIM template.

Troubleshooting

Issue	Likely Cause	Resolution
No/partial results	Devices not scanned recently	Re-run scans; verify agent/credential status, then re-export.
Missing publisher	Application metadata incomplete	Leave blank or enrich in the SIM Template if required.
Duplicate rows	Multiple detections across scans	Deduplicate by Device Name + Software Name + Version before import.
Encoding/import errors	CSV not UTF-8	Re-save the CSV as UTF-8.
SQLite query fails	Schema differs from example	Inspect tables/columns with `PRAGMA table_info()` or a DB browser and adjust the query.

Example output

Device Name,Software Name,Software Version,Software Publisher
WS-001,Google Chrome,129.0.6668.90,Google LLC
WS-001,Microsoft Edge,130.0.2849.68,Microsoft Corporation
LAP-015,Zoom,6.1.12,Zoom Video Communications
SRV-02,Oracle Java SE Runtime Environment,8.0.411,Oracle Corporation