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
- Deploy EUnifyer for your organisation
- Configure your domain
- Optionally federate EUnifyer with Google as an identity broker — users keep their Google credentials during transition
Phase 2 — Import data
- Go to Admin → Switch → Organisation Import
- Follow the Google Workspace import guide to create a service account with domain-wide delegation
- 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:
- Go to Admin → Data Sync
- Select your Google credential
- Choose which data types to sync (contacts, calendar, files, mail)
- Set a schedule (default: daily at 2:00 AM UTC)
- 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 via | Action 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 API | Switch to EUnifyer Drive REST API or S3 |
Phase 5 — Email validation
Before porting your domain’s email, validate everything works inside EUnifyer first:
- Import email — Your full Gmail archive is already in EUnifyer from Phase 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.
- 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
| Data | Migrated? | Notes |
|---|---|---|
| Yes | Full Gmail archive, labels mapped to folders | |
| Calendar | Yes | Events, attendees, recurrence |
| Contacts | Yes | Google Contacts entries |
| Files | Yes | Drive files + Google Docs/Sheets/Slides converted to Office formats |
| Roles | Manual | Mapped once during import |
| Google Chat history | No | Proprietary 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
| Phase | Duration |
|---|---|
| Setup + Google federation | Half day |
| Initial data import | 4–24 hours (background) |
| Coexistence + testing | 2–4 weeks |
| Third-party reconfiguration | 1–2 weeks per system |
| Email validation (internal testing) | 1–2 weeks |
| DNS cutover (email domain porting) | 1 hour |