How to Migrate Between Church Management Software Platforms

Switching church management software feels like moving houses while the family is still living there. Everything has to keep working while you're transferring the furniture. Miss something important, and you'll hear about it for months.

I've talked to dozens of church administrators who've been through this process. Some sailed through in four weeks. Others spent six months fixing data problems they didn't catch until after going live. The difference wasn't luck. It was preparation.

This guide walks through the migration process step by step, with specific attention to the things that go wrong when churches try to rush.

Before You Start: Audit What You Actually Have

Most churches don't know exactly what data lives in their current ChMS until they try to leave it. Before reaching out to new vendors, run an internal audit.

Member Data Inventory

Take stock of what you're working with:

• Total member/family records: This affects pricing on most platforms
• Active vs. inactive: Do you really need to migrate people who haven't attended in five years?
• Custom fields: List every custom field you've created. The new platform may not support all of them.
• Member photos: How many exist? Are they stored in the system or just linked?
• Documents and files: Background check forms, volunteer applications, signed policies

Giving Data Inventory

Giving history is sacred. Get this wrong and you'll spend December manually recreating giving statements.

• Years of history: How far back does your giving data go? Do you need all of it?
• Fund structure: General fund, building fund, missions, benevolence — list them all
• Recurring giving setups: These usually don't migrate. Donors will need to re-enroll.
• Pledges and commitments: Are these tracked in your current system?

Groups and Ministry Data

• Small groups: Names, leaders, members, meeting times
• Ministry teams: Volunteer assignments, roles, schedules
• Attendance records: Service attendance, group attendance, check-in history
• Event history: Past events with registration data

Write all of this down. When vendors tell you what they can and can't import, you'll know exactly what you're losing.

The Migration Timeline: Plan for 6-8 Weeks

Churches that try to migrate in two weeks usually regret it. Here's a realistic timeline:

Week 1-2: Data Export and Cleanup

Export your data from the current system. Most platforms export to CSV files. You'll likely get separate files for:

• Member/family records
• Giving transactions
• Groups and group memberships
• Attendance records
• Volunteer information

Critical step: Open these files in Excel or Google Sheets before importing. Look for obvious problems: duplicate records, weird formatting, missing data, special characters that might cause import errors.

This is also when you clean up your data. That family who moved away three years ago? Mark them inactive. The 47 test records from when you were learning the system? Delete them. Migrating clean data is dramatically easier than cleaning it up afterward.

Week 3-4: Import and Verification

Most vendors offer migration assistance. Take them up on it. Let them handle the import, then verify the results obsessively.

Verification checklist:

• Member count: Does the total match what you exported?
• Random spot checks: Pick 20 random families and verify all their info transferred correctly
• Giving totals: Run a giving summary report. Does the total match your old system?
• Group memberships: Check a few groups. Are the right people in them?
• Photos: Did they actually import, or do you have blank placeholders?

Don't skip the spot checks. Aggregate totals can look fine while individual records are scrambled.

Week 5-6: Staff Training

Your staff needs to learn the new system before you go live. This isn't optional, and "they'll figure it out" is a recipe for frustrated phone calls during service.

Focus training on daily tasks:

• Adding new visitors and members
• Recording attendance
• Processing giving (if applicable)
• Running the reports they use every week
• Sending email/text communications

Most vendors offer training sessions. Schedule them during weeks 5-6 so staff can practice on real data before go-live.

Week 7-8: Parallel Operation

Run both systems simultaneously for at least two weeks. Yes, this means extra work. But it also means you can catch problems before they become catastrophes.

During parallel operation, any new data (new visitors, new giving, attendance) should be entered into both systems. At the end of each week, verify the new data matches in both places.

Only shut down the old system when you're confident the new one is working correctly. Keep the old system accessible (even if just read-only) for at least six months. You'll need to look something up.

What Usually Doesn't Migrate Well

Some data transfers cleanly. Other data is a mess. Set expectations early.

Usually Works Fine

• Basic contact information (names, addresses, phone numbers, emails)
• Family relationships (who's in which household)
• Giving transaction history (amounts, dates, funds)
• Group names and basic membership

Often Problematic

• Custom fields: Your old platform's custom fields rarely map 1:1 to the new one
• Attendance history: The data structure varies wildly between platforms
• Check-in history: Usually doesn't transfer at all
• Volunteer service records: Who served when, in what role
• Group history: When people joined/left groups
• Notes and communications: Free-text notes on member records

Almost Never Works

• Recurring giving setups: Donors will need to re-enroll in the new platform
• Event registrations: Past event data rarely transfers
• Workflow automations: You'll rebuild these from scratch
• Email templates: Usually not exportable

Ask your new vendor specifically about each category. "Can you import our data?" is too vague. "Can you import five years of attendance history from Planning Center?" gets you a useful answer.

Migration Support: What to Ask Your New Vendor

Not all vendors handle migration the same way. Before committing, ask these questions:

1. Do you offer migration assistance, and what does it include?

   Some vendors import your data for you. Others hand you documentation and wish you luck. Know which you're getting.

2. Is there an additional cost for migration support?

   Migration fees of $200-500 are common. That's usually worth it.

3. Can you show me a sample import from my specific old platform?

   If they've migrated churches from your current ChMS before, they should know exactly what works and what doesn't.

4. How long does migration typically take?

   If they say "a few days," push back. That's either unrealistic or they're not including verification time.

5. What data won't transfer?

   An honest vendor will tell you upfront what you'll lose. Vague promises are a red flag.

Platform-Specific Notes

Migrating FROM Planning Center

Planning Center has excellent export tools. You can export most data as CSV files directly from the admin dashboard. Give history, people data, and groups all export cleanly.

Migrating FROM Breeze

Breeze exports to CSV and includes giving history. Their export format is relatively straightforward. Photos export as a ZIP file.

Migrating FROM Church Community Builder (CCB)

CCB exports can be more complex due to the platform's depth. Groups, processes, and custom fields often require extra attention during import.

Migrating FROM Legacy/Desktop Software

If you're coming from older desktop software (like older versions of ChurchTrac or PowerChurch), expect more manual work. These platforms often don't have modern export options. Budget extra time for data cleanup.

Giving Migration Deserves Extra Attention

I can't stress this enough: giving data requires special care. Here's why:

• Tax implications: Donors use your giving statements for tax deductions. Errors create real problems.
• Recurring giving: Recurring donations almost never transfer. You'll need to communicate with donors and help them re-enroll.
• Fund mapping: Your old funds need to map to new funds. "Building Fund" in the old system should become "Building Fund" in the new system, not "General Fund."
• Donor matching: Giving records need to attach to the right people. If John Smith in the giving export doesn't match John Smith in the member import, you have orphaned donations.

After importing giving data, run a summary report for the past 12 months. Compare totals to your old system. Then spot-check 10-15 individual donors to verify their giving history imported correctly.

Communicating the Switch to Your Congregation

Your congregation will notice some changes, especially around giving. Plan your communication:

• Two weeks before: Announce the change in the bulletin and from the pulpit. Explain why you're switching.
• One week before: Email regular donors directly. Explain that recurring gifts will need to be re-set up.
• Launch day: Have staff available to help people navigate the new giving platform.
• Two weeks after: Follow up with recurring donors who haven't re-enrolled.

Frequently Asked Questions

Final Checklist Before Shutting Down Your Old System

• All member data verified in new system
• Giving totals match between old and new
• Staff trained and comfortable with daily tasks
• Donors informed about recurring giving re-enrollment
• Parallel operation completed for at least 2 weeks
• Old system exported one final time as a backup
• Old system kept accessible (read-only) for reference

Switching ChMS platforms is a significant undertaking. But with proper planning, it doesn't have to be traumatic. The churches that succeed treat migration as a project, not an afterthought.

Still deciding which platform to switch to? Check out our best ChMS for small churches or read our detailed platform reviews.