Import assets from CSV into AssetPilot

Inventory → Import brings assets in from a CSV file. The wizard checks every row before anything is written, so you can fix problems first.

The import wizard in four steps.

Before you start

• Use one file per asset type. All rows in a file get the type you choose.
• Save Excel files as CSV (UTF-8) first.
• Download the type's template in step 1 to see the expected columns. Base columns are Tag, Name, Status, Serial, Location, Assignee email, Supplier, Purchase date, Purchase cost, Currency, Warranty end and Notes, followed by the type's own fields.
• A file can have up to 10,000 rows.

Step 1: Upload

Choose the asset type, then drop the CSV file.

Choose the Asset type, then drop the file or browse for it. AssetPilot shows the number of rows, the encoding and whether it found a header row.

Existing assets are matched by tag or serial number. You decide in step 3 what happens to matches.

Step 2: Map columns

11 of 13 columns matched automatically. One column needs a target and one is ignored.

AssetPilot matches columns by name, so Serial number maps to Serial and Owner email to Assignee email. Check each row:

Match	Meaning
Auto	Matched automatically. Change the target if it is wrong.
Check	No match found. Pick a target field.
Ignored	The column is left out of the import.

Tag and Name are required. Status values must match a lifecycle status. Locations are created if they don't exist. Assignee email matches a Jira user or an external person. Dates can be ISO (2026-09-14) or DD.MM.YYYY.

Step 3: Preview

48 of 50 rows are ready. Two rows have errors and will be skipped.

The preview shows how many rows will be created, updated and skipped, and validates every row. Rows with errors show the reason, for example:

• Serial "CN0X7P2D" is duplicated in row 2. Serial must be unique.
• Status "Loaned" doesn't exist. Use one of: Available, In use, Pending, In repair, Retired.

Under When a tag or serial already exists, choose:

• Skip the row to keep your current records unchanged, or
• Update the existing asset with the row's values to merge the file into AssetPilot.

Rows with errors are skipped. Fix them in the file and upload again, or continue without them.

Step 4: Import and review

Import finished: 42 created, 6 updated, 2 skipped, 1 location created.

Assets are written in batches of 100. The summary lists what was created, updated and skipped, and which locations were added.

Select Download error report to get the skipped rows with their problems. Fix them and import the same file again: rows that already exist are matched and updated, so nothing is duplicated.

From the summary you can Import another file, Open audit log or View assets.

Migrating from another tool

1. Export your assets from the old tool to CSV, one file per asset type where possible.
2. Create matching asset types and fields in AssetPilot, or start from a template.
3. Import each file, choosing Update if you run the same file more than once.
4. Spot-check a few records and the audit log.