> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/analyze/users-and-segments/data-management/imports.md).

# Imports

Bulk-load users, their attributes and their companies from a CSV file, match them against your existing base, and get a segment of everyone in the file.

**Dashboard path:** [Users & Segments > Data Management > Import History](https://i.usejimo.com/users/imports) (`/users/imports`)

## Import users from a CSV

Importing lets you create or update users in bulk from a CSV file, without waiting for them to show up in your product. Use it to seed a project before installation, to enrich your base with data that lives in another system, or to build an audience from a list someone handed you.

One import does three things: it adds the users who are not in Jimo yet, updates the ones who are, and creates a segment with every user in the file.

{% hint style="info" %}
An import is a **snapshot**, not a sync. It writes what the file contains, once. Nothing keeps updating afterwards. For a live connection, see Data Management and the integrations.
{% endhint %}

***

### Prepare your CSV file

**Headers**

Use the **first row as headers**, one column per attribute you want to import or use for matching.

* A column name **does not need to match** an existing attribute in Jimo: you choose the attribute during the import, or create a new one.
* Keep one row per user, with a column that identifies them: the **ID** your app sends with `identify`, their **email**, or both.
* Each column name must be unique. A file whose header row repeats a name is refused, and so is a file with no user row.
* To attach users to companies, add a column with the **company ID**, and one column per company attribute.

**Format**

Save the file in the CSV format (`.csv`). The file picker only offers CSV files.

{% code title="Example.csv" fullWidth="false" %}

```csv
id,email,plan,company_id,company_name,company_plan
1,johndoe@example.com,Pro,acme-001,Acme,Enterprise
2,janedoe@example.com,Free,acme-001,Acme,Enterprise
3,bobjohnson@example.com,Pro,globex-002,Globex,Business
```

{% endcode %}

***

### Run the import

{% stepper %}
{% step %}

### Pick the file

Click **Import users from CSV** and choose your file. The **Import from CSV** window opens on it, with a preview of the first rows and the number of rows and columns.
{% endstep %}

{% step %}

### Identifier Mapping

Tell Jimo which columns identify each row:

| Field                                   | What to pick                                                                 |
| --------------------------------------- | ---------------------------------------------------------------------------- |
| **User Identifier Field**               | The column that holds the ID your app sends with `identify`                  |
| **Email Field**                         | The column that holds the user's email                                       |
| **Company Identifier Field** (optional) | The column that holds the company ID. See [below](#company-identifier-field) |

Jimo matches each row to an existing user by the identifier first, then by the email.

Click **Continue**.

{% hint style="danger" %}
**Pick the same kind of ID your app uses.** If your app identifies users by an internal ID and your file holds another one, no row matches and every line becomes a new user.
{% endhint %}
{% endstep %}

{% step %}

### Attributes Mapping

Each column of the file gets a row, with three settings:

| Setting            | What it does                                                                                                                                                               |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Checkbox**       | Whether the column is imported. Uncheck the columns you do not need. The identifier columns are always imported.                                                           |
| **Jimo Attribute** | Where the column lands: an existing attribute, picked from **User Attributes** or the company attributes (marked **Company**), or a new one with **Create "column name"**. |
| **Data Type**      | The type of the values, **Text** by default.                                                                                                                               |

Jimo suggests an attribute for each column. Check each suggestion before you import.

At the bottom, two counts tell you what the import will do: **Identified users** already exist in Jimo and will be updated, **Unidentified users** will be created and become active once the Jimo SDK identifies them in your product.

Click **Import N rows**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
This is the moment an import creates [attributes](https://help.usejimo.com/docs/analyze/users-and-segments/data-management/attributes.md). A column mapped to **Create** becomes a custom attribute of your project, one per column.
{% endhint %}

***

### Company Identifier Field

When you pick a **Company Identifier Field**, each row joins the company whose ID is in that column. Jimo creates the company if it does not exist yet, and the row's company columns become that company's attributes.

When the company already exists, the user joins it. An empty company cell leaves that company attribute as it is.

The companies show on the Companies page as soon as the import starts.

***

### The imports list

Every import is listed here, with the file name as its name.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2Fnm0B6cadpdex9DKIrBUL%2FP-s16-import-history.png?alt=media&amp;token=f6ef924f-637b-40c2-b15d-0ea25d2c1d8f" alt="Imports with the creation date, name, description, rows detected, rows processed and status of each file"><figcaption></figcaption></figure>

| Column            | What it shows                                        |
| ----------------- | ---------------------------------------------------- |
| **Creation date** | When the import was started, and by which teammate   |
| **Name**          | The file name                                        |
| **Description**   | *Imported users from* followed by the file name      |
| **Row detected**  | How many rows Jimo read in the file                  |
| **Row processed** | How many rows the import has processed               |
| **Status**        | **In progress** while the import runs, then **Done** |

Some imports show **Draft**, with no row detected or processed.

The counts and the status can lag behind the import itself: the users, their companies and the import segment can already show in Jimo while the import still reads In progress at 0%.

Click an import to open its report: how many users were imported, how many were added and how many updated, and whether every row and value was imported.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FCBChutqakc0p8mme3AeM%2FP-s15-import-report.png?alt=media&amp;token=3cd3183e-8636-44e4-83f4-a4d303f1b74e" alt="The report of an import: 3 users imported, 3 added, 0 updated, and Every row and value was imported"><figcaption></figcaption></figure>

***

### The import segment

Each import creates a [user segment](https://help.usejimo.com/docs/analyze/users-and-segments/audience/segments.md) named after the file. Jimo tags every user of the file with *Imported from* followed by the file name, and the segment has one rule: **Tags** is any of that tag.

So the segment holds the users of the file, and only them. To add or remove someone later, add or remove the tag on their profile.

***

### Related pages

* Exports: the same operation, in reverse
* Companies: the companies an import creates or updates
* Data Management: when an import is the right inlet, and when it is not
* [Attributes](https://help.usejimo.com/docs/analyze/users-and-segments/data-management/attributes.md): what happens to the custom attributes an import creates
* [Segments](https://help.usejimo.com/docs/analyze/users-and-segments/audience/segments.md): the segment each import creates
* [Users](https://help.usejimo.com/docs/analyze/users-and-segments/audience/users.md): where the imported users land
