Why Move From cPanel or an In-House Mail Server to Google Workspace? What You Gain and What It Takes

If your business email runs on a cPanel hosting package, or on a server in your own rack, you have a mail system. You do not have a way for people to work together. Documents travel as attachments, the latest version is whoever sent it last, and the person who set it all up is the only one who knows how it works.

Moving to Google Workspace is often described as an email migration. It is better understood as a change in what your team can do, and in what you no longer have to look after. This article starts with that, then explains what the move involves. The technical detail is kept to one section near the end, for whoever on your team will do the work.

What your team gains

One place for files, not a trail of attachments. In Google Docs, Sheets and Slides, several people work in the same file at the same time. Drive keeps it in one place, with an access list you control. For a finance team chasing the final version of a budget, or a project team sharing a proposal with a client, that alone changes the week.

Storage that is part of the licence. Per Google's plan comparison, the Business editions include pooled storage per user: 30 GB on Starter, 2 TB on Standard and 5 TB on Plus. Compare that with a hosting package, where mailbox space usually comes out of the same disk allowance as your website, and a full mailbox is a support call.

Meetings without extra tools. Google Meet is included. The same comparison lists up to 100 participants on Starter, 150 on Standard and 500 on Plus, with recording saved to Drive on the higher plans. A cPanel mailbox gives you none of this.

Gemini, Google's AI assistant, on higher plans. Google's own comparison lists Gemini features in Gmail, Docs, Sheets, Slides and Meet on Standard and Plus, including meeting notes and summaries. Starter includes less. Whether this matters to you today is a fair question, but it is part of what the licence buys.

Control over who can see what. Every account is managed from one admin console. When someone joins, you create their account in minutes. When someone leaves, you suspend it the same day and their files stay with the company. On a plain mail host, offboarding usually means changing a password and hoping. Plus adds tools such as Vault for retention and eDiscovery, aimed at organisations with records obligations.

Work from a phone or a borrowed laptop. Staff sign in from any browser or the mobile apps. Nothing depends on a particular office PC or on the person who configured their email client.

What you stop carrying

Running your own mail is a job, whether or not anyone is assigned to it. With Workspace, the servers, the software updates, the storage and the mail delivery become Google's responsibility. That means:

• No single server to fail. Your mail no longer goes down because of one machine, one disk or one hosting account.
• No quota firefighting. The recurring "my mailbox is full" call goes away.
• No dependency on one admin. The setup lives in a console with proper roles, not in one person's head.
• Less exposure to local disruption. Power cuts and link failures still affect your office, but they no longer take your mailboxes offline with them.

Be realistic about what does not change. Your internet connection still decides how good the experience is, and Workspace is licensed per person per month, so it is a running cost where a hosting package is often a cheaper fixed line. The honest question is not "which is cheaper per mailbox" but "what does a day of lost email, or a week lost to version confusion, cost us". For some organisations, a plain mail host is still the right answer.

Who should be in the conversation

This is rarely only an IT decision. The people who feel the benefits and the costs are usually:

• The managing director or head of operations, who cares about whether the team can work together and whether the business depends on one person.
• Finance, who need to understand a per-person, monthly cost and how it is billed. We can invoice in Kwacha, though as we explained in our guide to buying Workspace in Africa, that is a convenience rather than a discount, because the underlying price follows the dollar.
• Legal or compliance, where you handle personal or sensitive data. Zambia has a Data Protection Act, No. 3 of 2021, and storing data with a foreign cloud provider, and moving it across borders, is a question to settle before the move, not after. We are not lawyers and this is not legal advice.
• IT, who will do the work and own it afterwards.

What the move involves

In plain terms, a migration runs in five stages:

1. Take stock. List every mailbox, shared address and system that sends email from your domain, such as your website form, your invoicing software and your scanner. Most surprises come from things nobody remembered.
2. Set up Workspace alongside the old system. Create the accounts and the admin basics. Mail still flows to the old server, so nobody notices anything yet.
3. Copy the mail across. Google's tools copy each person's existing email into their new account. This takes hours to days depending on volume.
4. Switch over. One change to your domain's settings points incoming mail to Google. After that, new mail arrives in Workspace.
5. Support people, then retire the old system. Run a short training session, support the first few weeks, take a final backup, and only then cancel the old hosting or switch off the server.

Two limits are worth knowing. Google's documentation is clear that these tools move email only, not calendars, contacts or Drive files, so those are planned separately. And your website does not have to move: it can stay on its current hosting while only email changes.

For your IT team

The following is the detail the person doing the work will want. It follows Google's Admin Help documentation, which is worth checking before you start because Google updates it.

Choosing the tool. In the Admin console, migration tools sit under Data > Data import & export.

• The data migration service (IMAP) suits a server with a trusted TLS certificate that Google can reach over the internet. cPanel mail is standard IMAP, so this is normally the right choice. Google lists Dovecot, Zimbra, Courier and Cyrus among compatible servers.
• Google Workspace Migration for Microsoft Exchange (GWMME) suits a server with no trusted certificate, one on an internal network Google cannot reach, or one that uses plain usernames instead of email addresses to log in. It runs on a Windows machine or from the command line.

What the IMAP import expects. Per Google's documentation:

• A super administrator must set up and run the import. Google states that resellers cannot run it for a customer, so a partner can plan, support and troubleshoot, but the import is started from your own admin account.
• IMAP must be turned on for the source and the Workspace accounts, and some servers need an application-specific password.
• One import covers up to 100 users, and you map accounts with a CSV file beyond 20 users.
• You can set a start date, exclude folders, and choose whether to include deleted and spam mail.
• A delta import after the first pass collects mail that arrived in between.
• Export the report before you exit the import, because Google notes you cannot reach it afterwards.

The switchover. Google's current instruction is a single MX record pointing to smtp.google.com, and it can take up to 72 hours to be recognised everywhere. Older accounts may show the previous aspmx records. If your DNS sits in the same cPanel account as your website, change only the mail records, not the whole zone. Lower the TTL a day or two beforehand, choose a quiet window with someone awake to check, keep the old server running until new mail is confirmed arriving, and then set up SPF, DKIM and DMARC so your messages are trusted by receiving servers.

Local realities. In an IMAP import, Google pulls mail from your server, so your server's upload capacity sets the pace. On a modest link, schedule the bulk copy for nights and weekends and use the start date to leave out mail nobody needs. Interruptions to power and connectivity are a reason to choose your cutover window carefully.

Questions to ask before you start

• Which Workspace plan fits our people, and how many seats do we really need?
• What does our data-protection position allow, and has someone with legal responsibility signed off?
• Which of our systems send email from our domain?
• How much mail do we have, and what link does it have to travel over?
• Who will own the admin console after the partner steps back?

If you want help answering those, the most useful first step is a short review of what you have today. From that we can tell you honestly how big the job is and whether Workspace is the right fit. We migrated our own company's email from Zoho to Google Workspace, so the process described here is one we have run ourselves.