Switching from GLPI
How to move your inventory into Tagaris: the migration wizard that reads GLPI through its REST API, what maps to what, and what to check afterwards.
The migration page reads your GLPI directly through its REST API and brings the inventory across in one go: computers, monitors, network equipment, peripherals, phones and printers, with their users, locations, purchase and warranty details, the location tree, people, statuses, consumables and software licences. A preview shows what would be created before anything is written, and running it again creates nothing that is already here. It is free on every plan and needs an administrator.
GLPI is a service desk and a CMDB as well as an inventory. Tagaris is an asset register: tickets, software installations and the components inside a computer stay in GLPI. If you are still weighing the two, the comparison page sets the tools side by side, and the live demo runs the current release in your browser.
What maps to what
What the migration reads from GLPI, and where it lands in Tagaris.
| In GLPI | In Tagaris | How it moves |
|---|---|---|
| Computers, monitors, network equipment, peripherals, phones, printers | Assets | Name, serial, manufacturer, model, comment as notes, and the first usable MAC address from the item's network ports. Items in the bin and templates are skipped. |
| Inventory number | Asset tag | Kept as it is. An item with no inventory number gets a tag made from its
GLPI id (for example GLPI-PC-42), the same every time, so a
second run still matches. |
| Type | Category | The item's own type (Laptop, Server, Switch) when it has one, otherwise the kind of item (Computer, Monitor and so on). |
| User and location | Assignee and location | GLPI keeps both, and so does Tagaris: the item's user becomes the assigned person and its location stays its location. |
| Financial information | Purchase date, value, supplier, warranty end | The warranty runs from the warranty start date if one is set, otherwise from the purchase date. Supplier names become vendor records. |
| Status | Statuses and custom status labels | A GLPI status is only a name, so Tagaris reads what it means from the name, in English or French ("En réparation" becomes Repair, "Au rebut" becomes Retired). A name that does not say ("On loan") follows what most items with that status are doing. Statuses that say more than In use, In storage, Repair or Retired are kept as custom status labels. |
| 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. |
| Users | People | Name and default email address. GLPI's built-in accounts (glpi, tech, normal, post-only and the system account) are skipped unless you have given them a real name. |
| Consumables and cartridges | Consumables | At the number of unused units, with GLPI's alert threshold as the minimum quantity, so the daily digest flags low stock. |
| Software licences | Software licences | Named after their software, with seats, expiry and value, and renewal reminders in the daily digest. |
| Entities | Organisations | Everything the token's user can see arrives in the one Tagaris organisation you are signed in to. To keep entities apart, run the migration once per organisation with a token that sees only that entity. |
The move, step by step
Assets, then Import, then "Migrate the whole register through its API", and choose GLPI under "Migrating from".
Turn on the REST API in GLPI
Setup, General, API, then Enable Rest API. It is switched off on a new GLPI. On the same page, open the API client (GLPI ships with one called "full access from localhost"): it only accepts requests from the address range it lists, so set the range to include the address Tagaris connects from, or clear it. If the client has an app token, copy it.
Generate an API token
Open your own user's preferences and, under Remote access keys, generate an API token. Use an account whose profile can read everything you want to bring across. A token is shown once.
Read, preview, migrate
In Tagaris, enter your GLPI address, the API token and the app token if there is one, then choose Read and preview. Neither token is stored. The preview shows one line per record type; Migrate now lands it all in one go, or not at all if something fails.
Tested against GLPI 11.0; the REST API is the same one GLPI 9.5 and 10 use. From Docker, the address GLPI sees is the Docker host's, not the container's. The full walkthrough, with the error messages, is in the importing guide.
After the migration
A short checklist to finish the move.
- Spot-check the asset count and a handful of records against GLPI.
- Check the statuses that were read from their names, and rename any custom status labels that came across.
- Give a tag of your own to any asset that arrived with a GLPI-PC-42 style tag, then print QR label sheets.
- Merge any vendors that are really the same company.
- Add custom fields in Settings for anything you tracked in GLPI beyond what the table above lists; only those fields are read.
- Schedule a backup, and run one restore test while the stakes are low.
What does not carry over
Tickets, contracts, documents, software installations, the components inside a computer, licence serial numbers, and user logins and profiles stay in GLPI. Tagaris starts a fresh dated history for each asset at migration, so keep your GLPI if you need the old trail for records. Tagaris has its own issues (small on purpose, with a no-login staff form) and contracts, but they start empty. LDAP sync has 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 GLPI API will need redoing against the Tagaris REST API.
Try the migration 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 first.