Migrating your business email
What happens when we move your business email from one provider to another — what transfers, what doesn't, how to avoid losing messages, and what to expect during the switch.
Your business email is critical. Unlike a website that can be down for a few hours, disruption to your email has immediate business consequences — missed client messages, failed invoices, or staff unable to communicate.
Email migrations require careful planning, the right order of operations, and testing before any changes go live.
Quick summary
Migrating business email involves moving your mailboxes, their existing messages, and your domain's email DNS records (MX records) to a new provider. The migration itself can be done with minimal disruption if properly sequenced. The most important steps are: back up all email before starting, set up the new account fully before switching DNS, and test before declaring done.
What you'll need
1–3 days Handled mainly by usCommon reasons for email migration
- Moving from web hosting email (cPanel) to Google Workspace or Microsoft 365
- Switching from Google Workspace to Microsoft 365 (or vice versa)
- Moving from one Google Workspace account to another (e.g. after a rebrand or domain change)
- Consolidating multiple email systems after a business merger
What transfers in an email migration
| What | Notes |
|---|---|
| Email messages | Transferred to the new mailbox via IMAP sync or migration tool |
| Sent items | Usually transfers with messages |
| Folders / labels | Transfers, though folder structure may need tidying |
| Contacts | Can be exported and imported separately |
| Calendar events | Can be exported and imported separately |
| Email address itself | The address (e.g. you@yourbusiness.com) stays the same |
What doesn't transfer automatically
Email filters, rules, and auto-replies are specific to each email platform and must be recreated manually in the new one. Shared mailboxes and distribution groups need to be set up fresh. Don't assume these carry over — check them after migration and rebuild as needed.
The migration process, step by step
We audit your current email setup. We identify all email addresses, aliases, shared mailboxes, distribution lists, and how your email is currently configured. Nothing gets missed.
We back up your email. Before making any changes, we export your mailbox contents. For Google Workspace, this is via Google Takeout. For other providers, we use an IMAP backup tool. This is your insurance policy.
We set up the new email accounts. New mailboxes are created on the new platform and fully configured — including any aliases, shared mailboxes, and distribution groups.
We migrate the message data. Using a migration tool or IMAP-to-IMAP sync, we copy all existing emails from the old mailboxes to the new ones. This can take hours for large mailboxes — it runs in the background.
We update your email app settings. We provide the new server settings for you to update in Outlook, Apple Mail, or any other email client your team uses. Or we reconfigure it for you.
We switch the MX records. The MX record (Mail Exchange record) is a DNS setting that tells the internet where to deliver email for your domain. Switching the MX record to the new provider is the moment new emails start flowing to the new platform. See email DNS records for more.
We update SPF, DKIM, and DMARC records. These DNS records tell other mail servers that your new platform is authorized to send email on your behalf. Getting these right prevents your outgoing emails from landing in spam.
We run a final sync. Any emails that arrived during the migration process are synced to the new mailbox so nothing is missed.
You confirm and we wrap up. You test that email is sending and receiving correctly on the new platform. Once confirmed, we give you the all-clear.
Before we start: what you need to do
There are a few things only you can do before we begin:
- Give us admin access to your current email platform. Invite
support@chykalophia.comas an administrator, unless your project lead has given you a different address. - Warn your team. During the migration window, email delivery continues — but instruct team members not to delete messages, change passwords, or make significant account changes until we give the all-clear.
- Identify all email addresses. Tell us about every address that needs to be migrated — including ones that may belong to staff who have left, as well as shared mailboxes and aliases.
Platform-specific notes
cPanel email (sometimes called "web hosting email") is the basic email that comes bundled with shared hosting plans. It works, but it lacks modern features, mobile sync quality, and deliverability is often poor.
Moving to Google Workspace or Microsoft 365 from cPanel is one of the most impactful email improvements a business can make.
The main challenge: cPanel doesn't have enterprise migration tools. We use IMAP migration (a standard email protocol) to copy messages across. This works well but can be slow for large mailboxes.
If you're migrating from one Google Workspace account to another (e.g. after a domain change), Google provides a migration tool in the Admin console called Data Migration Service.
If you're moving from Google Workspace to Microsoft 365, Microsoft provides a migration tool called the Exchange Admin Center, which supports Google Workspace as a source.
In both cases, we handle the migration tooling. You need to give us admin access to both the old and new accounts.
If you're moving from Microsoft 365 to Google Workspace, Google provides a migration tool in the Admin console called Google Workspace Migration for Microsoft Exchange.
If you're moving from one Microsoft 365 tenant to another, Microsoft has migration tools available in the Exchange Admin Center.
In both cases, we handle the technical configuration. You need to give us admin access to both accounts.
During the migration: what to expect
Email migration has a window where messages can land in either the old or new mailbox, depending on timing.
- Before MX record switch: All new email lands in the old mailbox as normal.
- After MX record switch: New email lands in the new mailbox. DNS propagation means this switch takes effect at different times for different senders — typically within 1–4 hours for most.
- After final sync: Any messages that arrived at the old mailbox during the transition are copied to the new one.
The result: no messages are lost, and the disruption window is very short.
Common questions
Related guides
- Pre-migration checklist
- Email DNS records (MX, SPF, DKIM, DMARC)
- Why your emails land in spam
- What is DNS?
- Give us Google Workspace admin access
- Give us Microsoft 365 admin access
Need a hand?
Learn more
Migrating between hosting providers
What a website hosting migration involves, how long it takes, what causes downtime, and how we minimize disruption when moving your site to a new host.
Google Workspace — the complete client guide
Everything you need to know about using Google Workspace for your business, from signing in to security, Gmail, Drive, Calendar, and more.