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

# How to Add Customers to a Static Segment via Import

Got a list of customers you want in a [static segment](https://help.maestra.io/segments/how-to-create-a-static-customer-segment.md)? Upload it as a file and Maestra Platform adds them all at once. It's handy for migrating segments from another system, loading lists for one-off campaigns, and any other job where there's no direct integration.

To load up to 10 files into different segments in one go, use [bulk import](#bulk-import).

> [!NOTE]
>
> A customer can only be in one segment of a segmentation at a time. When you add them to segment B, they automatically leave segment A.

Imports run under **Customer Data Platform → Imports**. Click **New import** to open the settings.

## Step 1. Choose the import type

* Pick the import type — **Customers → Static customer segments**.
* Pick the action — **Add customers to a static segment**.

Before you import, make sure the [static segmentation](https://help.maestra.io/segments/how-to-create-a-static-customer-segment.md) and the segment you need already exist in your account.

## Step 2. Prepare and upload the file

Work out which fields you need. The file has to contain at least one customer identifier.

| Field | System name | Required | Description |
| - | - | - | - |
| Email Mobile phone Discount card number Maestra customer ID Other customer identifiers created in your account | `CustomerEmail` `CustomerMobilePhone` `DiscountCard` `CustomerMindboxId` `CustomerExternalIdentity{System_name}` | ✅ At least one | The customer's identifier or contact |
| Segmentation external ID | `SegmentationExternalId` | Yes, unless set in the import settings | The segmentation whose segment the customers are added to |
| Segment external ID | `SegmentExternalId` | Yes, unless set in the import settings | The segment the customers are added to |

> [!WARNING]
>
> If the segment isn't set in either the import settings or the file, the customer is removed from the segmentation. For example, if they were in another segment of that segmentation, they leave it.

> [accordion] How to find the segmentation and segment IDs
>
> 1. Go to **Customer Data Platform → Segments**.
> 2. Find the static segmentation you need and click its name.
> 3. Click **More** to expand the segmentation details. The ID is in the **External ID** field.
> 4. Repeat for each segment.

Export the data from your source system and build the file. Use the first row for field names — the wording is up to you.

* Format: `.csv` or `.txt`.
* Check that the values match the allowed formats.

See [Preparing a file for import](https://help.maestra.io/import-data/preparing-a-file-for-import.md) for the full set of recommendations.

Upload the file and click **Continue**.

## Step 3. Map the file's fields

Maestra Platform maps the file's columns to its own fields automatically. Check the result and adjust it by hand if you need to:

* In the **Import** column, tick the fields you want to load. Unticked columns are skipped.
* In the **Maestra field** column, map each file column to a field on the account. Optional fields left unmapped are skipped.

> [!TIP]
>
> If a custom field you need doesn't exist yet, create it with the **Create custom field** button.

Click **Continue**.

## Step 4. Choose the segment

You can set the segment in two ways:

* **Add all customers to one segment** — pick the segment in the import settings. Every customer in the file lands in it.
* **Add customers to different segments** — add two columns to the file with the segmentation and segment external IDs, and skip the import settings. You'll find both IDs under [Segments](#step-2-prepare-and-upload-the-file).

When the segment is set in both the import settings and the file, the file wins.

## Step 5. Review and start the import

Before you start, Maestra Platform shows the first rows of the file with the mapping already applied. Check that the data looks the way you expect — that the right values landed in the right fields. Add an import comment if you need one.

If everything's correct, click **Start import**.

## How to track the import

Once started, the import appears in the list on the **Import** page. For each task you'll see:

* start date,
* import type,
* source file with its comment,
* load progress,
* rows imported and errors,
* who started it.

If errors came up during the import, some rows were skipped. Open the import details to see which rows had a problem and why. Fix them in the file and run the import again.

## Bulk import

Bulk import lets you upload up to 10 files at once. Each file runs as its own import in the list. Field mapping, extra settings, and the preview are skipped — fields are matched by their system names.

### Step 1. Prepare the files

In the first row of each file, use Maestra Platform system names instead of your own field names. You'll find them in the [field table](#step-2-prepare-and-upload-the-file).

You can set the segment for each file in two ways:

* **In the file** — add a column with the segmentation's system name.
* **In the import settings** — pick the segmentation from the dropdown for each file.

When the segmentation is set in both the file and the page, the file wins. See [how to find the segmentation and segment IDs](#step-2-prepare-and-upload-the-file).

### Step 2. Upload the files and start the import

1. Choose the [import type](#step-1-choose-the-import-type).
2. Turn on the **Bulk import** setting.
3. Upload the files.
4. For each file, pick the segmentation if it isn't set in the file.
5. Click **Start import**.

## The result

Once the task finishes, the customers show up in the segment you picked:

* The segment appears in the customer profile under **Current Segments**.
* The fact they were added shows up in **Segment history**.

You can use the segment in campaigns, flows, and analytics.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.