Choosing church management software without regretting it in a year

Most churches buy a church management system the same way: a staff member watches a demo, the feature list looks impressive, the board approves the line item, and eighteen months later the secretary is still keeping the real membership list in a spreadsheet because nobody could figure out where to put it in the software.

Almost every time, the cause is that nobody wrote down what the system had to do before the demo started.

Name the three jobs first

Before you look at a single product page, write one page answering this: what three things does this system have to do that we cannot do today?

For most congregations under 400 people, the honest answer is some combination of these six:

1. A member roll that one person maintains and everyone trusts. Names, households, addresses, phone numbers, membership dates, baptism records.
2. Attendance and check-in, mostly for children, mostly to satisfy the parents and the insurance carrier.
3. Giving records that produce a correct year-end statement without three weeks of reconciliation in January.
4. Groups and serving rosters, so the deacon over hospitality can see who signed up without emailing the office.
5. Email and text to the congregation, sent from the roll rather than from a separate list that drifts out of sync.
6. Service planning, meaning the order of worship, song keys, readings, and who is doing what on Sunday.

Rank those six. The top three are your requirements. Everything below the line is a bonus you will not pay extra for. Churches get in trouble when they buy for item six and then discover item one is clumsy.

The export test

Ask this question in every demo, before pricing: can I export every field, for every person, including giving history and custom fields, as a CSV, myself, without contacting support?

Then ask them to show it on screen. Not a promise. The actual button.

A vendor who exports cleanly is telling you they expect to keep you by being good. A vendor who routes exports through a support ticket, charges a data extraction fee, or exports people but not giving history has built a fence and you are the livestock. This one question predicts your next five years better than any feature comparison.

Run the same test on your current system before you migrate. If you cannot get your own data out of what you have now, that is the first project, and it is separate from choosing what comes next.

What the real options cost

Prices below were checked on 28 July 2026 on each vendor’s public pricing page. Verify before you sign, because these move.

Breeze charges $72 per month, flat, with no tiers by contact count and no contract. Giving is included at no monthly cost. Text messaging includes 250 messages a month, then $10 per 500. A worship tools add-on runs $29 per month. Breeze is the right answer for a church with one part-time administrator who wants the whole office in one place and does not want to think about modules. It is the wrong answer for a church that needs deep service planning or complex multi-campus structures.

Planning Center sells nine products separately, each with a free tier: People (free, unlimited database), Services (free for 5 team members), Check-Ins (free, 10 daily check-ins), Groups (free, 15 group members), Registrations (free, 5 attendees), Calendar (free, 1 room), Giving (free up to 10 donations a month), Publishing, and the Church Center member app. Giving then steps up by donation volume: $15 a month for 75 donations, $32 for 200, $69 for 500, $115 for 1,000, $179 for 1,500, and $239 for unlimited. A church plant can genuinely run People, Services, and the free tiers of the rest for nothing, then pay only for the module that outgrows its limit. Planning Center is the deepest option for worship and volunteer scheduling. The cost of that depth is that a small church can end up paying for four modules and using two.

Tithe.ly lists Free Giving at $0 a month, Church Management at $72 a month, an All-Access bundle at $119, a standalone church app at $89, and a website builder at $19. Premium onboarding is a $599 one-time fee. The bundle is the pitch; price the modules you actually need against it before you take it.

Rock RMS is open source and free to install. The cost is hosting and the person who maintains it. If your church has a working software developer among its members who has agreed in writing to a term of service, this is a real option. If your plan is “somebody in the congregation will figure it out,” it is not.

Covenant OS, our own church management system, is in development and not yet available. It is being built for congregations that want members, giving, service planning, and communications in one system without growth-industry framing. Until it ships there is nothing to buy, and nothing here should push you to wait. Choose from the list above and choose now.

Order of operations for the switch

Do not migrate in December, and do not migrate in the six weeks before Easter or Christmas.

1. Export everything from the old system. People, households, giving, attendance, notes, custom fields. Store the raw CSVs in a church-owned cloud folder and do not touch the originals.
2. Clean before you load. Deduplicate households. Kill the 60 records of people who left in 2019. Standardize phone formats. This takes a volunteer two evenings and saves a year of confusion.
3. Decide the household rule. Who counts as a household, how you record adult children living at home, how you handle divorced parents with shared custody in children’s check-in. Write it down. Every ChMS forces this decision and most churches make it accidentally.
4. Load people first, giving second, everything else after. Verify the person count matches before you import a single donation.
5. Run both systems for one giving cycle. One month, in parallel, comparing totals. Yes, it is duplicate work. It is also the only way you find the import that dropped 3 percent of your ACH gifts.
6. Set permissions before you invite staff. Decide who can see giving amounts by name. In most churches the answer is the financial secretary and one elder, and not the pastor. Set it that way on day one, because loosening later is easy and tightening later is a conversation nobody enjoys.
7. Write a one-page runbook. Where the data lives, who administers it, how to add a person, how to pull a directory, who to call. Keep it in the office, on paper.

What to skip

Skip anything sold on engagement scoring. A number that ranks members by how connected the software thinks they are will be wrong about the widow who calls three people a week and right about nobody. It also quietly teaches staff to treat the roll as a funnel.

Skip a system you cannot afford at double your current size, and skip a system you cannot afford at half. Churches shrink.

Skip the annual prepay discount in year one. Pay monthly until you have run a full giving cycle and a full check-in season. The discount is worth about one month; being able to leave in month four is worth more.

The test that matters after the sale

Six months in, ask the person who uses it most, alone, without leadership in the room: do you open this every week, or do you keep a spreadsheet? If there is a spreadsheet, the software lost, and no training will fix it. That answer costs nothing to get and tells you more than any dashboard.

Compare the same tools side by side in the church management directory, and price the giving side separately using what a giving platform actually costs.