Church management software: a practical guide for small and mid-sized churches

The short answer

Church management software (a ChMS) is the system of record for the people in your church and the work you do with them: profiles and families, forms and events, volunteer schedules and service plans, communication, and giving. For a small or mid-sized church, the right one is whichever keeps those things in one place, because almost every problem a church has with its software is the same problem — the same person exists in four systems and none of them agree.

That means the question to ask is not "which has the longest feature list", but "how many times will we type the same fact". A system that does eight things adequately and shares one record will beat three excellent tools that never speak.

The workflows a church management system should cover

Feature lists are easy to pad. Workflows are not. Walk each of these end to end in a trial, with your own data, before you judge anything:

• People and families. One profile per person, joined into households, with the history attached — not a spreadsheet export with a "notes" column.
• Forms and events. A form that creates or updates a person rather than landing in a separate inbox, and a registration that shows up on that person's record.
• Volunteer scheduling. Building teams, asking for availability, sending requests, and seeing who actually replied — including who declined and has not been replaced.
• Service planning. The order of service, who is on it, what songs are in it, and what the stage sees, ideally in the same place as the schedule.
• Communication. Email and text that reach the same people your records already describe, without maintaining a second list.
• Giving. Online and recurring gifts, funds, pledges, reconciliation, and year-end statements tied to the same person record.

The joins between those rows are the product. If adding someone to a team does not update their profile, or a gift does not appear on the giver's record, you have bought several tools in one invoice.

How to read the pricing

Church software is usually priced one of three ways, and each one fails a different church:

• Per person in the database. Punishes you for good record keeping. Churches on these plans quietly stop adding guests and archive people they should be following up, which is the exact opposite of what the system is for.
• Per module. Predictable, but check what happens when you only want two of five — and whether the modules you skip leave holes in the ones you keep.
• Percentage of giving. Fine in a slow month, expensive in a good year. Work out what it costs at your actual annual total, not your monthly average.

Then ask the questions the pricing page will not answer: what does it cost to get your data out, is support included or a tier, and what happens to your giving records if you leave. A vendor who is relaxed about export is telling you something.

What migration actually costs

The software is rarely the hard part. The two costs churches underestimate are the state of the data and the patience of the volunteers.

On data: whatever you export will contain duplicates, dead email addresses, and families that stopped being families some years ago. Migrating it unchanged moves the mess rather than fixing it. Budget a pass to merge duplicates and decide what "active" means before anything is imported, because every report you run afterwards inherits that decision.

On people: your volunteers did not ask for a new system. A migration that lands the week before Christmas, or in the middle of a building project, will be remembered as the software's fault. Move in a quiet season, keep the old system readable for one full giving year, and switch one ministry first rather than all of them at once.

A checklist you can take into a demo

Ask a salesperson to do these in front of you, in a trial account, with ten of your own people in it:

1. Add a visitor from a form, without typing them twice.
2. Put that person in a family, and see the family from each member.
3. Schedule them to serve, and show what happens when they decline.
4. Find every volunteer who has not replied to this Sunday.
5. Record a gift and see it on the same person's record.
6. Produce a year-end giving statement for one household.
7. Export everything, and open what comes out.
8. Do all of it on a phone, because that is where your volunteers are.

Anything that needs "we can do that with a custom report" or "that is on the roadmap" is a no for the season you are in.

Honest limits — including ours

Every system in this category has edges, and a guide written by a vendor is worth very little if it hides its own. Three of ours, plainly:

• Your links live on onesanctuary.app, not your own domain. This is deliberate — text messages from a shared, well-behaved domain are far less likely to be filtered by carriers than from dozens of new per-church ones — but if a custom domain is non-negotiable for you, it is a real difference.
• Shepherd, our AI assistant, is available to administrators and staff with the right permissions, not to every volunteer. It acts with the permissions of the person asking, which is the point, but it does mean it is not a congregation-facing feature.
• On an iPhone, completing a gift opens your browser rather than staying in the app. That is an App Store requirement for donations, not a choice we made, and it applies to everyone shipping a church app.

More generally: no church management system fixes a process nobody owns. If no one is responsible for merging duplicate people or following up guests, the software will simply record that fact more accurately.

Where to start

Start with the workflow that is costing you the most hours right now. For most small churches that is either the weekly scramble to fill serving slots, or reconciling giving by hand. Fix one, keep the same person record underneath it, and add the rest when the church is ready rather than when the contract renews.