There is no button that turns your spreadsheet into a church database. No importer, no upload screen, no mapping wizard that matches your columns to the right fields. If you are moving off a spreadsheet, someone is going to type every record in by hand — you, a volunteer, or (for free) someone at SundayBridge doing it for you. None of those options are as fast as a CSV import would be. All of them force a decision an import quietly skips: does this row still deserve to exist.
This is a guide to doing that typing without losing your evenings to it, and without losing anyone in the process. It assumes a spreadsheet with some mix of names, phone numbers, groups, and maybe a giving column nobody has trusted since 2022. It is written for the person who will actually do the entering, not the pastor who approved the switch.
Why there is no shortcut, and why that might be fine
A bulk import trusts your spreadsheet. It takes every row at face value: the duplicate Smith family entered twice under different spellings, the volunteer who left in 2023 and was never removed, the phone number that was correct for someone else's house before the area code split. None of that gets caught by a machine reading rows. It gets caught by a person who pauses on a name and asks, wait, is this still right.
Typing by hand is slower, and it is also the only point in this whole project where someone actually reads every record. Churches that have done this migration tend to say the same thing afterward: they found out how bad the spreadsheet actually was. Twelve people who had moved and never told anyone. A serving team roster with three names that hadn't served in over a year. A giving column with a formula error that had been quietly wrong since a March update nobody remembers making.
Freeze the spreadsheet before you touch anything
Pick a date — this Sunday, not “sometime soon” — and stop editing the old spreadsheet after it. Tell the other person who has edit access, if there is one. Every new visitor, every new gift, every schedule change from that date forward goes into SundayBridge directly, even while most of the old data is still sitting in rows waiting to be typed in.
Skip this step and you will be migrating a moving target: you will enter someone's old phone number on a Tuesday, and by Thursday the spreadsheet has the new one, and now you have two sources of truth and no way to know which is current. A frozen spreadsheet is a snapshot. A live one is a chase.
Sort people before you sort software
The temptation is to open both windows — spreadsheet on one side, SundayBridge on the other — and start at row one. Do a pass first instead. Sort the spreadsheet by household or last name and mark, in a spare column, who is still active, who moved away years ago, and who is a genuine duplicate. This is the pass that a CSV import would never make you do, and it is the one that keeps you from typing in a hundred people who shouldn't be there.
If your spreadsheet has never distinguished a household from an individual — one row per person with no sense that the Ramirez family of five is one unit — decide that before you start entering, not halfway through. Re-sorting a spreadsheet is free. Re-typing forty records because you changed your mind about grouping is not. If you are not sure how to think about that distinction, households vs. individuals lays out the tradeoffs before you commit to one.
Pace it in weekly blocks, not one long weekend
Thirty minutes, ten to fifteen households, once a week, for four to six weeks — that is a realistic plan for a church of 100 to 200 people. A weekend marathon sounds faster on paper. In practice it produces typos, because the fortieth household gets less attention than the fourth, and it produces burnout, because nobody wants to repeat an eight-hour data-entry weekend for the next migration.
- Week 1–2: people and households — names, contact info, which group or serving team they belong to.
- Week 3: current serving assignments and any background-check dates you track.
- Week 4: groups and their leaders, if you run small groups or classes.
- Week 5–6: giving history, if you are bringing any of it over at all.
A steady thirty minutes a week also means the person doing it is not dreading Sunday. If your church already has a rhythm for keeping records current, a weekly church admin rhythm is the same discipline applied after the migration is done — the pace you build now is the pace you keep later.
Giving history: bring over less than you think
The giving column is usually the messiest part of an old spreadsheet, and it is tempting to type in every year you have records for. Resist that. Current-year and prior-year giving cover almost everything a church actually needs: year-end statements and a trend line worth comparing. A gift from six years ago, entered by hand from a spreadsheet nobody has opened since, rarely gets looked at again.
If your treasurer wants the full history preserved somewhere, keep the old spreadsheet archived and readable rather than retyping every row into SundayBridge. Once the current and prior year are in, giving gets recorded, edited, and reconciled going forward the way any other church record does — and generating the year-end statement is a matter of the records already being there, not a separate project. If you want to think through what is worth tracking versus what is noise, tracking giving that respects the giver covers that decision in more depth.
Do not wait for the backfill to finish before using the system
The spreadsheet migration and the church's actual week do not have to be sequential. Enter this Sunday's new visitor the day they show up, even if last October's visitors are still sitting untyped in the old sheet. Log this week's gift the week it comes in, even while three prior months of gifts are still waiting for a Tuesday evening. The follow-up board and the giving record only need to be current from today forward; the historical backfill can run alongside real church life for as long as it takes.
This is also where most of the actual benefit shows up early. A guest who gets a follow-up owner and a date on their very first Sunday in the system does not have to wait for the rest of the directory to be typed in first. If you want a sense of what that first week ought to look like once someone is actually in the system, guest to member pathwalks through it end to end.
What good enough looks like
You will not finish this migration with a perfect database, and that is not the bar. The bar is that the names in front of you match the people in your building, the phone numbers ring the right house, and the follow-up that was supposed to happen last month actually has an owner and a date attached to it now instead of a sticky note that fell off someone's monitor. A church of 150 typed in over six weeks of thirty-minute sessions, by one tired but attentive volunteer, will be more accurate than the spreadsheet it replaced ever was — not because the software is smarter, but because somebody finally read every row.
If, partway through, you find yourself wondering whether the categories in your old sheet were ever the right ones — a groups tab that was really three overlapping lists, a serving column that hadn't been touched since a staff change two years ago — that is a normal thing to notice mid-migration, and cleaning up a church databaseis the guide for sorting that out once the typing itself is done.