A practical approach to how to migrate from event espresso to nexdirectory.
Separate event content, registrations and financial records before moving to NexDirectory and Pro ticketing.
Export event and registration data separately
Treat event pages, attendee details, ticket types, payments and refunds as related but distinct migration records.
ExploreProtect historical transactions
Retain the source system or a secure export for records that should not be recreated as new NexDirectory orders.
ExploreUse Pro for future native ticketing
Single-price paid checkout, verified guests, promo codes, transaction records and browser QR or manual check-in are Pro capabilities. Attendee CSV export remains Free.
Put this guidance into practice.
Define the cutover boundary
Choose which future events move and which historical registrations remain in the source system for reference.
Map a complete test event
Check the single ticket price, capacity, attendee fields, dates, tax and provider-side refund context without creating live charges.
Reconcile before launch
Compare event, attendee and order totals, test checkout and check-in, then document access to historical records.
Common questions.
Can Free replace paid registration?
Free includes RSVPs and waitlists, but native paid ticketing and QR check-in require Pro.
Should payment records be imported?
Preserve them according to legal and accounting requirements, but do not create duplicate charges or misleading new orders.
Can old QR codes be reused?
Do not assume so. Test the Pro check-in format and issue clear new attendee instructions where required.