Almost every list arrives as an Excel file, and almost none of them is laid out the way we would like. The Eventleash import does not demand a particular format: you upload the file you have and tell it which column is what.
Preparing the file
Excel and CSV both work. The only things that really matter:
- A header row with the column names. It is there so you can recognise them in the next step.
- One person per row. Two names in the same cell become one contact with a strange name.
- An email column, or at least a phone column.
You do not need to rename or reorder columns, and you can leave the ones you do not need: they are ignored at the mapping step.
Importing
- Under Contacts, open the import and upload the file.
- Map the columns: for each one pick the Eventleash field it corresponds to, or choose to ignore it.
- Check the preview. It shows how the first rows will be read, and it is the moment you notice you swapped first name and surname.
- Decide how to handle the privacy consents, in the box next to the import button (see The consents of imported contacts), and confirm.
The import flags rows with problems — a malformed email, an empty required field — and lets you decide whether to go ahead with the rest.
Mapping the columns
This is the step that decides everything. A few practical notes:
- Country goes in spelled out or as its standard code; a value we do not recognise is left empty rather than blocking the import.
- Language accepts
ITorEN. With no such column, contacts get the default language. - Groups can live in one column, separated by semicolons.
- Socials want the username only, not the full profile address.
- Yes/no columns (Receives emails and, for guests, Confirmed and Checked-in) accept
1,si,yesortruefor yes and0,noorfalsefor no. For Confirmed, a dash-puts the guest back to "no answer". An empty cell, or any other value, leaves things as they are: you can re-import a partial file without wiping anything. A check-in already made is never undone by an import, not even with0. Exports write these columns as1,0and-, so they come back in without losing anything. - The account custom fields are among the fields you can map columns to, under their own name. Values are read by type: dates also as
31/12/2026, list choices by their label in any active language, regardless of case, yes/no like the other yes/no columns. A value that does not fit (a choice that does not exist, an unreadable number) and an empty cell leave the stored value as it is. In exports each field has a column headed with its name. - Date of birth is the field that causes the most trouble: American and European formats resemble each other just enough to be got wrong. If you do not need it, ignore the column.
What happens to duplicates
Nothing dramatic, and this is the most important thing to know: the email identifies the contact. If the address is already in the address book, the existing contact is updated with the new data rather than duplicated.
The comparison ignores case and spaces, so Mario.Rossi@Company.com and mario.rossi@company.com are the same person.
What follows in practice:
- You can re-upload the same updated list as often as you like.
- An import is also a quick way to bulk update one field across many contacts.
- Mind the flip side: an empty cell in the file does not clear the value that was there. To empty a field, use bulk editing.
If two rows of the same file share an email, the last one wins.
The consents of imported contacts
In the last step, before importing, you have to tick the declaration: "As the data controller, I declare that the people concerned received my privacy notice and gave the consents indicated freely, specifically and in an informed way, and that I can prove it on request." Without it the import does not start. Only tick it if it is true: the proof is up to you, and Eventleash records that those consents came from an import.
With the declaration:
| Consent | What happens |
|---|---|
| Privacy notice | Every imported contact counts as having received it, on the date of the import. If you mapped the policy column its value applies; an empty cell counts as received |
| Invitations and measurement | They follow the subscribed and tracking columns of the file, with their dates if you mapped them (see Exporting). Without those columns new contacts come in without invitations or measurement, and those already in your address book stay as they are. Measurement is only possible together with the invitations |
An import never overwrites what a person chose by themselves: a form they filled in, the preferences page, an unsubscribe link, a spam complaint. If the file says otherwise, that consent stays as it is and the import log points it out. A consent written by an earlier import or entered by hand by your team, instead, is updated with the file's value.
Importing guests straight onto an event
From an event's page you can upload a file directly onto that event. That is the right route when the list arrives from the client the day before and there is no point going through the address book.
It works like the contacts import, with one difference worth knowing: if you map no email or phone column, the guests are created for that event only and do not enter the address book. The application says so plainly before you proceed.
When the email is there, every row also becomes a contact: that is nearly always what you want, because it is how the address book grows by itself, event after event.
Exporting
From the export button, on the contacts list or on an event's guest list. You pick the format: Excel, CSV or PDF. Excel is the one to use if the file is coming back into Eventleash; PDF is for the list you print and take to the door.
The export respects your active filters: filter by group and you export that group. It is the simplest way to prepare a list for a supplier, for reception or for the client.
Every row also carries the creation date: for contacts when they entered the address book, for guests when they were added to the event. The oldest contacts, created before the date was recorded, leave it empty.
Social accounts come out as clickable links, and re-importing that same file reads the usernames back correctly: the round trip loses nothing.
Contacts and guests also come out with the contact's consents, three columns each: policy (privacy notice), subscribed (invitations) and tracking (individual measurement) with their status, and next to each …AcceptedAt and …DeniedAt with the date it was last accepted and last refused. They re-import as they come out: the status takes the same values as the other yes/no columns, the dates the 2026-03-31 18:00:00 format (or just the date, or day/month/year as in 31/03/2026 18:00, or an Excel date cell), a dash - clears a date, and a value that is not a date, or a future date, is ignored without discarding the row. If you change a status without giving the date, the import time is used; on an existing contact empty cells change nothing. For new contacts, and for the declaration to tick, see The consents of imported contacts. Individual measurement only goes with the invitations: a row with tracking yes and subscribed no is saved with the measurement set to no. An import writes the consents of new contacts and of those who made no choice, but never changes a consent the person chose: given or refused on a landing or the RSVP page, changed on the preferences page or with the unsubscribe link, or with the email marked as spam. This holds in both directions and for the dates too, even when re-importing an older export: the contact is imported, those consents stay as the person left them and the import log lists them. Only the person can change them.
When something goes wrong
| Symptom | Near-certain cause |
|---|---|
| "No email column mapped" | You skipped mapping the email column — go back a step |
| Lots of rows rejected for an invalid email | Wrong CSV separator: the file opens as a single column. Re-export from Excel choosing CSV UTF-8 |
| The imported contacts already existed | Duplicate handling is working: they were updated, not ignored |
| Accented letters come out wrong | The CSV is not UTF-8. Re-export it from Excel as CSV UTF-8, or upload the .xlsx directly |
| The import button does not go ahead and asks you to confirm the declaration | You are importing consents: tick the declaration in the Privacy consents box. See The consents of imported contacts |
| The contacts you just imported get no campaigns | You imported them without consents, so without invitations. See The consents of imported contacts |
| The import stops halfway | File too large: split it into blocks of a few thousand rows |
If a list simply refuses to go in, send it to us: [info@eventleash.com](mailto:info@eventleash.com).
