Google will give your church a free @yourchurch.org email address, Drive storage, Meet, and the rest of Workspace through its Google for Nonprofits program — but the application doesn't happen on Google's site. It runs through a third-party validation service called TechSoup, and most churches get tripped up not because they're ineligible, but because they submit the wrong paperwork or skip a step Google assumes you already know about. This guide walks through exactly who qualifies, what TechSoup wants to see from a church specifically (which is different from what a typical 501(c)(3) nonprofit submits), and how to go from application to a working church email address without losing mail in the process.
Google's eligibility rules are written for nonprofits in general, but churches get special treatment under U.S. tax law that actually makes this easier. Under IRC Section 508(c)(1)(A), churches are automatically considered tax-exempt and are not required to file for formal 501(c)(3) recognition with the IRS the way a charity or foundation is. Google and TechSoup both recognize this — a church doesn't need an IRS determination letter to qualify, as long as it can otherwise document that it operates as a religious nonprofit.
What disqualifies an organization from Google for Nonprofits: government entities, schools and other educational institutions (they have a separate Google for Education program), healthcare organizations/hospitals, and any organization that doesn't meet Google's nondiscrimination policy. That last point matters for churches specifically — Google requires validated organizations to attest they won't discriminate in hiring or in delivering services based on protected classes including race, religion, sex, disability, age, or sexual orientation and gender identity. Most churches complete this attestation without issue since it applies to the church's general operations, not to ministerial or membership decisions, but it's worth reading the actual policy language on Google's site before you apply so there are no surprises mid-application.
One more practical requirement: your church needs a registered domain name (like gracechurch.org) that you control, since Workspace is built around custom-domain email. If you're still on a free Gmail or a church-management-platform email address, register your domain first — it's a prerequisite for activation, not just a nice-to-have.
The free tier — officially called Google Workspace for Nonprofits — gives you custom-domain email (you@yourchurch.org), Gmail, Calendar, Meet with extended participant limits, Chat, Drive, Docs, Sheets, and Slides, plus a shared pool of 30GB of storage per user. For a small-to-midsize church staff, that's functionally equivalent to Google's paid Business Starter plan, at no cost.
What it doesn't include: the free tier caps out on storage and doesn't include the higher-tier security and admin controls (Vault for e-discovery/retention, advanced endpoint management, enhanced support). If your church needs those, Google offers deep discounts — commonly cited around 70% off — on Business Standard and Business Plus editions once you're a validated nonprofit, purchased through a Google reseller rather than self-serve checkout. Most churches under a few hundred active users never need to upgrade past the free tier.
A detail that surprises churches migrating from an older host: the free nonprofit edition is Google's live, current product, not a legacy plan being phased out. Google folded what used to be called "G Suite for Nonprofits" into the mainstream Workspace for Nonprofits offering in 2021, so you're getting the same underlying platform your paid-Workspace neighbors use, with the storage and pricing being the only differences.
Google doesn't verify nonprofit status itself — it delegates that to TechSoup (in the U.S.; other countries use a regional validation partner listed on Google's nonprofit signup page). You'll need to create a free TechSoup account first, using the church's official name and address, not a pastor's personal information.
Once your account exists, search TechSoup's eligibility questionnaire for "Google for Nonprofits" and start the validation request. TechSoup will ask you to confirm your organization type (select religious organization/church where offered) and will then prompt you to upload supporting documents. This step typically takes TechSoup anywhere from a couple of business days to about two weeks to review, so start it before you need the email addresses live, not the week you're planning to cut over.
After TechSoup approves your organization, they issue a validation token — a unique code tied to your church's TechSoup account. That token is what you'll actually enter on Google's side, so don't lose the confirmation email it arrives in.
This is the step where churches most often stall, because the standard nonprofit checklist assumes a 501(c)(3) determination letter that most churches don't have and don't need. TechSoup accepts alternatives for churches, but you should have these ready before you start the application:
Your EIN (Employer Identification Number) confirmation letter from the IRS (form CP 575 or a 147C letter if you've lost the original) — this is the single most important document, since it proves the church is a real, registered entity. If your church is part of a denomination that holds a group exemption ruling (common among Methodist, Baptist convention, Catholic diocesan, and many other denominational structures), a letter from the parent body confirming your church is covered under that group ruling works in place of an individual IRS letter. Independent churches without a group ruling can typically submit articles of incorporation or bylaws that identify the organization as a religious nonprofit, along with proof of address (a utility bill or bank statement in the church's name).
Have your church's legal name exactly as it appears on the EIN letter, your physical address, and a staff or board member's contact information on hand too — mismatches between what you submit and what's on file elsewhere are the most common cause of a document getting kicked back for resubmission.
With your TechSoup validation token in hand, go to google.com/nonprofits and select Get Started. You'll sign up for Google for Nonprofits using your church's information, enter the validation token when prompted, and agree to Google's nonprofit terms (including the nondiscrimination attestation covered above).
Once Google for Nonprofits approves your account, you'll get access to a dashboard where you can activate individual products — Google Workspace is one of several (Google Ad Grants and YouTube Nonprofit Program are others you can enable from the same hub, worth a look while you're in there). Activating Workspace kicks off the standard Google Workspace signup flow: you'll create your admin account, and Google will ask you to verify you own your church's domain, usually by adding a TXT record at your domain registrar or uploading an HTML verification file.
Domain verification is where a lot of church volunteers get stuck, since it requires access to whoever manages the church's domain registrar (GoDaddy, Squarespace, Wix, etc.), not just the Google account. Track that access down before this step — it's the most common reason activations sit half-finished for weeks.
Mismatched legal names are the top cause: if your EIN letter says "First Baptist Church of Springfield" but you register with TechSoup as "First Baptist Springfield," expect a request for clarification. Copy the name exactly as it appears on your IRS documentation.
A P.O. box as your only address can also trigger a manual review, since TechSoup and Google both want to confirm a physical operating location. If your church mail goes to a P.O. box, include a secondary document (utility bill, lease) showing the physical address.
The nondiscrimination attestation is the other real rejection risk, though it's less common than the paperwork issues above. Read Google's nonprofit eligibility and nondiscrimination policy directly before applying if your church has any hiring or membership policies you're unsure how to characterize — it's better to know where you stand before TechSoup flags it than after.
Once Workspace is activated and your domain is verified, resist the urge to just start creating mailboxes and pointing MX records over immediately. If staff and volunteers currently have live email at your old provider (a church-management platform, a cheap hosting-bundled inbox, or personal Gmail forwarding), switching MX records before mailboxes and existing mail are migrated will bounce or lose incoming messages during the cutover window.
The safe order is: create all user mailboxes in the new Google Admin console first, migrate existing mail and contacts into those mailboxes (Google's Data Migration Service handles many common sources, though older or nonstandard church platforms sometimes need IMAP-based migration instead), confirm mail is landing correctly for a test user, and only then update your domain's MX records to cut traffic over live. Keep the old inbox reachable in read-only mode for a few weeks afterward in case anything was missed.
If your church's current setup involves several different email accounts across departments, forwarding rules built up over years, or a domain registrar nobody currently has login access to, this is the point where it's worth getting a second set of hands on the DNS and migration side specifically — it's a one-time job, but it's the part most likely to cause a dropped week of church email if it's rushed.
Get a free church email deliverability audit →No. Churches are automatically tax-exempt under IRC Section 508(c)(1)(A) and aren't required to file for a formal IRS determination letter. TechSoup accepts alternative documentation for churches, such as an EIN confirmation letter plus proof of religious nonprofit status (articles of incorporation, bylaws, or a denominational group exemption letter).
Typically a few business days to about two weeks, depending on document review volume and whether your first submission is complete. Applications with mismatched names or missing address documentation take longer because they get sent back for resubmission.
The base edition — custom-domain email, Calendar, Meet, Drive, and the core apps with 30GB pooled storage per user — is free indefinitely once your church is validated. Higher-tier editions with more storage and admin controls are available at a steep discount, not free, and are purchased separately through a Google reseller.
Yes. Submit your church's own EIN (churches generally still register individually with the IRS for banking and payroll purposes even under a group ruling) along with a letter from your denomination's parent body confirming your church is covered under its group exemption number.
Nothing changes until you update your domain's MX records. Set up and migrate mail into the new Google mailboxes first, verify a test account is receiving mail correctly, and only then repoint MX records — that avoids the bounced or lost messages that happen when providers are switched before mail is actually migrated.