Church management
Moving your church from spreadsheets to a church management system
A spreadsheet can work fine as a church database until three people are each keeping their own copy. This guide covers when to switch, how to get your files ready, which columns go to which fields, what to leave behind, and how to run both side by side until you trust the new system.
When and how should you switch?
Switch when you’ve ended up with several versions of the same list. Before you import anything, gather every sheet, pick the columns you’ll actually use, put one person on each row with a household ID, fix duplicates and dates, and set texting consent aside. Then import a small test file and check it by eye. After that, import the rest. Keep the old files read-only until the new system has handled at least one full cycle of the work that matters most to you.
This guide is just about the data. For the rest of the project, like owners, training, a pilot and a go-or-no-go meeting, use our church management software implementation checklist too.
Signs you’ve outgrown spreadsheets
Spreadsheets can work as a church database for a long time. They’re free, everyone knows how to use them, and they do exactly what you type. Here are some signs they’re now causing more trouble than they save:
- There’s more than one “master” list. The office directory, the kids’ ministry sheet, the newsletter export and the volunteer schedule are all a little different.
- Someone asks “is this the latest version?” and nobody knows.
- Families are stored on one row (“John & Mary Smith”), so you can’t tell who’s a child, who serves or who gave.
- Follow-up lives in a notes column, so nothing reminds anyone to do it.
- Sensitive details like allergies or pastoral notes are in a file anyone with the link can open.
- If one volunteer left, they’d take the only up-to-date copy with them.
- You copy the same email addresses by hand into a mailing tool, a texting tool and a giving platform.
A step-by-step migration checklist
- 1List every sheet. Ask each ministry what it keeps: the directory, guest cards, kids’ allergies, small groups, volunteer lists, baptisms, the Christmas mailing list. Write down who owns each file, about how many rows it has and when it was last updated. Before anyone edits anything, save an untouched, dated copy of every file.
- 2Decide which source wins for each fact. If the directory and the kids’ sheet have different phone numbers for someone, decide now which one to trust. Don’t leave it until the import.
- 3Pick your columns. Only keep a column if someone will use it in the next year. Map each one to a built-in field, a custom field, a milestone or nothing. If a column is blank for most rows, it probably maps to nothing.
- 4Put one person on each row. Split “John & Mary Smith” into two rows. Kids get their own rows too.
- 5Add a household ID. Give everyone who lives together the same value in a Household ID column (1, 2, 3 is fine), and mark who’s an adult and who’s a child. That way the new system can rebuild families instead of guessing from last names.
- 6Clean up duplicates. Sort by last name, then email, then phone. Merge the obvious ones in the spreadsheet, and flag the ones you’re not sure about for someone who knows the families. Two people with the same name and the same family email might be a parent and child.
- 7Fix dates. Use one format all the way through, ideally year-month-day (2026-03-14). Look for birthdays in the future, “1/1/1900” placeholders and years typed with two digits.
- 8Protect numbers. Excel drops leading zeros, so a ZIP code like 01234 turns into 1234, and it rounds numbers longer than 15 digits. Format ZIP code and ID columns as text before you edit, and check a few by eye.
- 9Keep consent separate. A phone number isn’t permission to text, and an email address isn’t permission to send a newsletter. Keep a separate list of anyone who’s asked not to be contacted, and of anyone whose texting consent you can actually show. Industry texting guidelines expect a record of when consent was given, how it was given, and the wording the person agreed to.
- 10Do a test import. Import 20 to 50 people, including a complicated household, someone with no email, and someone with a hyphenated or two-part last name. Open each one in the new system and compare it with the spreadsheet.
- 11Import the rest, then check again. Spot-check ten random people, five households and every custom field. Run a count and compare it with the number of rows in your file.
Mapping spreadsheet columns to ChMS fields
Every church management system names its fields a little differently, but most columns end up in one of a few places. Use this as a starting point and adjust it for whatever system you pick.
| Spreadsheet column | ChMS field | Watch out for |
|---|---|---|
| Name, Full name | First name and last name (split) | Couples on one row, and titles like “Dr.” in the name. |
| Nickname, Goes by | Preferred name | Keep the legal first name too, if you have it. |
| Shared family emails, typos and addresses that bounce. | ||
| Cell, Mobile, Phone | Mobile phone or home phone | Which number is a mobile, and carrier notes after the number. |
| Address, City, State, ZIP | Address fields | ZIP codes that lost their leading zero. |
| Birthday, DOB | Date of birth | Mixed date formats and placeholder dates. |
| Family, Household | Household (by household ID) | Grandparents or adult children in the same home. |
| Member, Status, Visitor | Membership type or status | Values that mean the same thing (“Member”, “Mbr”, “M”). |
| Baptized, Baptism date | Milestone with a date | A yes with no date, or a date with no yes. |
| Campus, Service | Campus | A service time isn’t a campus. |
| Allergies, Medical | A restricted field for children’s ministry | Who can see it after the move. |
| T-shirt size, School, Group | Custom field | Free text that should be a list of choices. |
| Notes | Notes, or split into fields | Several facts in one cell, and pastoral content. |
What not to import
- Pastoral and counseling notes. If you move them at all, put them somewhere only pastors can see, and only after you’ve decided whether to keep them.
- Prayer requests. People shared them at a particular time, and they don’t need to be carried into a new system.
- Columns nobody has touched in years, like a “2017 small group.”
- Bank details, card numbers or Social Security numbers. A church database shouldn’t hold them.
- Texting “consent” you can’t show. If all you know is that you have someone’s number, ask them again instead of assuming.
- People who asked to be removed. Put them on a do-not-contact list instead of quietly adding them back.
- Calculated columns, totals and formulas. Import the facts and let the new system add them up.
Running both systems side by side
Pick a cutover date. Before that date, the spreadsheet is still the official record, and the new system is a copy you’re checking. After it, every change goes into the new system only, and the spreadsheet becomes read-only. Rename it with “ARCHIVE” and the date, and take away edit access from everyone except one person.
The risky part is the overlap, when someone keeps updating the old file out of habit. Tell every ministry the date. Keep a short list of any changes made in the old file after cutover, and enter them by hand during the first two weeks. Keep the archive for at least a full year, so you can look things up when someone asks what you had before about a birthday, a baptism date or a household.
How this works in Sanctuary
In Sanctuary, you import with Move to Sanctuary, which is for Core administrators on paid plans. It takes CSV or Excel (.xlsx) files and reads them in your browser, and it only sends the people you choose to bring across. It matches your columns to its own fields, showing examples from your file. You can keep a column as a new custom field or milestone, or choose Don’t import. It also asks what each membership value in your file means in your own list of membership types. It groups people into households using a shared family or household ID column, flags rows with problems like future birthdays or invalid emails, and finds people who are already in Sanctuary. You can accept the strong matches all at once and decide on the uncertain ones yourself.
Importing doesn’t send any emails or invitations. For people already in Sanctuary, it only fills in blank fields and never overwrites anything. Until you mark the move as final, Undo removes only what the import added and clears what it filled in. It doesn’t bring texting consent across, so nobody you import gets a text until they agree to it. On the free Core plan, you can paste a list into Add many people instead, with name, email and phone. That list is checked against everyone already on file before anything is created. Afterward, Core administrators can merge any duplicates that slipped through, from the person’s profile or from the Core Overview.
What an import can’t fix
An import moves your data. It doesn’t decide what the data means. If nobody can tell you what “Active” meant in the old sheet, the new system won’t know either.
- Some history won’t fit any field. Expect to copy a few notes by hand or leave them in the archive.
- Automatic matching is cautious on purpose. Two records for one person are easier to fix later than one record that wrongly combines two people, so expect to do some merging after the move.
- Move to Sanctuary is part of Sanctuary’s paid plans. If you’re a small church with one clean sheet, Add many people or entering people by hand might be all you need.
- If your spreadsheet also has giving records, treat those as a separate project with your treasurer, and reconcile the totals before you trust any statement.
Sources
Microsoft Support, “Keeping leading zeros and large numbers” (Excel), support.microsoft.com.
CTIA, Messaging Principles and Best Practices (May 2023), section 5.1.2 on documenting opt-in consent, api.ctia.org.
See how Sanctuary keeps the work connected
Sanctuary keeps people, serving and giving on the same record. Core is free, with no limit on how many people you keep in it.