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

# Import a CSV

> Upload contacts in five steps with auto-detected column mapping.

CSV import is the fastest way to bring people into Path. Upload a file, pick a channel or event, confirm the field mapping, and start the import. Most files finish in well under a minute. Prefer to sync automatically? See [Connect Eventbrite](/platform/integrations/eventbrite) or [Connect Luma](/platform/integrations/luma).

<Note>
  **Before you start**

  * A TalkValue workspace with an active Pro trial. See [Plans and trial](/administration/billing/plans-trial-pro).
  * A CSV file with headers in the first row, encoded as UTF-8
  * 10 megabytes or less of file size
  * A column with email addresses. Every imported person must have one.
</Note>

## Run the import

<Steps>
  <Step title="Open Path and click Import Data">
    Sign in at [app.trytalkvalue.com](https://app.trytalkvalue.com), open **Path** from the left rail, and click **Import Data**. The Upload step of the import wizard opens.
  </Step>

  <Step title="Drop your CSV onto the upload area">
    Drag a `.csv` file onto the dropzone, or click **Select file** to browse. If you don't have one, click **Download sample template** to grab a template with the headers Path auto-detects. The file is analyzed in place, showing the row count, column count, and a preview of the first detected columns. Click **Continue**.
  </Step>

  <Step title="Pick a target (channel or event)">
    On the Configure step, choose where the contacts go:

    * **Channel.** A reusable source like `Newsletter` or `LinkedIn` that persists across events.
    * **Event.** A single dated gathering. Pick this when the file is an attendee list for one event.

    Pick from the list, or use the **Create channel** / **Create event** option to make a new one inline.
  </Step>

  <Step title="Confirm the column mapping">
    The **Map Fields** table shows every column in your CSV with its sample values and an auto-detected TalkValue field. Suggested fields appear at the top of the dropdown. Drag or pick a different field for any column you want to override, or set it to `-- Do not import --` to skip.

    **Email is required.** The Continue button is disabled until at least one column is mapped to Email. Full reference: [Column mapping](/path/import/column-mapping).
  </Step>

  <Step title="Review and start the import">
    On the Review step, confirm the row count, target, and field mapping. Click **Start Import**. Progress streams live. When it finishes, open **People** in the Path side panel to see the new contacts.
  </Step>
</Steps>

## CSV format

* **Encoding.** UTF-8.
* **Headers.** First row must contain column names. Path matches on the header text.
* **File size.** Up to 10 megabytes per upload. For larger files, split into multiple imports.
* **Required mapping.** At least one column must map to **Email**. Other fields are optional.
* **Supported target fields.** Email, First Name, Last Name, Full Name, Phone, Job Title, Company Name, Address, LinkedIn URL, X URL, Joined At.

## Troubleshooting

### The upload is rejected with a file-size error

The file is larger than 10 megabytes. Split it into smaller CSVs and import each one in turn. Path deduplicates by email, so the same person across two files updates the existing record rather than creating a copy.

### Email is not auto-detected

Path didn't recognize your header for the email column. Open the Map Fields table, find the column that contains email addresses, and pick **Email (Required)** from the dropdown. The Continue button enables once Email is mapped. Full reference: [Column mapping](/path/import/column-mapping).

### A row failed during import

Path reports rows with invalid emails, invalid phone numbers, or unparseable dates and continues importing the rest. After the import finishes, the result screen lists the failed rows with their error reason so you can fix them in the source file and re-import.

## Related

* [Column mapping](/path/import/column-mapping). Full field reference and how auto-detection works.
* [Connect Eventbrite](/platform/integrations/eventbrite). Sync events and attendees automatically.
* [Connect Luma](/platform/integrations/luma). Sync events and attendees automatically.
* [People, companies, channels, events](/platform/concepts/data-model). Entity primer.