Tabletop convention migration
Practical comparisonKeep the tabletop depth. Modernize the operating model.
If your convention has outgrown disconnected operations, Apiary brings registration, scheduling, live command, commerce, and community memory into one tabletop-native system.
Badge fee comparison
Compare the published checkout math.
Apiary's current badge fee is 3.5% plus $1.00 per paid badge, with card processing included. Tabletop.Events currently publishes 6% plus $0.99 per badge, also with processing included.
Badge price
$30.00
- Apiary fee
- $2.05
- Tabletop.Events fee
- $2.79
- Difference
- $0.74 less
Badge price
$65.00
- Apiary fee
- $3.28
- Tabletop.Events fee
- $4.89
- Difference
- $1.61 less
Badge price
$110.00
- Apiary fee
- $4.85
- Tabletop.Events fee
- $7.59
- Difference
- $2.74 less
| Badge price | Apiary fee | Tabletop.Events fee | Difference |
|---|---|---|---|
| $30.00 | $2.05 | $2.79 | $0.74 less |
| $65.00 | $3.28 | $4.89 | $1.61 less |
| $110.00 | $4.85 | $7.59 | $2.74 less |
Illustrative fee-per-badge calculation before taxes, discounts, refunds, or foreign-card surcharges. Tabletop.Events pricing checked July 16, 2026. Verify its current terms on the official pricing page.
Why teams evaluate Apiary
The decision is about the operating model, not just the checkout fee.
Apiary is designed around the complete organizer loop and the organizational memory a recurring convention builds over time.
Tabletop-native public experience
Games, GMs, seats, tables, waitlists, tournaments, a lending library, personal schedules, and Find Your Table share one attendee journey.
Director-level live operations
Volunteer coverage, issues, incidents, decisions, risks, handoffs, fallbacks, and an operations journal stay visible during the event.
Commercial and partner operations
Badges, merch, workshops, vendors, sponsors, charity, settlements, and relationship workflows connect to the same convention record.
Memory across event years
Persistent player profiles, partner history, achievements, journeys, templates, and cloning help the next convention start from what the team learned.
A controlled move
Rehearse the convention before changing the public path.
Apiary includes schedule-import previews and attendee-migration dry-run foundations. A migration should still be treated as an event project with explicit review gates.
- Step 1
Inventory
Export and review attendees, badges, events, rooms, tables, policies, and integrations.
- Step 2
Map
Choose Apiary modules and terminology, then map source fields without changing live data.
- Step 3
Rehearse
Exercise registration, scheduling, check-in, refunds, communications, and closeout in a mock convention.
- Step 4
Cut over
Publish only after organizer signoff, a rollback plan, and a clearly communicated attendee path.
Explore the fit before planning a cutover.
Start an organizer workspace, model your convention with the tabletop preset, and validate the workflows that matter to your directors and attendees.