Church Data Backup: How to Protect Member Records, Financials and Sermon Media

Most churches keep their whole administrative life on one or two office computers and a handful of logins. The member directory, years of giving history, the books, the board minutes and every recorded sermon often sit in places only one staff member or volunteer really understands. If one of those places fails, you could be rebuilding from paper and memory.

Church data backup means keeping current copies of your member database, giving and accounting records, documents, photos and sermon recordings somewhere other than the computer or service they live on, and proving you can restore them. A sound plan follows the 3-2-1 rule from CISA: three copies, on two types of storage, with one off-site. Back up at least daily, keep one copy offline, and test a restore at least twice a year.

What Does a Church Need to Back Up?

A church needs to back up anything it would have to rebuild by hand: membership records, giving and accounting data, payroll, governing documents, photos, sermon media, email and website content, and the list of accounts that unlocks all of it.

Where each one lives varies from church to church. The table shows a typical setup, so check it against your own.

What to protect	Where it usually lives	Why it matters
Member and household database	Church management software, desktop or cloud	Contact details, attendance, family connections and pastoral notes
Giving and contribution records	Church management or online giving system	Year-end giving statements and donor history
Accounting and payroll	Accounting software, payroll service	Audits, tax filings, staff pay history
Documents and minutes	Shared drive, office computer, email	Bylaws, contracts, insurance policies, property records
Photos	Phones, cameras, a shared folder	Church history that can’t be retaken
Sermon audio and video	Media computer, external drives	Original recordings and editing project files
Email and website	Microsoft 365, Google Workspace, web host	Correspondence and the church’s public face
Accounts and access list	Someone’s head, a notebook	Who can log in to what, and how to recover each account

Paper-only records count too. Older baptism, marriage and membership registers can be scanned so a digital copy joins the rest of your backups.

One detail to watch: church software sometimes treats member photos as a separate selection from the main data. When you set up a church database backup, check that pictures and attachments are included.

Why One Copy on One Computer Is Not a Backup

A file that exists in only one place is not backed up, however carefully that computer is looked after. Hard drives fail, laptops get stolen, buildings flood or burn, someone deletes the wrong folder, and ransomware can encrypt everything the computer can reach.

CISA’s guidance for small organizations sets out the 3-2-1 rule: keep 3 copies of important files, on 2 different types of storage media (such as a hard drive and the cloud), with 1 copy stored off-site, away from your building. CISA also recommends combining on-site and remote backups and protecting them with physical security, encryption and offline copies.

The offline copy matters more than it used to. CISA and the FBI have advised organizations to keep encrypted backups separated from everyday systems, because ransomware groups look for backups they can reach and encrypt or delete those too. A USB drive left plugged in beside the office computer carries the same risk as the computer itself.

Our Software Is in the Cloud, So Aren’t We Covered?

Not entirely. A cloud vendor backing up its own servers protects the vendor’s service, not your ability to get your records back after someone at your church deletes, overwrites or loses them. You still want a copy you control, or a clear, tested promise from the vendor.

The built-in recycle bins in the tools most churches use have firm limits:

• SharePoint and OneDrive (Microsoft 365): Microsoft says a deleted item stays in the recycle bins for 93 days from the time it was deleted. After that, Microsoft keeps backups for 14 more days to support a full site restore, and then the data “isn’t recoverable.”
• Google Drive: Google says files moved to the Trash are deleted forever after 30 days, and users can empty the trash sooner.

A recycle bin is a safety net for an accident someone notices quickly. If nobody spots the problem until next quarter, the deleted files are gone, and the same happens when encrypted files sync back over the good copies. Before you rely on any church management system or online service, ask the vendor:

• How often do you back up our data, and how long do you keep each backup?
• Does the backup include photos, attachments and giving history?
• Can we export everything ourselves, in a format we can open without your software?
• If one of our staff deletes records, will you restore them, and how fast?

How Often Should Church Backups Run?

Back up each kind of information as often as you can afford to lose work on it. For most church offices, that means daily for documents and finances, and a fresh copy of each sermon recording right after the service.

Two plain questions set the schedule. How much work could you stand to re-enter if the last backup is all you have? Technicians call that the recovery point. How long can the church run without that information before Sunday, payroll or year-end statements suffer? That is the recovery time. New Zealand’s government cybersecurity agency treats a daily backup as a reasonable baseline for ordinary office files, with more frequent protection for data that changes often and would be hard to redo.

Information	Suggested backup frequency	Notes
Member and household database	Daily	More often during busy seasons such as Easter or a membership drive
Giving and accounting	Daily	Always before closing a month or printing year-end statements
Payroll	After each payroll run	Keep the payroll service’s reports as well
Documents and minutes	Daily	Automatic, so nobody has to remember
Sermon audio and video	After each service	Copy the original file, not the uploaded version
Photos	Weekly, or after each event	Pull them off personal phones into a church folder first
Accounts and access list	Whenever something changes	Store it in a password manager, not a spreadsheet

These are practical starting points, not rules. The best schedule depends on your size: a small congregation with one part-time administrator may need less than a large church running several ministries.

Sermon Recordings and Photos: The Big Files

Video takes up far more space than everything else a church stores, so it needs its own plan.

Here is roughly what one hour of 1080p video takes up at common bitrates.

Recording bitrate	Approximate size per hour
5 Mbps	2.25 GB
8 Mbps	3.6 GB
10 Mbps	4.5 GB

By our own estimate, a weekly 60 to 90 minute service recorded at 2.5 to 5 GB per hour adds up to roughly 130 to 390 GB a year for a single copy of the finished video. Camera originals and editing project files can multiply that. Check the size of your own files; it’s easy to underestimate.

YouTube and Facebook re-encode what you upload, so the version you could download later is not the file you recorded. A platform is a place to show the video, not a place that promises to keep your master. Keep the original export, and the project files if you edit, in your own backup.

How Do You Know the Backup Works?

You know a backup works only when you have restored from it. A green “backup completed” message tells you a job ran; it does not tell you the files inside can be opened.

CISA advises testing your backups so your team can restore data both fully and partially, and can roll back at least seven days if needed. Here is a simple restore test you can run:

1. Pick a real file: last month’s giving report, a recent sermon video, or a few member records.
2. Restore it from backup to a different location, so you don’t overwrite the original.
3. Open it and confirm it is complete and current.
4. Note how long the restore took and anything that didn’t work.
5. Record the date, the result and who ran the test.

Our recommendation is to run this test at least twice a year, quarterly if you can, and any time you change software, replace a computer or change who handles backups. Rotate which kind of information you test so every category gets checked.

How Long Should a Church Keep Records, and What About Privacy?

Keep records as long as tax, legal, grant and insurance rules require, and protect member information as carefully as financial data, because both can carry legal duties. Your backup plan should cover the full retention period, not just this year.

Member records deserve particular care. Missouri’s breach-notification law, RSMo 407.1500, applies to “any person” that owns or licenses personal information of Missouri residents, and its text contains no exemption for nonprofits or religious organizations. Personal information there means a name combined with items such as a Social Security number, a driver’s license number, financial account or card numbers with access codes, or medical or health insurance information. If that information is exposed, notice must be given “without unreasonable delay.”

Many churches in the KC metro draw members from both sides of the state line, and Kansas has its own breach-notification law. This is general information, not legal advice; ask your attorney what applies to your church. Encrypting backups and limiting who can open them reduces the chance that a lost drive becomes a privacy problem.

Who Looks After the Backups When Volunteers Come and Go?

Write a one-page backup plan and give it an owner, so the routine survives staff and volunteer changes. Backups often stop with little warning when the one person who set them up moves on.

Your one-page plan should list:

• What is backed up, by category
• How often each backup runs, and whether it is automatic
• Where each copy lives, including the off-site and offline copies
• Who checks that backups ran, and how often
• Who runs the restore test, and when it is next due
• Who the second person is if the first is unavailable
• Where account passwords and recovery codes are kept, and who can get to them

Review it each year when the board reviews the budget. When someone with access leaves, update the plan and the passwords the same week.

What a Managed IT Provider Can Take Off Your Plate

A managed IT provider can run, watch and test your backups for you, so your staff and volunteers can focus on ministry instead of technology. ThrottleNet offers IT support for churches and works alongside the people you already have rather than replacing them. You can also read about managed IT for church management in Kansas City.

For churches and other organizations across the KC metro, ThrottleNet provides:

• Ongoing verification of your managed business backup
• Microsoft 365 / Google Workspace backup and security
• Business continuity and disaster recovery planning
• 24/7 monitoring
• A multi-tier help desk, the reason problems get solved faster

ThrottleNet clients are also backed by the $500,000 Cybersecurity Protection Program, which covers ransomware and data theft as well as downtime and recovery expenses. In ThrottleNet’s own words: ThrottleNet customers have never paid a ransomware attack.

ThrottleNet also offers a free on-site assessment and security report, a plain look at what you have today and where the gaps are.

Frequently Asked Questions

What is the 3-2-1 rule for backing up?

For a small church office, it might look like this: the working files on the office computer, a nightly copy to a backup drive kept in a locked cabinet and disconnected between runs, and an automatic copy to a cloud backup service. Two copies in the same building on the same network only count as one location.

What are the three main types of database backups?

Full, differential and incremental. A full backup copies everything and is the simplest to restore, but it is the slowest and takes the most space. A differential copies what changed since the last full backup, so a restore needs the full plus the latest differential. An incremental copies only what changed since the last backup of any kind; it is the smallest and fastest, but a restore needs every piece in order, and one damaged piece breaks the chain.

How do you back up a church database?

If your church management software is installed on an office computer, start with its built-in backup or export tool, which usually saves the database to a single file. Save that file somewhere other than the computer it came from, set it to repeat on a schedule, and remember that restoring a database file typically replaces the current data, so test restores in a separate location. If the software is cloud-based, ask the vendor for a full export you can keep.

How many years does a church need to keep financial records?

IRS guidance generally ties retention to the period a return can be examined, usually three years after it was due or filed and longer in some cases. Employment tax records should be kept at least four years, and exemption documents and minutes permanently. Many churches adopt seven years for ordinary financial and donor records as a policy. State, grant and insurance requirements can call for longer.

Start With One Restore Test This Month

You don’t need to fix everything at once. Pick one category, such as last month’s giving records, and try to restore it this month. What you learn from that one test shows you where to start.

From there, write the one-page plan, add an offline copy, and ask your cloud vendors the questions above. If you would rather have someone check your backups for you, contact ThrottleNet and ask for the free on-site assessment. Our team can sit down with your administrator or treasurer and go through each step together. For the wider picture on keeping services running, see the church IT playbook.