How to migrate from spreadsheets or another ChMS without losing anything
A church data migration goes well when you export everything first, keep the old system readable, move people and households before anything else, and check the result with the people who know your church. Most of the risk is in duplicates and households, not in the file transfer. This guide gives a week-by-week plan that works whether you are leaving spreadsheets or another church management system.
The fear behind most delayed software switches is simple: "What if we lose something?" Years of member records, family connections, notes, attendance. It is a reasonable fear, and it is also very manageable. Data rarely disappears in a migration. What goes wrong is quieter: duplicates nobody merges, families split into strangers, and a new system that nobody trusts because the first thing they looked up was wrong.
This guide is a practical plan for moving your church's data, whether it lives in spreadsheets, a shared Google Sheet, or another church management system (ChMS). It applies whatever software you are moving to.
What should you do before you export anything?
Before exporting, decide who owns the migration and what "done" means. One person, often the church administrator, should own it, with a pastor or elder available to answer "is this the same person?" questions.
Write down three things:
- Where your data lives today. Most churches discover it is in more than one place: the ChMS, a kids' ministry spreadsheet, the worship leader's scheduling app, a list of small group rosters in someone's email.
- What you actually use. If nobody has opened the "spiritual gifts" custom field in five years, you do not have to carry it across.
- Your switch date. Pick a natural boundary, such as the start of a month or the week after a big season, and work backwards from it.
What data should you export from your current system?
Export everything you can, even the things you do not plan to import. A complete export is your insurance policy; you can always decide later that something was not worth moving.
At minimum, export:
- People: names, emails, phone numbers, addresses, birthdays, membership status, and any custom fields.
- Households or families: who lives with whom, and who the adults and children are.
- Groups and rosters, including who leads each group.
- Serving teams and upcoming schedules.
- Kids' information: guardians, allergies and medical notes, authorized pickups.
- Attendance and participation history, if you want insight into trends from day one.
- Giving records, kept safely even if you do not import them (more on that below).
Most systems export to spreadsheet files (CSV or Excel). Do not spend a weekend cleaning them first. Messy exports are normal, and the useful cleanup happens after import.
Store the exports somewhere private. These files contain your whole congregation's contact details, birthdays and children's medical notes. Do not email them around or leave them in a shared folder anyone can open.
Why are duplicates and households the hardest part?
Duplicates and households are hard because they need human judgment, not technical skill. A spreadsheet cannot know that "Bob Smith" at one email and "Robert Smith" at another are the same man, or that the Garcias who share an address are one family while the two Nguyens at the same address are a mother and her adult son who has his own household.
Do the duplicate review in one sitting, with someone who knows the congregation. Work through likely matches together and decide each one. Then review households the same way: check that children are attached to the right adults, especially in blended families and where custody matters for kids' check-in.
This is the part every rushed migration skips, and it is why people stop trusting the new system. Give it the time.
Should you migrate attendance history and old notes?
Migrate recent attendance history if you will use it, and leave the rest in a read-only archive. A year or two of attendance lets you see who has been drifting and how ministries are trending from your first week in the new system. Ten years of it rarely gets looked at.
Old free-text notes deserve a careful look before moving. Some contain pastoral information that should only ever be seen by a few people. If you bring them across, make sure they land somewhere with the same or tighter permissions than before.
Should you migrate giving history?
Usually, no: keep past giving where it is and start new giving cleanly. Giving records are financial records. Your old system or payment processor already holds them accurately, they tie to bank deposits you have already reconciled, and people will need statements that match what they received before.
A common pattern:
- Switch online giving at a clean month boundary, ideally the start of a calendar year.
- Keep the old giving system or processor readable for as long as you may need to issue statements or answer an audit question.
- Tell givers the date their recurring gifts move, and give them a simple way to set them up again.
What is a realistic migration timeline?
For most small and mid-size churches, a month is realistic from first export to the whole church on the new system.
| When | What happens | Who is involved |
|---|---|---|
| Before week one | Agree what moves; export everything; set up the new account | Administrator, pastor |
| Week one | Import people and households; duplicate and household review | Administrator plus someone who knows everyone |
| Week two | Roles and permissions; groups, teams and ministries | Staff and key ministry leaders |
| Week three | Kids check-in, events with payment, giving (if moving) | Kids ministry lead, treasurer |
| Week four | Invite the church; run a real Sunday | Everyone, with leaders going first |
A tiny church with clean spreadsheets can move faster. A church with thirty years of data in three systems will take longer. Both are normal.
How do you check that nothing was lost?
Check counts, then spot-check people you know. Counts first: compare the number of people, households, groups and group members in the old export against the new system. Small differences are expected (merged duplicates, archived records), but you should be able to explain every large one.
Then spot-check twenty people you know well, including:
- a large family with children,
- a blended family,
- someone with a recent change of address or name,
- a small group leader and their group roster,
- a child with allergy information.
If those twenty look right, the rest very likely do too. If one is wrong, find out why before moving on, because the same cause usually affects others.
How do you avoid confusing your congregation during the switch?
Import silently, then invite deliberately. Nobody in your church should get an email from the new system until you are ready. Run both systems side by side for a few weeks if you need to, and announce the change once, clearly, with a date.
The single biggest predictor of whether people adopt the new system is whether their leaders use it in week one. Ask your small group leaders, worship lead and volunteer coordinators to post first, so when members arrive there is something there for them.
How Churchory helps
Churchory is church management software for small and mid-size churches. Start free with Core (your people directory, families, roles and church-wide email and push), then add only the products you need, like groups, events, Sunday serving and check-in, kids, care, chat and voting, or get everything with Churchory One.
When you switch to Churchory, our staff run the migration for you, for free, from Planning Center, Breeze, CCB, Tithe.ly/Elvanto, Realm/ACS, Servant Keeper, ChurchTrac or spreadsheets. You request it from inside the app and upload your exports to a private, admin-only storage area. We bring across people and households, groups with rosters and leaders, upcoming events, serving teams and schedules, documents and kids' information, plus 12–24 months of attendance and participation history at summary level. Giving ledgers are deliberately not migrated: your previous system or processor stays the record of past gifts. Imports are silent, so nobody is emailed until you decide to invite them.
If you would rather bring in history yourself, Settings has a self-serve importer for past attendance (check-in, group and kids) and serving records from a CSV or Excel file. It has column presets for Generic spreadsheets, Planning Center and Breeze exports, shows you a preview before anything is written, never messages anyone, and can undo an import afterwards.
Read the full week-by-week plan on our switching page, see how Churchory compares on our comparison pages, or start with the free Core directory. If you are the one running the move, our page for church administrators is a good next stop.
Churchory products in this guide
Try Churchory free for 45 days
Pick only the products you need. No credit card, no contract, and help from the people who build it.
Frequently asked questions
How long does it take to switch church management software?
For most small and mid-size churches, plan on about a month from first export to the whole church using the new system. The file import itself takes hours; the time goes into cleanup, roles and inviting people well.
Will we lose data when we switch church software?
You should not, as long as you export a complete copy first and keep the old system readable until you have checked the new one. Nothing about importing into a new system deletes anything from the old one.
Should we migrate giving history to new church software?
Often it is better not to. Many churches keep their old system or payment processor as the record for past gifts, start new giving cleanly at a month boundary, and keep the old records available for statements and audits.
Should we clean our spreadsheet before importing it?
Do light cleanup only. Fix obviously broken columns, but do the real deduplication after import, when the new system can show you likely duplicates side by side.
Does Churchory charge to migrate our data?
No. Churchory staff run the migration for free from Planning Center, Breeze, CCB, Tithe.ly/Elvanto, Realm/ACS, Servant Keeper, ChurchTrac and spreadsheets, including 12–24 months of attendance and participation history.
How do we clean up duplicate people?
Use the merge tool: it combines duplicate records without losing their history, and an import always shows possible duplicates for review before anything merges. You can also download a spreadsheet of current values, change it, and upload it back with a preview of every change before it applies.
Who is Churchory for?
Churchory is for small and mid-size churches, and especially for the pastors, church administrators and ministry leaders who run them with a few staff and a lot of volunteers. Nothing in it assumes a full-time IT person: the kiosk, the sign-up links and the apps are built for the volunteer who was trained once and is standing at a table at 9:58 on a Sunday.