Guides & Resources › Software Guide

Union member data in multiple systems: what it costs to keep your roster in one tool and your messages in another

A practical guide for any local whose member records live in one place and whose email, text, or portal lives in another: how locals end up there, the five ways split systems break, and a field-by-field map for deciding which system holds the truth.

We're an eMembership publication and naturally know our own platform best. This guide is written to be useful to any local running more than one system, including a local that decides to keep all of them. It draws on Department of Labor recordkeeping guidance, published eMembership client stories, and what unions tell us about the systems they run now. The one section about our platform is labeled as ours.

Key Takeaways
  • The second subscription is the small cost. The larger one is keeping two systems in agreement, and it gets paid in staff hours that never appear on an invoice.
  • Split systems break in five predictable ways: stale contact data, members on the wrong list, dues status that disagrees, double data entry, and no record of which system was right.
  • Ask one question of every field. For each piece of member data, which system is authoritative? If the answer is "it depends," your local has two systems of record for that field.
  • The Member Data Ownership Map sorts each field into one of four states: owned, mirrored, copied, or forked. Forked fields are where the damage happens.
  • Fix eligibility fields first. Member status and dues standing decide who gets a ballot, a dispatch, or a service. A wrong address costs a mailing. A wrong status can cost a vote.
  • Consolidating doesn't require replacing every tool. One system holds the record, the others read from it, and channels such as your website stay channels.
  • This is also a recordkeeping question. OLMS expects the records behind a filed report to be kept for at least five years and protected from unauthorized changes, and it can ask a union for a description of each electronic storage system it uses.

Is it a problem to keep union member data in multiple systems?

Not automatically. Plenty of locals run a membership database alongside an email tool, a website, a portal, or software from their international, and many of those arrangements work.

What decides it is narrow. Two systems are manageable when one of them is clearly the record for each piece of member data and the other only reads from it. They become a problem when both accept changes to the same data. From that point on, the local has two versions of its membership and no automatic way to know which one is right.

The visible cost of two systems is the second subscription. The cost that grows is reconciliation: the hours staff spend comparing lists, re-keying changes, and fixing the message, ballot, or bill that reached the wrong person because one system knew something the other didn't.

✓

Two systems that both hold a member's record drift further apart every week nobody reconciles them.

How locals end up with union member data in multiple systems

Almost no local decides to run two systems. It accumulates them, one reasonable decision at a time.

Fire locals show the pattern clearly. Your local may already have an IAFF SMART login. It may also have a website vendor that runs its public site, its news posts, and the member email list that goes with them. Each made sense when it was set up. Together they mean the local's member contact information can live in at least two places, maintained by different people on different schedules.

The same pattern shows up in every kind of local, usually by one of three routes.

A tool from the international

Some internationals provide software to their affiliates, sometimes at no cost to the local. That tool may hold a roster, a member login, or a communications channel. If the local also keeps its own database for dues, employers, or grievances, it now has member data in two systems that were never designed to agree with each other.

A website vendor that added a member list

Website platforms can add member logins, email sign-ups, and event registration. Every one of those collects member data. Over time the website's list turns into a second roster, and members update their email address there because it's the screen they actually see.

A spreadsheet that never went away

Most locals have one. The steward list, the retiree list, the phone list someone started keeping because the database was wrong once and never trusted again. A spreadsheet is a system: it has its own copy of member data, its own editor, and no connection to anything else.

✓

When two systems disagree, someone on staff becomes the real system of record. Usually it's whoever remembers which one to trust.

The five ways split member data systems break

Every pattern below starts the same way. A change lands in one system and doesn't reach the other.

1. Contact data goes out of date

A member updates an address, phone number, or email in one system, and the other keeps the old one. That happens more often than most lists account for: Census Bureau estimates show 11.8 percent of people in the U.S. moved to a different residence in 2024, roughly one in eight in a single year. Mail comes back, texts go to a number the member gave up, and the member reasonably concludes the union isn't keeping track.

2. Members end up on the wrong list

A status change (retirement, withdrawal, suspension, a move to a different unit) gets recorded in the membership database but never reaches the email or text list kept somewhere else. A notice or ballot then reaches someone it shouldn't, or misses someone it should.

3. Dues status disagrees between systems

The treasurer's records say a member is current. The portal, built from an older export, says they're behind. Or it runs the other way. The member sees one answer, staff see another, and sorting it out takes longer than the payment it's about.

4. Staff enter the same data twice

Someone keeps the systems close by re-keying changes, or by exporting a spreadsheet from one and importing it into the other. That holds up as long as the person has time, remembers, and doesn't transpose a digit. An export is a photograph of your data on the day it ran.

5. Nobody can say which system was right

When the two disagree, there's usually no record of which value changed last, who changed it, or why. Resolving it means asking around, and the answer lives in someone's memory rather than in the record.

These aren't abstractions. Before it consolidated, IUOE Local 139 in Wisconsin ran membership and dispatch on two separate systems across four regional offices. Its published story describes two of these failures directly. Without real-time visibility into member status, suspended or blacklisted members occasionally got dispatched anyway. And updated contact information collected during dispatch often never made it back into the membership database.

✓

The fields that do the most damage when they disagree aren't the ones that change most often. An address changes far more often than a member's status, but a wrong status decides who gets a ballot.

What split systems cost a local

Staff time. Reconciliation rarely has a budget line. It shows up as the afternoon someone spends comparing lists before a mailing, the cleanup after a campaign bounces, and the phone call with a member who saw different numbers in different places. Because the work is spread across several people and many weeks, it's easy to undercount.

Member trust. A member who receives a notice meant for someone else, or who updated their address and still gets mail at the old one, draws a conclusion about how carefully the union handles their information. That conclusion is slow to reverse.

The records behind your LM report. Under the LMRDA, unions must keep the records that verify their filed reports for at least five years after filing, and the Office of Labor-Management Standards lists dues records for current and former members among them. OLMS's compliance tip on electronic recordkeeping says an electronic system should prevent and detect unauthorized creation, alteration, or deletion of records and include an indexing system for finding them. It also says a union must make available to OLMS, on request, a complete description of each electronic storage system it uses.

Split systems make each of those harder to show. If dues status lives in two systems that disagree, the local has to be able to say which one verifies the report, and it has two systems to describe and two sets of controls to stand behind. Our guide to LM-2 and LM-3 reporting requirements covers what those reports draw on. None of this is legal advice, so confirm specific compliance questions with your own counsel.

✓

OLMS can ask for a description of each electronic storage system a union uses. Two systems of record means two descriptions to write and two sets of controls to defend.

The Member Data Ownership Map: which system owns each field

The test fits in one sentence. For every piece of member data your local keeps, which system is authoritative? If the answer is "it depends," you have two systems of record for that field.

A system of record is the one system whose value for a piece of data is treated as correct when systems disagree, and the place where that value gets changed. A single source of truth is what a local has when every field has exactly one system of record and everything else reads from it.

The map asks the question one field at a time, because few locals are consolidated or split as a whole. A local's address field might be in good shape while its status field is in two places. For each field, write down two things: every place it can be edited, and how a change made in one place reaches the others. Those two answers put the field in one of four states.

The four states of a member data field

StateWhat it looks likeHow a change travelsRisk
OwnedOne system holds the field. Every other tool displays or uses it by reading from that system.It doesn't need to. There's one copy.Lowest
MirroredOne system owns the field. Another keeps a copy that updates automatically, in one direction only.Automatically, from the owner outward, on a known scheduleLow, as long as nobody edits the copy
CopiedOne system owns the field in principle, but the copy moves by hand: an export, an import, or someone re-keying it.Whenever someone remembers and has timeMedium, and rising with every week between copies
ForkedTwo or more systems each accept edits to the field.Not reliably. Each system holds its own version.Highest. This is the "it depends" answer.

Fields to map first

Use this as a starting worksheet. The middle column lists places a second copy commonly hides. Your own map fills in where each field can actually be edited and which of the four states it's in.

FieldWhere to look for a second copyWhat a fork in this field decides
Member status (active, retired, withdrawn, suspended)International's tool, email and text platforms, portal, steward spreadsheetsWho receives ballots, notices, and services
Dues standing and balancePortal, treasurer's spreadsheet, accounting systemWhat a member is told they owe, and what supports your LM report
Mailing addressWebsite member list, international's tool, mailing listsWhether mail arrives
Cell phone number and emailEmail platform, text platform, website sign-upsWhether urgent messages arrive
Communication opt-ins and opt-outsEmail and text platformsWhether you're honoring the preference a member gave you
Employer, classification, unit, or stationDispatch or scheduling tools, spreadsheetsContract coverage, dues rates, and who a targeted message reaches
Officer and steward rolesWebsite, international's tool, spreadsheetsWho has access, and who members are told to call
Portal or app loginPortal, international's login, website loginWhat a member sees when they check their own record

How to read your map

Start with the forked fields. They're the only state where the local genuinely can't say which value is right. Within that list, fix eligibility first: status, standing, and the employer or unit fields that decide coverage. Then money. Then contact data. A forked address costs a returned envelope. A forked status can put a ballot in the wrong hands.

Copied fields come next. The fix for a copied field is usually one of two moves: automate the copy and make it one-way, which turns it into a mirrored field, or stop keeping the copy and read from the owner, which makes it owned.

Mirrored and owned are where you want to end up, and a local doesn't need every field to be owned. A mirrored field with a one-way flow and a known schedule is a sound arrangement. If one of your systems is a CRM, our guide to CRM for labor unions sets out rules for running a union system of record alongside one.

✓

A field can only fork when two systems will accept an edit to it. Close the second door and the disagreement can't start.

How to consolidate union software without replacing everything

Consolidation can sound like ripping everything out and moving to one platform. For some locals that's the right call. For many others, the map points to something narrower.

One system of record. Choose the system that will own the eligibility and money fields. In most locals that's whichever system already holds dues, employers, and the records behind the LM report, because those are the hardest fields to move and the ones outside parties can ask you to prove.

Other tools read from it. Email, text, the portal, and dispatch don't need rosters of their own. They need access to the record, through a built-in module or an integration, so that a change in the record reaches them without anyone re-keying it. Where a tool has to keep its own copy, make the flow one-way and turn off editing on the copy wherever the tool allows it.

Channels stay channels. A website is where members find you. It doesn't have to be where member data is kept. We drew the same line between a website platform and a membership system of record in our guide to firefighter union software: the website can show a member their record without becoming a second place that record gets changed.

The same reasoning applies to software from your international. Both systems can coexist. The international's tool can keep doing what it does for the international, and your local's system can be the record for your local's dues, employers, and representation. What matters is that everyone knows which one is the record for each field, and that the other one isn't quietly accepting edits.

✓

Consolidation is a decision about where each field gets edited. How many tools you keep is a separate question.

What most unions get wrong about member data in multiple systems

They count subscriptions instead of reconciliation. Two licenses are easy to see on a budget. The hours spent keeping two rosters in line aren't, so the second system looks cheap when locals compare costs.

They pick the surviving system by feature list. When a local does consolidate, the temptation is to keep whichever system does more. The better test is which system already owns the fields that are hardest to get right: status, standing, employers, and the dues history behind your filings. A system with fewer screens that holds those fields correctly is usually the one to build around.

They treat a regular export as an integration. A spreadsheet someone exports on the first of every month is still a copied field, however reliable the habit. An integration moves a change without a person in the loop, in one direction.

They clean the list instead of closing the leak. A one-time cleanup of the email list feels like progress. If members can still change their address on the website while staff change it in the database, the lists start drifting apart again the next morning.

How eMembership approaches union member data in one system

This section is about our own platform. Everything above applies regardless of what a union decides.

eMembership was built for labor unions and has been in continuous development since 2008. Member management keeps each member's profile, contact details, chapter and employer history, dues standing, signed documents, and communication history on one record. Addresses are validated and flagged when undeliverable, and the system prevents duplicate records from accumulating over time.

Measured against the map, communications fields are owned rather than copied. Integrated Email and Text builds recipient lists live from the member database, so delinquent and inactive members are excluded based on their current record and staff don't export or maintain a separate contact list. Every email and text is logged back to the member's communication history. Bulk email goes out through Mailchimp or SendGrid and text through Twilio or Azure Communication Services, all managed from inside eMembership. The local holds its own accounts with those services, connected during implementation.

The Member Web Portal and the Member Mobile App are member-facing layers on the same database, so a member's address change or payment writes to the record staff work from. There are 18 configurable modules, and the paid Discovery Process determines which ones a given union needs.

For the systems a local keeps, union software integrations run through a secure REST API, documented with Swagger, that reads and writes to the member database, plus bulk data pipelines through technologies such as SFTP, Boomi, and Microsoft Azure services. A union can use the API to let members log in and check their balance from the website it already owns, which keeps the website a channel. Integrations are scoped during Discovery, so the local knows how data will move before go-live.

IUOE Local 139 is the clearest example of consolidation among our clients' published stories. The local retired its two legacy systems for membership and dispatch and now runs all four regional offices on one real-time system in eMembership. According to its story, contact updates collected during dispatch are now saved directly to the membership record, and real-time status visibility ended the inadvertent dispatching of suspended or blacklisted members. You can read how Local 139 unified dispatch across four offices.

eMembership has enabled us to run our operations and to engage with our members in ways we never thought possible.
Jessica S., Director of Membership and Communications, PSE SEIU Local 1948

Whether eMembership is the right answer depends on how many of your fields are forked today and which system already holds your dues and employer records. A local that wants its operations and its member communications on one record, with its other tools reading from it, is the kind of local we tend to fit well.

Frequently asked questions

Is it bad to use more than one system for union members?
Not on its own. Many locals run a membership database alongside an email tool, a website, or software from their international. The problem starts when two systems both accept changes to the same member data, such as status, dues standing, or contact details. Then the local has two versions of its records and no automatic way to tell which is right. If each field has one clear system of record and the others only read from it, more than one system can work well.
What is a system of record?
A system of record is the one system whose value for a piece of data is treated as correct when systems disagree, and the place where that value is changed. For a labor union, it's usually the system that holds dues, employers, and the records that verify its LM report. Other tools can display that data, but they shouldn't be where anyone edits it.
Can our membership database sync with our email or text tool?
Often, yes, depending on the platforms. The safest arrangement runs one way: recipient lists come from the membership database, and the email or text tool doesn't become a second place where member data gets edited. The exception worth planning for is an unsubscribe or opt-out a member makes inside the email or text tool, which needs a path back to the record so the next list honors it.
Our international gives us free software. Should we still use our own system?
Both can coexist. The international's tool can keep serving the international's needs, and your local's system can be the record for your own dues, employers, and representation. Decide, field by field, which system is the record, and make sure the other isn't quietly accepting edits to the same data. Your local's officers sign its LM report, so the records that support it should sit in a system your local controls.
How do we choose which system becomes the record?
Start with the fields that are hardest to get right and that outside parties can ask you to prove: member status, dues standing, employers, and the dues history behind your filings. The system that already holds those correctly is usually the one to make the record. Then map every other field to it and move each one toward a single place where it's edited.
Does consolidating mean replacing our website?
No. A website is a channel, a place members find you. It can display a member's information by reading it from the system of record without storing its own copy. Consolidation decides where member data gets edited. Members can still see their information in as many places as you like.
David Stone · eMembership

Is your member data living in more than one place?

If your roster, your dues, and your member messages sit in different systems, start by mapping which one owns each field. When you're ready to talk through what you're running now, see how eMembership's member management keeps one record at the center, or book a short intro call. We'll walk through your current setup before recommending anything.

Book an Intro Call