---
title: "Import Mapping via CSV"
slug: "import-mapping-via-csv"
updated: 2024-09-18T08:12:11Z
published: 2024-09-18T08:12:11Z
---

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

# Import Mapping via CSV

## Prerequisites

1. Have your import CSV file ready before you start.
2. The CSV file must include the mapping type, a **Source**, and a **Destination**.
3. The **Source**names must match those in the JSON file obtained from the external data source. The destination names are the ones within Mapp Engage.

## Procedures

### Import Mapping

This import overwrites all mappings.

1. Go to *Data Management > Mapp Conne*ct and open the integration you want to edit.
2. Open the **Mapping**tab*.*
3. Select**Import Mappings**, then **Add New Import,** and select the file to upload.
4. Once the file is uploaded, click **Import**.

![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/image(578).png)

### Import Field Mapping

This import uses different CSV formats to import the user and other subtypes.

1. Go to *Data Management > Mapp Conne*ct and open the integration you want to edit.
2. Open the *Mapping tab.*
3. Select the field mapping you want to edit and click **Edit**.
4. Select**Import Mappings**, then **Add New Import,** and select the file to upload.
5. Once the file is uploaded, click **Import**.

![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/image(579).png)

#### Format for subtype “user”

- Allowed mapping types: member, Custom, Standard, None
- The custom attribute destination has to exist beforehand to be imported correctly.
- The member attribute destination has to contain a valid groupId.

```plaintext
CUSTOM,source1,atrribute1
MEMBER,source2,1:attribute2
```

#### Format for all subtypes except user

```plaintext
cols,cold
col1,col2
col2,col3
```