cPanel email to Google Workspace

Why is a cPanel email migration different?

A cPanel email migration is different because your email and your website usually share the same hosting account, the same server, and often the same DNS zone. A careless DNS change can take the website offline, and a careless hosting change can cut off email. The mailbox copy itself is a standard IMAP move. The care goes into DNS and server settings.

Most cPanel hosts also include an email routing setting for each domain. It tells the server whether it handles your mail locally or whether mail lives somewhere else. After you switch to Google Workspace, this setting matters, and we cover it below. For a wider view of IMAP, Exchange, and Notes moves, see our email migration guide.

How do you copy cPanel mailboxes into Google Workspace?

You copy cPanel mailboxes with an IMAP migration tool that signs in to each mailbox on your hosting server and copies its messages into the matching Google Workspace user. Google's data migration service in the Admin console can do this for basic moves.

The steps:

1. Verify your domain in Google Workspace and create a user for each cPanel mailbox you want to keep.
2. Get the IMAP server name and port from your host. They can confirm the right values for your account.
3. Collect each mailbox password, or reset passwords from the email accounts area in cPanel.
4. Test one mailbox, then copy the rest while people keep working.

This is a good time to clean up. Hosting accounts often collect old mailboxes nobody uses. Only create Google Workspace users for the ones you need, and turn shared addresses into Google Groups where that makes sense.

How do you change DNS without breaking your website?

You change only the MX records and the SPF record, and you leave every other record alone. Start by finding where your DNS is hosted. It may be in cPanel's zone editor, at your domain registrar, or with a separate DNS service. The MX change only works where your domain's nameservers point.

Then follow these steps:

• Export or screenshot the full zone before you edit anything.
• Replace the old MX records with the Google Workspace values shown in the Admin console.
• Update SPF so it authorizes Google, and keep any other senders you still use.
• In cPanel, set the domain's email routing to remote, so the server stops treating your mail as local.

That last step fixes a common problem. If routing stays local, mail sent from the website, such as contact form messages, may be delivered to the old mailbox on the server instead of to Gmail. Our MX record cutover guide covers timing, and our guide to SPF, DKIM, and DMARC covers the authentication records.

What does not move from cPanel automatically?

Settings and anything stored outside the mailbox do not move automatically. An IMAP copy brings mail and folders. It leaves behind:

• Forwarders and autoresponders.
• A default or catch-all address.
• Mailing lists set up on the host.
• Spam filter rules.
• Contacts and calendars saved in the host's webmail.

List these during discovery and decide how to rebuild each one in Google Workspace. Google Groups can replace mailing lists and shared forwarders. Our list of what does not migrate automatically is a useful checklist.

When can you delete the old cPanel mailboxes?

You can delete the old cPanel mailboxes after the final sync is complete, no new mail is arriving there, and every user has confirmed their messages are in Gmail. Keep them for a short buffer period, in case someone spots a missing folder.

Do not cancel your hosting plan if your website still lives there. You are only moving email. Removing old mailboxes also frees up disk space on the hosting account.

Next step

Our IMAP migration service handles cPanel moves, including the DNS and routing changes that keep your website safe.