> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/vendors/importing-from-csv.md).

# Importing from CSV

If you already have a list of vendors in a spreadsheet, you can import them into Vendor Space in one step instead of adding them one at a time. This is especially useful when you're migrating from another tool or starting a new season with a returning vendor list.

***

## How to Import Vendors

1. Click **Vendors** in the sidebar
2. Click the **Import** button in the top right
3. Upload your CSV file
4. Optionally select one or more **events** to assign the imported vendors to
5. Click **Import** to process the file

Vendor Space will create a new vendor profile for each row in your file. If you selected events, every imported vendor will be assigned to those events and placed in the **Lead** stage of the [vendor pipeline](/docs/vendors/vendor-pipeline.md).

***

## CSV Column Reference

Your CSV file must include headers in the first row. Only **name** and **email** are required -- all other columns are optional.

| Column                 | Required | Description                           |
| ---------------------- | -------- | ------------------------------------- |
| `name`                 | Yes      | The vendor's company or business name |
| `email`                | Yes      | The vendor's email address            |
| `primary_contact_name` | No       | Name of the main contact person       |
| `phone`                | No       | Phone number                          |
| `address_line1`        | No       | Street address (first line)           |
| `address_line2`        | No       | Suite, unit, or apartment number      |
| `city`                 | No       | City                                  |
| `state`                | No       | Province, state, or region            |
| `postal_code`          | No       | Postal or ZIP code                    |
| `country`              | No       | Country                               |
| `notes`                | No       | Internal notes about the vendor       |

> **Tip:** Column order does not matter as long as the header names match exactly. Extra columns in your file will be ignored.

***

## Import Limits

You can import up to **500 vendors** per file. If you have more than 500 vendors, split them across multiple CSV files and import them one at a time.

***

## Preparing Your File

Here are a few things to keep in mind before uploading:

* **Save your spreadsheet as a CSV.** If you're working in Excel or Google Sheets, go to **File > Download > CSV** or **File > Save As > CSV** before uploading.
* **Use the exact column names listed above.** The importer matches by header name, so `name` works but `Company Name` will not.
* **Check for duplicate emails.** If a vendor with the same email address already exists in Vendor Space, the importer will skip that row to avoid creating duplicates.
* **Remove blank rows.** Empty rows in your file can cause unexpected results.

***

## Example CSV

Here is a minimal example showing what a valid import file looks like:

```
name,email,primary_contact_name,phone,city
Sweet Bee Bakery,hello@sweetbee.ca,Maria Santos,416-555-0199,Toronto
Timber & Thread,info@timberandthread.com,Jake Williams,,Vancouver
Green Roots Farm,greenroots@email.com,,,Ottawa
```

***

## After Import

Once your import completes, you will see a summary showing how many vendors were created and how many were skipped. From there, you can:

* Review the imported vendors in your vendor list
* Open any vendor's [company profile](/docs/vendors/company-profiles.md) to verify or update their details
* Begin moving vendors through the [pipeline](/docs/vendors/vendor-pipeline.md) for their assigned events

> **Tip:** If you regularly work with the same vendors season after season, keep a clean master CSV so you can quickly import returning vendors into new events.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://vendorspace.gitbook.io/docs/vendors/importing-from-csv.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.