A staff transition is stressful enough without discovering, three weeks later, that the departed associate pastor's inbox still receives wedding inquiries, the finance team can't find last year's budget emails because they lived in a personal Gmail account, and nobody remembers the password to the account that owns your church's domain. When church staff leaves, email access is rarely handled the way a business would handle it — and that gap creates real risk: lost donor correspondence, locked-out calendars, security exposure if a disgruntled former employee retains access, and continuity breaks when congregants email a name that no longer works there. This guide walks through exactly what to do, in order, whether the departure is a routine retirement or a sudden resignation.
Most churches run lean. There's no HR department running an offboarding checklist, no IT admin reviewing access logs, and often no formal email policy at all. Staff and volunteers frequently use personal Gmail or Yahoo accounts for ministry work because nobody ever set them up with an official @yourchurch.org address — which means when they leave, the church doesn't just lose access, it loses the actual data, since it was never on church-owned infrastructure to begin with.
Even churches that do use Google Workspace or Microsoft 365 often skip the step of assigning a real IT owner. The person who knows the admin password may BE the person leaving. That single point of failure is the most common reason church staff transitions turn into a scramble.
As soon as a departure is confirmed — resignation, termination, or planned retirement — someone with admin rights should log into the Google Workspace Admin Console (admin.google.com) and do three things: suspend the user's account (not delete it yet), reset the account password so the former staff member can't sign back in, and revoke any active sessions and app-specific passwords under Security > Manage user sessions.
Suspending rather than deleting is the key move. A suspended account keeps every email, calendar event, and Drive file intact and stops all sign-in and mail delivery instantly, but nothing is destroyed. Deleting a user immediately queues their Gmail, Drive, and Calendar data for permanent removal (Google gives a short recovery window, typically 20 days, after which it's gone for good). Suspend first; decide what to do with the data later.
If the departure is sudden or adversarial, also remove the person from any Google Groups, shared Drive folders, and the domain's list of admins if they had elevated access — a former staff member with lingering admin rights is a real security exposure, not a hypothetical one.
Congregants, vendors, and donors will keep emailing the old address for months — sometimes years — after someone leaves. The fix is routing mail forward, not hoping people update their address books.
In Google Workspace Admin Console, go to the suspended user's account and set up email forwarding (or a routing rule) so mail sent to pastor.mike@yourchurch.org auto-forwards to a current staff member or a role-based inbox like office@yourchurch.org. You can do this even on a suspended account because forwarding is a mail-routing setting, not a login. Alternatively, set up an auto-reply that tells senders the person has left and gives a new contact — many churches do both: forward silently for 90 days while also auto-replying with updated contact info.
For a departing senior pastor, it's worth keeping this forwarding active for 6-12 months. Wedding, funeral, and counseling inquiries to a pastor's personal address can trickle in for a surprisingly long time.
Church email often contains things you cannot afford to lose: donor giving records referenced in correspondence, counseling notes, board and finance committee discussions, vendor contracts, and safeguarding/child-protection documentation. Some of this carries real legal retention requirements (financial records tied to tax-exempt status, any documentation related to reported incidents), and some is simply institutional memory you don't want walking out the door.
Before you consider deleting a departed staff member's account, export their mail. In Google Workspace, an admin can use Google Vault (included in Business Plus and above, or purchasable as an add-on) to place a litigation hold or export mailbox contents to a searchable archive. If you don't have Vault, a simpler option is Google Takeout run by the admin on the user's behalf, or transferring ownership of their Drive files and exporting their mailbox via the Data Migration Service into an archive mailbox or a designated staff member's account.
If the departing person managed financial or HR-adjacent correspondence, loop in your treasurer or board chair before archiving — they may need specific threads preserved separately for audit purposes.
Email is only part of the picture. A departing staff member's Google Calendar likely owns recurring events (staff meetings, facility bookings, sermon planning) that will vanish or orphan if the account is deleted without transfer. Before suspending long-term, have the admin reassign calendar ownership: open the calendar in question from the Admin Console's data transfer tool (Admin Console > Data > Transfer data between users), which moves both Drive files and calendar events to a new owner in one operation.
Also check Google Groups membership — if the person was the sole owner of a group like staff@yourchurch.org or elders@yourchurch.org, the group can become unmanageable once they're suspended. Reassign group ownership to a current staff member as part of the same pass.
Don't forget shared logins to third-party tools that used the church Gmail for sign-in or password recovery (Planning Center, Mailchimp, your website host, Canva). A departing staff member's email is often the recovery address for accounts that have nothing to do with email itself.
Once records are preserved and forwarding is set up, most churches land on one of three long-term choices for the address itself. First, convert it to a role-based alias — turn pastor@yourchurch.org into an alias that delivers to whoever holds that role now, rather than a personal name. This is the cleanest long-term fix and prevents this entire scramble the next time someone leaves. Second, keep it as an archived, non-licensed mailbox for a defined retention period (Google Workspace lets you keep a suspended account without paying for a full license in some plans, or you can downsize to an Archived User license, which costs less and still lets you search/export the mail). Third, delete it entirely once forwarding, records, and transfers are confirmed complete — usually not before 90 days.
Many churches we work with move toward role-based addresses (office@, giving@, care@, pastor@) for anything congregation-facing, and reserve personal @yourchurch.org addresses for internal use only. It's a small structural change that makes every future staff transition dramatically less risky.
The churches that handle this well aren't smarter — they just wrote down the steps once. A simple offboarding checklist, kept in a shared drive that at least two people (not just the departing person) can access, should include: who has admin rights to the Google Workspace or Microsoft 365 console (and a documented backup admin), the suspend-not-delete rule, forwarding setup steps, the records-retention decision, and calendar/Drive/group ownership transfer.
The single highest-leverage fix is simply ensuring at least two people — ideally including a board member or treasurer, not only staff — have documented admin access to your email platform. If the only admin is the person who just resigned, everything above becomes far harder to execute calmly.
Get a free church email deliverability audit →No. Suspend the account first, not delete it. Suspending blocks sign-in and stops new mail delivery while preserving every email, file, and calendar event. Deletion starts an irreversible countdown (Google gives roughly 20 days to recover a deleted user before data is gone permanently), so only delete after you've exported records, transferred calendar/Drive ownership, and set up forwarding.
Most churches keep forwarding active for 6-12 months for senior/pastoral roles, since wedding, funeral, and counseling inquiries can arrive long after someone leaves. For administrative or support staff, 90 days is usually sufficient. Pair forwarding with an auto-reply pointing senders to the correct current contact.
This is the most common failure point. If nobody else has admin access, contact Google Workspace support directly to verify domain ownership and regain admin control (you'll need to prove organizational ownership, e.g., via DNS records). Going forward, always designate at least two admins, including one board member who isn't day-to-day staff.
Possibly. Financial correspondence tied to your organization's tax-exempt status, any documentation related to safeguarding or reported incidents, and HR-related communications often carry retention obligations that outlast the employee. When in doubt, export and archive rather than delete, and check with your treasurer, board, or denominational compliance office before permanently removing anything.
A role-based address (like office@yourchurch.org or pastor@yourchurch.org) is tied to a job function rather than a specific person, and delivers to whoever currently holds that role. Using role-based addresses for anything congregation-facing means a staff transition no longer requires forwarding, auto-replies, or re-training congregants on a new address — it's the single biggest structural fix churches can make to avoid repeating this problem.