Google Workspace gives your church professional email addresses, shared calendars, Google Drive storage, and video conferencing — and for qualifying churches, it's completely free. The nonprofit edition (called Google Workspace for Nonprofits) includes up to 2,000 users at no cost, which covers nearly every congregation in the country. The catch? You can't apply directly through Google. Churches must first verify their nonprofit status through TechSoup, a third-party technology partner Google uses to confirm eligibility. This process trips up a lot of ministry staff because it involves two separate applications on two different platforms. This guide walks you through every step in plain language so you can get your church's Google Workspace account set up without the confusion.
Google for Nonprofits is open to 501(c)(3) organizations in the United States — and the vast majority of churches qualify because they are automatically granted 501(c)(3) status under IRS code without needing to apply. However, Google's program does have a few firm exclusions you should know about before you start.
Your church will NOT qualify if it is a government entity, a hospital or healthcare organization, a school or academic institution (those use Google Workspace for Education instead), or if your organization engages in political campaign activity. Standard churches, ministries, para-church nonprofits, and faith-based community organizations almost always do qualify.
One important note: Google does not require churches to hold a formal 501(c)(3) determination letter in all cases, but TechSoup — the verification gateway — does require documentation proving your nonprofit status. If your church has an EIN (Employer Identification Number) and files as a religious organization, you're in good shape. If you're unsure, gather your EIN, your state registration documents, and any IRS correspondence before you begin.
TechSoup (techsoup.org) is a nonprofit technology marketplace that Google, Microsoft, Adobe, and others use to verify eligibility for discounted or free software. Your first job is to register your church there and get a validation token.
Go to techsoup.org and click 'Register' in the top right corner. Choose 'I work for a nonprofit or library' and fill in your organization's details. You'll need your church's legal name (exactly as it appears with the IRS or your state), your EIN, your mailing address, and basic contact information for the primary administrator.
After submitting, TechSoup will ask you to upload documentation proving your nonprofit status. For churches, the most commonly accepted documents include an IRS determination letter, a state certificate of incorporation, or documentation showing your church's affiliation with a recognized religious denomination. TechSoup's review typically takes 5–7 business days, though it can be faster. You'll receive an email when your organization is validated.
Once validated, log back in to your TechSoup account and navigate to 'My Account' then 'Eligibility and Verification.' You'll see a section for Google for Nonprofits — this is where you'll find the unique token you need for the next step. Copy it carefully; you'll paste it into Google's application form.
With your TechSoup token in hand, go to nonprofits.google.com and click 'Get Started.' Sign in with any existing Google account — this doesn't have to be your final Workspace account, just an account Google uses to communicate with you during the review process.
Fill out the application form with your church's information: organization name, website URL, country, and the TechSoup validation token from Step 1. Google will ask you to agree to the Google for Nonprofits Additional Terms of Service, which include confirming your church does not discriminate in ways that violate applicable laws.
Google's review typically takes 2–14 business days. You'll receive an email at the address associated with the Google account you used to apply. Once approved, you'll have access to the Google for Nonprofits hub, where you can activate individual products — including Google Workspace for Nonprofits, Google Ad Grants, and YouTube Nonprofit Program.
After Google approves your nonprofit status, log in to nonprofits.google.com, go to 'Google Workspace for Nonprofits,' and click 'Get Started.' This will launch a setup wizard that walks you through creating your Google Workspace account.
The most important step here is connecting your domain. Your church will need a domain name (like firstbaptistchurch.org) to use Google Workspace — you can't create professional email addresses without one. If your church doesn't have a domain yet, you'll need to purchase one before completing this step. Namecheap and Google Domains are popular, affordable options (typically $12–$15/year).
Once you enter your domain, Google will ask you to verify ownership. The most common method is adding a TXT record to your domain's DNS settings — your domain registrar's help center will have specific instructions for doing this. After verification, you'll set up your first admin account (this becomes your church's primary administrator email, e.g., pastor@firstbaptistchurch.org), and then you can begin creating accounts for staff, ministry leaders, and volunteers.
The free Google Workspace for Nonprofits plan includes 30 GB of pooled Google Drive storage per user, Gmail, Google Meet, Google Calendar, Docs, Sheets, and Slides. For most churches, this is more than enough. If you need more storage or advanced security features, Google also offers discounted Workspace Business Standard and Business Plus plans for nonprofits at roughly 70% off standard pricing.
If your church staff is currently using personal Gmail accounts, a hosted email service, or an older provider like GoDaddy or Yahoo, you'll want to migrate those emails into your new Google Workspace accounts so nothing gets lost.
For churches moving from personal Gmail accounts, Google Workspace includes a free data migration tool in the Admin Console (Admin > Data Migration). You can import emails, calendar events, and contacts from existing Gmail or Google accounts. The tool runs in the background and doesn't disrupt current email access during the migration.
If you're migrating from a non-Google provider (like Microsoft 365, GoDaddy Workspace Email, or Outlook), Google's migration tool supports IMAP-based transfers. You'll need the IMAP server settings for your old provider, plus the email credentials for each account being migrated. For larger churches with many staff accounts, a service like switchmyemail.com can handle the entire migration for you — including mapping old addresses to new ones, preserving folder structures, and handling any technical errors that come up.
After migration, update your domain's MX records to point to Google's mail servers. This tells the internet to deliver all new email for your domain to Google Workspace. Your domain registrar's DNS settings panel is where you'll make this change — Google provides the exact MX record values in the Admin Console under Domains > Manage Domains.
The most common rejection reason from TechSoup is a mismatch between the organization name on your application and the name on your documentation. Make sure your legal church name is identical across all forms — even small differences like 'First Baptist Church Inc.' vs. 'First Baptist Church' can cause a delay.
Another frequent issue is not having a public-facing website or having a website that doesn't clearly identify the organization as a church or nonprofit. TechSoup and Google both review your website as part of their validation. Your site should clearly display your church's name, mission, address, and contact information. Even a simple one-page site works — what matters is that it's live and clearly represents your organization.
If your church was rejected by Google (not TechSoup), the most common reasons are using a free domain (like a .weebly.com or .wixsite.com subdomain instead of a real domain), or checking a box on the application that triggers an eligibility concern. Read Google's rejection email carefully — they usually specify the reason. You can reapply after fixing the issue, and Google support for nonprofits can be reached through the nonprofits.google.com help center.
From start to finish, expect the process to take anywhere from one to three weeks if everything goes smoothly. TechSoup validation typically takes 5–7 business days. Google's review after that takes 2–14 business days. If you need to gather documents or purchase a domain, add a few extra days on the front end.
Once both approvals come through, the actual Workspace setup — creating accounts, verifying your domain, and updating MX records — can be completed in a few hours. Email migration (if needed) may take an additional 24–48 hours depending on the volume of data being transferred.
To avoid delays, start by gathering everything before you begin: your church's EIN, legal name, nonprofit documentation, domain name (or budget to purchase one), and a list of all staff who will need accounts. Having this ready makes the TechSoup application fast and reduces the chance of back-and-forth during review.
Get a free church email deliverability audit →Not necessarily. Churches in the U.S. are automatically tax-exempt under IRS code and are not required to apply for a formal 501(c)(3) determination letter. However, TechSoup still needs documentation showing your church is a legitimate nonprofit religious organization. An EIN confirmation, state registration, or denominational affiliation documents will typically suffice. If you do have a determination letter, it makes the process faster.
No. Google Workspace requires a real registered domain (like yourchurch.org or yourchurch.com) that your organization owns and controls. Subdomains from free website builders are not eligible. You'll need to purchase a domain from a registrar like Namecheap, Google Domains, or GoDaddy — typically $12–$15 per year — before you can complete the Workspace setup.
The free Google Workspace for Nonprofits plan supports up to 2,000 user accounts, which is sufficient for virtually any church. Each account comes with access to Gmail, Google Meet, Drive, Calendar, Docs, Sheets, and Slides. Storage is pooled across users in the organization.
Your existing emails can be migrated into Google Workspace using Google's built-in migration tool (for Gmail or IMAP sources) in the Admin Console. After migration, you'll update your domain's MX records to route all new incoming mail to Google's servers. During the transition, you can keep your old email active so no messages are lost. A migration service like switchmyemail.com can manage this process end-to-end if you'd prefer not to handle it yourself.
TechSoup requires organizations to re-verify their eligibility periodically — typically every one to two years. You'll receive a reminder email when your validation is approaching expiration. The renewal process is simpler than the initial application since your organization is already in TechSoup's system. Keeping your TechSoup account active is important because it maintains your eligibility for Google for Nonprofits and other tech donation programs.