Church management
A church management software implementation checklist
Switching church software takes more than an import. This six-week plan walks you through cleaning up your data, practicing your Sunday workflows and deciding whether you’re ready to launch.
How long should it take?
Plan on about six weeks, with one person in charge and one ministry trying it first. Don’t launch just because the import finished. Launch when staff can do the things that can’t go wrong on a Sunday, finance has reconciled the giving records, and every important set of data has an export or a backup plan.
Copy the headings below into your project tool and put a person’s name on every line, instead of “the team.” Work through them in order: agree on what “working” means, clean up the old data, set up the simplest version of each workflow that does the whole job, and then train people and launch.
Before you start: owners and goals
Name one person to run the project who can make decisions, one person who knows your people and household records, and an owner for each critical workflow: finance, children’s check-in, volunteer scheduling and communication. In a small church one person may cover several of these. Write the names down anyway.
- Set a launch date, plus a separate go-or-no-go meeting at least three business days before it.
- Write three results you can measure, like “a first-time guest becomes one clean person record” or “finance can reconcile a batch without fixing a spreadsheet.”
- List what you’re leaving out for now. Old notes, old registrations and every custom report can often wait for a later phase.
- Pick one ministry to go first, with a patient leader and real work every week.
- Agree how people will report problems and who decides whether a problem holds up launch.
The six weeks at a glance
- 1Week 1, inventory and scope: list every system, spreadsheet, form, integration, owner and recurring task you have now.
- 2Week 2, clean and map the data: decide what counts as active, merge duplicates, make households consistent, and note where every field will go.
- 3Week 3, set up the basics: permissions, teams, funds, forms, communications, check-in rules, service templates and default notifications.
- 4Week 4, pilot and train: run one ministry’s real work through the system, then train people by role on the tasks they actually do.
- 5Week 5, practice and reconcile: walk through a whole weekend, compare financial totals, test the exceptions and practice your backup plan.
- 6Week 6, decide, launch and settle in: hold the go-or-no-go meeting, switch over in the smallest safe step, and have someone staffing one place people go for help.
Week 1: list your systems and set the scope
Start with where your information lives today, before you look at the new product’s settings. That includes your ChMS and giving platform, and also the volunteer spreadsheet, the children’s allergy list, the newsletter list, paper connection cards, the shared calendar, your accounting software, and the private document someone updates after every baptism.
- For each one, note the owner, record count, export format, last updated date, and whether it holds sensitive information.
- Decide which source wins when two disagree. Don’t let the import order decide by accident.
- List every automatic email, text, webhook, payment, calendar sync and accounting handoff that could keep running after you switch.
- Decide what you’ll move, keep as a read-only archive, or leave behind on purpose, and write down why.
- Before anyone starts cleaning, export a dated backup and leave it untouched.
Week 2: clean up and map the data
Decide what makes two people duplicates, how households are set up, which contact detail wins, what “active” means, and which notes should come along. Work on a copy and keep the original export untouched.
- Merge the obvious duplicates. Flag the unclear ones for a person to decide.
- Make phone numbers, emails, dates, addresses, names and household relationships consistent.
- Split free-text fields that hold several facts. One “notes” column is rarely safe to map to one field.
- Decide exactly where consent, communication preferences, child safety information, giving funds and custom fields will go.
- Import a small sample, look at it in the new system, export it again and compare the two before the full import.
Week 3: set up for the roles you really have
Build the smallest setup that handles each launch workflow from start to finish. Start with permissions. A scheduler doesn’t automatically need giving history. A finance volunteer doesn’t need children’s medical notes. A ministry leader shouldn’t need administrator access.
- Create accounts by role and test each one while signed in as that role.
- Set up funds, giving categories, statements and reconciliation rules with your finance owner.
- Build one reusable service plan and one volunteer schedule, from the request through the reminder and a decline.
- Make a guest form and check that it matches an existing person instead of creating a duplicate.
- Set up labels, rooms, guardian matching, allergies, emergency contacts and check-out permissions.
- Check the default notifications so testing doesn’t message the church and launch doesn’t quietly message nobody.
Week 4: pilot one ministry and train by task
The pilot needs real people, real changes and someone who didn’t set the system up. Ask them to do their normal work without coaching. If only the person running the project understands a workflow, it isn’t ready.
- Train administrators on exceptions, exports, permissions, fixing duplicates and audit history.
- Train ministry leaders on the two or three tasks they own. They don’t need to learn every menu.
- Give volunteers one page showing how to respond, update their availability, check in, or do their part.
- Record short how-to videos only once the setup stops changing, so they match launch day.
- Keep a log of changes made during the pilot and who needs to be told.
Week 5: practice the weekend and the exceptions
Talk through a whole weekend together, from the first staff task through Monday follow-up. Include the hard cases: a late decline, a family who never registered, a donor using a different email, a printer that fails, the internet going down, and an urgent permission change.
- Reconcile the processor total, ChMS total, expected deposit, fees, refunds and accounting handoff.
- Produce a sample statement and check the household, funds, dates and totals.
- Test check-in and secure check-out with the real devices, printers, labels, rooms and network.
- Send scheduling requests and reminders to the pilot team, and check that replies show up for staff.
- Export current people, giving, scheduling and attendance data and make sure the files are usable.
- Practice the backup plan: paper check-in, attendance by hand, an offline contact list, or putting off a workflow that isn’t critical.
The go-or-no-go checklist
Don’t launch a critical workflow unless every statement that applies to it is true:
- Every critical workflow has a named owner, a trained backup and a written plan for when it fails.
- A representative sample was imported, checked and exported again, and nothing went missing that you can’t explain.
- Finance approved funds, donor matching, reconciliation, reports and statements.
- Children’s ministry approved permissions, guardian matching, labels, room rules and emergency access.
- Staff tested with their own permissions. Nobody is relying on a shared administrator login.
- The pilot finished a real cycle and anything blocking launch is fixed.
- Old automations are turned off or left on deliberately, and everyone knows which system sends each message.
- The church knows what’s changing, when, where to get help, and what isn’t changing yet.
Launch week and the first 30 days
- 1Within 24 hours: reconcile transactions and attendance, merge urgent duplicates, and post known problems with workarounds.
- 2After the first weekend: meet each workflow owner and sort problems into blocking, recurring or cosmetic.
- 3After two weeks: review permissions, undelivered messages, duplicate rates, unanswered requests and what people ask for help with.
- 4After 30 days: compare results with the goals you set before week one, then approve the next phase.
What this checklist doesn’t cover
We sell church software and wrote this guide. It can’t account for every church, legal requirement, accounting practice, safeguarding policy, processor contract or older integration. A multisite church, or one moving years of financial history, may need to run both systems side by side for longer and get outside help. Your finance, legal and child safety owners should approve decisions in their areas.
Software can’t decide who owns what. If nobody can sort out duplicate records, approve permissions or decide how a guest is followed up, those problems will move into the new system with you.
See how Sanctuary keeps the work connected
Sanctuary keeps people, serving and giving on the same record. Core is free, with no limit on how many people you keep in it.