> For the complete documentation index, see [llms.txt](https://docs.eventnook.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventnook.com/online-registration-manage/bulk-upload+.md).

# Bulk Upload+

Bulk Registration Upload Guide: Importing Your Guest List

EventNook offers a powerful **Bulk Upload** feature that allows organizers to import a guest list in bulk using a CSV file. This process simplifies adding large numbers of attendees quickly and efficiently. Here’s a step-by-step guide to help you navigate through the bulk upload process:

You can watch a quick video here and you can also follow the steps written in the [#steps-to-upload-your-guest-list](#steps-to-upload-your-guest-list "mention")

{% embed url="<https://www.youtube.com/watch?v=9TvYccI7SDE>" %}

{% hint style="success" %}
First Login to <https://onsiteapp.eventnook.com> if you haven't logged in to the Onsite Management.
{% endhint %}

### Steps to Upload Your Guest List

**Go to Manage > Bulk Upload** in the EventNook Onsite App for your event.

1. **Step 1: Select and Upload a CSV File**
   * Choose the prepared CSV file containing your guest list and submit it for upload.
2. **Step 2: Field Mapping**

   * Match the columns in your CSV file to the corresponding fields in your event’s registration form.
   * Ensure that each column is correctly mapped to ensure data is transferred to the appropriate fields.
   * Optionally, import external **QR Code IDs** (unique identifiers assigned to attendees) if your data comes from a third-party platform (e.g., CVent, Eventbrite, or Splashthat). This ensures the **EventNook Kiosk App** can recognize and scan their QR codes for event check-ins.

   If the data is clean and passes validation, proceed to the next step.
3. **Step 3: Preview and Confirm**
   * Review the uploaded data to ensure everything is accurate. Once confirmed, proceed with the upload.
4. **Step 4: Send Confirmation Emails (Optional)**
   * Optionally, send personalized confirmation emails to attendees. To proceed, click **Send Now** and all attendees will receive the email in a few minutes.
   * You can customize the email content, including adding a QR code image, before sending.

#### **Important Notes:**

{% hint style="info" %}

* **Guest List Limit**: Each bulk upload supports up to **300 attendees**. You can split the data into batches and upload them separately for larger lists.
* **Duplicate Entries**: The system does not automatically check for duplicate entries. If you upload the same guest list more than once, it will result in duplicate records. However, you can delete the duplicate batch if necessary.
* **Required Fields**: Only **Name** and **Email** are compulsory fields. You can either upload **First Name/Last Name** as a pair or a **Full Name**. If the registration form uses Full Name only, that and the Email field will be required. Other fields, even if set as compulsory in the registration form, are optional for bulk upload.
  {% endhint %}

### Processing Time

The entire process usually takes between **30 seconds to a couple of minutes**, depending on the number of records being uploaded.

This guide helps you streamline the registration process by quickly uploading guest lists, ensuring smooth check-in and communication for your event.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eventnook.com/online-registration-manage/bulk-upload+.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.