Skip to main content

Importing assets and people

Tagaris imports your existing records rather than asking you to retype them. Assets come in from a CSV file, with source presets that recognise Snipe-IT and Halo exports and translate their status values. People come in from a CSV file or, on the free beta, directly from Microsoft Entra ID. Every import runs through a preview (a dry run), so nothing is written until you confirm, and the preview shows exactly what will happen.

The asset importer is a four-step wizard: upload, map columns, preview, then commit. Find it at Assets, then Import.

How it works​

  • The first row of the file must be a header row.
  • You map each Tagaris field to a column in your file. The wizard guesses the mapping from the header names; adjust anything it gets wrong. Only "Name" is required.
  • Categories, locations and people referenced by name are created automatically if they do not already exist.
  • Duplicate serial numbers and MAC addresses are flagged as warnings, not errors, so the row still imports. Rows with real problems (a missing name, a tag already in use, an unreadable date) are reported and skipped.
  • The limit is 5000 rows per file. Split a larger export into several files.

Dates are read as YYYY-MM-DD or DD/MM/YYYY. Prices are a plain number.

Migrating from another system​

If your file was exported from another asset system, choose that system from the Source list before or after you upload. The wizard then recognises its column names and translates its status values into ours. You can still adjust the mapping by hand, so a preset only needs to get most of the way there.

Snipe-IT​

Export your assets from Snipe-IT to CSV, then choose "Snipe-IT" as the source.

  • Common columns (Asset Tag, Name, Serial, Model name, Category, Manufacturer, Supplier, Status, Location, Purchase Cost, Purchase Date, Checked Out To, Notes) are mapped automatically.
  • Statuses are translated: Deployed becomes In use, Ready to Deploy and Pending become In storage, Out for Repair and Out for Diagnostics become Repair, and Archived and Lost/Stolen become Retired.
  • Snipe-IT's warranty is a length in months, not an end date, so it is not imported. Set warranty end dates afterwards if you need them.
  • "Checked Out To" is imported as the assignee. People are created by name.

Snipe-IT users, licences, accessories, components and consumables are separate records. Import people with the People importer (People, then Import); stock and licences are entered in Tagaris directly or through the API.

Halo​

Export your assets from HaloITSM or HaloPSA to CSV, then choose "Halo" as the source. Halo's asset field names are configurable, so check the mapping and set any column the wizard did not recognise. Common statuses (Active, In Stock, Spare, Faulty, Decommissioned, Scrapped) are translated.

People​

Import people (asset assignees) from People, then Import. Two sources:

  • CSV: upload or paste a file. It needs a name column, or separate first name and last name columns, and an optional email column. Common header names from Snipe-IT and Halo user exports are recognised. People are matched to existing ones by email, so re-running only adds new people.
  • Microsoft Entra: an administrator can pull people straight from Entra ID. This reuses the same Entra app you set up for Microsoft 365 email or single sign-on, so there is nothing new to register beyond granting the app the User.Read.All application permission with admin consent. Enabled users with a name are imported; disabled accounts are skipped. As with a CSV, people are matched by email, so pulling again only adds new starters. Nothing is written to the directory, and nothing is saved until you confirm the preview. The Entra pull is a free beta feature, enabled by a key from beta@tagaris.co.uk (the same beta as device sync).

Round-trip​

An asset CSV exported from Tagaris (from the assets list) re-imports with the generic source: the column names already match. This is a simple way to move assets between organisations or instances. For a full copy of everything, use a backup (see Backups and restore) or the full organisation export in Settings, Organisation, Data.