Skip to Content
Email Migration Service

Move every
mailbox.
Zero downtime.

We migrate your organisation from any email platform to any other. Google Workspace, Microsoft 365, cPanel, Zoho, on-premise Exchange. Full data fidelity and no disruption to your team while it happens.

Google Workspace
Microsoft 365
Exchange On-Prem
cPanel Mail
Zoho Mail
BITHOST EMAIL MIGRATION — LIVE STATUS client: acmecorp.com · Google Workspace → Microsoft 365 · phase: active migration ● IN PROGRESS SOURCE Google Workspace MAILBOXES 247 accounts total DATA VOLUME 1.84 TB emails + attachments + contacts + calendar DOMAIN acmecorp.com MX: Google (active) ✓ Verified and accessible MIGRATION ENGINE OVERALL PROGRESS 68% TRANSPORT ✓ TLS 1.3 encrypted ✓ DKIM preserved ✓ SPF updated THROUGHPUT 42 GB/hr ITEMS MIGRATED 168 / 247 mailboxes 1.26 TB transferred ETA: 6h 40m remaining DESTINATION Microsoft 365 MAILBOXES READY 168 of 247 completed DATA RECEIVED 1.26 TB integrity verified · 0 errors DOMAIN acmecorp.com MX: M365 (cutover pending) ◎ MX cutover on completion MAILBOX STATUS — LAST 6 UPDATED ✓ j.smith@acmecorp.com 4,812 items · 2.1 GB · contacts: 381 · calendar: migrated · complete ✓ a.patel@acmecorp.com 3,240 items · 1.4 GB · contacts: 207 · calendar: migrated · complete ◎ cfo@acmecorp.com 6,112 items · 8.4 GB · transferring now · 72% complete ◎ sales@acmecorp.com (shared) 14,881 items · 5.2 GB · shared mailbox · queued next ○ m.chen@acmecorp.com pending · scheduled 08:45 · estimated 45min ○ d.kumar@acmecorp.com pending · scheduled 09:30 · estimated 30min bithost-migration ~
Migration progress
68%
168 of 247 mailboxes complete
Data integrity
0 errors TLS 1.3
Google Workspace to M365 Zero Downtime Cutover Exchange to Google Contact and Calendar Migration cPanel to Business Email DKIM and SPF Reconfiguration Zoho Migration Shared Mailbox Migration Full Data Fidelity MX Cutover Management Google Workspace to M365 Zero Downtime Cutover Exchange to Google Contact and Calendar Migration
Why organisations move

The real reasons companies
switch email platforms.

Most email migrations get stuck not because of the data but because of the DNS, the downtime risk, and the 200 users who will call IT the moment something looks wrong. We have done this enough times to know where every risk lives.

Licensing cost restructuring

Moving from Google Workspace to Microsoft 365 or vice versa is often driven by licensing deals, bundle pricing with other Microsoft or Google products, or a consolidation decision made at the IT procurement level.

Acquisition and merger

Two companies on different email platforms need to consolidate. One side is on Exchange and the other is on Google. Resolving that without losing historical mail, contacts or calendar access is the migration problem we solve most often.

Security and compliance requirements

Industry regulations, government contracts or internal security policy changes can mandate a specific platform. Moving to a platform with a specific data residency, audit log or retention policy requirement is a common driver.

Moving off on-premise infrastructure

Ageing Exchange servers, expiring hardware support contracts and the cost of maintaining on-premise mail infrastructure push organisations toward cloud email. We handle the full move from on-prem Exchange to M365 or Google Workspace.

Shared hosting to professional email

Growing businesses that started on shared cPanel hosting email need to move to a professional platform that supports SPF, DKIM, DMARC and gives users mobile sync, shared calendars and proper collaboration tools.

Team growth and admin overhead

Managing 10 users on cPanel is fine. Managing 200 is not. Organisations hit a point where user provisioning, password resets, shared mailboxes and distribution lists need a proper admin console and directory sync.

Migration routes

Every platform
combination covered.

The route does not matter as much as doing it right. We migrate emails, contacts, shared calendars, distribution lists and shared mailboxes with full data fidelity regardless of where you are starting from or going to.

Google Workspace
Microsoft 365

Google to M365

The most common enterprise migration route. We move all Gmail, Drive-linked emails, Google Contacts, Google Calendar events and shared drives data over to Exchange Online, SharePoint and M365 Contacts. MX records are cut over with a maintenance window of under 30 minutes.

Gmail to ExchangeCalendar syncContactsShared mailboxes
Microsoft 365
Google Workspace

M365 to Google

Moving from Exchange Online to Gmail requires careful handling of Outlook-specific folder structures, rules, and the calendar and contacts data models which differ significantly between the two platforms. We translate all of this without data loss.

Exchange to GmailCalendar convertFolder mappingRules migrate
Exchange On-Prem
Cloud Email

On-premise Exchange to cloud

Moving off Exchange 2010, 2013 or 2016 to either M365 or Google Workspace. We handle the hybrid configuration, public folder migration, distribution list recreation and the decommissioning plan for the on-premise server.

Hybrid configPublic foldersDistribution listsDecommission plan
cPanel / Hosting
Business Email

cPanel to business email

Moving from shared hosting email to Google Workspace or M365. We export all IMAP mailboxes, migrate every message and folder, set up your custom domain on the new platform and handle the SPF, DKIM and DMARC DNS records for your domain.

IMAP exportDKIM setupSPF recordsDMARC policy
Zoho Mail
M365 or Google

Zoho and other providers

If your source or destination is not listed above, the answer is still yes. If a platform exposes IMAP or an export API, we can migrate from it. We have handled Fastmail, Rackspace Email, Yahoo Business Mail and several regional providers.

IMAP migrationAny sourceAny destinationData verified
Any Platform
Any Platform

Staged and phased migrations

Large organisations often cannot migrate all mailboxes at once. We run staged migrations by department, by location or by user group. Users on the old and new platform can still email each other throughout the migration period with no disruption.

Phased rolloutCoexistenceDepartment firstRollback ready
How a migration works

Five phases.
No surprises.

01
Discovery and scoping

We audit your current mail environment. Mailbox count, total data volume, shared mailboxes, distribution lists, mail rules, calendar sharing and any third-party integrations that connect to your current email platform.

02
Destination setup

We provision your new email environment, create all user accounts, configure admin policies, set up shared mailboxes and distribution lists, and verify domain ownership before a single byte of mail is moved.

03
Pre-migration sync

We run the initial bulk migration while your team continues working on the old platform. This moves the majority of historical email, contacts and calendar data before the cutover, so the final switch window is as short as possible.

04
MX cutover

We run a final delta sync, update your MX, SPF, DKIM and DMARC DNS records, and switch your domain to the new platform. New mail starts arriving in the new platform within minutes of DNS propagation.

05
Verification and handover

We verify every mailbox for data completeness, test inbound and outbound mail flow, check calendar and contact sync, and hand over admin credentials with full documentation. A 14-day post-migration support window is included.

Phase 01 — Discovery and scoping Example engagement
Discovery — what we found before touching anything
247 active mailboxes across 3 domainsacmecorp.com (primary) plus two legacy acquisition domains still receiving mail that nobody had noticed.
14 shared mailboxes not in the user directoryCreated directly in Google Admin over the years without corresponding user records. Would have been missed by a naive export.
3 third-party apps connected via Gmail APICRM, support desk and an email archiving service. All need to be reconfigured to point at M365 after cutover.
Total volume: 1.84 TB across all mailboxesAverage 7.4 GB per mailbox. Largest single mailbox: CFO at 84 GB. Estimated migration time at 42 GB/hr: 44 hours pre-sync.

The two legacy acquisition domains were the critical discovery. Mail was still arriving there and being forwarded. If those MX records had not been updated during cutover, inbound mail would have been lost to the old platform.

Destination setup — before migration begins
User accounts
247 of 247
Shared mailboxes
14 of 14
Distribution lists
38 of 38
Domain verified
3 of 3
Licences assigned
247 of 247

Destination fully provisioned before a single mailbox is migrated. Users receive their new credentials in advance so they can log in and verify their account before the cutover date.

Pre-migration sync — bulk transfer in progress
Mailboxes done
168 / 247
Data transferred
1.26 TB
Contacts migrated
18,440
Calendar events
94,200
Error rate
0.00%

Team is still working normally on Google Workspace throughout this phase. New mail arriving during pre-sync is picked up in the final delta sync before cutover. No user disruption at this stage.

MX cutover — the switchover sequence
Final delta sync completed — 0 missing itemsSaturday 02:14. Delta covered 6 hours of new mail since last sync. 1,842 new items transferred in 8 minutes.
MX records updated — M365 now primaryTTL set to 300 seconds 48 hours before cutover. Propagation complete within 4 minutes of update.
SPF record updated for all 3 domainsRemoved Google SPF include. Added M365 include. DMARC policy left at p=quarantine during 48-hour verification window.
DKIM selectors active on M365Selector1 and selector2 both signing outbound mail. Verified via MXToolbox and external send test.

Total cutover window: 22 minutes. First new mail arrived in M365 inboxes at 02:36. Old Google Workspace platform left running in read-only for 30 days as fallback archive.

Verification and handover — post-migration checks
All 247 mailboxes verified for item count paritySource vs destination item counts checked. 0 mailboxes with a discrepancy greater than 3 items (duplicates from delta sync, expected).
Inbound mail flow tested across all 3 domainsExternal send test from Gmail, Yahoo and Outlook confirmed delivery into M365 for all domains including legacy acquisition domains.
Outbound mail authenticated and deliverableDMARC pass confirmed. SPF and DKIM both passing. No mail landing in spam during 48-hour post-cutover monitoring window.
Admin documentation and credentials transferredGlobal admin credentials, documentation, DNS records map and 90-day retention policy configuration handed to client IT team.

14-day post-migration support window open. Client IT team has a direct escalation path for any user-level issues in the first two weeks. No issues raised in this engagement.

What we guarantee

No data loss.
No mail left behind.

Every migration we run carries the same baseline commitments regardless of the number of mailboxes or the platform combination. These are not aspirations. They are the conditions we meet on every engagement.

0

Emails lost during migration

Every item migrated is verified against the source. Any discrepancy is investigated and resolved before we close the engagement.

<30m

MX cutover window for most migrations

With pre-migration sync complete before the cutover, the actual window where mail might be in transit between platforms is under 30 minutes.

14

Day post-migration support window included

Every engagement includes a 14-day post-cutover support window for user-level issues, delivery anomalies and any DNS-related questions that arise.

100%

Of your historical mail accessible day one

Users log into the new platform and see their complete email history. Nothing is archived separately or requires a second retrieval step.

500+
mailboxes migrated
in a single engagement
6
email platform
combinations handled
0
emails lost
across all migrations
14 days
post-cutover support
included as standard
FAQ

Before we scope
your migration.

No. The bulk of the migration runs while your team continues working on the old platform. The actual cutover window, when we switch the MX record so new mail flows to the new platform, is typically under 30 minutes and is scheduled for a weekend or overnight. Users log in Monday morning and their full email history is there waiting for them.
For a 50-mailbox migration the total elapsed time from engagement start to completed cutover is typically 5 to 7 business days. For 250 mailboxes it is 10 to 14 days. The limiting factor is rarely the data transfer speed. It is the pre-migration setup, the DNS change windows, and your team availability to participate in verification before we close out. We give you a specific timeline after the discovery phase.
Both migrate with full fidelity. Calendar events including recurring series, attendees, responses and meeting links are migrated and recreated in the destination calendar system. Contacts migrate with all fields including phone numbers, addresses and notes. Shared calendars and resource calendars are handled separately and require mapping from the old permission model to the new one, which we do as part of setup.
Yes. Shared mailboxes, functional email addresses, distribution groups and mailing lists all migrate. We recreate them on the destination platform with the same membership and permissions where the platforms allow it. We document any cases where a permission model on the old platform has no direct equivalent on the new one and provide a recommended alternative configuration.
This is one of the most commonly overlooked parts of an email migration. During discovery we identify every third-party app connected to your current email via OAuth, API key or SMTP relay. CRM systems, support desks, e-commerce platforms, marketing tools and archiving services all need to be reconfigured or reconnected after cutover. We document every integration and provide a reconfiguration checklist your team can follow.
We handle the full DNS email authentication configuration as part of every migration. This means creating or updating SPF records for your new platform, enabling DKIM signing on the destination and configuring DMARC with a policy appropriate for your stage of deployment. We monitor for authentication failures in the 14-day post-migration window and adjust if anything surfaces.
Yes. Organisations with multiple domains on the same platform are common. We scope each domain as part of the discovery phase and handle MX, SPF and DKIM updates for each domain separately as part of the cutover. Alias domains and legacy acquisition domains that are still receiving mail are included in scope at no additional cost.

Ready to move?
Let us handle
every mailbox.

Tell us your source platform, destination, mailbox count and your target timeline. We will send you a scoped migration plan within 24 hours.

Plan my migration
Google Workspace · Microsoft 365 · Exchange · cPanel · Zoho · Any provider