Sanctuary compared with Church Community Builder
A Church Community Builder alternative now that CCB is Pushpay’s ChMS
Church Community Builder is now part of Pushpay. Pushpay calls the product ChMS, has retired the standalone CCB website, and offers it alongside Pushpay Giving, apps and Insights in a platform called ChurchStaq. Sanctuary is newer and smaller, with a free people database and plans you can sign up for on your own that add scheduling, service planning and giving, with check-in and Shepherd on the larger plans.
Competitor information reviewed from first-party sources on .
The practical difference
How to think about Sanctuary and Church Community Builder
Many CCB churches looking around aren’t missing a feature. They’re reacting to the changes around the product: a new name, a combined website, and CCB being packaged into Pushpay solutions. Pushpay says the ChMS is still an integral part of its product line and that it keeps investing in it. If you’re happy with where Pushpay is taking it, staying is a reasonable choice.
CCB is strongest in groups, process queues for follow-up, rooms and resources, and a large catalog of integrations, and those are hard to give up. Sanctuary is a better fit for a small or mid-sized church that mostly uses CCB as a people database with volunteer schedules and giving, and wants those connected without booking a demo before it can buy. Sanctuary’s importer already understands CCB’s exports, so it’s less work to try it.
An honest comparison
When Church Community Builder may be the better choice
- Your ministry runs on groups, and you use process queues to move guests, care needs and volunteers through follow-up.
- You book rooms and resources with approvals and per-room calendars inside the same system.
- You depend on integrations. Pushpay lists more than 80 of them with 44 partners.
- You want Pushpay Giving, a leader app and Pushpay’s reporting from the same company as your ChMS.
Consider Sanctuary
When Sanctuary may fit your church better
- You want people and household records, forms, event registration, the calendar and tasks free, with no limit on people.
- You want to get started on your own, without a demo. Start with free people records, then add scheduling, giving and Shepherd together in one plan when your church is ready.
- You want Move to Sanctuary to read CCB’s Export Individuals file and contribution reports, keep each Ind ID and link gifts to the right people.
- You want gifts charged on your church’s own Stripe account, which the church owns and can log into.
- You want event room booking that warns you about clashes, and follow-up tasks on a person, without building a bigger workflow system.
Before you switch
Questions to answer with your team
- Which CCB features does your staff use every week? Groups, process queues, forms, resources, check-in or scheduling?
- How much of your follow-up depends on process queues? Sanctuary has tasks on a person and live sheets, but nothing that works like process queues and no dedicated small-groups product.
- Which integrations can’t you do without, and could any of them be dropped if your records lived in one place?
- When does your current Pushpay agreement end, and does that leave you time to test with real data first?
Migration
A safer way to evaluate the move
- Choose the Pushpay ChMS (formerly CCB) option in Move to Sanctuary. It tells you which CCB people export to run and reads that file as it comes, keeping each Ind ID and keeping families together.
- Add giving as separate files. Move to Sanctuary reads CCB contribution exports and Pushpay Giving transaction files, and links each gift to its person by the CCB person ID.
- Make a list of every group, process queue and integration, and decide what will replace each one before you change anything.
- Moving in with Move to Sanctuary comes with paid plans. Check every match before you save, and keep the move undoable until you mark it final.
Continue evaluating Sanctuary
Sanctuary is not affiliated with Church Community Builder. Product names and trademarks belong to their respective owners.