If your church still runs email through cPanel or GoDaddy's hosting email, you already know the pain: tiny mailboxes, spam filters that let junk through but block real donor replies, and an interface volunteers dread opening. Google Workspace fixes all of that, but the migration itself is where most churches get nervous, and rightly so. A botched move can drop years of donor correspondence, financial confirmations, and pastoral counseling emails into the void. The good news is that a cPanel-to-Google-Workspace migration is a well-understood process with a proven order of operations. Done correctly, your staff and volunteers keep every message, your church.org email addresses never change, and there's no day where email simply stops working. This guide walks through exactly how to do it, in the order that prevents data loss, using either Google's own tools or an IMAP transfer, plus the DNS changes that make mail keep flowing during the cutover.
Before migrating a single message, log into cPanel and go to Email Accounts to get a complete list of every mailbox tied to your domain — not just the obvious ones like pastor@ and office@, but also older accounts like giving@, youth@, or a former staff member's mailbox that nobody remembers is still receiving donor receipts. Note the storage size used by each one; cPanel shows this next to each account, and it tells you how long the migration will realistically take.
Also pull your current MX records (Zone Editor in cPanel, or GoDaddy's DNS Management page) and write down the exact values before you change anything. If the migration needs to be rolled back for any reason, you'll want the old mail routing information on hand.
Finally, check whether any mailboxes have forwarders or autoresponders set up in cPanel. These don't automatically carry over to Google Workspace and need to be recreated manually after the move, so listing them now saves a scramble later.
Sign up for Google Workspace using your church's existing domain (e.g., gracechurch.org) but do not activate MX records yet. During setup, Google will ask you to verify domain ownership — the easiest method for a cPanel-hosted domain is adding a TXT record via the Zone Editor, since it doesn't affect existing mail flow at all.
Once verified, create a user account for every mailbox from your Step 1 audit, using the exact same email address (pastor@gracechurch.org stays pastor@gracechurch.org). This is what makes the migration invisible to the outside world: nobody emailing the church needs to learn a new address, and no old business cards or bulletins become outdated.
At this stage, both cPanel email and Google Workspace mailboxes exist side by side, but mail is still flowing to cPanel only. This overlap period is intentional and is what allows the actual message transfer to happen safely.
Google provides a free built-in tool called Data Migration Service, found in the Google Workspace Admin console under Data Migration. It connects directly to your cPanel mail server over IMAP and pulls a full copy of each mailbox — every folder, every sent item, every attachment — into the matching Google Workspace mailbox. Because it copies rather than moves, the originals stay untouched in cPanel as a safety net until you've confirmed everything arrived.
To set it up, choose 'Email' as the migration source, select 'IMAP' as the protocol, and enter your cPanel mail server's hostname (usually mail.yourdomain.org or the server name your host gave you), along with the port (993 for IMAP over SSL, which virtually all cPanel hosts support). You'll need each mailbox's existing password, or an app-specific password if 2FA is enabled on the old system.
Migrate one or two test mailboxes first — ideally a small one and a large one — and manually compare message counts and folder structure against the original cPanel mailbox before migrating the rest. For churches with mailboxes larger than a few gigabytes (common for a bookkeeper's account full of donor receipt PDFs), run the migration overnight, since IMAP transfer speed depends on your host's server load and can take several hours for the largest boxes.
Once every mailbox is confirmed matching, don't delete anything from cPanel yet. Keep it as a read-only backup for at least 30 days after cutover.
This is the step people fear most, but the risk is timing, not the change itself. In your DNS provider (cPanel's Zone Editor or GoDaddy's DNS panel if GoDaddy hosts your DNS separately from your website), replace the existing MX records with Google's five MX records (ASPMX.L.GOOGLE.COM as priority 1, plus the four ALT servers Google provides at setup). Do this only after Step 3's message copy is verified complete, since new mail will now route to Google Workspace instead of cPanel.
DNS changes propagate gradually, typically within 1-4 hours but occasionally up to 24-48 hours depending on your host's TTL (time-to-live) setting. During propagation, some incoming mail may still briefly hit the old cPanel server. Because you haven't deleted the cPanel mailboxes, nothing is lost either way; just check the old inbox once more after 48 hours and manually copy over anything that arrived during the transition window.
Also update your SPF record at this stage to include Google's sending servers (include:_spf.google.com), and set up DKIM signing in the Google Admin console under Apps > Gmail > Authenticate Email. Skipping this step is the single most common reason a church's donation receipts and newsletters start landing in supporters' spam folders after migrating.
Any email forwarders you documented in Step 1 (info@ forwarding to the office manager's personal Gmail, for example) need to be rebuilt in Google Workspace as either a Group or a Routing rule in the Admin console, since cPanel forwarders don't migrate automatically. Groups work well for anything that should reach multiple people, like a prayer-request or benevolence-fund address.
If your church used a cPanel mailing list (via Mailman or a simple alias) for a congregation-wide announcement list, this is a good moment to move it into Google Groups instead, which gives volunteers a much friendlier way to manage the subscriber list without touching server settings.
Double-check autoresponders too, especially any 'out of office' or 'thank you for your donation, a receipt will follow' automated replies tied to a giving@ address. These are easy to forget and their absence isn't obvious until a donor asks why they never got a confirmation.
Give staff and key volunteers a short walkthrough of Gmail's interface changes, particularly if they're used to cPanel's Webmail (Roundcube or Horde) or Outlook desktop pointed at the old IMAP server. The two most common points of confusion are Gmail's label-based organization instead of folders, and where 'Sent' mail lives.
Have each mailbox owner do a final personal check: search their new Gmail account for a few specific known emails (an old donor thank-you, a board meeting invite from six months ago) to confirm the full history genuinely came across, not just recent mail.
Once everyone has confirmed their history is intact and mail has been flowing correctly through Google Workspace for at least two weeks, you can safely cancel the old cPanel/GoDaddy email hosting plan. Keep an export of the old mailboxes in a compressed file for your records if your host offers one before you cancel.
Get a free church email deliverability audit →No. As long as you keep using the same domain, every address (pastor@yourchurch.org, office@yourchurch.org, etc.) stays exactly the same. Only the mail server behind the scenes changes, from cPanel to Google's servers.
For a typical church with 5-15 mailboxes, expect the technical setup and message transfer to take 1-2 days, plus a 24-48 hour DNS propagation window. Most churches complete the entire process, including staff training, within a week.
Because you don't delete the cPanel mailboxes until well after cutover, any mail that briefly still routes to the old server during DNS propagation remains retrievable. Check the old cPanel inbox once 24-48 hours after the switch and manually copy over anything that landed there.
The mailbox creation and message migration steps are point-and-click in Google's Admin console, but the DNS record changes (MX, SPF, DKIM) require comfort with your domain registrar's control panel. Many churches have a volunteer with basic tech skills handle it, or use a migration service for the DNS portion specifically to avoid mistakes that cause mail delivery problems.
Yes. Google's Data Migration Service copies every folder and message, including sent mail and archived folders, so financial confirmations and donor correspondence transfer along with everything else. This is exactly why verifying message counts before switching DNS matters: it confirms nothing was skipped.