Breeze is a good piece of software. It is also, for a lot of small churches, more than they need and more than they can justify once giving is down or the person who championed it has moved on. If you are thinking about switching, the hard part is not choosing a replacement — it is getting your records out cleanly, so you do not spend the next year missing something you did not know you needed.
This is a practical walkthrough of what to export, what a smaller tool will actually do with that data, and what it will not do at all. Read it before you cancel anything.
Why churches leave Breeze
The reasons are rarely dramatic. A church of 90 people signed up for Breeze when they had big plans: multiple campuses, a full check-in kiosk, staff scheduling, an events registration system with online payment. Two years later, three volunteers use it to look up phone numbers and one person enters giving on Monday mornings. The subscription did not shrink to match the actual use.
Other churches leave because the person who set it up left, and nobody who remains wants to learn a system built for a staff of twelve when the actual staff is a part-time secretary and a treasurer who also teaches fourth grade. Complexity has a maintenance cost even when you are not using most of it — someone still has to know where things live.
Neither reason is a knock on Breeze. It is a mismatch between the tool and the church, and it is worth naming honestly before you go looking for the next thing, because the next thing can have the exact same mismatch in the other direction if you are not careful about what you actually need.
Export everything before you touch cancel
Do this step first, in this order, while your subscription is still fully active:
- The people directory. Every profile, household grouping, contact info, and any custom fields or tags you have used for years without thinking about them.
- Giving history. By person, by fund, by year. You will need this for statements and for continuity — a giver who has supported the church for a decade should not lose that history the week you switch systems.
- Attendance records. Even a simple weekly count by service or by group, exported as far back as you can get it.
- Group and class rosters, with leaders noted, so you are not reconstructing who is in which small group from memory.
- Any notes tied to pastoral care or follow-up that you would be uncomfortable losing. These are the records people forget to export and then regret.
Save everything as CSV in a folder with the date in the name. You are building a paper trail, not just a backup — if a question comes up in six months about what someone gave in a year you have already switched away from, you want the original export, not a memory of it.
What a smaller tool will actually do with that export
Here is the part that surprises people: most smaller church tools, SundayBridge included, do not have a CSV import feature. Export exists on our side — you can pull your own directory back out as CSV any time — but there is no button that reads a Breeze file and populates 200 profiles automatically.
What we do instead is load it by hand, for free, as part of getting set up. That is slower than an import wizard and also more honest about what actually happens: someone has to look at your Breeze export, decide how households map, catch the duplicate entries Breeze may have accumulated over the years, and enter clean records rather than copying over old mess. A smaller list of 80 to 150 people is a few hours of work, not a project.
If a tool advertises one-click import from Breeze, ask what it actually does with duplicate profiles, inconsistent household groupings, and giving records tied to people who no longer attend. An import that runs fast and imports your mess perfectly is not actually the win it sounds like.
A related read if this is your first time cleaning up records that have drifted: cleaning up a church database before you migrate it anywhere.
What a smaller tool will not replace
This is the honest part, and it matters more than the export mechanics. Breeze does a number of things that most smaller, cheaper tools simply do not attempt:
- Child check-in kiosks. If your kids’ ministry relies on a printed name-tag kiosk on Sunday mornings, confirm the new tool has one before you commit — several smaller, cheaper platforms do not.
- Online giving and payment processing. Breeze can take a gift online. A tool that only records giving will track what came in but will not process the transaction itself — you would keep whatever processor you already use.
- Email and SMS messaging. If your team sends a weekly email blast or text reminders from inside the church database, check whether the new tool sends anything at all. Some do not, and you would need a separate tool for that.
- Staff roles and permissions. Breeze can restrict what a part-time volunteer sees versus what a pastor sees. A single-login tool cannot — everyone who has the password sees everything.
None of these are dealbreakers by default. They are things to check against how your church actually operates, not assume away because the new tool is cheaper and simpler.
What actually gets smaller and simpler
What most churches gain by downsizing is fewer screens for the same weekly tasks. A profile per person with groups, serving, giving, and care on one page, a follow-up board that shows a guest with an owner and a date so nothing quietly goes cold, and reports you can pull and export without hunting through a menu built for a much bigger operation. If your team already runs a weekly admin rhythm, a simpler tool tends to fit that rhythm rather than fight it.
If you have not yet compared what different tiers of church software actually offer, it is worth reading how to choose church management software before you settle on a replacement, so you are choosing based on what your church does every week rather than what looked impressive in a demo.
Run both systems for a month before you commit
Do not cancel Breeze the day you sign up for something new. Enter a few weeks of real activity — a Sunday of attendance, a batch of giving, a new guest — in both systems and compare the numbers. If they match, you have real confidence the migration held together. If they do not, you have caught it while Breeze is still there to check against, instead of six months later when someone asks what a giver contributed last year and neither system has a clean answer.
The overlap costs a month or two of paying for both. It is cheap insurance against the alternative, which is discovering a gap in your giving records the week before you print year-end statements.
A short honest checklist
- Export people, giving, attendance, groups, and care notes from Breeze while it is still active.
- Confirm whether the new tool needs a manual load (most do) or claims automatic import (ask how it handles duplicates).
- List every Breeze feature your church actually uses weekly — not what you signed up for, what you use — and check each one against the new tool.
- Keep Breeze running alongside the new system for a month and compare the numbers.
- Only cancel once a real Sunday’s worth of data matches in both places.
Switching software is rarely about the software. It is about whether the next tool matches what your church actually does on a Sunday, not what it aspired to do when someone first signed the contract. SundayBridge is built for the smaller version of that job — one profile per person, a follow-up board that ages what nobody has picked up, giving and reports without the extra screens — and it says plainly what it does not do, so you are not guessing during the switch.