Import assets by exporting your existing list to CSV with one row per asset and a header row, then mapping each column to a Stackroom field. Only a name is required. Categories, locations and departments are created from the values in your file, and re-importing updates rather than duplicates.
Stackroom lets you bring your existing inventory in from a CSV (comma-separated values) file. It uses a template-based approach with validation, so your data lands cleanly and nothing is silently dropped.
Just switching from another tool? Export your data from it as CSV first — most tools and spreadsheets can. Then follow this guide, or ask us for a white-glove migration from the Migration Center.
Before you start
- Export or build a spreadsheet with one row per asset.
- Save it as .csv (UTF-8 encoding is safest).
- Keep the header row — column names are how Stackroom maps your data.
Standard columns
These columns map to core asset fields. Only name is required; the rest are optional but recommended.
- Column
nameRequiredYesExampleDeWalt Impact Driver - Column
categoryRequiredNoExamplePower tools - Column
brandRequiredNoExampleDeWalt - Column
modelRequiredNoExampleDCF887 - Column
serialRequiredNoExampleSN-48213 - Column
locationRequiredNoExampleNorth Site - Column
purchasePriceRequiredNoExample199.00
| Column | Required | Example |
|---|---|---|
name | Yes | DeWalt Impact Driver |
category | No | Power tools |
brand | No | DeWalt |
model | No | DCF887 |
serial | No | SN-48213 |
location | No | North Site |
purchasePrice | No | 199.00 |
Custom fields
Any extra column you include becomes a custom field on the imported assets, so your own attributes come across too — add as many as you need.
Import in four steps
- 1Upload your file
Choose your .csv in the importer. Stackroom reads the header row to detect your columns.
- 2Map your columns
Confirm how each column maps to a Stackroom field, or leave extras as custom fields.
- 3Review validation
The importer flags rows with issues before anything is created, so you can fix and re-upload.
- 4Confirm the import
Approve, and your assets are created — ready to label, assign and track.
Troubleshooting
- Rows rejected? Check for missing names or malformed numbers in price fields.
- Odd characters? Re-save the file as UTF-8 CSV.
- Wrong mapping? Rename the header to match the standard column, or remap during import.
Migrating a large or complex catalog? Send us your export and we'll handle the import with you — see the Migration Center.
Frequently asked questions
What format does the CSV need to be in?
A standard comma-separated file with a header row and one row per asset, saved as UTF-8. Most spreadsheets and asset tools export this directly. Only the name column is required; everything else is optional but worth including while you are there.
Will importing twice create duplicates?
No, provided the rows carry a code you already track. Matching on an existing reference updates the record instead of creating a second one, which is what makes a re-import safe after you have corrected a column.
Can I import custom fields?
Yes. Any extra column becomes a custom field on the imported assets, so attributes you already track come across rather than being flattened away.
What happens to rows with errors?
They are reported rather than silently dropped, with the reason. Fix those rows and re-import just them, or correct the source file and import the whole thing again.