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

# Import a CSV

> Bring a spreadsheet in as a new table, checking the column names and types Oneprofile guessed before the rows are added.

Oneprofile builds a new table straight from a CSV file. Upload it, check the columns Oneprofile matched, fix anything that looks wrong, then add the rows.

<Frame caption="The Import a CSV dialog, on the column mapping step.">
  <img src="https://mintcdn.com/oneprofile/CSWJORDcrWxYd_Pk/images/find-leads/import-a-csv.png?fit=max&auto=format&n=CSWJORDcrWxYd_Pk&q=85&s=eb5aba12407dc0e70d377d496ab6bf65" alt="The Import a CSV dialog showing Table name and Rows to import fields above a list of the file's columns, each with a Column name box, a Type dropdown and its sample values." width="1440" height="900" data-path="images/find-leads/import-a-csv.png" />
</Frame>

## Import your file

<Steps>
  <Step title="Open the dialog">
    On **Tables**, choose the **Import a CSV** card. You can also click **New** and pick **Import a CSV**.
  </Step>

  <Step title="Add your file">
    Drag a CSV onto the dialog, or click to choose one. The first row is used as the column names, and files must be under 50MB.
  </Step>

  <Step title="Review the column mapping">
    Oneprofile lists every column under **Column name**, **Type**, and **Sample values**, with a type already guessed, such as **Text**, **Number**, **Date**, or **Email**. Edit a name in its box, change a wrong **Type**, or untick a column to leave it out.
  </Step>

  <Step title="Check the sample values">
    The mapping table shows only the start of a few values. Click the expand icon on a column to read all of them.
  </Step>

  <Step title="Name the table and set how many rows">
    **Table name** starts as the file's name. **Rows to import** starts at as many of the file's rows as your table can hold. Lower it to add fewer.
  </Step>

  <Step title="Create the table">
    Click **Create table**.
  </Step>
</Steps>

Oneprofile takes you straight to the new table. Adding the rows is a run, so you can start working before it finishes.

## Good to know

<AccordionGroup>
  <Accordion title="The dialog is reading your file">
    While it reads, the drop area says **Reading the file…**. A large file takes a moment. That message means it is working rather than stuck.
  </Accordion>

  <Accordion title="Reading every value in a column">
    The expand icon on a column is labelled **See all sample values**. It opens a dialog titled **Sample values for "…"**, with the column's name in place of the ellipsis.

    The dialog lists every sampled value with its row number, and names how many rows of the file it is showing. Click **Close** when you are done.

    <Tip>
      A column can look empty in the mapping table just because its first values are blank. Open its sample values before you trust the type Oneprofile guessed.
    </Tip>
  </Accordion>

  <Accordion title="Your file has more rows than your plan holds">
    Oneprofile names the file's size and how many rows your plan holds per table, then adds only the rows up to that limit.

    <Note>
      An **Upgrade** chip sits next to the message and takes you to raise the limit.
    </Note>
  </Accordion>

  <Accordion title="Create table is greyed out">
    It stays disabled until the mapping is valid, and the dialog names what is wrong. You will see "Include at least one column." or "Every included column needs a name." A column name used twice is called out by name.

    **Table name** cannot be blank either. Clearing it puts "The table needs a name." under the field.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Import from a tool" icon="download" href="/find-leads/import-from-a-tool">
    Add rows from a tool you already use.
  </Card>

  <Card title="Enrichment columns" icon="sparkles" href="/enrich/enrichment-columns">
    Add columns that fill themselves in.
  </Card>
</CardGroup>
