Sync Eventbrite Attendees to QR Code Check-In

Your event already has registrations, but moving the guest list to a different check-in system creates a practical risk: guests arrive with one QR code while your door team expects another. This guide gives you a migration checklist, a record-validation process, guest messaging, and a door rehearsal plan so you can make the switch without confusing registration, payment, and admission.

Separate ticket sales from door admission

Treat this as a change to your admission workflow, not a move of your ticket sales or payment processing. Keep sales, payment questions, and refunds in your existing ticketing workflow; use the check-in system to manage invitations and entry.

VenueWS supports Eventbrite sync for bringing the guest list into its event workflow. Each guest or party receives a signed, revocable QR and a personal web page, but the software does not sell tickets, process ticket payments, or take donations.

Before connecting anything, write down:

• Registration source: Where staff look up an order or registration.
• Admission list: Which event guest list the scanners will use.
• Payment owner: Who handles purchase and refund questions outside the check-in system.
• List owner: Who checks changes and resolves discrepancies.
• Guest instruction: Which QR guests must present at entry.

Avoid running competing admission lists at the same entrance. If a guest needs help, send them to an exception desk rather than having staff admit them through whichever system finds a record first.

Prepare the source list and connect the correct event

Start with the registrations you intend to admit. Review the source event for cancellations, refunds, name changes, group bookings, and staff or vendor records that may need different handling.

Save a dated reference export before the migration. This gives your list owner a snapshot for comparison, not a second live check-in list.

Define what a record represents

A buyer, an attendee, a party, and an invitation are not necessarily the same thing. Establish whether each invitation should admit one person or a named party, then check how group bookings appear after sync.

Pay particular attention to repeated email addresses. The destination system does not issue two invitations to the same email, so several attendees associated with one address deserve explicit review. Do not assume they will become separate invitations or automatically become a correctly sized party.

Connect and inspect before sending

Use the Eventbrite sync for the intended destination event. Check the event identity, date, location, and guest-facing details before distributing new invitations.

Do not assume a particular sync interval, field mapping, or handling of later changes. Confirm those behaviors in your setup and test anything that affects admission. Avoid adding a separate CSV import on top of the sync unless you have a clear reconciliation plan.

Your preparation checklist is:

• Confirm the source and destination events match.
• Save the source-list snapshot.
• Decide how individual and party admission should work.
• Identify repeated emails and group bookings.
• Assign someone to review the imported list before invitations go out.

Reconcile imported records, not just totals

A matching total is useful, but it is not enough. A list can have the expected number of records while containing the wrong people, incorrect party sizes, or missing admission distinctions.

Compare the synced list with your source snapshot. Keep separate counts for invitation records and people expected. A party invitation can represent multiple people, so those totals may legitimately differ.

Check representative cases

Inspect examples covering the situations your event actually has:

• An individual registration with a unique email.
• A group booking or repeated purchaser email.
• A corrected attendee name or email.
• A canceled or refunded registration, if present.
• A late registration added after the initial sync.
• An attendee with a special access category, if applicable.

For each case, check the destination name, email, party size, and intended admission treatment. If the source has ticket categories, do not assume those categories automatically become zones, seating assignments, or VIP settings.

Resolve unexpected records before sending invitations. Do not assume a refund automatically revokes an admission QR; verify the resulting guest record and revoke access when appropriate.

Record discrepancies in a simple working list: affected guest, issue, owner, correction, and recheck status. Keep financial details out of that list unless they are necessary for the person resolving the issue.

Tell guests exactly which QR to present

For the new check-in workflow, guests should present the QR from their new event invitation or its Apple or Google Wallet pass, not the original ticket-order QR.

Make that distinction explicit. “Your QR is attached” is not enough when guests already have a confirmation email containing a code.

Example guest message

Subject: Your entry QR for [event name]

“For entry to [event name], please use the QR available through this new invitation. You can open your personal guest page or add the pass to Apple or Google Wallet; no guest app is required. Please present this entry QR rather than the QR in your original ticket confirmation. Your purchase remains in the original ticketing system, and payment or refund questions should go to [contact].”

Send invitations by email, or by WhatsApp if the venue has enabled it. Check your own test invitation on a phone before sending broadly: the event name, address, instructions, and QR access should all be clear.

If you require a waiver or release, explain that guests must accept it before their QR appears. Have the text reviewed by a lawyer. Staff should understand this requirement so they do not mistake an unfinished acceptance step for a missing registration.

Rehearse the actual door workflow

Run a rehearsal with the phones or tablets, staff roles, and entrance location you intend to use. Pair scanner devices with their one-time codes and confirm that each is working on the correct event.

Use controlled test invitations. Rehearse the decisions staff will make, not just whether the camera can read a code.

Scanner test checklist

• Valid admission: Open the new guest QR on a phone and scan it.
• Duplicate presentation: Present an already-used code and confirm staff understand the refusal.
• Revoked invitation: Revoke a test QR and check its treatment.
• Wrong venue: Test a wrong-venue code and rehearse the explanation.
• Required acceptance: Check what happens when a required waiver remains unsigned, including the on-the-spot signature workflow.
• Re-entry: Test IN/OUT handling if guests may leave and return.
• Party arrival: Rehearse your policy for party members arriving separately.
• Original ticket QR: Have someone present the old code and practice redirecting them to the new invitation.

The scanners work offline and sync later. Still, test disconnected operation and reconnection before relying on it. Do not assume disconnected devices immediately share admission activity; decide how staff will coordinate while connectivity is unavailable.

Rehearse guest lookup on the scanner, too. A person with a dead phone should enter an approved lookup process, not force staff to improvise an exception.

Control late changes and prepare the exception desk

A successful initial sync does not finish the job if registration remains open. Assign the list owner to check new registrations, cancellations, and corrections through the final door briefing.

Confirm how quickly changes appear in your actual setup rather than describing the sync as instant. Before opening doors, reconcile the latest source records and make sure affected guests have the correct entry instructions.

Give the exception desk a short decision checklist:

• Original ticket QR only: Help the guest find the new invitation, then use the approved lookup process if needed.
• Missing admission record: Ask the list owner to verify the source registration before granting entry.
• Payment dispute: Refer it to the payment owner outside the check-in workflow.
• Party-size mismatch: Resolve it against the registration and your admission policy.
• Previously used QR: Investigate rather than automatically overriding the result.

Keep these conversations away from the active scanning lane. That lets door staff handle routine arrivals while the exception desk checks records carefully.

Finish with a clear handoff

Your migration is ready when the list is reconciled, guests know which QR to bring, and staff have practiced both routine entry and exceptions. Keep the registration source available for verification, but make the designated admission list the door team's working record.

You can set up your event in VenueWS, connect the Eventbrite sync, and validate the workflow before distributing entry invitations. After the event, use the attendance CSV export and event summary to review no-shows and identify improvements for the next door briefing.