Replacing Planning Center without losing a Sunday

Think about the lobby twenty minutes before a Sunday service. Families are lined up at the kids’ check-in, labels are printing, a volunteer is looking up a first-time guest, and someone is giving on their phone before they find a seat. Whatever software you run, that half hour has to keep working. Any move off Planning Center starts there.

Planning Center is good software, and plenty of churches run well on it. This guide is for the ones that have decided to move to a single platform they own, usually because they’re paying for several Planning Center products plus the tools around them, and none of it knows that the same person shows up in each. If you’re still weighing that decision, start with Socio Connect vs Planning Center and paying for nine platforms.

If you’ve decided, the rest of this is about doing it well. It’s the same approach we used to move a client off One Church Software, another church management system, and it follows the four phases we use on every build: Discover, Design, Build, Launch and grow.

Before you start: know what you’re moving

Planning Center is a family of products, and most churches use some of them rather than all. Start by listing the ones you pay for and what each one holds. Here is the full set, at published prices:

Then list what sits around it: the texting service, the email tool, the form builder, a separate app. A move to one platform usually replaces those too, and they hold people’s data just as Planning Center does.

Phase 1: Discover

Discovery is where the move is won or lost, and it’s mostly questions.

Map the data. For each product, write down what it holds: profiles and households, group rosters and attendance, check-in history, gifts and pledges, registrations, serving teams and schedules. Note which of it you actually use, and how far back you need it.

Map the journey. Write down the path people take from first visit to serving, and what shows that someone has reached each step. This is what the new platform is being built to show you, so it’s worth doing properly. There’s a guide to it in how to map your member journey.

Decide what stays. Not everything has to move. Accounting usually stays in your accounting system. Some churches keep an archive of old Planning Center exports for history they rarely need, rather than migrating every record.

Phase 2: Design

Design the member record. One entry per person, with households and relationships modeled from the start. This is the decision that’s hardest to change later, so it comes first. We wrote about why in what changes when every tool shares one person.

Design permissions. Who sees what: group leaders, campus staff, the care team, finance. Planning Center has its own permission model per product; this is the moment to decide what yours should be across everything.

Design the Sunday. Walk through a real Sunday screen by screen: a family arriving, kids checking in, labels printing, a first-time guest filling in a card, a gift given on the app. If any step is slower than today, fix it in design rather than after launch.

Phase 3: Build

Getting the data out. Planning Center lets a church export People and Check-Ins data as CSV files, and its API, which a church can use with a personal access token, covers People, Groups, Check-Ins, Giving, Services and Calendar. Between the two, most of what a church holds can be brought across. For anything the exports and API don’t cover, plan an archive rather than a migration.

Matching people. The same person may appear in Planning Center and in your texting and email tools with different spellings and addresses. Bringing them together as one person is careful work. Expect some manual review, and budget time for it. During import, the built-in assistant maps your spreadsheet columns and finds likely duplicates, and nothing is merged until a person says so.

Test imports, more than once. Import your real data into the new platform early, check it with the people who know it best, fix what’s wrong, and do it again. By launch, the import should be boring.

The build takes 16–36 weeks, depending on scope. The migration work runs alongside the build rather than after it.

Phase 4: Launch and grow

Run both side by side. Keep Planning Center running while the new platform goes live, for as long as your team needs to be confident. If you’d rather keep part of Planning Center running during the move, its API lets the new platform stay in step with it for the transition.

Switch in an order that protects Sundays. A sensible order is people and groups first, then events and serving teams, then check-in, and giving last. Each step is live and trusted before the next begins.

Pick an ordinary Sunday. Never switch check-in on Easter, Christmas, or the first week of a series. Choose a normal week, with extra volunteers on hand.

Tell people about the app. Your congregation will move from the Church Center app to your own. Tell them early, from the platform and in person, and make the first login simple.

Giving needs the most care

Giving is the part of the move to plan most carefully, for three reasons.

Recurring gifts. Stored card details belong to the payment processor, not to Planning Center or to us. Whether recurring gifts can move without donors setting them up again depends on the processors on both sides, so ask both, in writing, before you set a date. If donors do need to set them up again, plan the communication as carefully as the launch.

Giving statements. Donors need one accurate year-end statement. Either switch giving at the turn of the year, or decide up front how that year’s gifts from both systems will be combined into one statement.

Processing fees. Every gift pays a card processor whatever platform you use, so a move doesn’t remove processing costs. What it can remove is any platform fee charged on top. Compare the rates on both sides before counting anything as a saving.

The checklist

1. List every Planning Center product you use, and what each one holds
2. List the tools around it: texting, email, forms, the app
3. Map your member journey, from first visit to serving
4. Decide what you keep about each person, and who can see what
5. Export People and Check-Ins data, and keep an archive copy
6. Ask both payment processors how recurring gifts move
7. Decide how giving statements work for the year you switch
8. Run a full test import with your real data, more than once
9. Run the new platform alongside Planning Center for several weeks
10. Switch on an ordinary Sunday, never a major one
11. Tell your congregation about the new app before launch week
12. Keep Planning Center until your team is confident nothing is missing

When not to move

If you use one or two Planning Center products, your team isn’t reconciling lists every week, and the questions you need answered already have answers, stay. A move is a real project, and it should solve a real problem.

If you’re paying for most of the list above plus the tools around it, and the people who care for your congregation still can’t see who needs them, it’s worth planning properly. Bring your list of products to a call and we’ll go through the move with you, including whether now is the right time.

• Socio Connect vs Planning Center, product by product
• Add up what your tools cost today
• How we build, phase by phase
• Book a 30-minute call

Sources on Planning Center’s API and exports: The Planning Center API and Export data, Planning Center help center.