# Add via import

## Overview

The import function allows you to create and update multiple records efficiently in bulk. Instead of manually adding records one by one, you can prepare your data in a spreadsheet and import hundreds or even thousands of records at once.

This is especially useful for:

* Initial data migration from legacy systems
* Batch sample creation in research projects
* Bulk inventory loading
* Large-scale data entry with multiple fields per record

## How it works

The import process is straightforward:

1. **Prepare your data** in a TSV or XLSX file with column headers matching your table structure
2. **Select the file** and specify any project assignments
3. **Map the columns** from your file to the corresponding fields in Labii
4. **Review and execute** the import to create all records at once

## Required fields

When importing new records, ensure that all **required fields** (marked with an asterisk \* in your table settings) are included in your import file. Missing required fields will cause the import to fail for those records.

## Advanced features

* **Update existing records** by including UIDs (Unique IDs) to match and modify records
* **Execute workflows** after import to automatically perform actions like creating vials or samples
* **Use special syntax** like `{{INDEX}}` for auto-numbering or `{{LETTERINDEX}}` for letter sequences
* **Multiple value support** for fields that accept multiple selections

## For detailed instructions

For comprehensive guidance on file preparation, field formatting, workflow execution, and troubleshooting, see [**Import Records**](/user-guide/list-view/import.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.labii.com/user-guide/add-record/add-via-import.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.