After importing profiles to Synerise, you can direct various actions towards them, such as:
- Sending messages ([email](/docs/campaign/e-mail), [SMS](/docs/campaign/SMS), [mobile push](/docs/campaign/Mobile), [web push](/docs/campaign/Webpush), [in-app messages](/docs/campaign/in-app-messages)).
- Creating [predictions](/docs/ai-hub/predictions).
- Creating [query rules](/docs/ai-hub/ai-search/query-rules) in [AI search engine](/docs/ai-hub/ai-search).


## Requirements
---
- You need user permissions that grant you access to Simple Imports or/and Automation
- Prepare a file that contains one of the following profile identifiers: (the list contains recommended column names, if you use different names you will be able to map/transform data during the process):
    - `email` - use it only if you use [unique emails](/docs/settings/configuration/non-unique-emails) in Synerise. If you use non-unique emails, don't use `email` as an identifier during the import, use `customId` instead.
    - `uuid`, 
    - `clientId` - can be used only when updating an existing profile
    - `customId`,
    - `phone` - Phone number is treated as an identifier only if no other identifier is provided. Then, if a profile with this phone number does not exist and non-unique emails are disabled, an anonymous profile is created.  
      This is the only required column, the rest is optional.
        
      <div class="admonition admonition-warning"><div class="admonition-icon"><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2.5"><path stroke-linecap="round" stroke-linejoin="round" d="M12 9v2m0 4h.01m-6.938 4h13.856c1.54 0 2.502-1.667 1.732-2.5L13.732 4c-.77-.833-1.964-.833-2.732 0L4.082 16.5c-.77.833.192 2.5 1.732 2.5z" /></svg></div><div class="admonition-body"><div class="admonition-content">

      If you choose an email as an identifier, pay attention to the correct format of emails. Otherwise, your import will fail.

      </div></div></div>

    - Spaces and special characters in the column headers are not allowed.
    - `.csv` files must be UTF-8 encoded
    - Maximum file size: 200 MB.


### Tips for preparing a CSV file

- Recommended file metacharacters:
    - A character that splits columns (delimiter): `,`
    - A character that is used to contain the text (quotation mark): `"`
    - A character (escape character) that changes the default interpretation of a sign or string followed by the escape character: `\`
- Attributes (column names) and values are case-sensitive (firstname and Firstname are not the same)
- If you will use Automation Hub as a [method of import](/docs/assets/imports/introduction-to-imports#import-methods), below you can find the instructions how to transform the optional default profile properties:

| Profile's property                                                            | Required name                                                                                                                                         | Accepted values                                                                                                                                                                      | Other comments                                                                                                                                                                    |
|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Profile's first name                                                          | `firstName`                                                                                                                                           | A string                                                                                                                                                                             | n/a                                                                                                                                                                               |
| Profile's last name                                                           | `lastName`                                                                                                                                            | A string                                                                                                                                                                             | n/a                                                                                                                                                                               |
| Date of birth in the profile                                                  | `birthDate`                                                                                                                                           | the `yyyy-mm-dd` format, months must be zero-padded (for example, May is `05`)                                                                                                        | For example, `1999-09-09`                                                                                                                                                         |
| Profile's company                                                             | `company`                                                                                                                                             | A string                                                                                                                                                                             | n/a                                                                                                                                                                               |
| Profile's city of residence                                                   | `city`                                                                                                                                                | A string                                                                                                                                                                             | n/a                                                                                                                                                                               |
| Profile's street address                                                      | `address`                                                                                                                                             | A string                                                                                                                                                                             | n/a                                                                                                                                                                               |
| Profile's zip code                                                            | `zipCode`                                                                                                                                             | A string                                                                                                                                                                             | n/a                                                                                                                                                                               |
| Profile's province of residence                                               | `province`                                                                                                                                            | A string                                                                                                                                                                             | n/a                                                                                                                                                                               |
| Code of profile's country of residence in accordance with the ISO 3166 format | `countryCode`                                                                                                                                         | A string                                                                                                                                                                             | n/a                                                                                                                                                                               |
| Profile's gender                                                              | `sex`                                                                                                                                                 | `FEMALE`, `MALE`, `OTHER`, `NOT_SPECIFIED`                                                                                                                                           | These values are transformed during import as follows: <br> - NOT SPECIFIED and OTHER to `0` <br> - FEMALE to `1` <br> - MALE to `2` <br> These values will be presented as such in a profile's card |
| Marketing agreements of the profile                                           | <br> - for email: `agreements.email` <br> - for web push: `agreements.webPush` <br> - for mobile push: `agreements.push` <br> - for SMS: `agreements.sms` | <br> - for email: `true`, `false`, `True`, `False`, `1` (true), `O` (false) <br> - for web push: `true`, `false` <br> - for mobile push: `true`, `false` <br> - for SMS: `true`, `false` | If you use non-unique emails, email marketing agreement is saved as a custom attribute which takes the following values: `enabled`, `disabled`                                    |
| Tags assigned to a profile                                                    | `tags`                                                                                                                                                | An array of strings                                                                                                                                                                  | n/a                                                                                                                                                                               |
| A profile's phone number                                                      | `phone`                                                                                                                                               | The phone number can contain digits, spaces, and an optional `+` at the beginning.                                                                                                   | For example: `+48111222333`; `+48 111 222 333`                                                                                                                                    |


**Example**

<figure>
<img src="/api/docs/image/54176ad07f146575310749eba44b7c2f42c1b327/docs/settings/_gfx/client-import-example-file.png" alt="Exemplary file for a profile import" class="large" >
<figcaption> Exemplary file for a profile import </figcaption>
</figure>

For more details about parameters and their accepted formats, click [here](https://developers.synerise.com/ProfileManagement/ProfileManagement.html#operation/BatchAddOrUpdateClients).

## Procedure
---

### Selecting the file for import 

In this part of the process, you will upload a file from your device.

1. Go to <img src="/api/docs/image/54176ad07f146575310749eba44b7c2f42c1b327/icons/data-modeling-hub-icon.svg" alt="Data Modeling Hub icon" class="icon"> **Data Modeling Hub > Imports > New import**.
2. As the data type for import, select **Profiles**.
3. As the import method, select one of the following options:
    - Import a local file - To import a single `.csv` file to Synerise.
    - Import in Automation - To import a .`csv`, `.json`, `.jsonl`, and `.xml` files and execute periodical imports.


      <div class="content-tabs" data-tab-group="tabgrp-1264">
      <div class="tab-buttons"><button class="tab-button" data-tab-id="tabgrp-1264-0" data-tab-group="tabgrp-1264" data-tab-active="true">Local File</button><button class="tab-button" data-tab-id="tabgrp-1264-1" data-tab-group="tabgrp-1264">Automation</button></div>

      <div class="tab-panel" data-tab-id="tabgrp-1264-0" data-tab-group="tabgrp-1264" data-tab-active="true">

      1. Upload the `.csv` file by using the **+ Upload file or drop one here** field.
      2. Optionally, you can customize the file metacharacters by clicking the arrow down icon.
          1. From the **Delimiter** dropdown, select the character that marks the end of a column.
          2. From the **Quotation mark** dropdown list, select the characters that contain the text or data type.
          3. From the **Escape character** dropdown lists, select the character which changes the default interpretation of a character or a string followed by the escape character.
      3. To proceed to the next step, click the **Next** button. 

      ### Mapping the columns with parameters in Synerise

      In this part of the process, you will connect the columns from the file with their counterparts (the existing parameters) in Synerise. This way, you will point which parameters in Synerise will contain the profile information from the imported file.  
      You can also exclude parameters from the import. During the mapping process, you can't add new columns to the imported file.

      On the user interface, you will be presented with two columns - the left column displays the names of the columns from the imported file, the other contains dropdown lists with the parameters available in Synerise. The dropdown lists indicate **required** parameters for a successful import. 

      1. Next to the file column name, from the dropdown list, select the corresponding parameter in Synerise. Perform this step for all columns in your file. 
      2. To exclude a parameter from import, next to the column name, click this icon: <img src="/api/docs/image/54176ad07f146575310749eba44b7c2f42c1b327/icons/mapping-arrow.png" alt="An arrow icon" class="icon" >  
          **Result**: The icon changes to <img src="/api/docs/image/54176ad07f146575310749eba44b7c2f42c1b327/icons/dont-import-icon.png" alt="Don't import icon" class="icon" >

      ### Launching import

      After steps described above you'll be redirected to the mapping summary. If it's correct, to launch the import, click **Run import**.

      </div>

      <div class="tab-panel" data-tab-id="tabgrp-1264-1" data-tab-group="tabgrp-1264">

      1. Select the method of delivering the file:
          - Local File - This option allows you to upload a file from your device.
          - SFTP protocol - This option allows you to upload a file from a server using the SFTP protocol.
          - HTTPS protocol - This option allows you to upload a file from a server using the HTTPS protocol.  
          - Amazon S3 - This option allows you to upload a file from Amazon S3 bucket.
          - Azure - This option allows you to upload a file from Azure Blob Storage.
          - Google Cloud Storage - This option allows you to upload a file from Google Cloud Storage.
      2. Click **Go to import template**.  
      3. Define the settings of the [Scheduled Run node](/docs/automation/triggers/scheduled-run).
      4. Depending on the method of delivering the file, configure the settings of [Local File](/docs/automation/integration/http-integrations/http-get-file) or the [Get File](/docs/automation/integration/http-integrations/http-get-file) node that uses HTTP protocol or the [Get File](/docs/automation/integration/sftp-integrations/sftp-get-file) node that uses SFTP protocol. 
      5. If the data requires modification, configure the settings of the [Data Transformation node](/docs/automation/operation/data-transformation-node). If you have prepared the transformation rules for the data structure of the imported file, select it from the dropdown list. If not, create it from scratch.  
          You can remove this node if your data doesn't require transformation.
      6. The rest of the nodes in the default template don't require any further configuration.
      7. If your workflow is ready, click **Save & Run**.

      </div>
      </div>


## Reserved parameters
---

You are not allowed to create the following parameters while mapping. These are default parameters available in Synerise (they already exist in Synerise).


<table>


<tbody>
<tr>
<td>address</td>
<td>agreements</td>
<td>anonymous</td>
<td>anonymous_type</td>
</tr>

<tr>
<td>avatarUrl</td>
<td>birthdate</td>
<td>birthDate</td>
<td>businessProfileId</td>
</tr>

<tr>
<td>city</td>
<td>clientId</td>
<td>company</td>
<td>confirmation_hash</td>
</tr>

<tr>
<td>confirmed</td>
<td>countryCode</td>
<td>country_id</td>
<td>created</td>
</tr>

<tr>
<td>customId</td>
<td>custom_identify</td>
<td>deletedAt</td>
<td>displayname</td>
</tr>

<tr>
<td>displayName</td>
<td>email</td>
<td>external_avatar_url</td>
<td>facebookId</td>
</tr>

<tr>
<td>firstname</td>
<td>firstName</td>
<td>geo_loc_as</td>
<td>geo_loc_city</td>
</tr>

<tr>
<td>geo_loc_country</td>
<td>geo_loc_country_code</td>
<td>geo_loc_isp</td>
<td>geo_loc_lat</td>
</tr>

<tr>
<td>geo_loc_lon</td>
<td>geo_loc_org</td>
<td>geo_loc_query</td>
<td>geo_loc_region</td>
</tr>

<tr>
<td>geo_loc_region_name</td>
<td>geo_loc_status</td>
<td>geo_loc_timezone</td>
<td>geo_loc_zip</td>
</tr>

<tr>
<td>ip</td>
<td>lastname</td>
<td>lastName</td>
<td>last_activity_date</td>
</tr>

<tr>
<td>newsletter_agreement</td>
<td>ownerId</td>
<td>phone</td>
<td>province</td>
</tr>

<tr>
<td>receive_btooth_messages</td>
<td>receive_push_messages</td>
<td>receive_rfid_messages</td>
<td>receive_smses</td>
</tr>

<tr>
<td>receive_webpush_messages</td>
<td>receive_wifi_messages</td>
<td>sex</td>
<td>source</td>
</tr>

<tr>
<td>tags</td>
<td>time</td>
<td>type</td>
<td>updated</td>
</tr>

<tr>
<td>uuid</td>
<td>zipCode</td>
<td></td>
<td></td>
</tr>
</tbody>
</table>