Skip to content

Choosing church management software without regretting it in a year

The three jobs a ChMS has to do, the export test that predicts your exit, Breeze, Planning Center, Tithely and Rock RMS prices read on 29 July 2026, and a migration order that keeps the office open.

Church Posting 9 min read Software and tools

Updated


Three people around a table of printed pages and a laptop in a wood paneled church office
Illustration made for Church Posting

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.

One question at the top, whether you can export every field for every person including giving history and custom fields as a CSV yourself without contacting support, branching into the four answers a vendor gives. Only the first, yes and here is the button, is clean. A support ticket, a data extraction fee, and people but not giving history are all treated as a no. Two closing panels say to run the same test on your current system first and to ask the person who uses the software most, six months after the sale, whether they still keep a spreadsheet.
Three of the four answers are the same answer. Sort the vendors by which box they land in before you look at a single price.

What the real options cost

Prices below were read off each vendor’s own public pricing page on 29 July 2026, and each is linked so you can check it against today’s. Verify before you sign, because these move.

Breeze charges $72 per month, flat, with no tiers by contact count and no contract: the page says “No setup fees. No contract. Cancel anytime.” Giving is $0 a month with unlimited donations. Text messaging includes 250 messages a month, then $10 per 500. A Worship Tools add-on runs $29 per month, and Breeze also sells a bundle of the ChMS with Worship Tools, Church Apps and Sites at $119 per month (Breeze pricing). 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. Note what the flat rate means in both directions: a 900-member church pays the same $72 as a 90-member church, which is a bargain at the top of that range and an overpayment at the bottom compared to a stack of free tiers.

Planning Center sells its products separately, each with a free tier: People free with an unlimited database, Services free for 5 team members, Check-Ins free to 10 daily check-ins, Groups free to 15 group members, Registrations free to 5 attendees, Calendar free with 1 room, Giving free up to 10 monthly donations, Publishing free at the Essential level, and the Church Center member app free. Music Stand is listed as a $5 per month add-on, and the page states “No contracts” and “Cancel anytime” (Planning Center pricing). 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 (Planning Center Giving). 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. Where each of those free tiers actually stops is the whole subject of free church management software.

Tithely lists Free Giving at $0 a month, Church Management at $72 a month, an All-Access bundle at $119 marked down on the page from $228, a Custom Church App at $89, and a Custom Church Website at $19. Premium onboarding is a $599 one-time fee, described as five video training sessions, 60 days of support, and data transfer help (Tithely pricing). The bundle is the pitch. Add up the modules you would actually turn on before you take it, because $119 beats $72 plus $89 plus $19 only if you were going to run all three.

Rock RMS is open source. Its site presents two paths: managed cloud hosting where “Our hosting partners handle installation, updates and maintenance,” or “Install Rock on your own server. For teams with technical experience,” and it prints no price on the home page (Rock RMS). The software is free to install and the cost is hosting plus 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.

A one-year calendar bar with two hatched closed seasons, the six weeks before Easter on 28 March 2027 and mid-November through the end of December, leaving open windows of six and thirty-three weeks. Beneath it, the seven migration steps laid out across seven weeks, where step five, running both systems through one full giving cycle, occupies four of those weeks on its own.
The seven steps take seven weeks because one of them is a calendar month you cannot compress. Count backward from the closed season, which usually means starting in April or waiting until next year.
  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. The four tiers of member data and who should see each are laid out in protecting the data a church holds about its members, and that post is also where the counseling-notes rule lives, which is the one migration mistake you cannot undo.
  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.

Where this decision touches the rest of the stack

A ChMS is one of four purchases, and buying them in the wrong order is how a church ends up paying twice.

Giving is priced separately and the rate matters more than the subscription, so run those numbers with what giving platforms actually cost your church. The general ledger is a different product from the member roll, and a ChMS with a giving module is not an accounting system; church accounting software covers fund accounting and where the two systems have to meet. Room and volunteer scheduling is the piece most often bought twice, once inside the ChMS and once as a calendar tool, and church event planning software prices that side. If the reason you want a system is to know who is actually attending, read average attendance hides whether your church is growing or shrinking first, because the counting method matters more than the database.

Compare the same tools side by side in the church management directory.

Sources

  • Breeze pricing, $72 per month flat, giving $0, 250 texts then $10 per 500, Worship Tools $29, bundle $119. Checked 29 July 2026.
  • Planning Center pricing, free tier limits by product, Music Stand $5 per month. Checked 29 July 2026.
  • Planning Center Giving, subscription tiers by donation count. Checked 29 July 2026.
  • Tithely pricing, Church Management $72, All-Access $119, app $89, website $19, onboarding $599. Checked 29 July 2026.
  • Rock RMS, open source, hosted or self-hosted, no price printed on the home page. Checked 29 July 2026.

Rock RMS publishes no figure for hosted Rock on its home page, so this post states none. Ask a hosting partner directly and budget the maintainer’s time alongside the invoice.


Back to top