Map the work, not just the columns
List every place a signup changes after submission. The goal is to see which records must stay together, not to rebuild your workbook cell for cell.
- Identify the member roster, event form, guest list, benefit balances, and payment-status sheet.
- Write down who updates each one when a member adds a guest or cancels.
- Mark which information belongs in your accounting or dues system and should stay there.
Prepare a small, clean roster
MemberRelay can import member records from CSV. That is a roster import, not a promise to import historical event responses or reconstruct old benefit ledgers automatically.
- Choose a current roster export and check names and email addresses before importing.
- Start with the members needed for the pilot event; invite app users when the organization is ready.
- Set up current benefits and allocations deliberately rather than assuming spreadsheet formulas are accurate.
Pilot one real event
Set up its activities, guest rules, prices, capacity, and reservation window. Preview the member experience before publishing. Ask a small group to confirm that the choices and resulting balances make sense.
- Compare the new headcount and amount-due view with the old sheet during the pilot.
- Test a change and a cancellation, not only a first-time signup.
- Decide who will answer member questions and who may correct reservations or benefits.
Retire duplicate entry carefully
Once the team trusts the pilot, tell members which signup route is current and stop accepting new responses in the old form for that event. Keep any records you still need for your organization's retention and accounting practices.
- Export the event's current report when you need an external record.
- Continue using your existing accounting system for financial books and dues.
- Repeat with the next event only after the first one is comfortable for members and staff.
Ready for the app steps?
See the related Help guide for the exact MemberRelay workflow.
See how the roster import works