The spreadsheet is the unofficial software of UK churches. It's free. Everyone knows how to use it. And when it was set up five years ago by someone who has since moved away, it worked perfectly well — for a congregation of 40.
Now there are 120 members, three version of "the members spreadsheet", two admins who update different copies, and nobody is entirely sure which one is correct. Sound familiar?
Spreadsheets aren't bad. They're the wrong tool for the job — and using the wrong tool has a real cost, even if it doesn't show up on a budget line.
The Real Cost of Spreadsheet-Based Member Management
It's easy to think of spreadsheets as free. The licensing cost is zero (or close to it with Google Sheets). But cost is time, not just money. Here's where the hours go:
The "main" spreadsheet gets copied for different purposes — a safeguarding list, a rota, a giving record. Each copy drifts from the others. Reconciling them takes time nobody officially has.
Need to send an email to everyone in the under-18 ministry? You're filtering columns, copying email addresses into Gmail, and hoping the list is current. A proper database does this in two clicks.
When someone moves, the old address disappears. When a family leaves, the row gets deleted. Spreadsheets are current-state tools — they don't preserve history, and you can't answer "who was active in our congregation in 2024?"
Sharing a spreadsheet is all-or-nothing. The new youth group leader needs contact details for their group — but you don't want to share the full member directory including medical notes and safeguarding flags. Spreadsheets don't support this.
The GDPR Problem You Might Not Know About
⚠️ UK GDPR Compliance Risk
Under UK GDPR, churches (as data controllers) must be able to demonstrate how personal data is stored, who has access, and respond to subject access requests within 30 days. A Google Sheet with 30 collaborators and no audit log is a difficult position to defend. It doesn't mean enforcement action is imminent — but it means you're not meeting the spirit of the law.
Most UK churches that store member data in spreadsheets don't have a formal data protection framework. That's understandable for a volunteer-run organisation — but the Information Commissioner's Office has increasingly focused on charity sector compliance, and "we use Google Sheets" isn't a data protection policy.
A proper member database gives you:
- A clear data register (what you hold, why, for how long)
- Role-based access (so only the right people can see sensitive fields)
- An audit trail (who viewed or edited member records)
- Easy subject access request fulfilment (export a member's data in seconds)
- Soft-delete functionality (so you're not immediately destroying data, but not actively using it)
Before and After: What Changes When You Switch
Spreadsheet
Four versions of the member list. Email addresses copied manually into every announcement. New member added three weeks late. Phone number in two columns formatted differently. No record of when someone joined.
Member Database
One source of truth, updated in real time. Send to any group or filter with two clicks. New member added during welcome process. Data consistent, validated, searchable. Full history from join date forward.
The Migration: It's Not as Hard as It Sounds
The thing that stops most churches from moving off spreadsheets isn't reluctance — it's the perceived cost of migration. "Our data is messy" or "it'll take weeks" are the most common objections.
In practice, for a congregation under 200 members:
- Export your best spreadsheet to CSV. Pick the most complete version — usually whoever updated it most recently.
- Clean obvious errors. Duplicate rows, inconsistent name formatting, blank emails. This takes 30-60 minutes with basic Excel/Sheets skills.
- Import. Most church management platforms support CSV import with field mapping. For 200 records, this takes under an hour.
- Verify. Spot-check 10 random records. Fix anything that looks wrong.
- Archive the spreadsheet. Don't delete it immediately. Keep it as a read-only reference for the first month in case you need to check something.
- Communicate the change. Tell every admin that the spreadsheet is now read-only and all updates go in the new system.
Total time: 3-5 hours for a congregation of under 200. You'll recover that in the first month.
What to Look for in a Church Member Database
Not all church management software handles member data equally well. Key things to check:
- GDPR compliance — where is data stored? Is there a Data Processing Agreement? Can you export or delete a member's data on request?
- Role-based access — can you give different volunteers different levels of access?
- Group management — can you easily segment members into groups (ministry teams, age groups, etc.) for communications?
- Bulk import — CSV import is essential. It's how you get existing data in without manual re-entry.
- Family relationships — spouses, children, households. A database that treats every member as an individual makes family communication harder.
PewConnect was built with these requirements at the core — designed specifically for the UK church context where GDPR compliance isn't optional and most admins are volunteers, not database administrators.
Make spreadsheets your archive, not your system
PewConnect's member database was designed for UK churches. GDPR-compliant, bulk import, role-based access. Start your 14-day free trial.
Get Started FreeFrequently Asked Questions
Can we keep using our spreadsheets alongside church software?
You can, but it defeats the purpose. Parallel systems mean doubled maintenance. The fastest path to time savings is committing to one system as the single source of truth and archiving the spreadsheet.
What happens to historical data in our spreadsheet?
Import it. Even if it's imperfect, having member history in the new system is better than having it in a spreadsheet no one can find in two years. Most platforms allow custom fields so you can bring in data that doesn't fit standard fields.
Is a church considered a data controller under UK GDPR?
Yes. Any organisation that collects and processes personal data about identifiable individuals is a data controller. Churches storing member details (names, contact information, attendance records, financial giving) are processing personal data and must comply with UK GDPR. Registered charities should also have a data protection policy and, depending on scale, may need to appoint a Data Protection Officer.
What's the difference between UK GDPR and EU GDPR for church software?
Since Brexit, the UK operates under UK GDPR — which largely mirrors EU GDPR but is now a separate legal framework administered by the ICO rather than EU supervisory authorities. For most practical purposes (data storage, consent requirements, subject access requests), the obligations are the same. Software vendors operating only in the UK need to comply with UK GDPR; those serving EU members also need EU GDPR compliance.