Switching parish software without losing your records

The reason parishes stay on software they have outgrown is rarely loyalty. It is fear of the move. Years of members, giving history, and sacramental records live in the current system, and switching parish software feels like carrying the whole parish across a river on a single plank. The fear is reasonable, but the risk is smaller than it looks. A careful import loses nothing, and you keep a copy of everything the entire time. This is a plain guide to moving from Breeze, ACS, ParishSoft, or a stack of spreadsheets without leaving anyone or anything behind.

Why switching parish software feels scarier than it is

Most migration dread comes from a few specific worries: that a household will be split apart, that giving history will not add up, that the sacramental register — the thing you truly cannot recreate — will be mangled or dropped.

Those are the right things to worry about, and they are all avoidable. The key is that migration is a copy, not a move. Your old system keeps running until the new one is verified. Nothing is deleted on either side by importing. If a run looks wrong, you fix the mapping and import again. You are never one click away from losing the parish. You are working from a copy while the original sits safe.

What you are actually moving

It helps to name the pieces, because they migrate differently.

• People and households — names, contact details, family groupings, godparent and sponsor links, patron saints.
• Giving history — pledges, gifts, funds, and the dates and amounts behind year-end statements.
• The sacramental register — baptisms, chrismations, marriages, and memorials, with dates, clergy, and sponsors.
• Documents — scanned certificates and records that live as files.
• The books — chart of accounts and balances, if you are moving accounting too.

Each of these has a natural home in a fitted system. The register in particular deserves its own destination rather than a pile of custom fields — you can see how membership and relationships are modeled on the members feature page.

Importing from Breeze, ACS, or a spreadsheet

Every serious platform can export. Breeze, ACS, ParishSoft, and Realm all produce spreadsheet or CSV files, and a spreadsheet you already keep is just as importable.

The work is in the mapping — deciding that their "Family" becomes your household, that a giving column lands in the right fund, that a date reads as a date. Done well, it is unglamorous and reversible. A few practical habits:

• Export a per-person file, not a household rollup, when the system offers both. Individual rows map more cleanly, and you can regroup them.
• Keep the Family or household ID column. It is how you rebuild households on the other side.
• Do a small test import first — twenty or thirty records — and check them by eye before running the whole file.
• Reconcile totals. Giving history should sum to the same number on both sides. If it does not, the mapping is off, not the data.

We built an import path for exactly this and describe it on the migration page, including how Breeze exports and Family IDs are handled.

Keeping households and sacramental history intact

Two things distinguish a parish migration from a generic one, and both are where fitted software earns its place.

Households are relationships, not a shared address. Marriages and godparent links have to survive the move, which is why the household ID matters and why a per-person export regroups better than a flattened family export. On arrival, people should land back in the households — and the sponsorships — they belonged to.

The sacramental register is the record you cannot recreate. It should import as a permanent, certificate-ready archive: a baptism you can still print a certificate from in twenty years, with the officiating clergy and sponsors attached. If a system has nowhere proper to put that, it will scatter into notes and custom fields — a sign it was never built for a parish. This is the single best test of whether you are moving to fitted software or just to a different generic one.

A calm way to switch

Put together, a safe switch looks less like a leap and more like a checklist.

1. Export everything from the old system and keep the files.
2. Map and test-import a small batch, then check it by eye.
3. Import the full set. Reconcile giving totals and spot-check the register.
4. Run both systems in parallel for a giving cycle, until you trust the new one.
5. Only then retire the old subscription — with your export files archived, just in case.

Done this way, migration is patient clerical work, not a gamble. Your data stays yours throughout, in a format you can carry anywhere. If you want to see how the pieces land, the members feature page and the migration guide are the places to look, and we are glad to help a parish plan its move.