Migrating off a legacy church management system is the single most-feared project in church operations. The horror stories are real: lost giving history, broken statements, members who disappeared from the database, and a treasurer who had to redo six months of work. The good news is, with the right sequence and a calm head, it is genuinely manageable. Here is the playbook.
Why churches put it off
Most churches stay on a legacy ChMS years longer than they should. The reasons are universal: nobody has time to lead the migration, nobody fully understands what is in the current system, the giving history feels too sacred to risk, and the existing tool “mostly works.” All true. None of those reasons get easier next year.
The cost of staying is invisible: hours of staff time gone to workarounds, gifts mis-attributed, members not followed up with, reports nobody trusts, and AI capabilities you can’t use because the underlying data won’t support them.
Phase 1: Inventory what you have
Before exporting anything, write down what your current system actually contains. Not what it’s supposed to contain — what it actually contains today. Categories to inventory:
- People and families — including dormant records.
- Custom fields and tags — what they meant, who maintains them.
- Giving history — how many years, by donor, by fund.
- Pledges — active, completed, abandoned.
- Attendance history — service, group, kids.
- Group rosters — small groups, classes, ministries.
- Volunteer assignments — current and historical.
- Background-check records.
- Pastoral notes — what is there, who can see it, what should migrate.
- Communication history — emails sent, SMS sent.
- Saved reports and dashboards — which ones are still used.
This inventory is half the project. Most surprises in a migration come from data nobody knew was there.
Phase 2: Decide what to clean before you move
Migration is the cheapest moment to clean. After cutover, every cleanup is a database edit; before cutover, every cleanup is just an export filter.
Reasonable cleanup decisions:
- Mark dormant member records (no activity in 5+ years) as archived rather than migrating them as active.
- Resolve obvious duplicates (same email, same address, similar names).
- Drop custom tags nobody has used in two years.
- Standardize address formatting if you have the patience.
- Decide which historical pastoral notes really need to migrate — some don’t.
What to not clean: anything financial. Move giving history exactly as recorded. The audit trail and the donor’s tax record depend on it.
Phase 3: Get your exports
Most legacy ChMS platforms export reasonably well, even if grudgingly. The standard set:
- People & families CSV (with relationships preserved).
- Giving transactions CSV (one row per gift, with date, donor, fund, amount, method).
- Pledges CSV.
- Attendance CSV.
- Group rosters CSV.
- Custom fields, exported as additional columns or separate files.
If your current vendor makes export hard, that is a meaningful data point about the relationship. Ask early in the contract review what the export situation looks like — before you sign with anyone new, too.
Phase 4: Map and validate
The new platform’s import tool will ask you to map fields — old column to new column. This is where small mistakes become large ones. Best practices:
- Import a small sample first — 50 families, one month of giving.
- Spot-check the imported records against the old system, including totals by fund.
- Run a year-end statement on the test set in both systems and compare.
- Verify that recurring gifts, ACH/card splits, and refunds came through correctly.
Only after the sample is bit-exact should you do the full import.
Phase 5: Run in parallel (briefly)
For 2–4 weeks, run both systems in parallel for the things that matter most: giving entry and attendance. This is annoying. It is also the cheapest insurance available. Two weeks of double-entry is much cheaper than a year of explaining why the giving statements are off.
During parallel-running:
- Reconcile daily, not weekly.
- Treat any discrepancy as urgent — the longer it sits, the harder to find.
- Keep a written log of fixes; you will need it for the post-mortem.
Phase 6: The cutover sequence
The order matters. A clean cutover sequence:
- Week 0: Final clean export from the legacy system; final import to the new one.
- Week 1: Online giving switches to the new platform. Old giving links redirect.
- Week 2: Staff workflows (followup, attendance, scheduling) move to the new platform. Old logins disabled for these workflows.
- Week 3: Member-facing portal launches. Year-to-date giving is visible.
- Week 4: Communications (email, SMS) move over. Old templates archived.
- Week 6: Read-only access to the legacy system is preserved for reference; write access is shut down.
- Month 3: Legacy system is shut down entirely; final archive is downloaded and stored.
What to communicate to your church
Members do not need to know the architecture. They need to know what changes for them, in plain language:
- Where to give now, with the new link.
- That recurring gifts will continue uninterrupted (and confirm that this is true).
- Where to find their giving history and statements.
- How to log in to the new portal, with one clear instruction.
- Who to call if anything looks wrong.
One short message a week, for three weeks, beats one long message that nobody reads.
The most common mistakes
- Skipping the sample import. The full import goes wrong, and you have no clean baseline to roll back to.
- Cutting over giving the same week as everything else. If anything goes sideways, you have nowhere to fall back.
- Underestimating the recurring-gift continuity problem. Some processors require donors to re-authorize on a new platform. Find out before, not after.
- Letting the legacy system run forever in parallel. It becomes a shadow database that competes with the truth.
- Not assigning a single owner. Migrations need one accountable human, not a committee.
The bottom line
A church migration is a logistics problem, not a software problem. Inventory carefully. Clean what is safe to clean. Validate small before you commit big. Cut over in the right order. Communicate plainly to your church. Keep one person accountable. Six weeks later, you will wonder why you waited so long.