Switching from Snipe-IT
How to move your asset register into Tagaris: the migration wizard that reads Snipe-IT through its API, the CSV preset as the fallback, what maps to what, and what to check afterwards.
There are two routes. The migration page reads your Snipe-IT through its API and brings the whole register across in one go: assets, people, locations, statuses, custom fields, stock, licences and maintenance records, with a preview before anything is written. The CSV importer's Snipe-IT preset is the fallback for when the two servers cannot reach each other. This page walks through both. It is free on every plan and needs an administrator.
If you are still weighing the two products rather than moving, Tagaris vs Snipe-IT compares them side by side, 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, notes, MAC address and last audit date. Tags are kept exactly as they are, so the labels already on your kit stay right. |
| Status labels | Statuses and custom status labels | Deployed becomes In use; Ready to Deploy and Pending become In storage; undeployable labels become Repair; Archived, Lost/Stolen and Broken become Retired. Labels that say more than that (Out for Repair, Out for Diagnostics and your own) are created as custom status labels and kept on the asset by the API migration. With a CSV, recreate them in Settings. |
| Checked out to | Assignee | Checked out to a user becomes assigned to that person; checked out to a location, or not checked out, becomes that location. Check-out and check-in work the same way after the move. |
| Users | People | The API migration brings users across as people (name and email). With a CSV, 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 (still in testing). |
| Accessories | Accessories | Same concept: stock checked out to people, with quantities and a minimum-stock threshold. The API migration brings them across at the quantity on hand. Not part of the asset CSV. |
| Components | Components | Same concept: stock installed into assets. The API migration brings them across at the quantity on hand. Not part of the asset CSV. |
| Consumables | Consumables | Same concept: issued stock that counts down, with low-stock alerts in the daily digest. The API migration brings them across at the quantity on hand. Not part of the asset CSV. |
| Licenses | Software licences | Tracked with renewal reminders in the daily digest. The API migration brings across the name, seats, expiry and cost. Product keys and who holds each seat do not come across. Not part of the asset CSV. |
| Custom fields | Custom fields | The API migration creates each custom field that holds a value, with its dropdown options, and keeps the values on the assets. With a CSV, define them in Settings first. |
| Depreciation | Straight-line depreciation | Set per category; feeds the asset value and disposal reports. |
| Maintenances | Maintenance records | The API migration brings them across. Logged per asset, alongside the physical audit (stock-take) workflow. |
| Locations | Locations | The location tree comes across as it is. Multi-level (site, floor, room, rack), with printable QR labels for rooms as well as assets. |
| Suppliers | Vendors | Supplier names become vendor records, and the name stays on each asset. Spellings that differ only by case or spacing become one vendor. |
| Warranty (months) | Warranty end date | Snipe-IT stores warranty as a length in months; Tagaris stores an end date. The API migration works the end date out from the purchase date and the months. The CSV preset leaves it unmapped, so set end dates afterwards. |
Route one: the whole register through the API
Assets, then Import, then "Migrate the whole register through its API". No files to export, and far more comes across than the asset CSV can carry.
Create an API token in Snipe-IT
Open your account menu, choose Manage API keys and create a token. Use an account that can view everything you want to bring across.
Read and preview
In Tagaris, enter your Snipe-IT address and the token, then choose Read and preview. The token is used for that read only and is never stored. The preview shows one line per record type: how many are in Snipe-IT, how many would be created, and how many are already here.
Migrate now
It all lands in one go, or not at all if something fails. Running it again creates nothing that is already here, because records are matched on what identifies them (asset tag, a person's email, a location's place in the tree), so you can migrate, tidy up in Snipe-IT and run it again for what is new.
Tested against Snipe-IT 8.7. The Tagaris server has to reach your Snipe-IT over the
network; from a Docker container, localhost means the container, so use
the server's name or address. The full walkthrough is in the
importing guide.
Route two: a CSV export
For when the two servers cannot reach each other. The CSV 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. Stock, licences and users are separate records in Snipe-IT and are not part of the asset CSV: import people with the People importer and enter stock and licences in Tagaris directly.
After the import
A short checklist to finish the move.
- Spot-check the asset count and a handful of records against Snipe-IT.
- After a CSV import: set warranty end dates, recreate custom statuses and custom fields in Settings, and enter stock and licences. The API migration does all of this.
- Merge any vendors that are really the same company ("Dell" and "Dell UK Ltd").
- 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, images and uploaded files stay in Snipe-IT: Tagaris starts a fresh dated history for each asset at import, so keep your Snipe-IT if you need the old trail for records. User logins, passwords and permissions do not come across; people are records to assign kit to, and colleagues are invited as users separately. Licence product keys, who holds a checked-out accessory or licence seat, and encrypted custom field values (which Snipe-IT hides from its API) stay behind. An asset checked out to another asset keeps its location and gets a line in its notes saying what it was attached to. LDAP and Active Directory sync have no Tagaris equivalent; single sign-on is OpenID Connect with Microsoft Entra ID, Okta, Google Workspace or any provider, on every plan, and view-only people are free. 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 see the migration page and walk the CSV wizard with a sample file first.