> ## Documentation Index
> Fetch the complete documentation index at: https://docs.laneapp.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Import CSV

> Bring feedback and customers into Lane in bulk from a spreadsheet — mapped to the right fields and linked to the right accounts.

When you're moving to Lane from another tool — or just have a backlog of feedback in a spreadsheet — CSV import brings it in bulk. You upload a file, map its columns to Lane's fields, preview the result, and import. Imported feedback runs through the same [processing pipeline](/insights) as anything else, so it's extracted, classified, and clustered into [Signals](/signals) right away.

Import lives in **Settings → Import**, and is also offered during onboarding so you can seed your workspace on day one. Customers can additionally be imported from the [Customers](/customers) page.

## What you can import

* **Feedback** — customer requests, notes, tickets, or any free-text feedback.
* **Customers** — companies and their attributes (name, domain, size, revenue).

## How it works

The flow is the same for both types:

1. **Upload** your CSV file.
2. **Confirm the file** and choose the **starting row** — so header rows or preamble don't get imported as data.
3. **Map fields** — line up each Lane field with the CSV column that feeds it.
4. **Preview & import** — check a sample of how the data will land, then import.

## Mapping feedback

When importing feedback, you map your columns to these fields:

* **Description** *(required)* — the body of the feedback. This is the one field import can't proceed without, since it's what Lane processes.
* **Title** *(optional)* — a short summary. Leave it unmapped and Lane generates one for each item automatically.
* **Customer Email** *(optional)* — map this and Lane links each row to the right customer: it matches an existing contact or creates one, and groups contacts under a company by email domain. This is the difference between an anonymous pile of feedback and feedback tied to real accounts.
* **Customer Name** *(optional)* — used alongside the email when creating new contacts.
* **Tags** *(optional)* — apply one or more tags to every row in the import as a bulk default.

<Tip>
  Always map Customer Email if you have it. It's what carries revenue and tier into your Signals — feedback linked to accounts is what makes prioritization meaningful.
</Tip>

## Mapping customers

When importing customers, you map your columns to the customer fields — **name**, **domain**, **size**, and **revenue**. Domain is worth mapping: it's what Lane uses to auto-link incoming feedback to the account and to fetch the company logo.

## FAQs

**Q: Which fields are required?**\
A: For feedback, only **Description** — Title is generated if you don't map it. For customers, map at least a name.

**Q: What if my file has header rows?**\
A: Choose the starting row during the confirm step so headers or preamble aren't imported as data.

**Q: Does imported feedback get processed?**\
A: Yes — it goes through the same pipeline as any other feedback, so Insights are extracted and it clusters into Signals.

**Q: How does customer linking work on import?**\
A: Map a **Customer Email** column and Lane matches or creates the contact and groups it under a company by email domain — no manual linking afterward.

**Q: Can I import during onboarding?**\
A: Yes. CSV import is part of onboarding so you can bring your existing feedback in from the start.