Skip to Content
IntegrationMigrate from Google Workspace

Migrate from Google Workspace

This guide walks you through migrating an organisation from Google Workspace to EUnifyer. Like the Microsoft migration, this is designed to be gradual with a coexistence period.


Migration Phases

Phase 1 — Set up EUnifyer

  1. Deploy EUnifyer for your organisation
  2. Configure your domain
  3. Optionally federate EUnifyer with Google as an identity broker — users keep their Google credentials during transition

Phase 2 — Import data

  1. Go to AdminSwitchOrganisation Import
  2. Follow the Google Workspace import guide to create a service account with domain-wide delegation
  3. Run the import for all users

Google Docs, Sheets, and Slides are automatically converted to Office formats (.docx, .xlsx, .pptx) during import and uploaded to EUnifyer Drive, where they can be edited with Collabora.

Phase 3 — Coexistence

Run both systems in parallel. Instead of manually running delta imports, enable automatic sync which runs daily and keeps EUnifyer up to date with changes in Google Workspace.

Setting up continuous sync:

  1. Go to AdminData Sync
  2. Select your Google credential
  3. Choose which data types to sync (contacts, calendar, files, mail)
  4. Set a schedule (default: daily at 2:00 AM UTC)
  5. Enable — EUnifyer will automatically sync new data on schedule

You can also trigger a manual sync at any time from the sync dashboard. See Continuous Sync for details.

Phase 4 — Redirect third-party systems

System connects viaAction required
Google SSO (OIDC)Switch to EUnifyer OIDC
Gmail (IMAP/SMTP)Update to EUnifyer mail server
Google Calendar (CalDAV)Update CalDAV URL to EUnifyer
Google Contacts (CardDAV)Update CardDAV URL to EUnifyer
Google Drive APISwitch to EUnifyer Drive REST API or S3

Phase 5 — Email validation

Before porting your domain’s email, validate everything works inside EUnifyer first:

  1. Import email — Your full Gmail archive is already in EUnifyer from Phase 2
  2. Test internally — Users send and receive emails between EUnifyer mailboxes using the EUnifyer domain. This confirms delivery, spam filtering, and clients work without touching your live domain.
  3. Test externally — Send/receive test emails to personal addresses to verify external delivery

Only proceed to the DNS cutover once email is fully validated.

Phase 6 — DNS cutover

Update MX records to point to EUnifyer’s mail server and decommission Google Workspace licences.

Email is the last thing you switch. Files, calendar, contacts, and SSO can all move first. The domain’s email routing only changes when you are confident the system works end to end.


What Gets Migrated

DataMigrated?Notes
EmailYesFull Gmail archive, labels mapped to folders
CalendarYesEvents, attendees, recurrence
ContactsYesGoogle Contacts entries
FilesYesDrive files + Google Docs/Sheets/Slides converted to Office formats
RolesManualMapped once during import
Google Chat historyNoProprietary format

Delta Imports

After the initial import, run the import again to bring over only new items. EUnifyer skips previously imported data automatically.

Current limitation: One-directional (Google → EUnifyer). Bidirectional sync is on the roadmap.

For automatic daily sync instead of manual re-runs, see Continuous Sync.


Timeline Estimate

PhaseDuration
Setup + Google federationHalf day
Initial data import4–24 hours (background)
Coexistence + testing2–4 weeks
Third-party reconfiguration1–2 weeks per system
Email validation (internal testing)1–2 weeks
DNS cutover (email domain porting)1 hour