> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://ayuda.peewah.co/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to import registrants from a file

If you already have a list of people, you can load them into your event at
once from a **CSV file** instead of adding them one by one.

---

# 1. Start from the template

👉 [Download the import template](https://storage.googleapis.com/ems-backend.appspot.com/Formato%20Carga%20de%20Asistentes.xlsx)

**Required columns:** first name, last name, email.

---

# 2. Add your own fields

If your registration form asks for more — institution, license number,
specialty — add a column for each.

> 🔴 **The column name has to match the field name exactly.** Same
> capitalization, same spaces, same accents and punctuation.
>
> `Licence number` will not match a field called `License Number`. The row
> imports, the answer goes nowhere, and you find out when you export.

**Multiple-choice fields that accept more than one answer** need their values
in square brackets:

```
[29] [Bogotá]
```

**Single-answer fields do not use brackets.** Writing them with brackets is
the second most common reason a row fails.

---

# 3. Save it as CSV

In Excel: **File → Save As**, and choose **Comma Separated Values (.csv)**.

Before importing, check that:

- The columns are in the right order
- There are no empty rows at the bottom
- No stray characters got in

> 💡 **The empty-rows one catches people.** Deleting the contents of a row does
> not delete the row, and Excel will happily export a thousand blank lines that
> all come back as errors.

---

# 4. Import

**1.** Go to **Registration**.

**2.** Click the **three dots** under the **New registration** button.

**3.** Choose **Import attendees**.

**4.** Pick the **ticket type** these people should get.

**5.** Upload the CSV and click **Import**.

---

# 5. Read the result email

When it finishes you get an email with the outcome.

If some rows failed, the email says how many and **attaches a file with the
reason for each one**. That file is the useful part — it tells you exactly
which rows to fix rather than making you guess.

---

# Why rows usually fail

| | |
|---|---|
| **Already registered** | That person is in the event, from an earlier import or their own registration |
| **Duplicate emails** | Two rows with the same address in one file |
| **Not really a CSV** | Saved as `.xlsx` with the extension changed |
| **Missing a required field** | No first name, last name or email |
| **Column name does not match** | See the warning above — the most common of all |

> 💡 **Import ten rows first, then the rest.** Every one of these failures shows
> up on ten rows just as clearly as on a thousand, and fixing ten is quick.

---

# Need help?

Write to us at **soporte@peewah.co** and our team will get back to you.

---