Somewhere in the sales conversation, someone usually asks the question directly: “so it just pulls in our spreadsheet, right?” And the honest answer, for most church software built around real data hygiene rather than a flashy demo, is no. There is no button that reads your file and populates two hundred people records correctly. What actually happens is a person — you, a volunteer, or someone on the other end offering to help — opens your spreadsheet next to the new system and works through it row by row, deciding what each cell means and where it belongs.
That sounds slower than it is, and it catches problems an automated import would happily wave through. Here is what the process actually looks like, so you know what you are walking into before you start, and so it does not feel like unpaid labor you were not warned about.
Why there is no import button in the first place
A CSV importer sounds simple until you look at what it has to survive. Every church spreadsheet is a slightly different shape: one lists spouses on the same row, another gives them separate rows with no obvious link. One column called “phone” holds seven different formats. A cell that says “moved” is doing the job of a status field nobody built. An importer either rejects all of that and asks you to reformat everything first — which is its own multi-hour project — or it imports it wrong, quietly, and you find the damage three months later when a mailing goes to a dead address.
A person reading the row makes the judgment call an importer can't: is this really two people or one household, is this note actually a care concern, is this contact still active. That judgment is the actual work of getting your data right, and no piece of software does it for you, whichever tool you land on.
Sort before you type a single row
The mistake that turns hand entry into a slog is starting at row one and typing straight down. Sort first. Every church spreadsheet has at least three tiers hiding inside it: people who were at church last month, people who haven't been seen in two years, and people who show up once as a guest and never again. Typing all three in with equal care wastes the same hour three different ways.
A simple pass with a highlighter, or a new column in the old file, sorting rows into active, uncertain, and clearly gone, pays for itself many times over in the entry that follows. The uncertain pile is worth a phone call or a text before you decide; the clearly-gone pile can wait, or never get typed at all. If your sheet has grown genuinely messy over the years, it is worth reading how to clean up a church database before you start typing, since fixing a duplicate on paper takes thirty seconds and fixing it after entry takes ten minutes.
The row-by-row decisions nobody warns you about
Once sorting is done, the actual entry is a series of small judgment calls, over and over. Is “Sarah and Tom Whitfield” one household or two people who happen to share a row. Does the kid listed under “notes” get their own profile or stay attached to a parent's. Is the scribbled “allergic to peanuts, tell the nursery” a care note or something that belongs somewhere more visible.
None of these are hard decisions individually. What makes hand entry feel long is that there are hundreds of them, and each one asks you to think for a second rather than just copy. Deciding your household structure once, before you start, removes the biggest recurring decision from the pile — our piece on households versus individuals walks through the tradeoffs so you are not re-litigating it on row forty and row two hundred differently.
Giving history deserves its own slower pass
People data can absorb a small mistake — a wrong middle initial is embarrassing, not damaging. Giving history cannot. A transposed digit or a contribution logged under the wrong name is a trust problem the moment someone notices it on a statement, and at year end someone will notice. Do this pass separately from the people entry, more slowly, and reconcile the totals against your bank deposits before you consider it done rather than after.
If you are moving mid-year, plan for a full year of history to land correctly, because a giver expects a correct January statement regardless of when your church switched tools. It is worth reading how giving records should be handled before you type a single contribution, since the habits you set in this first pass are the ones that stick.
Who actually does the typing
For most small churches, this work gets split between whoever offered to help set the system up and one or two volunteers who know the people in the spreadsheet best. That second part matters more than it sounds — someone unfamiliar with the congregation will type exactly what the cell says, while someone who knows the Whitfields will catch that “Tom” and “Thomas” are the same person three rows apart. Local knowledge is doing real work here that a stranger, human or automated, cannot replicate.
SundayBridge will load your spreadsheet by hand for you, at no cost, precisely because that local read-through matters more than speed. It is still worth having a volunteer sit alongside that process at least once, so someone on your team understands the decisions that got made and can explain them later.
What to do the moment entry is finished
Do not delete the old spreadsheet. Not this week, not this quarter. Set it aside, read-only, somewhere obvious, and treat it as your one source of truth for anything that looks wrong later. The temptation is to declare the migration complete and archive the old file out of sight; resist it for at least a year, because you will find a handful of small errors in the first few weeks and you will want the original to check against.
The other early task is teaching the two or three people who touch the record regularly how the new habit works, which is less about the software and more about a weekly discipline. A short weekly rhythm is what turns a one-time entry project into a record that stays accurate, rather than one that is perfect on launch day and quietly rotting again by fall.
Hand entry is slower than an import button and more honest than one. Every row gets read by a person who can tell the difference between a duplicate and a divorce, which is the whole point.