How to Choose Church Management Software (ChMS): A Buyer’s Checklist

A church management system (ChMS) is the shared database and toolset behind the weekly life of a church: who belongs, who came, who gave, who serves and who needs a phone call. Most products share the same modules. They differ in depth, and in whether everything comes in one package or as paid add-ons.

Start with people and problems, not features. Before you visit a single vendor website, answer these questions with the people who will use the system.

• Who will use it, and how often? The pastor weekly, the administrator daily, the treasurer at month end, volunteers on Sunday morning.
• How big is your church, really? Count everyone you would store, visitors and children included. Many pricing tiers use this number, not formal membership.
• What hurts today? Duplicate spreadsheets, lost visitor cards, giving totals rebuilt by hand every January, rotas that live in someone’s inbox. Name the three biggest pains.
• What must not break? Your bank reconciliation, a report your denomination needs, the way your board approves the budget.
• Who decides and who pays? Agree on the budget range and the final decision-makers before the demos start.

These criteria separate a system you will still like in five years from one you will leave in two. The last column is what to ask each vendor.

Accounting deserves a closer look. Some products record gifts and leave the books to a separate accounting package; others include full double-entry bookkeeping. If your treasurer is happy with dedicated accounting software, a clean export of giving is enough. If the books live in a spreadsheet, an integrated ledger with a simple mode saves double typing. UK churches that claim Gift Aid should also ask how declarations are recorded.

In the European Union and the United Kingdom, data protection is not optional for churches. Under the GDPR (and the UK GDPR, which is materially the same on these points), church membership reveals religious belief, a special category of personal data under Article 9.

Article 9(2)(d) lets religious not-for-profit bodies process data about their members, former members and people in regular contact with them, in the course of their legitimate activities and with appropriate safeguards, provided the data is not disclosed outside the church without consent. A church may keep a membership database; its tools must respect those conditions.

• The vendor is a processor. A company handling data on the church’s behalf is a processor under Article 28 GDPR and must sign a data processing agreement (DPA) with the church. No DPA, no deal.
• Know where the data goes. Hosting, email and payment providers are sub-processors. Transfers outside the EU/EEA need a legal mechanism, such as an adequacy decision or standard contractual clauses.
• Look for built-in tools for individual rights. Exporting or erasing one person’s data, consent records and an audit log should be features, not support tickets.
• Check permissions. Pastoral notes, prayer requests and giving should be visible only to the people who need them.

Vendors charge on different bases, so compare them for the same church size, over the same period, with everything you would actually switch on.

Online giving has its own cost. Payment providers charge a fee per gift and some vendors add a platform fee on top; ask for both, and whether donors can cover them. For each shortlisted product, estimate:

• The subscription at today’s size and at one and a half times that size.
• Every add-on module you expect to need within two years.
• Payment and platform fees on a year of your current online giving.
• One-off costs: setup, data migration and training.

Copy this questionnaire, delete what doesn’t apply to your church and send the same version to every vendor on your shortlist. Written answers are much easier to compare than impressions from a demo.

CHURCH MANAGEMENT SOFTWARE: VENDOR QUESTIONNAIRE
Church: ______________   Contact: ______________   Date: __________

About us: [number of people we would store], [who will use it: pastor,
administrator, treasurer, volunteers], [must-haves from our brief]

DATA PROTECTION AND HOSTING
1. Will you sign a data processing agreement with our church?
   Please send us a copy.
2. In which countries are our data and backups stored?
3. Who are your sub-processors (hosting, email, payments, support
   tools), and where does each one operate?
4. How is our data encrypted, who on your team can access it,
   and is that access logged?
5. How do we export or erase the data of one person who asks us to?

PORTABILITY
6. Can an administrator export all our data (people, families,
   attendance, giving, notes, files) without contacting you?
   In which formats?
7. What happens to our data if we cancel, and for how long can we
   still download it?

PRICING
8. What will we pay per year at our size today, and at one and a half
   times that size? Which modules or users cost extra?
9. What fees apply to online giving (yours and the payment
   provider’s)? Can donors choose to cover them?
10. Is there a minimum contract term? How do we cancel?

FIT AND DAILY USE
11. Can you demo these scenarios with us: registering a new family,
    recording Sunday’s attendance and offering, scheduling next
    month’s volunteers?
12. Do you support simple and double-entry bookkeeping, restricted
    funds and year-end giving statements?
13. Which interface languages are available, and can each user
    choose their own?
14. What can a volunteer do from a phone?
15. How do permissions work? Can we limit who sees pastoral notes
    and giving?

MIGRATION AND SUPPORT
16. Can you import our spreadsheets or our current system’s export?
    Who maps the data, and at what cost?
17. How do we reach support, in which languages, and what response
    time should we expect?
18. What have you shipped in the last six months, and what is next?

A scoring matrix keeps the most polished demo from winning by default. Weight each criterion from 1 to 3, rate each product from 1 to 5, multiply and add up.

Example: export weighs 3 and Product A gets a 4, so that line is worth 12. Set weights before the demos, let each person score alone, and drop any product that fails a must-have, whatever its total.

1. 1

   Write your brief

   One page, agreed with the people who will use the system.

2. 2

   Build a shortlist of three

   Three products are enough to compare and few enough to test properly.

3. 3

   Send the questionnaire and book demos

   Ask to see your scenarios, such as registering a new family or recording Sunday’s offering, rather than the standard tour.

4. 4

   Trial with real data

   Import a real subset: fifty people, a month of giving, one rota. Demo data always looks good; yours shows the gaps.

5. 5

   Involve your treasurer and a volunteer

   Let the treasurer close a month, and a volunteer check in a family on their phone, without help.

6. 6

   Test the export

   Export everything from the trial and open it. If the file is incomplete or unreadable, you have your answer.

7. 7

   Decide and plan the migration

   Set a switch-over date, clean your data before importing, run both systems for a few weeks and train people in short sessions.

Red flags during the evaluation:

• No data processing agreement, or vague answers about where data is stored.
• Export only through support, only partial, or only for a fee.
• Prices only after a sales call, with no written quote.
• Long contracts with automatic renewal and no way to leave early.
• Demos that avoid your scenarios and stick to a script.
• No visible product changes in the past year.

Mistakes churches often make:

• Choosing on price alone, or on the longest feature list.
• Letting one enthusiastic person decide for everyone.
• Importing messy spreadsheets as they are, duplicates and outdated records included.
• Switching every module on at once instead of starting with people, attendance and giving.
• Forgetting to tell the congregation what data the church keeps, and why.

To see how one product answers these questions, here is Assemblea, the platform that publishes this guide. Hold us to the same questionnaire as everyone else, and read our comparison with other church management systems.

• One platform, not add-ons: members and families, attendance and calendar, online giving via Stripe with recurring gifts, accounting with a simple mode and double-entry, a standard church chart of accounts and annual giving statements, volunteers and rotas, small groups, email and WhatsApp communications (where configured), child check-in, service planning, members’ meetings with digital voting and generated minutes, a member portal and statistics.
• Data protection: EU hosting, GDPR by design (consent records, export and erasure for individuals, audit log) and four permission levels per section (security).
• Portability: full church data export, spreadsheet import and presets for exports from several other church management systems (import).
• Languages and devices: six interface languages (English, Italian, Spanish, French, Brazilian and European Portuguese); it runs in the browser on any device.
• Pricing: a free plan for up to 50 members and paid plans with prices adapted to each country (pricing). Online giving carries a 1% platform fee plus Stripe’s own fees.