Case Study · Associations
Their membership system had no way in. We built one.
The National Hydropower Association keeps its member records in a system that accepts no data from other software. Staff were typing event registrations into it by hand. We built one connector that links it to their event registration and newsletter tools, and does that entry for them.
At a glance
- Client
- National Hydropower Association
- Industry
- Trade association
- Engagement
- Custom integration, since 2022
- Systems
- Membership system, Cadmium, Rasa
3 systems
kept in step by one connector
The outcome
3
systems connected, one of which has no way to accept data from outside
4
separate syncs running, added one at a time since 2022
4x a day
new event registrations are picked up and entered
The problem
Every list was moved by hand.
NHA runs on three systems from three vendors: a membership system that holds every member and contact, Cadmium for event registration, and Rasa for its newsletter. The membership system is the master record, and it has no bulk upload and no way for other software to send it data.
So people did the moving. Each Monday someone downloaded about 20 reports, merged them into one spreadsheet and uploaded it to the newsletter tool. When people registered for an event, staff downloaded the list and typed each person into the membership system. The vendor's own upload service was the only alternative, and it took three to seven business days.
It almost takes more time to prepare the list to upload than it does to just manually enter them.
What we built
One connector that works the screens like a person would.
Cadmium and Rasa both have an API, which is a supported way for software to exchange data, so the connector talks to them directly. The membership system has none. For that one, the connector signs in and uses the same screens a staff member would: it reads the reports, looks up each organization and contact, creates the ones that are missing, and registers them for the event. Data moves both ways, out of the membership system to the newsletter and into it from event registration.
It started in 2022 as one nightly sync and has grown to four. NHA staff run it from their own admin screen, where they choose which reports feed the newsletter, upload any attendee spreadsheet to be registered, and review a short list of records the connector could not place by itself.
Members to the newsletter
Every night, the current contact list goes from the membership system to Rasa. Live since 2022.
Registrations into membership
Event registrations from Cadmium are entered four times a day. In use since 2025.
Unsubscribes kept in step
Contacts who become inactive are removed from the newsletter list. Added in 2026.
Exhibitors to their committee
Exhibitors from the expo system are added to the right committee. Added in 2026.
The sync has totally changed our workflow in an amazing way.
The result
Staff check the exceptions, not every record.
The first newsletter sync loaded about 7,000 contacts and has run nightly since. Event registrations now reach the membership system four times a day, where the vendor's upload service took days. When the connector cannot match a person or an organization with confidence, it puts the record on a list for staff instead of forcing a match, so their time goes to the handful that need a decision.
Because the connector can register people from any spreadsheet, NHA also uses it for events that never touch the registration system. The work has continued for four years, one sync at a time, as the team found the next piece of manual entry worth removing.
Before
- A newsletter list rebuilt by hand every Monday from about 20 reports
- Event registrations typed into the membership system one person at a time
- A vendor upload service that took three to seven business days
- Exhibitors added to their committee by hand
After
- The newsletter list updates every night without anyone touching it
- Registrations entered four times a day by the connector
- Any attendee spreadsheet can be uploaded and registered
- Staff review a short list of exceptions
Contact
Staff re-typing data because one system will not accept it?
Most projects like this start with an Operations Audit. Two weeks to map the systems and where the payback is.
A senior engineer reads it and replies within one business day.