Support

May 25, 2021 at 7:57 am

Hi Laura,

The attendee importer add-on can be used to import attendees onto events, however, Group/MER registrations are basically imported as singles and are no longer within a group.

When you use the importer add-on it lists out all of the fields within the CSV and then allows you to map some EE fields to those CSV fields (custom questions, first name, email etc). It will not allow you to specify the unique values generated by EE such for registrations such Transaction ID, Unique Code (Reg Code) etc, EE will regenerate those when the attendee is imported, so to answer these:

1) Should I clear these fields?
2) Will the system add these fields itself?

You don’t need to clear them from the CSV, just don’t set them as a mapped field and EE will generate a value (if it’s required for the registration).

How many registrants do you have on the old event(s) to import?

3) I also want to make sure that others can still register under the same events through the internet as usual after I have uploaded some of the registrants.

Within Event Espresso, those imported registrations are ‘normal’ registrations so they won’t affect others.

4) Do I need to upload them separately by event, or can I do it all at once with the proper ticket types field left from last years CSV file?

Do you use multiple ticket types within the event and do users register onto multiple ticket types in a single group?

May 25, 2021 at 3:29 pm

It’s about 50 volunteers and Director’s guests.

Hmm, ok.

The reason I asked is in relation to group registrations, if they are important for your setup you’ll need to manually re-add the registrations to keep the groups. Not ideal with 50 registrations really.

This will make a little more sense with an explanation of what group registrations are in EE so more on this shortly.

I have multiple events with multiple ticket types in each event. (Directors wanted to create a separation between certain ticket types, so I had to use the multi event add on.) You can go to this page to see how it’s set up. https://tocift.org/register/

The attendee importer will import all of the registrations in the CSV you pass to it onto the ticket selected during the import process, which means you’ll likely need to break out your CSV’s into each individual ticket type for this to work.

The importer has 6 ‘stages’.

1. Select Event.
2. Select Ticket that event to set on the import rows.
3. Uploads the CSV containing the attendee data.
4. Map the CSV to registration questions on the event and some select ‘core’ fields.
5. Verify the selection.
6. Complete (do the import).

So if you have a CSV from all of the ticket types within your old event, you can’t select which of the rows in the CSV will be assigned to the ticket. You’ll need CSV’s containing only the rows for ticket a, then another for the rows for ticket b and so on.

Another question from my end:
I don’t understand by what you mean by “set them as a mapped field.” Will this procedure be self evident in the Importer add-on?

Apologies, I thought you’d tried out the importer.

Stage 4 above, ‘Map CSV columns’ will be evident when you use the importer, but it looks something like this:

https://monosnap.com/file/acOGPNnR5LrTJ38RawYY6Dt7n58EGX

The fields on the left are what EE has found in the CSV, each field can be ‘mapped’ to a field on the event by selecting it in the dropdown. For example if you have a custom question ‘Whats for dinner?’ in the CSV, you could map that to a ‘mains’ field on the event if that’s what you had.

Note that ALL of the fields in the CSV are shown, but that doesn’t mean you can map them all to a viable field. Transaction ID for example, you can’t map that to anything that would make sense, but the importer doesn’t know what the Transaction ID field is, its just another field so is shown all the same.

I don’t think these registrations have to be in a “group.” I’m not really sure how a “group” is relevant to the output on the CSV. Are you referring to the different Events as a “group,” or do you mean separate “transaction” groups?

When you select multiples of tickets (be more than 1 of a single ticket, multiple ticket types or ticket from multiple events) EE ‘groups’ all of those registrations in a single group. You can see this in the registration list where it shows 1/3, 2/3 and 3/3 across 3 registrations and one of those will have a * highlighting that specific reg is the ‘primary registrant’ of the group.

A quick example, select 3 tickets (just select a qty of 3 for a single ticket) and create a registration. Add attendee information and then stop at the payment options step.

Now, look at the registrations created. You’ll see you have a group registration in the way I explained above.

You can’t re-created those ‘groups’ with the attendee importer.

I would like for the Director’s guests to be in one “event” and the volunteers to be in another, but if I can’t, it’s not a big deal.

You can do this using the importer, but not as a single group, meaning the directory and his guest registrations are no longer ‘linked’ together in a ‘group’. They will all just be individual registrations on the events.