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

# Column mapping

> How Path auto-detects CSV columns and how to override the mapping manually.

The Configure step of the import wizard shows a **Map Fields** table: every column in your CSV, side by side with the TalkValue field it maps to. Path auto-detects the common headers; you can override any of them, skip columns you don't want to import, and create new channels or events inline.

<Note>
  **Before you start**

  * You're partway through an import. See [Import a CSV](/path/import/csv-quickstart) for the full flow.
  * At least one column must map to **Email**. The Continue button stays disabled until you map it.
</Note>

## How auto-detection works

Path inspects the headers in the first row of your CSV and suggests a TalkValue field for each one. Common patterns (`email`, `first_name`, `company`, `linkedin`, `phone`, `joined_at`, and their variations) are detected automatically. When Path is confident, the suggested field appears under a **Suggested** group at the top of the dropdown.

If Path can't make a confident guess, the column shows up unmapped and you pick the right field manually. Columns left unmapped, either by Path or by you, are skipped during import.

## Supported target fields

| Field            | What it stores                                                                                   |
| ---------------- | ------------------------------------------------------------------------------------------------ |
| Email (Required) | Primary email address. One column must map here.                                                 |
| First Name       | Given name.                                                                                      |
| Last Name        | Family name.                                                                                     |
| Full Name        | Full name in a single column. Use either Full Name or the First Name + Last Name pair, not both. |
| Phone            | Phone number.                                                                                    |
| Job Title        | Title at the person's company.                                                                   |
| Company Name     | Company display name. Used when the email domain isn't enough to group reliably.                 |
| Address          | Mailing or visit address.                                                                        |
| LinkedIn URL     | LinkedIn profile URL.                                                                            |
| X URL            | X (Twitter) profile URL.                                                                         |
| Joined At        | Date the person joined the channel or event.                                                     |

## Override the mapping

<Steps>
  <Step title="Find the column you want to remap">
    Scroll the Map Fields table. Each row shows the source field name, two sample values from your CSV, and the current TalkValue field.
  </Step>

  <Step title="Open the field dropdown">
    Click the field cell to open the picker. Suggested fields appear at the top; the full field list sits below under **All Fields**, with **-- Do not import --** as the first option.
  </Step>

  <Step title="Pick the right field, or skip">
    Select the field you want. To skip the column entirely, pick **-- Do not import --**. Fields already used by another column are dimmed in the picker. Each target field can be mapped by at most one source column at a time.
  </Step>

  <Step title="Confirm Email is mapped">
    Above the table, you'll see a counter like `4 of 8 fields mapped`. If Email isn't mapped yet, a red **Email mapping is required** warning appears. Map it and the Continue button enables.
  </Step>
</Steps>

## Troubleshooting

### Path suggested the wrong field for a column

Pick the correct one from the dropdown. Suggestions are convenience, not constraint; your manual choice always wins.

### A field I need isn't in the list

The fields above are the full set Path maps. If your CSV has columns that don't match any of them, leave them as **-- Do not import --**. Unmapped columns are skipped; the data stays in your source file.

### Two columns hold the same data, which one do I map?

Pick one. The same target field can only be mapped by one column at a time; the other gets dimmed in the dropdown. If both columns have useful values, consolidate them in the source file before re-importing.

## Related

* [Import a CSV](/path/import/csv-quickstart). The full upload-to-import flow.
* [Connect Eventbrite](/platform/integrations/eventbrite). Skip CSVs and sync events directly.
* [Connect Luma](/platform/integrations/luma). Skip CSVs and sync events directly.