This site is for full design and build projects.Support and maintenance → websitesupport.io
London
Design Works
Design and build for complex organisationsLondon · Est. 2009
Insights / Memberships
Memberships27 Aug 2026 · 3 min read

One member record: what it actually takes to get there

Most membership bodies know the same person as four different records: one in the CRM, one in the events system, one in the learning platform and one in finance. Bringing them together is less about technology than it is about agreeing who owns what.

A hand pointing at a printed bar chart report on a desk, with a tablet and coffee cups behind

A member changes their job title in the events system when they book a conference. They update their address in the learning platform. Finance holds a different email for invoices. Membership still has the details from when they joined. Each team trusts its own version, and none of them is complete.

Everyone agrees there should be one member record. The difficulty is that getting there means taking decisions most organisations have avoided for years.

Decide who owns each field

The core of consolidation is a simple table: for every piece of member information, which system is the master copy, and who is allowed to change it. Contact details might be owned by the member themselves through their account. Grade and membership status by the membership team. Invoicing details by finance. CPD records by the learning platform.

Questions to answer for every field
  • Which system holds the master copy?
  • Who can change it: the member, a team, or an automated process?
  • Which other systems need to read it, and how quickly?
  • What happens when two systems disagree?

Match people before you merge them

Before records can be combined, you need to know which records belong to the same person. Email addresses change, names are spelled differently and people use work and personal accounts. Automated matching gets you most of the way, but there will be a residue of uncertain matches that someone needs to review.

A wrong merge is worse than a duplicate. Duplicates are untidy. Merges can be irreversible.

Give members a single front door

A single record works best when members have a single place to see and update their details. One login, one account area, showing membership, bookings, learning and invoices together. It reduces the number of places where details can drift, and it is what members expect.

Take it in stages

  • Start with a shared identifier that every system can store
  • Connect the systems that change member data most often first
  • Clean and match records before connecting, not after
  • Move ownership of fields one area at a time, with the teams involved

One member record is achievable, but not in a single leap. It is a series of small, agreed decisions, each of which makes the next one easier. The technology follows once those decisions are made.