If your church is still running staff email off a personal Gmail account or a shared inbox nobody reliably checks, there's a faster fix than most people realize: Google for Nonprofits gives eligible churches Google Workspace — custom @yourchurch.org email, Calendar, Drive, and Meet — at no cost, with discounted upgrades if you outgrow the free tier. The catch is that the application process trips up a lot of churches. It runs through a third-party validation step most congregations have never heard of, and there's a non-discrimination policy clause that causes real confusion for religious organizations. This guide walks through exactly what you get, whether your church qualifies, and how to get through the application without the back-and-forth that stalls most requests.
The free tier is functionally equivalent to Google Workspace Business Starter: custom email addresses on your own domain (pastor@yourchurch.org instead of a generic Gmail address), Gmail with 30GB of pooled cloud storage per user, Google Calendar, Docs/Sheets/Slides, Drive, and Google Meet video calls with up to 100 participants. There's no per-user fee and no limit on how many staff or ministry leader accounts you create.
It does not include everything in the paid tiers — no meeting recording, no advanced security controls like Vault for e-discovery, and no enhanced support. If your church later needs those features, or wants more per-user storage, Google for Nonprofits also unlocks steep discounts (historically up to 70-80% off list price) on Business Standard and Business Plus through Google's nonprofit pricing, rather than requiring you to pay full commercial rates.
For most churches under a few hundred members, the free tier alone is enough to replace scattered personal email accounts with a real, professional domain-based system.
Google's baseline eligibility requirement is nonprofit status recognized in your country — in the US, that means holding a valid 501(c)(3) determination letter from the IRS (or being a church that qualifies as tax-exempt under section 501(c)(3) even without having filed for a determination letter, which is common since churches aren't legally required to apply for that status). You'll need your EIN and legal organization name to match your registration paperwork.
Google explicitly excludes government entities, schools and universities (they have a separate Google for Education program), and healthcare organizations/hospitals. Churches, denominational offices, and standalone ministries generally fall into the eligible "community, faith-based, and religious organization" category.
The part that generates the most confusion is Google's non-discrimination policy: nonprofits can't discriminate in the provision of services based on race, religion, sex, disability, sexual orientation, or gender identity. Some churches worry this disqualifies them because they require staff and clergy to affirm a statement of faith. In practice, that's a standard religious employment exemption and doesn't block approval — the policy targets discrimination in the services or programs the organization provides to the public, not internal doctrinal requirements for ministry staff. If you're unsure how your church's specific bylaws read against this, it's worth a quick read of Google for Nonprofits' published eligibility guidelines before you apply, since we're not able to give you a legal opinion on your bylaws.
Step 1 — Register with a validation partner. In the US, Google requires nonprofit status to be verified through TechSoup before you can apply. Create a free TechSoup account, submit your organization's legal name, EIN, and address, and upload your IRS determination letter if you have one (or documentation showing your church's tax-exempt status if you don't). Validation typically takes a few business days.
Step 2 — Get your validation token. Once TechSoup approves your organization, they issue a nonprofit validation token — a code tied to your organization's verified status.
Step 3 — Apply at google.com/nonprofits. Sign in with the Google account you want to be your organization's admin, enter your validation token, and fill out the application with your church's domain name (or purchase one if you don't have it yet — Google Workspace setup will prompt you).
Step 4 — Verify domain ownership. Google will ask you to add a TXT or CNAME record at your domain registrar to prove you control the domain. This is the single most common place non-technical church admins get stuck — if your church's website was built by a volunteer or an outside vendor, you may need their help logging into the DNS settings.
Step 5 — Wait for approval, then provision users. Approval typically takes anywhere from a few days to a couple of weeks. Once approved, you'll set up the Google Workspace admin console and start creating email accounts for staff and ministry leaders.
Getting approved is only half the job — your church's email won't actually work until the domain's MX records point to Google's mail servers. In the Workspace admin console, under Apps > Google Workspace > Gmail, Google will give you the exact MX record values to add at your domain registrar (usually five records pointing to different Google mail server priorities).
This is also the moment to add SPF and DKIM records, which tell other mail servers your outgoing church emails are legitimate and not spam. Skipping this step is the number one reason a newly migrated church's emails start landing in recipients' spam folders — donation receipts, event invites, and pastoral emails all suffer if deliverability isn't set up correctly from day one.
If your church previously had email through GoDaddy, Office 365, or a hosting provider's built-in email, you'll also need to plan the cutover carefully so you don't lose incoming mail during the DNS propagation window (usually a few hours, sometimes up to 48).
Application stuck in review: this usually means TechSoup or Google needs more documentation. Check the email address you registered with (including spam folder) for a request for additional proof of nonprofit status.
Denied for "discrimination" language in bylaws: if your church's governing documents restrict staff or membership roles by religious belief in a way that reads ambiguously, reach out to Google for Nonprofits support directly and clarify that the restriction applies to religious leadership qualifications, not to who the church serves. Many churches successfully appeal an initial denial this way.
Domain verification fails: double-check you added the TXT record to the exact domain (not a subdomain) and that you're not still on your registrar's default "parking page" nameservers, which can block custom DNS records until you switch to standard DNS management.
No one on staff can access the domain registrar: this is common when a departed volunteer set up the website years ago. You may need to contact the registrar's support with proof of church ownership to regain access before you can proceed.
Once your church's Workspace domain is live, the remaining work is moving everyone off their old email — whether that's a mix of personal Gmail accounts, an old hosting-provider inbox, or a legacy system like Office 365. Google's Data Migration Service can pull over mail, contacts, and calendar events from most providers directly inside the admin console, but it works best with clean IMAP or Exchange access and can take real setup time to configure correctly, especially with multiple staff mailboxes and years of email history.
This is the stage where churches most often get stuck — not because Google Workspace is hard to use, but because migrating years of mail, updating DNS without downtime, and training a mostly-volunteer staff to actually use the new system takes hands-on setup most church offices don't have time for. If you'd rather have someone handle the migration end-to-end instead of learning DNS records and mail migration tools yourself, that's exactly the kind of setup switchmyemail.com handles for churches and small nonprofits.
Get a free church email deliverability audit →The core tier (equivalent to Business Starter — custom email, Calendar, Drive, Meet) is genuinely free with no per-user fee and no time limit, as long as your church stays approved as a nonprofit. You only pay if you choose to upgrade to Business Standard or Business Plus for extra features, and even then nonprofits get a steep discount off list price.
It's the most straightforward path, but not strictly required — churches are automatically considered tax-exempt under IRS rules even without filing for a formal determination letter. If you don't have one, be ready to submit alternative documentation of your tax-exempt status during TechSoup validation.
Google for Nonprofits excludes organizations that discriminate in the services they provide to the public, but this generally does not disqualify churches for requiring staff or clergy to affirm a statement of faith, which is a standard religious employment practice. If your application is denied and you believe it's due to a misread of your bylaws, you can appeal directly with Google for Nonprofits support.
TechSoup validation typically takes a few business days, and Google's review after that can take anywhere from a few days to a couple of weeks. Budget two to three weeks total if you want a buffer, and start well before any date you're hoping to have new email addresses live.
Yes. Once approved for Google for Nonprofits, you keep nonprofit pricing on paid tiers indefinitely, so you can start on the free plan and upgrade specific users or your whole domain to Business Standard or Business Plus later without reapplying from scratch.