Every church spreadsheet starts as one clean idea — a list of names and phone numbers — and ends up as something closer to a junk drawer. There is a column for “notes” that means five different things depending on the row. There is a household squeezed into one cell as “the Petersons + kids.” There is a giving total that lives three tabs away from the person it belongs to. None of this was anyone's fault. It just happens when a document built for one Sunday keeps getting reused for six years.
The instinct, once the mess becomes obvious, is to go shopping for software and hope the new tool sorts it out on the way in. It will not, and no honest tool will claim otherwise. A database only knows what you tell it, and it needs the same thing you need: a person record that means one person, and a household record that groups the people who live together. Getting there is a restructuring job you do in the spreadsheet itself, before you touch anything new. Here is how to do it once, carefully, so you only do it once.
Why a spreadsheet and a database disagree about what a row is
A spreadsheet does not care what a row represents. You can put a person on one row, a family on the next, and a giving total on a third, and the spreadsheet will hold all three without complaint. A database is stricter, on purpose. It wants every row in a table to be the same kind of thing: a table of people where every row is one person, a table of households where every row is one household, a table of gifts where every row is one contribution tied to a person. That strictness is not bureaucracy. It is what lets you later ask a simple question — who gave last month, who has not been seen in two months, who is on the greeting team — and get a real answer instead of a scavenger hunt across tabs.
So the real work of “converting a spreadsheet to a database” is not technical at all. It is deciding, row by row and column by column, what kind of thing each piece of data actually is. Do that honestly and the move into any structured tool becomes almost mechanical. Skip it and you will spend your first month in the new system discovering, one confused volunteer at a time, that the data never really had a shape.
Pull the three spreadsheets out of your one spreadsheet
Open the file and look past the column headers to what is actually in it. Almost every long-running church sheet is secretly three documents wearing one tab: a directory of who your people are, a log of things that happened to them over time (attendance, giving, check-ins), and a scratchpad of context that does not fit either category (who is grieving, who cannot be reached by phone, who quietly does the coffee every week). These three things belong in different tables and they move at different speeds. If you are weighing the bigger question of leaving spreadsheets altogether, our guide on moving off spreadsheets walks through that decision; this one is about the column-level work underneath it.
Copy the directory information into its own tab first. That becomes the seed of your people table, and everything else — giving, attendance, notes — will eventually reference back to a person in it. Do not try to structure all three at once. People first, because nothing else means anything without a stable person to attach it to.
Decide, once, what counts as a household
This is the single decision that shapes everything downstream, and it is worth making deliberately rather than letting old habits pick it for you. Does “the Petersons” mean one row with five names crammed in, or does it mean one household record linked to five individual people, each with their own age, email, and serving history? Almost every real church record needs the second shape, because a fourteen-year-old in the youth group and her father on the finance committee are not the same record even though they share an address. We go through the tradeoffs in detail in households versus individuals, but the short version for a spreadsheet is this: give every person their own row, then add a household column that groups rows together by a shared ID or last name. You can always merge later. You cannot easily unmerge a family that was flattened into a single cell.
Turn each column into one field that means one thing
Once you have a people tab, go column by column and ask a blunt question: does this column ever mean two different things depending on the row? A “status” column that sometimes says “member,” sometimes says “visited once in 2022,” and sometimes says “do not call” is really three columns pretending to be one. Split it before you move it anywhere. A database field, like a good spreadsheet column, should answer exactly one question about exactly one kind of thing.
Watch especially for these:
- Dates written as text. “Joined last spring” needs to become an actual date, even an approximate one, or no system will ever be able to sort by it.
- Phone numbers in five formats. Pick one format and reformat the column now, not after import.
- A single “notes” column carrying pastoral care, serving roles, and allergy information at once. Split it into a notes column, a serving column, and, if it matters, a care column.
- Giving totals sitting in the same row as the person. Those totals belong in their own table, one row per gift, each row pointing back to a person. Otherwise you can never show a trend over time, only a single frozen number.
Add a staging tab before you touch the original
Do the restructuring in a copy of the file, not the file everyone still uses on Sunday morning. Duplicate the sheet, rename the copy something obvious like “Directory — restructured,” and do your column-splitting and household-grouping there. This buys you two things: a working sheet nobody breaks while you experiment, and an easy way to compare your new structure against the old one when something looks off. A staging tab also gives the rest of your team something to react to before the change is final — show the volunteer who has entered data for years, and let them catch the row you misread before it becomes permanent.
Work in small batches rather than all at once. Restructure fifty rows, check them against the original, then do the next fifty. It feels slower than a single pass through the whole sheet, but errors compound quietly in a spreadsheet, and catching a misassigned household on row sixty is much easier than discovering it on row six hundred.
Clean before you convert, not after
It is tempting to move the mess as-is and promise yourself you will clean it up later, once it is somewhere “real.” In practice, later never comes, and a messy spreadsheet becomes a messy database with better fonts. Duplicate people, dead email addresses, and members who quietly left three years ago are all easier to spot and fix while everything is still visible in one flat file. Sort by name and scan for duplicates. Sort by last-contact date and mark who is genuinely inactive. This is slow, unglamorous work, and it is the entire difference between a database you trust and one you double-check.
If your sheet has gotten badly tangled — years of half-updates, three different people entering data their own way — it may be worth a dedicated pass before you go further. Our guide on cleaning up a church database covers deduplication and standardization in more depth than fits here.
What “moving it in” actually looks like
Once your sheet has one clean people tab, a household column, a separate giving log, and a separate attendance log, you have done the hard part. What comes next depends on the tool you choose, and it is worth knowing before you pick one whether it can take a spreadsheet in at all. Most church software, SundayBridge included, does not import a CSV automatically — the risk of an automated import quietly misreading a column is exactly the kind of silent error a small church cannot afford. What we do instead is load a cleaned spreadsheet in by hand, for free, once you have done the structuring described above. That hand-entry step is also a second set of eyes on your data, which catches things a script never would.
If you are still deciding which tool is worth that effort at all, our guide to choosing church management software lays out the questions worth asking before you commit.
Keep a copy of the original, unedited spreadsheet somewhere safe before you start restructuring. If you second-guess a decision three weeks in, you want the source to check against, not just your memory of what used to be in cell F12.