How to organise your church members without spreadsheets

To organise your church members without spreadsheets, you move to one record per person, linked to their family, their groups and their journey in the church (visitor, regular attender, member). Each role sees only what it needs. You do not have to start from zero: you reuse the sheet that already exists, clean it, import it and fix the errors before saving.

Why the spreadsheet stops being enough

A spreadsheet is a great tool. For a cell group of twenty or a birthday list, it works perfectly. The problem starts when it becomes the database for the whole church.

First, versions. Someone saves members_final.xlsx, someone else opens members_final_v3.xlsx, and months later the team no longer knows which one is right. Google Sheets has a version history, but Google’s own help warns that some changes, such as rows added or deleted, may not show in the edit history.

Then, privacy. Whoever opens the file usually sees everything: contacts, birthdays, pastoral notes. In its help pages, Google says sheet protection should not be used as a security measure, because people who can view it can copy, print or export the data, and Microsoft says sheet-level protection is not meant to be a security feature. In a church this weighs more: knowing who belongs to a church reveals religious beliefs, a special category of data (see the GDPR guide).

Finally, connections. A spreadsheet does not know that Marta and Rui are married, that their son is in the youth group and that Marta serves on reception on Sundays. Each of those things ends up in a column, in a separate sheet, or in a copy that one ministry makes for itself.

What a member record should hold

Record what you will actually use. For most churches, this is enough:

• name, email and mobile;
• date of birth (for ages and birthdays);
• family or household;
• status: visitor, regular attender, member, inactive;
• dates that matter: first visit, baptism, joining as a member;
• groups and ministries they take part in;
• consents, when needed.

Anything you will not use should not be requested. The less data you hold, the less you have to protect. Pastoral notes and health information should exist only when there is a clear reason, and only be seen by whoever supports the person.

Families, not loose rows

Instead of repeating the surname and address on four rows, create a family and link the people to it. That way you see couples, children and grandparents at once, and a change of address is made in one place.

Tags and groups, instead of columns

When a new need appears, the sheet gets a new column: “Kids volunteer”, “baptism course”, “receives the magazine”. A year later there are thirty columns, almost all empty. Tags and groups solve the same problem without bloating the record, and let you save filters such as “members without a group” or “visitors in the last 60 days”.

From sheet to system, in five steps

This path works with any tool. We describe how Brado’s importer handles it, because it is the one we know best.

1. Decide who stays

Before importing, decide what “member” means today. People who have not appeared for years can stay out, or come in as inactive. A shorter list imports faster and starts cleaner.

2. Clean the sheet

Put one person per row and one piece of data per column. Write one phone number and one email per cell. Keep dates in a single format. Do not worry about getting everything right: Brado’s importer recognises several date and phone formats, restores the zero that Excel tends to eat in postcodes and flags possible duplicates, both within the file and against the people the church already has (same email, or same name and date of birth). A couple who share a phone number do not count as a duplicate.

3. Save as .xlsx or CSV

The importer accepts CSV and Excel (.xlsx), with up to 20,000 rows per import. If your sheet is in an older format, such as .xls, or in OpenDocument, save it again as .xlsx or CSV. If you come from another tool, exports from Planning Center, ChurchTools or ChMeetings are recognised by their headers.

4. Import and review before saving

Brado shows what will happen before saving: how many rows are fine, how many have warnings, how many were rejected and why, row by row. The file is read in your browser and only the people you confirm go to the server. You can download the error report to fix in the original sheet. If the plan does not cover everyone, the import is refused as a whole rather than stopping halfway. Once saved, you can undo it within 24 hours.

5. Delete the loose copies

This is the step almost everyone forgets. If the list is still in five files, in three people’s inboxes and in a messaging group, you moved the data into the system but kept the risk. Set a date to archive the original sheet as read-only and delete the rest.

After importing: give people structure

Importing is half the work. The other half is making the list work for you.

Define the journey. Visitor, regular attender, member. If you do not know how many visitors came back a second time, the article on cell groups and visitors shows a simple flow to follow them up.

Link people to groups. Each cell group, ministry or serving team should have its people linked. That is what later lets you build a rota or send a message to one group only.

Give access by role. The office sees contacts, the treasury sees donations, the cell leader sees only their group. Few people need to see everything. Reviewing access twice a year is enough for most churches.

Keep the consents. For visitors and for more sensitive data, record that the person agreed, to what and when. If someone asks for their data, you can export it in one go.

What the spreadsheet is still good at

You do not have to throw spreadsheets away. A one-off analysis, a list to print for the service, a comparison of attendance between two years: all of these are still quicker in a sheet. The difference is one of role. The church database lives in the system, and the sheet is an export you make, use and delete.

If you are deciding between keeping the sheet and switching, the Brado or spreadsheet page compares the two honestly, including the situations where the sheet is the better choice. To assess other options, use the guide to choosing church management software.

Common mistakes when switching

• Migrating everything, rubbish included. If the sheet has duplicates and people who have left, the system inherits them. Clean first.
• Keeping two sources of truth. When the sheet and the system diverge, the team no longer knows which is right. Pick one.
• Giving everyone access to everything. It is what happens by default in a shared sheet. In a system, set roles from day one.
• Asking for data nobody uses. Every extra field is a piece of data to protect and a question that puts off the person filling it in.

How to start

If you have a sheet with your members, you are halfway there. Book a demo of 30 minutes to see how a list of people, a record and a family look. Then take a look at the pricing and the platform page to see what else Brado does beyond people.

This is general information and does not replace legal advice.