Your congregation's memory.
Only one copy exists.

What a church office actually holds

Walk into most congregation offices and you will find one desktop computer, sometimes two, doing an enormous amount of quiet work. Here is what is usually sitting on it, often without anyone thinking of it as "data" until it is gone.

• Membership and directory records. Names, addresses, family relationships, and contact information built up over years of new members, moves, and life changes; the working list a congregation uses to stay connected to its own people.
• Giving and contribution records and year-end statements. The record of who gave what, and when, used to produce the year-end giving statements members rely on for their own records.
• Baptism, marriage, and funeral registers, and other membership registers. The record of the milestones a congregation has witnessed, in some cases stretching back decades before the office ever had a computer at all.
• Board and committee minutes. The decisions a congregation's leadership has made over the years, and the record of how and why those decisions were reached.
• Bylaws and incorporation documents. The governing documents that establish how the congregation operates and is organized.
• Sermon audio and video archives. Years, sometimes decades, of recorded teaching and preaching, often the only recording that exists of a particular message, or of a particular pastor's ministry.
• Newsletter and bulletin back issues. Week after week, year after year, of the congregation's own account of its life: announcements, prayer requests, milestones, and news.
• Photo archives from decades of church life. Baptisms, weddings, vacation Bible school, mission trips, building dedications, and anniversary celebrations; a visual record that a shoebox of prints slowly became a folder of digital files.
• Facility and cemetery records. Building plans and maintenance history, and, for congregations that maintain one, a cemetery's plot records and burial history.
• Benevolence-fund records. The record of assistance given to members and neighbors in need, often handled with particular care and confidentiality.
• Payroll and QuickBooks. Pastoral and staff payroll, along with the bookkeeping that keeps the congregation's finances in order.

Some of this data lives inside the systems your church management software hosts. Much of it does not. A scanned marriage register, a folder of sermon videos, a decade of newsletter PDFs, or a spreadsheet of cemetery plots is often sitting only on the office computer, saved there by whoever had the job at the time.

A different kind of loss

Most small businesses that lose their files lose something operational: an invoice, a customer list, a set of financial records that, however painful to reconstruct, describes a relationship that is still ongoing and can in some way be rebuilt. A congregation's office computer often holds a different kind of thing.

A baptism recorded decades ago cannot be re-recorded. A funeral service program for a member who has since passed cannot be recreated from memory. A sermon preached by a pastor who has since retired or passed away exists, if it exists at all, as the one recording that was made of it. A photograph from a groundbreaking held forty years ago is not a business record with a retention schedule attached to it. It is a piece of the congregation's own history, and in many small congregations it exists in exactly one place.

This is what makes a congregation's office computer different from almost any other small-business machine covered in our guides. The loss here is not primarily financial or administrative, though it can be both of those things too. It is a loss of the record a community holds of itself, built up over years or decades, that nobody else holds a second copy of. That is the reason a backup matters here in a way that goes beyond the usual case for protecting business files.

Your registers, treated as records worth protecting

Membership rolls, and baptism, marriage, and funeral registers carry real weight in the life of a congregation, and we want to be careful about exactly what we are, and are not, saying about them.

Everyday Backups makes no claim about the legal, canonical, or ecclesiastical standing of any register, membership roll, or sacramental record. For many denominations, the official or canonical register of a baptism, marriage, or funeral may be maintained by, or required to be reported to, a diocese, synod, presbytery, or other denominational body, separate from whatever copy your local office keeps. We are not in a position to tell you what your denomination requires, and we do not try. What we do is help make sure that whatever copy your congregation's office keeps on its own computer, whether that is the current working record, a scanned historical register, or a spreadsheet built from an older paper ledger, has a backup somewhere other than that one machine.

Where backup gaps hide in a congregation office

• One office computer carrying everything. Many congregations, especially smaller and independent ones, run the entire administrative life of the church off a single desktop in the office. If that machine fails, a hard drive dies, or it is affected by a storm, everything on it is gone unless a separate copy exists somewhere else.
• Mistaking your church management software or online giving platform for a backup. Your church management software and your online giving platform keep their own records in their own systems, but the reports, statements, and files your office exports and saves locally, a year-end giving report or a membership export, for example, are only as safe as whatever backup covers that computer. These are named here only as software categories, not any specific product, with no integration or compatibility claim implied.
• Sermon recordings kept only on the recording device or an old external drive. A camera memory card, an aging external hard drive in a closet, or a folder that was never copied anywhere else is a single point of failure for years of preached messages.
• Photo archives scattered across volunteer phones and personal cloud accounts. The volunteer who takes pictures at every church event keeps them on a personal phone or a personal cloud account. When that volunteer's role changes, or the phone is lost, the photos can go with them.
• Cloud sync mistaken for backup. Saving files to a synced folder keeps a current copy, but sync also copies deletions and, in a ransomware event, encrypted files, to every synced location. Version history in these tools exists but is limited and is not a substitute for a separate backup.
• Volunteer and staff turnover without a handoff. A church administrator, secretary, or long-serving volunteer retires or moves on, and the files they kept, sometimes on their own laptop, leave with them, or nobody else knows where the historical archive actually lives.
• No one has tested a restore. A backup nobody has opened since it was set up is a backup nobody can be sure of. A short check every few months, recovering one file, confirms it is actually working.

A gentle backup standard for a congregation office

You do not need an IT department or a technical background to protect your congregation's records. CISA (the U.S. Cybersecurity and Infrastructure Security Agency) recommends a simple framework called the 3-2-1 rule for organizations of any size: keep 3 copies of your data, on 2 different types of media, with 1 copy off-site or offline. Applied to a church office, here is what that looks like in practice.

• Keep a copy separate from the office computer. The working copy on the office desktop is one. A backup stored in a separate cloud service, not just a synced folder, is a second. A copy kept off-site, at a member's home or a denominational office, for example, can be a third.
• Keep version history, not just the newest copy. A backup that only keeps the most recent version cannot recover from an accidental deletion or a ransomware attack that has already reached the current files. Version history lets you step back to a point before the damage occurred.
• Encrypt your backups in transit and at rest. Membership records, giving records, and benevolence-fund records deserve the same basic protection any organization would give sensitive information.
• Set up alerts for failed backups. A backup can quietly stop working, a full drive, a changed password, a network hiccup, and you want to know right away, not the day you actually need it.
• Name one person as the backup owner. It does not have to be complicated, and it does not have to be staff. A volunteer with a regular role in the office can watch for alerts and run a quick restore check.
• Test a restore every few months. Pick one file, a scanned register page, a sermon recording, a photo. Restore it. Confirm it opens. That short exercise is what turns "we have a backup" into "we know our backup works."

For a broader, printable version of these steps, see the small-business backup checklist. If your congregation also runs a school, preschool, or a wider set of nonprofit programs alongside the church itself, our backup for schools and nonprofits guide covers that side of the operation.

Church management software, online giving, and QuickBooks: what backup covers

Two categories of software generate much of a congregation office's daily records: whatever church management or online giving platform the congregation uses, and its accounting software. Understanding what backup does and does not cover for each is worth a few minutes.

What a backup does not do

We would rather be plain about the limits of what we offer than let anyone assume more than we can honestly promise.

Everyday Backups does not provide tax, nonprofit-status, charitable-deduction, or contribution-substantiation advice, and we do not tell you what your congregation is required to retain, or for how long. Requirements around giving statements, contribution substantiation, and 501(c)(3) recordkeeping vary and are a matter for your accountant, your denominational office, or your attorney, not a backup vendor. A backed-up copy of a giving record is simply a copy of a record you already keep, not proof of anything to the IRS or any other authority, and using our service does not satisfy any regulatory or recordkeeping requirement.

A backup is also not a security or privacy control. It does not protect donor or member data from being viewed or accessed by the wrong person, it does not prevent a data breach, and we make no claim about donor-data privacy compliance of any kind. What a backup does is much narrower, and we think still valuable: it gives you a way to recover your files if something happens to the computer or the files themselves, whether that is a hardware failure, an accidental deletion, a ransomware attack, or storm damage. Recovery, not security or compliance, is what we provide.

Storms, fires, and the one computer in the office

Many congregations keep their office in a building that, like any building, is exposed to fire, flooding, or storm damage. A computer holding decades of registers, sermon archives, and photographs is just as exposed as anything else in that building.

An off-site, encrypted backup means that if the office computer is ever damaged or destroyed, whether by a hurricane, a fire, a burst pipe, or simple hardware failure, the records on it still exist somewhere the damage did not reach. This does not protect the building itself, and it makes no claim about insurance or disaster response. It covers one specific thing: making sure your congregation's records survive even if the machine holding them does not. See our hurricane season business file backup guide for more on preparing files ahead of storm season.