Migration
Google Workspace migrations
Every migration we run is priced per mailbox and scheduled around a single weekend cutover. Discovery and permission mapping consume most of the elapsed time; the data transfer itself is rarely the constraint on a project of fewer than 500 seats.
Pick the migration path you are actually on. Each page states the duration, the fixed price, the failure modes we plan around and the parts of the job we do not cover, so you can scope the work before speaking to anyone.
Moves out of Google Workspace are quoted the same way as moves into it. We would rather run a clean export than argue you into a platform that no longer fits.
Pages in this section
- Google Workspace migration servicesMail, Drive, calendars and permissions moved to Google Workspace on a fixed per-mailbox price, with a cutover window agreed before work starts.Typical duration, 50 seats: 3–4 weeks end to end
- Office 365 to Google Workspace migrationMove Exchange Online mail, OneDrive, SharePoint sites and Teams files to Google Workspace with permissions mapped and a single weekend cutover.Exchange Online mailbox: Gmail user account, full folder tree preserved
- Google Drive to SharePoint migrationMove shared drives and My Drive content into SharePoint and OneDrive with permissions translated, Google-format files converted and links remapped.Shared drive: SharePoint document library
- IMAP to Google Workspace migrationMove mail from cPanel, Zimbra, Rackspace or any IMAP host into Gmail with folders preserved, read state intact and no lost messages at cutover.Common sources: cPanel, Zimbra, Rackspace, Dovecot, Courier, Kerio
- Google Vault export and retention supportExport Vault data for legal hold, subject access requests or platform exit, with search scoping, defensible chain of custody and usable output formats.Mail output formats: PST or MBOX, plus a metadata index
- Google Workspace vs Microsoft 365Google Workspace against Microsoft 365 on seat price, storage model, admin effort and offline working, plus what a switch actually costs to execute.Entry list price: Business Starter £5.75 / $7 vs Business Basic at a comparable seat price
- Google Workspace MX records and cutoverThe current Google Workspace MX record, the TTL behaviour that sets your cutover window, and the SPF, DKIM and DMARC records that must come first.Current MX record: smtp.google.com at priority 1, single record
What this doesn't cover
- We do not migrate on-premises file servers that have never been indexed; that is a data-classification project first.
- Legal hold and eDiscovery continuity across platforms needs your counsel's sign-off, not ours.
- We do not rewrite line-of-business applications that authenticate against the old directory.
Questions we get asked
- How long does a Google Workspace migration take?
- A 50-seat migration runs three to four weeks end to end, with one weekend cutover and two delta syncs at 7 and 14 days. Larger estates are staged by department rather than compressed.
- Is there downtime during cutover?
- Mail delivery does not stop. Inbound mail queues at the sending relay while the MX record propagates, then delivers to the new tenant, typically within an hour.
Not sure which of these you need?
Send us the shape of your estate — seat count, current platform, and the deadline you are working to — and we will tell you which of these pages applies and what it costs.