--- title: "Importing Event Attendees" slug: "importing-event-attendees" updated: 2025-12-03T11:38:05Z published: 2025-12-03T11:38:05Z --- > ## Documentation Index > Fetch the complete documentation index at: https://help.nexudus.com/llms.txt > Use this file to discover all available pages before exploring further. # Importing Event Attendees You can easily import Event attendees to Nexudus in a few steps on the Admin Panel. **Click on each of the steps below for step-by-step instructions.** ## Step 1. Downloading the template The first step of the process is to download the import template you'll use to add customers. You can get this template from [**Settings > Imports**](https://dashboard.nexudus.com/settings/importers/coworker) on the Admin Panel. 1. Log in to [dashboard.nexudus.com](https://dashboard.nexudus.com/) if you aren't already. 2. Click [**Settings > Imports**](https://dashboard.nexudus.com/settings/importers/coworker). 3. Click on the **Event attendees** tab. 4. Click on **Download template**. The download should only take a few seconds. You'll find the template file in the *Downloads* folder of your device. ## Step 2. Editing the template The second step is to add your data to the import template. The example below illustrates how to do this in Excel, but you can use any spreadsheet tool that can open and edit CSV files. 1. Open the import template file you've downloaded in Step 1. *You should see the column headers in row 1 and a few rows of dummy data underneath.* ![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%28219%29.png) 1. Add your space's data in each column following the dummy data's template. Need to include multiple products on the same invoice? Add each product as its own row, making sure they all have identical details in the following columns: - Location - InvoiceNumber - Email - Date - DueDate If the invoice has already been paid, make sure all the relevant rows also have identical details in the following columns: - PaidOnDate - PaymentReference - PaymentDescription 1. Remove the dummy data rows from the import template, making sure you don't remove any of the column headers. 2. Save your changes. Always save your file as a **CSV UTF-8** file. ![Imports_SaveFormat](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/Imports_SaveFormat.png) You're now ready to format your data before the reupload. ## Step 3. Formatting your template The third step is to ensure your template is properly formatted for a successful import in Nexudus. Make sure you over the following formatting elements before uploading your import template. ### Date Columns All columns that include a date should be set to the **yyyy-mm-dd hh:mm** format. This format isn't available by default in most spreadsheet tools, but you can add this custom format to your date columns in a few clicks. Here's how to do it in Excel: 1. Select the entire date column in your import template. 2. Right click the column. 3. Select **Format cells**. 4. Click **Custom**. 5. Add **yyyy-mm-dd hh:mm** in the *Type* field. 6. Click **OK**. The dates in your column should now appear in the right format, for example **2021-10-11 16:00**. Repeat the process for every column that includes a date in your import template. ### YES or NO Columns All columns that include YES or NO should always be uppercase. ### Address Columns If your file includes an Address columns, make sure the addresses are between double brackets when they contain one or multiple commas. *For example if your address is 12 Street, XYZ Building, City, you should make sure it is added as "12 Street, XYZ Building, City" in your template.* ### Columns Including Existing Nexudus Items All columns that include the name of items that already exist in your Nexudus account must always be an exact match in your import file. The spelling is case-sensitive and includes spacing. *For example, if a product's name in Nexudus is **Notepad**, the product name in your import file must be **Notepad**. Using alternative spellings such as **Note Pad** or **notepad** will result in an import failure.* Don't reopen your import file once you've saved all your changes and closed the file. Doing so will automatically reset the custom date format you've defined and you'll need to reformat the date columns a second time. ## Step 4. Uploading the edited template The last step of the data import process is simply to upload your edited import template file back in Nexudus. 1. Log in to [dashboard.nexudus.com](https://dashboard.nexudus.com/) if you aren't already. 2. Click [**Settings > Imports**](https://dashboard.nexudus.com/settings/importers/coworker). 3. Click the tab that corresponds to your edited import template file. 4. Click **Select file**. 5. Select your edited import template file. 6. Click **Open**. *The larger your file is, the longer it will take to upload.* 1. Click **Load preview**. 2. Click **Import data**. You've successfully imported your data into Nexudus. Couldn't complete the import? Check out our article on [Troubleshooting Import Errors](/v3/docs/troubleshooting-import-errors) or get in touch with us at [support@nexudus.com](http://mailto:support@nexudus.com). --- ## Import columns explained | Column | Details | Format / Data Type | Required or Optional | | --- | --- | --- | --- | | **CoworkerId** | Internal ID of the coworker associated with the purchase | - | Internal field that isn't required | | **CoworkerEmail** | Email of the customer purchasing the tickets. | Email of an existing customer in your Nexudus account. | **Required****** | | **CoworkerName** | Full name of the customer purchasing the event tickets. | Name of an existing customer in your Nexudus account. | **Required****** | | **AttendeeEmail** | Email of the person attending the event. | It should match the email of the customer if they purchased the ticket for themselves. It can be the email of another customer or someone external wishing to attend the event if the ticket was purchased for them. | **Required****** | | **AttendeeName** | Full name of the person attending the event. | It should match the name of the customer if they purchased the ticket for themselves. It can be the name of another customer or someone external wishing to attend the event if the ticket was purchased for them. | **Required****** | | **EventName** | Name of the event | Exact match (case and spelling) with an existing event in your Nexudus account. | **Required****** | | **EventProductName** | Name of the event ticket purchased. This applies to paid and free tickets. | Exact match (case and spelling) with an existing ticket for the event in your Nexudus account. | **Required****** | | **EventId** | Unique identifier for the event | - | Internal field that isn't required | | **PurchaseOrder** | Purchase order or transaction identifier. | Only relevant if you use purchase order numbers when you invoice customers. | **Optional** | | **DueDate** | Date when payment for the event ticket is due, in cases where your event is a paid one. | yyyy-mm-dd hh:mm | **Optional** |