Membership CRM
One membership CRM for everyone around your organization: donors, newsletter subscribers, and event registrants tracked as contacts in the same database as your members.
- Contacts are created automatically from event registrations, newsletter signups, donations, and forms
- Track each person's full history and move them through custom statuses toward membership
- Convert a contact into a member in one step, with their history transferred
Built for associations, nonprofits, federations, and volunteer organizations, replacing the mailing tool and spreadsheets kept next to the member register.
Contacts at a glance
| Contact record | A person tracked without a login account: a donor, newsletter subscriber, event registrant, or form respondent |
|---|---|
| Automatic creation | From newsletter signups, event registrations, donations, and form submissions; plus manual entry and CSV import |
| History per contact | Donations, event attendance, payments, signed documents, email logs, newsletter subscription, tags, and notes |
| Statuses | Custom, defined by your organization, each with a color and a position in the pipeline; every change timestamped |
| Duplicate prevention | Email and phone act as unique identifiers; every source matches existing members and contacts before creating a record |
| Merge tool | Suggests likely duplicates by matching names and similar emails; merges can be rolled back for 30 days |
| Conversion to member | One action creates a member account from a contact; payments, events, tags, and subscription history transfer |
| Chapter contacts | Each chapter manages its own contacts, while the national level keeps access across all of them |
The built-in CRM for
Audiences bigger than the membership
Organizations with a few dozen member accounts but thousands of people on an email list, currently scattered across a mailing tool and spreadsheets.
Teams tired of re-entering data
When someone finally joins, nobody should retype their record. The contact's history becomes the member's history automatically.
Chapters that collect their own prospects
Each chapter gathers its local subscribers and event registrants, while the national level sees the whole database.
From first touch to member
Every interaction feeds one contacts database, and every contact can become a member without losing history.
Event registration
Non-member registrants become contacts, with attendance recorded
Newsletter signup
Confirmed subscribers arrive from your website widgets
Donation
Every donor gets a contact record with donation history
Form submission
Public forms create a contact for each respondent
One contact record
Each source checks your existing members and contacts by email address first, so the same person never becomes two records.
Your pipeline to membership
Move each contact through statuses your organization defines, and see how many people sit at each stage.
Member
One action creates a member account. Payments, event attendance, tags, and subscription history transfer with the person.
Status names above are examples. Your organization defines its own.
Everything the contacts database does
Where contacts come from
Orgo creates contact records automatically from four sources: newsletter signups, event registrations, donations, and form submissions. Every record carries its source, so you always know how a person entered your database.
A newsletter signup widget embedded on your website creates a contact once the subscriber confirms their email. The new contact is marked as subscribed and can carry a tag from the widget it came through.
A non-member who registers for an event becomes a contact, whether the event is free or ticketed. Attendance is recorded on the contact record, so you can see every event a person attended before they ever joined.
A donation creates a contact record for the donor if one does not already exist, and donation history accumulates on that record. Today's donor is often tomorrow's member.
A form set to accept responses from anyone with an email address creates a contact for each new respondent. Forms restricted to logged-in members do not create contacts.
Admins can add a contact by hand or import contacts in bulk from CSV, alongside members, historical payments, and event attendance. Contact statuses can be assigned directly from a spreadsheet column during import.
One record per person
Every source that creates contacts checks your existing members and contacts by email address first, so the same person never turns into two records.
Email addresses are matched on every entry point: if a donor later subscribes to your newsletter with the same email, both actions land on one contact record. The system refuses a second contact with an email already in use.
For records that slipped in as duplicates, for example through an import of an old mailing list, Orgo suggests likely matches based on similar emails and matching names. Merging lets an admin choose which data survives, and works between two contacts or between a contact and a member.
Every merge is logged with a snapshot of both records, and an admin can roll a merge back for up to 30 days.
The contact record
A contact record holds a person's full history with your organization in one profile: donations, event attendance, payments, signed documents, email logs, and newsletter subscription.
For each contact you can see every payment, every event attended, every document signed, and every email sent, plus whether they are subscribed to your newsletter. No cross-referencing between a mailing tool and a spreadsheet.
Contacts can carry tags for segmentation, dated notes attributed to the admin who wrote them, and the same custom fields your organization defines for member profiles.
Each contact carries its own subscription state and a personal unsubscribe link. Unsubscribes are recorded on the contact record and logged.
Custom statuses for the path to membership
Contact statuses in Orgo are custom: your organization defines its own set, each with a name, a color, and a position in the pipeline.
Statuses are defined per organization rather than chosen from a fixed list, so they can mark how close a contact is to joining, for example a lead you want to become a member. Every status change is timestamped.
Admins move a contact along the pipeline until they become a member, and status counts are visible at a glance, so you can see how many people sit at each stage.
Segmentation, email, and chapters
Contacts can be filtered by status, tag, source, newsletter subscription, chapter, and custom fields, and email can be sent to exactly the segment you select.
Newsletters can go to all members, all contacts, only subscribed contacts, a specific group or chapter, event attendees, or a static or dynamic list your organization creates, such as donors.
In a multi-chapter organization, each chapter manages its own contacts while the national level keeps access across all of them.
Admins with sufficient permissions can export contacts to CSV at any time, and every export is logged, so you can see who exported what and when.
From contact to member
A contact becomes a member through a single action that creates a user account and transfers the contact's history to it.
An admin creates a member account directly from a contact record. Profile details carry over, and the new member receives an email to confirm the account and set up access.
Donation and payment history, event attendance, tags, custom fields, and newsletter subscription move to the member account, so years of engagement are not lost at the moment someone joins.
If a person registers as a member using an email that already exists as a contact, their contact data is transferred to the new account. The merge tool also lets admins combine a contact with an existing member.
Contacts cannot log in to the member platform: they have no password and no member permissions. The one exception is a limited event view, where a contact can authenticate to see only the events they registered for.
Membership CRM FAQ
A member is a person with a login account and membership rights, while a contact is a person tracked without an account, such as a donor, a newsletter subscriber, or an event attendee. Keeping both in one database preserves a person's engagement history if they later join as a member. In Orgo, contacts and members share one database, and a contact can be converted to a member with their history intact.
No. People who donate, subscribe, or attend events can be tracked as contact records without accounts, which keeps the barrier to engagement low. In Orgo, contacts have no password and cannot log in to the member platform, but their donations, subscriptions, and event attendance are still recorded on their profile.
Most organizations track them in a spreadsheet or a separate email tool, which splits a person's history across systems and often loses it entirely. A membership database with a contacts tier records attendance automatically: in Orgo, a non-member who registers for an event becomes a contact, and every later event they attend accumulates on the same record.
Deduplication is usually done by matching email addresses, since an email identifies one person across systems. Orgo's import matches each row against existing members and contacts by email and skips duplicates, and a merge tool suggests remaining likely duplicates based on similar emails and matching names, with a 30-day rollback on every merge.
Yes. A non-member who registers for a free or ticketed event becomes a contact, with the registration recorded on their record. If their email already belongs to an existing member or contact, the registration attaches to that record instead of creating a new one.
Two ways. An admin can create a member account directly from the contact record, which carries the data over and emails the person to confirm the account. Or the person registers as a member themselves, and if their email matches an existing contact, the contact's data is transferred to the new account.
Yes. Event attendance, donation and payment history, tags, custom fields, and newsletter subscription all transfer to the new member account, so the record continues rather than starting over.
Each Orgo plan includes an allowance for contacts alongside the allowance for members, and plans differ in how many contacts they include. See the pricing page for current allowances.
Yes. Organizations that use HubSpot can enable an integration that pushes contact creation and updates to HubSpot automatically. Contact changes can also trigger webhooks for custom integrations.
Yes. Orgo's CSV import covers contacts as well as members, historical payments, and event attendance, and contact statuses can be assigned from a spreadsheet column during import. Re-uploading the same file skips rows that already exist, matched by email.
Related features
Membership management software
Where a contact lands once converted: profiles, fees, and the member directory.
Event management software
The events whose non-member registrants feed the contacts database.
Newsletter
The signup widgets and audience segments that run on contacts.
Fundraising software
The donation pages that create donor contact records automatically.
Contacts documentation
Technical depth on contact records, sources, and conversion.
See the contacts database live
- 1 30 minutes, no obligation. Discovery first: we ask about your structure before showing anything.
- 2 An honest fit assessment. If we're not the right fit, we'll tell you in the first 10 minutes.
- 3 A tailored quote within one business day, based on what we learn together.