Every church database eventually collects the same barnacles: two records for the same Bob Smith, phone numbers that ring a stranger, emails that bounce, and a long tail of people who last attended when the old pastor was still around. None of it is a crisis. All of it quietly erodes trust in the record — and once the team stops trusting it, they stop using it.
The good news is that a cleanup is a calm, finite job when you take it in order. Do not try to fix everything at once. Take these passes, one at a time.
Pass one: merge the duplicates
Duplicates are the worst offenders because they split a person's history in half — some attendance here, some giving there, and neither record telling the whole story. Find them by name, then by email and phone, since the same person often appears once as “Bob” and once as “Robert.” When you merge, keep the record with the most history and fold the other into it rather than deleting outright, so nothing is lost.
Pass two: retire, don't delete
Next, the people who have clearly moved on. The instinct is to delete them, but deletion throws away giving history you may need for years and erases the fact that they were ever part of the church. Retire them instead: mark them inactive so they leave your active counts and mailing lists but stay in the record. If they return — and some will — their story is still there. This distinction also keeps your attendance numbers honest, since inactive people stop inflating your active base.
Pass three: fix the contact data
Now standardize what is left. Put phone numbers in one format. Flag emails that bounce. Fill the obvious gaps. This is unglamorous work, but it is the difference between a directory a volunteer can act on and one they second-guess. If you are doing this ahead of a move to new software, do it in the old file first — it is far easier to clean before you import, as covered in moving off spreadsheets.
Pass four: keep it clean
A cleanup you do once is a cleanup you will do again in two years. The way to avoid the second one is a light weekly rhythm and clear ownership of the record, so small errors get fixed as they appear instead of accumulating into another big job.
Cleanup is also easier when a person is one record with everything hanging off it. In SundayBridge, each person carries their household, groups, and history in one profile, so a merge or a retire is a single deliberate action rather than a hunt across tabs — but the judgment calls, which Bob is which, who has really left, are yours to make; the software can only make them easy to act on. The reward is a directory your whole team trusts.