Switching

Church membership software for small churches: how to move off spreadsheets without losing anyone

What moves, what stays, what to import first, running both side by side, and a 30-day plan with a before-you-import checklist.

By Steven Chen · November 9, 2026 · 12 min read

When is it time to move a church off spreadsheets?

Spreadsheets are a fine way to run a small church, right up to the point where there are several of them and they disagree. You know you are there when the kids list, the email list and the member spreadsheet each have a different phone number for the same family. When a group leader texts you on Saturday for a roster. When the allergy notes live in one volunteer's Notes app. When the only full list is on a laptop that goes home with one person.

This article assumes you've decided to move. If you're still deciding, start with whether a small church needs church management software at all. If you're choosing between tools, the independent buyer's guide to church management software covers what to look for. Everything below is about the move itself, done so that nobody falls out of the list on the way.

What should move, and what should stay?

The first mistake is trying to move everything. Church membership software is a directory of people and the things they do together: households, groups, serving teams, attendance, kids information, and often giving. It is not your bookkeeping or your sermon archive. Decide up front:

Write your version of this table before you touch any data. It settles arguments later, and it shows how big the job really is. For most small churches that is a few hundred people, twenty households to untangle, ten groups and five serving teams.

Clean the list first

Never import a messy list. Every duplicate, every family split across four rows, every phone number typed three ways is harder to fix inside the software than in a spreadsheet, and you'll be fixing it in front of people trying to use the new system. The full method is in how to clean up your church member list in an afternoon. The short version: gather every list into one sheet, one row per person, give each person a household and a status, merge duplicates, drop the fields you don't use, and make a copy before you start.

Budget a week for this. It is the step most likely to be skipped, and the step that decides whether the move goes well.

Households and duplicates

Households are the part spreadsheets handle worst, so they deserve their own pass. A household is the people at one address who should be treated as a family: for mailing, for kids check-in, for "the Parks are bringing dessert." Add a Household column and give every row a household name. Pick one adult as the primary contact. Children belong to a household even with no email and no phone, and adult children who have moved out get their own.

Then duplicates. The same person appears three times because they filled in a welcome card, joined a group and signed a kid in, and each list spelled the name differently. Sort by last name, then by phone, then by email, and look for near matches. Watch for the traps that fool an import:

• A couple who share one email address. Many imports treat them as one person or refuse the second. Give one of them a blank email instead.
• Nicknames and legal names: Bob and Robert, Beth and Elizabeth. Decide which the directory shows and put the other in a nickname field if you have one.
• Hyphenated and changed surnames. Search by first name and phone, not by surname.
• Phone numbers with and without a country code, or with dots instead of dashes. Make them one format before import.

For each duplicate, keep the row with the most recent contact details, copy anything missing into it, and delete the rest. Do it in one sitting. The payoff is a directory with real households rather than a shared surname, which is what the People directory in Churchory is built around, and what most software expects on import.

What should you import first?

Order matters because everything else points at people. A group roster is a list of people. A serving team is a list of people. An attendance record is a person and a date. Import in this order and each step lands on something that exists:

1. People and households. Import a test batch of ten first, ideally your ten messiest households. Check that the families came through as families, the phone numbers dial, and the statuses are right. Fix the spreadsheet, not the software, then import the rest.
2. Groups. Create each group, name its leader, and add the roster. A roster name that isn't in the directory yet is a person you missed in step one. Add them to the people list first.
3. Serving teams. Create each team and its members, then enter the current schedule, not the history. If you're rebuilding the schedule anyway, the guide to making a volunteer schedule people keep is a good moment to fix the rotation.
4. Attendance. Enter this year's Sundays if you have them, or start fresh from the first Sunday on the new system. Old attendance belongs in the archive.
5. Kids details and giving, if they move. Allergies, pickup notes and medical flags go in last, with access limited to the kids team. Giving history goes in only if you're using a giving product, and only after people are stable, because every gift attaches to a person.

Before you import: a checklist

• A dated backup copy of every original spreadsheet, somewhere you won't edit it
• One row per person, no household rows, no blank rows between sections
• A Household column filled in for every row, and one primary contact per household
• A Status column with a short, consistent set of values (member, regular, guest, inactive)
• Every phone number in one format, every email lowercased, no shared emails
• Every date (birthdates, join dates) in one format, with the year
• Column headings that match the software's import template, in the same order
• A ten-row test import done, checked and corrected
• The roles decided: who is an administrator, who leads which group, who sees kids details, who sees giving
• A cutover date written on the calendar, two to three weeks after the main import

How do you run both side by side?

For two to three weeks after the main import, the spreadsheet and the software both exist, and that is the most dangerous stretch of the move. Someone updates a phone number in one and not the other, and you're back to two lists that disagree.

Make one person the owner of every change during this window. New family on Sunday, changed address, someone leaving a group: it goes to that person, who enters it in both places the same day. Everyone else reads from the software and sends changes to the owner. Tell the leaders this twice.

Once a week, check the two against each other. Count the people and households in each. Pick ten people at random and compare field by field. Pick two groups and compare rosters. Fix what differs, in both. By the third check there should be nothing to fix, and that is your signal to cut over. Don't let the window run past a month: double entry wears people down, and the longer both exist the more likely someone treats the spreadsheet as the real list again.

How do you tell the congregation?

Most of the church doesn't care which software you use. They care about three things: what changes for them, whether their information is safe, and who to ask when something looks wrong. Answer those three in one plain message, two weeks before cutover, in every channel you have: from the front on Sunday, in the bulletin, by email, and in whatever group text people actually read. If you have a communication plan, this is a normal announcement in it.

Tell them what they get: the directory on their phone, their group and serving schedule in one place, and one form to update their details. Tell them what you need: check your household's details, and install the app if there is one. Tell them who sees what, in a sentence: leaders see their own groups, the kids team sees kids details, and nobody sees giving except the people you name. Offer a way to opt out of the directory, and honor it.

Then put a table in the lobby for two Sundays with two patient volunteers and a sign that says "Check your details here." Most corrections and app installs will come from that table.

How do you train volunteers on their phones?

Train people on the device they'll use on Sunday morning, which for almost every volunteer is their own phone, not the office laptop. A group leader who learned attendance on a desktop will not find the button at 9:58 on a phone in a noisy hallway. Keep sessions to ten minutes, after a service, and give each person one task to learn:

• Group leaders: open your roster, take attendance, log a prayer request.
• Serving team leads: see this month's schedule, approve a swap.
• Kids team: check a family in, read the allergy flag, read the pickup code.
• Greeters: look up a family, add a first-time guest.

Have each person do the task on their own phone while you watch, not watch you do it. Print a one-page sheet per role with screenshots and pin it where that team gathers. Pair anyone nervous with a teenager. Repeat the session once, two weeks later, for the people who missed it.

A 30-day migration plan

Thirty days is realistic for a church of a few hundred with one part-time administrator. A church of sixty can do it in two weeks. One with years of giving history should allow six weeks and move giving last.

What do you do with the old spreadsheets?

On cutover day, do four things to every old list. Rename it with ARCHIVE and the date at the front of the file name. Make it view-only, with edit access for the administrator alone. Move it into one archive folder only the administrator can open. And delete every other copy: the one on the kids coordinator's laptop, the one the treasurer emailed to himself, the export on the pastor's phone. Those copies are the privacy risk, and the ones someone will quietly keep updating.

Keep the archive for a year, or whatever your retention policy or denomination requires, then delete it. Shred paper forms once every name is confirmed in the software. Give old group texts one last message: "This group has moved to [place]. Here's how to find it." Then mute it.

When a spreadsheet is enough

If your church is forty people, one person keeps the list, and there are no groups or kids classes to roster, a single clean spreadsheet with a single intake form does the job. Clean it once, route every new name through one form, and don't move until something in the first section of this article starts to hurt.

When software helps

The move pays off the moment more than one person needs the list, somewhere other than a desk. A group leader checking a roster on a phone, a kids volunteer who needs the allergy flag without every family's address, a serving team that swaps a Sunday without texting the pastor. Software gives you one directory, roles that decide who sees what, and a phone in every pocket that shows each volunteer their part of it.

If you're switching from another system rather than from spreadsheets, the steps are the same with one change: export everything as CSV first, and ask the new vendor whether they'll run the import for you. Churchory's guide to migrating church data without losing anything covers the export side in more detail.

If you want to start with Churchory, Core (the directory, households, roles, and church-wide email and push) is free forever, and each product you add has a 45-day trial with no card at app.churchory.com/signup.

Common questions

How long does it take to move a church from spreadsheets to church management software?

About a month for a church of a few hundred people: a week to clean the list, a week to import people and groups, and two to three weeks running the old and new systems side by side before you switch off the spreadsheet.

What church data should be moved into membership software first?

People and households first, because everything else points at them. Then groups, then serving teams, then this year's attendance. Leave old attendance, old giving and the budget spreadsheet for later or for the archive.

Should a church keep its old spreadsheets after switching software?

Keep one read-only archive copy in a folder only the administrator can open, for a year or whatever your retention policy says. Delete the working copies, including the ones on personal laptops and phones, the day you switch.

How do you switch from one church management software to another?

Export everything as CSV, clean it in a spreadsheet, and import it in the same order: people, groups, teams, attendance. Ask the new vendor whether they will run the import for you; some do it for free.

How much does church membership software cost for a small church?

Pricing models differ. Some charge by the number of people in your database, some a flat price per feature. Churchory's Core directory is free and each product is $250 a year with no people-count tiers. Compare on what you will actually use.

Small Church Admin is written by the team behind Churchory. Choosing software? Read how a small church should choose church management software.