> For the complete documentation index, see [llms.txt](https://kasplo.gitbook.io/kasplo-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kasplo.gitbook.io/kasplo-doc/product-docs/overview/contacts/how-to-import-contacts-to-kasplo.md).

# How to Import Contacts to Kasplo

Importing contacts into Kasplo is simple and supports both email-only and multi-channel (Email, SMS, WhatsApp) subscribers. This guide walks you through the process, requirements, and tips for a success-full import

***

###  What You’ll Need

* A **CSV file** (max size: **250MB**)
* **Email Address** is **mandatory** for every contact
* Optional: **Phone Number** in **E.164 format** (e.g., `919876543210`)
* Optional: **Country Code** (e.g., `IN`, `US`) — used to format phone numbers correctly if missing `91` or similar

> ⚠️ If both Phone Number and Country Code are provided, they must match.
>
> And in the excel make sure that the + isnt added for the country code column. 

***

### 📤 Steps to Import Contacts

1. **Navigate to**: `Contacts → Import`

   <figure><img src="/files/K6vpnmNiHrivpzYpk1zG" alt=""><figcaption></figcaption></figure>
2. **Upload your CSV file**

   **Choose import settings**:

   * Update existing contacts (optional)
   * Assign to lists (optional)
   * Add tags (optional)

   <figure><img src="/files/LQzGy6AkagT4GAlf52zn" alt=""><figcaption></figcaption></figure>
3. **Map fields**:
   * Email (required)
   * Phone/WhatsApp (optional)
   * Custom fields (e.g., name, status,city, gender)

     <figure><img src="/files/Xybrp5YlN6pdCBBcLswY" alt=""><figcaption></figcaption></figure>
4. **Start Import**

***

### Field Mapping Made Easy

Kasplo helps you quickly map your CSV columns to:

* System fields (Email, Phone, Country Code)
* Existing custom fields
* Create **new custom fields on the fly**

***

### Track Progress via Jobs

After starting the import:

* Visit the **Jobs** section to monitor status
* See progress, completion, and total records processed
* Download the **error log** if any records failed (e.g., missing email, invalid format)

<figure><img src="/files/wU4fNmFJ6XM2ciGQHGev" alt=""><figcaption></figcaption></figure>

***

### Common Import Errors

<table data-header-hidden><thead><tr><th></th><th width="309.661376953125"></th></tr></thead><tbody><tr><td><strong>Error Type</strong></td><td><strong>Description</strong></td></tr><tr><td>Missing Email</td><td>Email is required for every contact (e.g., email field left blank: <code>—</code>)</td></tr><tr><td>Invalid Format</td><td>Email or phone number is not in a valid format (e.g., <strong>+919876543210 / E.164</strong>, <strong>user@example.com</strong>, <strong>john.doe@company.co</strong>)</td></tr><tr><td>Mismatched Country Code</td><td>Phone number and country code conflict (e.g., country code <strong>+91</strong> with number <strong>+91 9876543210</strong>)</td></tr><tr><td>Duplicate Records</td><td>Same email found multiple times (if skipping duplicates is enabled) (e.g., <strong>user@example.com</strong> appearing in multiple rows)</td></tr></tbody></table>

***

### Best Practices

* Always clean your data before uploading
* Use standard headers (email, phone, country\_code, etc.)
* Double-check phone numbers are in E.164 format
* Avoid importing contacts who’ve unsubscribed or been suppressed