The situation is familiar to almost every event organizer. The guest list is ready, the ticketing system is open, the import button is in sight, and still something goes wrong. All data lands in one column. Names with accents turn into strange characters. First names and last names shift, which immediately affects badges, emails and access control.
At that moment, a CSV file feels like a small technical detail. In practice, it is often the difference between calm preparation and last-minute chaos at the door. If you understand what a CSV file is, you also understand why attendee lists move smoothly from Excel to a CRM, email tool or ticketing system, or why they fail completely.
Why every event organizer should understand CSV
CSV is simple enough to work almost everywhere, but also simple enough to be saved or read incorrectly. That matters for event teams because attendee data constantly moves between tools: spreadsheets for early registration, email platforms for reminders, CRM systems for relationship management and ticketing software for check-in.
Forum Standaardisatie describes CSV as an open standard for data exchange in the Netherlands, based on RFC 4180. That explains why the same plain file format is still expected by many different systems.
Practical rule: importing attendee lists without understanding CSV is not troubleshooting. It is hoping the format happens to match.
A CSV file is not outdated administrative leftovers. It is the quiet backbone under many event workflows. When you understand the format, you prevent issues before they show up in badge printing, email segmentation or access scanning.
The anatomy of a CSV file
A CSV file is best understood as a table without formatting. Each line is a row. Each part of that row sits in a fixed field. There are no colors, filters, formulas or tabs. There is only plain text with a predictable structure.
For an attendee list, one line is one attendee. The individual pieces of information, such as first name, last name and email address, are separated by a character. That character is the delimiter.
In Excel, the list might look like a normal table:
| First name | Last name | |
|---|---|---|
| Sara | Jansen | sara@company.com |
| Omar | El Idrissi | omar@company.com |
In a text editor, the same data looks more like this:
First name;Last name;Email
Sara;Jansen;sara@company.com
Omar;El Idrissi;omar@company.com
That is the core answer to what is a CSV file. It is not a smart workbook, not a database and not a styled spreadsheet. It is structured text.
Why comma does not always mean comma
CSV stands for Comma-Separated Values, but in many European spreadsheet settings a semicolon is used instead of a comma. That is a common reason imports fail, and it is also covered in Lamper Design's explanation of CSV files.
- Comma delimiters are common in English-language and international systems.
- Semicolon delimiters are common in Dutch and European Excel settings.
- Tabs and other delimiters exist too, but make imports easier to misread.
So a CSV is less a file with commas and more a flat table where fields are separated consistently.
Creating and opening a CSV file
Most organizers do not create CSV files by hand. They export them from Excel or Google Sheets. That is fine, as long as someone checks what the file actually contains afterwards.
In Microsoft Excel, this usually happens through Save as and then a CSV format. In Google Sheets, it happens through Download and then the CSV file type.
The export button is rarely the real problem. The source sheet is. Empty columns, duplicate header rows, hidden spaces and extra notes above the table all travel into the exported file.
Many people double-click a CSV and only inspect it in Excel. That is understandable, but not always reliable. Excel immediately tries to display the data neatly and may interpret dates, numbers or characters on its own.
A simple text editor is often better for checking the raw structure:
- are fields separated with commas or semicolons
- does the first line contain clear column names
- are there unexpected quotes, empty lines or comments
For teams that collect extra attendee data, such as company, dietary preference or job title, this article about custom fields in event software is useful context for planning the mapping before import.
Common CSV problems and fixes
Most CSV errors feel chaotic, but they follow recognizable patterns. The symptom on screen looks large, while the cause is usually small. For attendee lists, three issues explain most failures.
Microsoft's CSV import and export guidance links regional settings to delimiter behavior and explains how text files can be imported or exported cleanly.
Everything appears in one column
If the import preview does not show a clean table and the full line appears in one field, the file probably uses a different delimiter than the system expects. Open the file in a text editor and check the separator. Then export again with the right setting, or choose the right delimiter in the import screen if that option exists.
Lotte;Peeters;lotte@organisation.be
If the import tool expects commas, that line will not be split into three fields.
Accents and special characters break
When names with accents turn into strange characters, the character encoding usually does not match. Save the file as UTF-8 and check it again in a text editor. This matters for international events because names, addresses and company names often contain characters outside basic ASCII.
Quotation marks look like pollution
CSV uses quotation marks to keep text with delimiters inside one field. That is not an error. It is protection. A company name such as "Jansen, De Vries and Partners" remains one field because of the quotes.
Do not remove all quotation marks manually. First check whether they are doing useful work.
| Symptom | Likely cause | First check |
|---|---|---|
| Everything in one column | Wrong delimiter | Open in a text editor |
| Broken characters in names | Wrong encoding | Save as UTF-8 |
| Shifting columns | Text contains delimiter | Check quotes |
CSV import checklist for event data
Event data is not only about the file format. An import only works well when the content is logical, clean and mapped to the right fields. SumUp describes CSV as a broadly supported exchange format for spreadsheets, databases, CRM systems and analytics software. That broad compatibility is why CSV remains common in event operations.
Check the content first:
- Use clear column names such as First name, Last name, Email and Ticket type.
- Find duplicate attendees, especially after merging sources.
- Remove empty rows that can create ghost records or errors.
- Clean invisible spaces, especially at the start or end of email addresses.
An import tool does not read what an organizer means. It reads columns and tries to connect them to fields. That makes field mapping essential.
| CSV column | Purpose | Target field |
|---|---|---|
| First name | Personal greeting | first_name |
| Last name | Badge and CRM | last_name |
| Confirmations and campaigns | ||
| Ticket type | Access or segmentation | ticket_type |
When a platform uses extra relationship data or audience segments, it helps to define the structure first in an event CRM and audience management environment.
When a CSV file is not enough
CSV is strong for transfer. That is where the format shines. But when an organization starts treating a CSV as the permanent home for operational data, its limits become clear.
Vendino's overview of CSV limitations explains that CSV does not store formatting, formulas or complex relationships. That makes it unsuitable as the full source of truth for rich data such as ticket types, guest lists and communication history.
An organizer can export an attendee list as CSV without issue. A complete event process, however, often contains more than a flat table:
- one contact with multiple orders
- several ticket types inside the same booking
- communication history per attendee
- tags, preferences and custom fields that relate to each other
Those relationships belong in a real database, not in a text file. A CSV can carry the information temporarily, but it cannot manage it logically. For organizers moving from older ticketing systems, a guide to migrating from Eventix is often more useful than another spreadsheet workaround.
CSV remains useful. It just should not become the final system.
Teams that work with attendee lists every day do not need theory. They need a process that stays reliable. Tiqqo helps organizers manage ticketing, CRM and marketing in one environment, so data has to move through separate exports less often. See how that works on the Tiqqo website.