Switching from Snipe-IT
How to move your asset register into Tagaris with the built-in Snipe-IT import preset: what maps to what, the steps, and what to check afterwards.
The Tagaris asset importer ships with a Snipe-IT preset. It recognises the column names in a Snipe-IT CSV export, translates Snipe-IT's status values into Tagaris statuses, and runs the whole import as a preview before anything is written. A typical migration is an export from Snipe-IT and an import into Tagaris, and this page walks through it.
If you are still weighing the two products rather than moving, the FAQ covers how they compare, and the live demo runs the current release in your browser.
What maps to what
The two systems share the same shapes, so most concepts carry straight over.
| In Snipe-IT | In Tagaris | How it moves |
|---|---|---|
| Assets | Assets | Asset tag, name, serial, model, category, manufacturer, supplier, status, location, purchase cost and date, assignee and notes are mapped automatically by the preset. |
| Status labels | Statuses and custom status labels | Deployed becomes In use; Ready to Deploy and Pending become In storage; Out for Repair and Out for Diagnostics become Repair; Archived and Lost/Stolen become Retired. Recreate any custom names as custom status labels in Settings, with your own colour on a built-in behaviour. |
| Checked out to | Assignee | "Checked Out To" becomes the asset's assignee, and people are created by name. Check-out and check-in work the same way after the move. |
| Users | People | Import the Snipe-IT user export with the People importer, which recognises its header names and matches by email. Or pull people from Microsoft Entra ID (free beta). |
| Accessories | Accessories | Same concept: stock checked out to people, with quantities and a minimum-stock threshold. Not part of the asset CSV; enter them in Tagaris or load them through the API. |
| Components | Components | Same concept: stock installed into assets. Entered directly or through the API. |
| Consumables | Consumables | Same concept: issued stock that counts down, with low-stock alerts in the daily digest. Entered directly or through the API. |
| Licenses | Software licences | Tracked with renewal reminders in the daily digest. Entered directly or through the API. |
| Custom fields | Custom fields | Defined per organisation in Settings and recorded on each asset. |
| Depreciation | Straight-line depreciation | Set per category; feeds the asset value and disposal reports. |
| Maintenances | Maintenance records | Logged per asset, alongside the physical audit (stock-take) workflow. |
| Locations | Locations | Multi-level (site, floor, room, rack), with printable QR labels for rooms as well as assets. |
| Warranty (months) | Warranty end date | Snipe-IT stores warranty as a length in months; Tagaris stores an end date. The preset deliberately leaves it unmapped, so set warranty end dates after the import. |
The move, step by step
The importer is a four-step wizard: upload, map columns, preview, commit. Up to 5,000 rows per file.
Export from Snipe-IT
Build a custom report in Snipe-IT with the columns you want and download it as CSV. Export your user list the same way.
Choose the Snipe-IT preset
In Tagaris, go to Assets, then Import, and pick Snipe-IT as the source. The wizard maps the common columns and translates the statuses. Anything it does not recognise falls back to manual column mapping.
Preview, then commit
Every import runs as a dry run first. The preview shows exactly what will be created, warns on duplicate serials and MAC addresses, and writes nothing until you confirm.
Categories, locations and people referenced by name are created automatically if they do not already exist. The full walkthrough is in the importing guide.
After the import
A short checklist to finish the move.
- Spot-check the asset count and a handful of records against Snipe-IT.
- Set warranty end dates, since the months field does not carry over.
- Recreate any custom statuses and custom fields in Settings.
- Enter accessories, components, consumables and software licences, or load them through the API.
- Set minimum quantities on stock so the daily digest can flag low stock.
- Print QR label sheets for assets and rooms.
- Schedule a backup, and run one restore test while the stakes are low.
What does not carry over
Asset history stays in Snipe-IT: Tagaris starts a fresh dated history for each asset at import, so keep your Snipe-IT export if you need the old trail for records. LDAP and Active Directory sync do not have a Tagaris equivalent; single sign-on is OpenID Connect through Microsoft Entra ID, on the paid tiers. Anything you built against the Snipe-IT API will need redoing against the Tagaris REST API.
Try the import before you commit to it
The live demo runs the current release in your browser with demo data loaded, so you can walk the import wizard with a sample file first.