Migrating cPanel email to Google Workspace is safe when you do it in the right order: copy the mail first, switch the MX records second, and catch up last. Done that way, nothing is lost and nobody stops working. This guide walks through the order that keeps mail safe, written for Kenyan businesses on shared hosting.
TL;DR — Quick Summary
Order matters. Set up Google Workspace and verify your domain. Copy old mail with Google’s data import tool while mail still arrives at cPanel. Switch the MX record to Google. Run a delta import to catch anything that arrived during the switch. Then fix devices, forms and forwarders. DNS changes usually take effect within minutes.
What should you check before migrating cPanel email?
Most migration problems are decided before anything is copied. Check these first:
- List every mailbox in cPanel under Email Accounts, with its size. Large mailboxes take longer to copy.
- Note forwarders, autoresponders and filters. They live on the server and do not move with the mail, so you will rebuild them in Google.
- Confirm IMAP access. Google’s import tool needs IMAP turned on and a mail server that accepts connections from Google’s IP ranges. Ask your host if a firewall could block it.
- Get a password for every mailbox. The tool needs one per mailbox. Reset any you do not know in cPanel.
- Find where your DNS is managed: your host, your registrar or a service such as Cloudflare. You will edit the MX record there.
- Lower the MX record’s TTL to the lowest value your DNS host allows before the switch. A low TTL makes the cutover faster.
Still choosing a platform? Compare your options in our business email in Kenya comparison or read Zoho Mail vs Google Workspace in Kenya.
How do you migrate cPanel email to Google Workspace? Step by step
Step 1: Set up Google Workspace and verify your domain
Sign up, add your domain and verify ownership with the record Google gives you. Then create a Google user for each mailbox, using the same address (for example info@yourcompany.co.ke). Do not change the MX record yet. Mail keeps arriving at cPanel while you prepare.
Step 2: Copy the old mail with Google’s data import tool
In the Admin console, go to Data, then Data import & export, then Data import, and choose IMAP. Enter your IMAP server (on cPanel hosting this is usually mail.yourcompany.co.ke) and click Test connection. Most cPanel hosts use port 993 with SSL, so confirm the settings with your host.
- Map your mailboxes with a CSV: upload a file with the columns Source ImapUser, Source ImapPassword and TargetGUser, one row per mailbox. Each import handles up to 100 users, and the file must be under 128 MB.
- Settings: choose a start date, decide whether to include deleted and spam mail, and exclude folders you do not need.
Click Start import and watch the dashboard, which shows imported, skipped and failed items in real time. Google emails you a report when it finishes. Details are in Google’s IMAP import guide.
The IMAP import copies email. If your cPanel mailboxes hold contacts or calendars, export them from webmail (vCard and ICS files) and import them into Google Contacts and Calendar.
Step 3: Switch the MX record to Google
At your DNS host, remove every existing MX record, then add one: host @, priority 1, value smtp.google.com. Some registrars need a trailing period. Old MX records left in place can send mail to the wrong server. The change usually takes effect within minutes. See Google’s MX record guide.
One cPanel setting catches many people out. In cPanel, go to Email, then Email Routing, select the domain and choose Remote Mail Exchanger. On Local Mail Exchanger, the server keeps accepting mail for your domain and delivering it to the old mailboxes, so Google never receives it.
Step 4: Run a delta import to catch stragglers
In the first minutes after the switch, some mail can still land on the old server. Once the switch has taken effect, run a delta import in the same tool. It copies mail that arrived after the first import, and retries items that failed.
Step 5: Fix everything that still points at the old server
- Phones and Outlook: remove the old IMAP account and add the Google account.
- Website contact forms: update their mail settings so they send through a Google address.
- Forwarders and autoresponders: rebuild them in Gmail, or as aliases and groups.
- SPF, DKIM and DMARC: publish one SPF record for Google and remove the old host’s include. Our SPF, DKIM and DMARC setup guide shows how.
Step 6: Close the import and keep the old mailboxes for a while
Export the import report first, because Google deletes the configuration and reports when you exit the import. Then exit it. We recommend keeping the old cPanel mailboxes for about a month as a safety net.
What usually breaks, and how do you prevent it?
Mail itself rarely fails. The small things around it do.
| Problem | Why it happens | How to prevent it |
|---|---|---|
| Mail still goes to the old server | Old MX records were left in place, or cPanel Email Routing is set to Local | Remove old MX records and set Email Routing to Remote Mail Exchanger |
| Mail missing in Gmail | The import start date or exclusions skipped it | Check the start date and excluded folders, then run a delta import |
| Forwarders and autoresponders gone | They live on the server, not in the mailbox | Rebuild them in Gmail as forwarding rules, aliases or groups |
| Contact form emails in spam | The site still sends through the old mail account | Update the form’s mail settings and set up SPF and DKIM |
| Duplicate SPF records | The old host’s SPF was kept next to Google’s | Publish one SPF record and merge the senders |
| People think email has stopped | Old IMAP profiles are still on phones and Outlook | Remove the old account and add the Google account |
Our experience migrating cPanel email
We recently moved a client’s website hosting and email from cPanel webmail to Google Workspace. We migrated everything without losing any data and without affecting the normal operations of the business.
How much does it cost to migrate cPanel email to Google Workspace?
Google licences are paid to Google or through Studio6 managed billing. See current rates on Google’s pricing page. Studio6 charges a one-time setup fee of KES 6,500 plus KES 1,500 for each mailbox migrated. Optional monthly support is KES 3,000.
| Mailboxes | One-time fee (setup plus migration) |
|---|---|
| 3 mailboxes | KES 11,000 |
| 5 mailboxes | KES 14,000 |
| 10 mailboxes | KES 21,500 |
| 25 mailboxes | KES 44,000 |
If you are moving up from hosting email, ask about discounted or waived migration fees.
Frequently asked questions
Will I lose email when I migrate from cPanel to Google Workspace?
Not when it is done in the right order. Old mail is copied first while mail still arrives at cPanel, then the MX record is switched, and a delta import picks up anything that arrived in between.
How long does it take to migrate cPanel email to Google Workspace?
Copying time depends on mailbox size, and Google shows progress in real time. The MX change usually takes effect within minutes, so the cutover itself is quick. Plan it outside working hours and keep the old mailboxes for a few weeks.
Do I need to cancel my cPanel hosting?
No. Your website can stay on cPanel hosting. Only the mail routing changes: you point the MX record at Google and stop using the cPanel mailboxes.
Does Google’s import tool move contacts and calendars from cPanel?
For IMAP sources such as cPanel, the import tool copies email. Export contacts and calendars from your webmail and import them into Google Contacts and Google Calendar.
Can I keep my email addresses when I move to Google Workspace?
Yes. Your addresses live on your domain, so they stay the same. Only the platform behind them changes.
Need help choosing or moving?
Studio6 sets up, migrates and supports business email for Kenyan teams. Tell us how many people you have and where your email lives today, and we will recommend a path. Talk to Studio6
