A pastor sends a welcome message from gracechurch.pastor@gmail.com. A volunteer coordinator sends event details from mary.volunteer1979@yahoo.com. The messages are warm and personal, and they often land in spam.
Moving a ministry to email on its own domain is one of those projects that feels intimidating until you walk through it once. The whole thing takes about an afternoon. The payoff in trust, deliverability, and continuity is substantial.
Why Domain Email Matters More Than It Used To
Two things changed in the last few years. First, Gmail and Yahoo started enforcing strict authentication requirements on bulk senders. A church newsletter sent from a personal Gmail address now gets flagged by spam filters at scale. Second, donors and members increasingly read the from-address as a trust signal. A message from pastor@gracechurch.org reads differently than one from gracechurch1875@gmail.com.
Beyond that, there is the continuity question. When the volunteer coordinator moves on, what happens to all the emails sent from her personal address? When the pastor retires, who controls the relationships built through their personal account? Domain email keeps the ministry's correspondence with the ministry, not with individuals.
The 12-Step Walkthrough
The steps below cover the full setup. Most ministries can complete this in one afternoon with one person comfortable navigating settings menus.
Step 1: Choose and Buy a Domain
If you do not already own one, register a domain through a reputable registrar. Cloudflare Registrar offers domains at cost with no upselling. Porkbun is similar. Avoid GoDaddy — pricing is high and the upsell experience is exhausting.
Use the shortest, clearest domain available. gracechurch.org is better than gracechurchcommunityoffaith2026.org. The .org and .church TLDs both work well for ministry contexts.
Step 2: Apply for Nonprofit Email Pricing
Google Workspace and Microsoft 365 both offer free or heavily discounted plans for registered nonprofits. Google Workspace for Nonprofits gives you the Business Standard plan free for unlimited users at small organizations. Microsoft 365 Business Basic is free for up to 300 nonprofit users.
Both require a TechSoup validation for US nonprofits, which takes about a week. Submit the application before you need the email — you cannot rush the verification.
Step 3: Pick a Provider
For most ministries, Google Workspace is the practical choice because staff and volunteers already know Gmail. Microsoft 365 makes sense if your team already lives in Outlook and Teams.
We have set up both. The difference for end users is small. Pick whichever your team already prefers and move on — this is not a decision worth weeks of debate.
Step 4: Verify Your Domain
Both providers verify domain ownership by asking you to add a TXT record to your DNS. The record looks like google-site-verification=abc123 or MS=ms12345678. You add it through your domain registrar's DNS panel.
This step takes 10 minutes, but DNS propagation can take a few hours. Submit the verification and move on to other steps while it propagates.
Step 5: Add MX Records
MX records tell the world where to deliver email for your domain. Google Workspace uses a single MX record pointing to smtp.google.com. Microsoft 365 uses a record like gracechurch-org.mail.protection.outlook.com.
Add these in your DNS panel. The exact values are in your provider's setup guide. Delete any old MX records that point elsewhere — having multiple MX configurations is a common source of bizarre delivery failures.
Step 6: Add an SPF Record
SPF (Sender Policy Framework) tells receiving servers which IP addresses are allowed to send mail for your domain. Without it, your messages get downgraded or rejected.
The record is a TXT entry that looks like v=spf1 include:_spf.google.com ~all for Google Workspace, or v=spf1 include:spf.protection.outlook.com -all for Microsoft 365.
You only get one SPF record per domain. If you also send through Mailchimp or another bulk tool, you add their include in the same record: v=spf1 include:_spf.google.com include:servers.mcsv.net ~all.
Step 7: Add DKIM Signing
DKIM (DomainKeys Identified Mail) cryptographically signs outgoing messages so receiving servers can verify they really came from you. Both Google and Microsoft generate a DKIM key during setup and ask you to add it as a TXT record.
Without DKIM, Gmail and Yahoo will increasingly mark your messages as suspicious. With it, deliverability stays high. Skip this and your church newsletter starts landing in spam folders six months from now.
Step 8: Add a DMARC Record
DMARC ties SPF and DKIM together with a policy. It tells receiving servers what to do if a message fails authentication.
Start with a soft policy: v=DMARC1; p=none; rua=mailto:dmarc-reports@gracechurch.org. This monitors traffic without rejecting anything. After a month of reports, tighten to p=quarantine or p=reject.
DMARC is the step most ministries skip, and it is increasingly the step Gmail uses to decide whether your mail is legitimate. Do not skip it.
Step 9: Create User Accounts
Create accounts for each staff person at firstname@gracechurch.org. Avoid putting role titles in the local part — pastor@ is fine for a public-facing alias but should not be someone's primary mailbox, because pastors change.
Step 10: Set Up Aliases and Shared Mailboxes
Create role aliases like info@, give@, prayer@ that forward to the right person or team. Aliases are free in both Google Workspace and Microsoft 365. For accounts multiple people need to access (info@, for instance), use a shared mailbox or Google Group rather than sharing one person's password.
Step 11: Migrate Existing Mail
If staff want to bring over their old Gmail or Yahoo messages, both providers offer migration tools. Allow a day for large mailboxes. Most people find they do not actually need old messages, but the option is there.
Step 12: Update Everywhere the Old Address Lives
This is the step most often missed. Update the new address on your website, social profiles, donor receipts, business cards, vendor accounts, and bank records. Set up forwarding from the old addresses for at least six months while everyone adjusts.
A Note on Stewardship
Email is one of those infrastructure decisions that quietly shapes how a ministry communicates for years. Setting it up carefully is a small act of caring for the people you write to — your messages reach them, the trust is built into the address itself, and the relationships outlast any individual staff member.
If you want help walking through the setup or migrating an existing ministry off personal email, reach out through our contact page.