> ## 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 a backlog that's been sitting in a spreadsheet becomes ranked [Signals](/signals), tied to real customers, without anyone reading it row by row.

<Tip>
  CSV import is built for spreadsheets with many rows. For a single document, upload it in **Add Feedback**. For a small export with a handful of customers, attach it in [Lane](/agent) and ask it to save each comment.
</Tip>

Import lives in **Settings → Import**. A simpler version is offered during onboarding so you can seed your workspace on day one, and the **Import** menu on the [Customers](/customers) page leads here too.

## What you can import

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

## How it works

The flow is the same for both types:

1. **Upload** your CSV file. The upload screen shows the size limit; split very large files into smaller ones.
2. **Select the starting row**: click the first row of data, or type its number, so header rows or preamble aren't imported as data.
3. **Map fields**: line up each Lane field with the CSV column that feeds it.
4. **Preview & import**: check how the data will land, then import. A progress bar shows the upload.

During onboarding the flow is shorter: upload, map, and 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 each row gets a numbered placeholder title.
* **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** *(required)*, **domain**, **size**, **revenue**, and **renewal date**. Domain is worth mapping: it's what Lane uses to auto-link incoming feedback to the account and to fetch the company logo. Rows without a name, or with a domain that's already in Lane, are skipped, so re-importing a list doesn't create duplicates.

Renewal dates are read as year-month-day, like `2027-03-31`, so a date such as `03/04/2027` is never guessed the wrong way round. Once you map the column, Lane tells you how many of its cells aren't in that format before you import; those customers are still imported, just without a renewal date.

## After you import

Imported feedback is analyzed as soon as it's uploaded, using AI credits from your workspace balance. If you run out partway through, the rest waits until credits are available again. Very short rows, a few words or less, are imported but not analyzed, since there's nothing in them to act on.

Large imports are grouped into Signals shortly after they finish, rather than row by row, so give your Signals a little while to fill in.

## FAQs

**Q: Which fields are required?**\
A: For feedback, only **Description**. For customers, map at least a name.

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

**Q: Does imported feedback get processed?**\
A: Yes. It's analyzed as soon as it's uploaded, like any other feedback, and grouped into Signals; for large imports, grouping happens shortly after.

**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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.