Switch from Luma to Who's In
Luma takes 5% on paid tickets and surfaces your event in their consumer-facing discovery feed. Move to Who's In with 2.7% on paid tickets and your own branded organiser presence. Free events stay free; paid events keep more margin.
Every Events feature included free forever. No credit card required.
Why organizers switch from Luma
5% Luma fee on paid tickets
Luma's pricing is 5% on paid ticket sales (plus Stripe processing). For a $50 ticket, Luma takes $2.50 + $1.75 Stripe = $4.25 total. Multiplied across hundreds of tickets, the platform fee adds up.
Who's In Events is free for free events. For paid events, the platform fee is 2.7% (plus Stripe processing). On the same $50 ticket: $1.35 platform + $1.75 Stripe = $3.10. Saves ~25% on each paid ticket vs Luma.
Luma owns the discovery feed — not your brand
Luma surfaces events in their consumer-facing discovery feed. Members find your event via Luma's brand, not yours. The brand experience is Luma's; you're a tile in their feed.
Who's In gives you a branded organiser page. Members find your events via your URL, your brand, your colours. Luma-style discovery is fine for top-of-funnel; Who's In is your home.
Limited recurring + multi-event tools
Luma's recurring event tools are basic. Multi-event series (a 6-week workshop, a quarterly speaker series) require manual setup of each event with no template inheritance.
Who's In supports recurring events natively, starts new events from ready-made templates, and offers Who's In Conference (a paid plan) for multi-track agendas if you outgrow simple events.
Step 1: Export from Luma
Get your data out
Export attendee list
In Luma admin, navigate to Events > [Your Event] > Guests > Export. Captures attendee name, email, ticket type, registration timestamp.
Document upcoming events
Events > Upcoming. Take screenshots or export of upcoming events with date/time/location/ticket pricing.
Document recurring patterns
If you run a recurring series, document the pattern (weekly, monthly, etc.) for replication in Who's In.
Export ticketing + revenue data
Each event > Sales > Export. CSV with ticket sold, attendee, payment, fee breakdown.
Cancel Luma listing on cutover
After migrating, decide whether to leave events on Luma for discovery (top-of-funnel) or remove entirely. Most organisers keep Luma for discovery, redirect to Who's In for the actual ticket purchase.
Step 2: Set up on Who's In
Get running in minutes
Create your Who's In organiser presence
Sign up at whos-in.app. Add organisation name and branding.
Recreate upcoming events
For each event, set name, date, time, location (or virtual link), capacity, ticket pricing. Use the Luma export as your reference.
Import attendee list per event
For each free event, import the Luma CSV from the attendee list (name and email), then choose whether to email everyone the event link. Paid events take new bookings through checkout.
Configure ticketing + Stripe Connect
Set a ticket price and connect Stripe (about 10 minutes, one time). Ticket money, minus the 2.7%, is transferred to your own Stripe account at the moment of sale.
Set up recurring + multi-event series
Turn on repeat for weekly or monthly series and future dates are created for you. For a one-off run of events, start each one from an event template.
Notify attendees of new home
Send email blast to your Luma audience with the new organiser URL. Include the founder's note + the value-add (better recurring tools, lower fees, branded experience).
Feature Mapping: Luma to Who's In
| Luma Feature | Who's In Equivalent |
|---|---|
| 5% on paid tickets | 2.7% on paid tickets |
| Luma-branded organiser page | Branded organiser page |
| Consumer discovery feed | Your brand + your audience |
| Free for free events | Free for free events |
| Basic recurring events | Recurring events + event templates |
| Mobile app | Branded PWA + Wallet passes |
| Email reminders | Email reminders + a morning-of WhatsApp reminder (signed-in guests who turn it on) |
| AI-suggested attendees | Not on Events (Conference has rule-based matchmaking) |
| Basic check-in | QR check-in + capacity dashboard |
| Limited member CRM | Attendee list + CSV export (member CRM is on Clubs and Studio) |
| Limited integrations | Webhooks (via Zapier or Make) + REST API with OAuth |
| No conference / studio mode | Conference + Studio + Clubs available |
Total migration time: ~2 hours
Most organizers complete their migration in a single sitting. No technical skills required.
Migration FAQ
Ready to switch from Luma?
Create your free account and start migrating in under ~2 hours. All Events features included.
No credit card required. Free forever for community events.