Stackroom

Importing assets with a CSV

A complete guide to preparing and importing your asset data using a CSV file — file requirements, standard columns, custom fields and troubleshooting.

6 min read

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.

  • Columnname
    RequiredYes
    ExampleDeWalt Impact Driver
  • Columncategory
    RequiredNo
    ExamplePower tools
  • Columnbrand
    RequiredNo
    ExampleDeWalt
  • Columnmodel
    RequiredNo
    ExampleDCF887
  • Columnserial
    RequiredNo
    ExampleSN-48213
  • Columnlocation
    RequiredNo
    ExampleNorth Site
  • ColumnpurchasePrice
    RequiredNo
    Example199.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

  1. 1
    Upload your file

    Choose your .csv in the importer. Stackroom reads the header row to detect your columns.

  2. 2
    Map your columns

    Confirm how each column maps to a Stackroom field, or leave extras as custom fields.

  3. 3
    Review validation

    The importer flags rows with issues before anything is created, so you can fix and re-upload.

  4. 4
    Confirm 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.