Integration Overview

EUnifyer is designed to work alongside your existing infrastructure. Whether you are migrating from another provider or connecting third-party systems, EUnifyer uses open standards and protocols so you are never locked in.

What EUnifyer Imports Today

EUnifyer can import data from Google Workspace, Microsoft 365, and Zoho Workplace — both at the personal level and for entire organisations.

Roles and permissions are configured once during the import wizard and do not require ongoing synchronisation.

How import works

1. Connect — Provide admin credentials (service account, app registration, or OAuth token)
2. Discover — EUnifyer scans your source provider and lists all users and groups
3. Map — Assign groups to EUnifyer roles, choose which users to import
4. Select — Pick data types to import (mail, calendar, contacts, files)
5. Run — Import runs in the background with per-user progress tracking

For step-by-step instructions, see:

• Personal Import — Import your own data
• Organisation Import — Migrate an entire organisation

Delta imports

You can re-run an import at any time to bring over new data that was added to the source after the initial import. EUnifyer skips items that were already imported and processes only new entries — so each subsequent run is faster than the first.

This is useful during a transition period when some users are still working in the old system while others have moved to EUnifyer.

Note: Delta imports are one-directional (source → EUnifyer). Changes made inside EUnifyer are not pushed back to the source.

Continuous sync

Instead of manually re-running imports, admins can enable automatic sync that runs on a daily schedule. EUnifyer uses provider delta APIs (where available) to fetch only changed data since the last sync.

See Continuous Sync for setup instructions and details.

Connecting Third-Party Systems

Many organisations use specialised systems — education portals, HR platforms, ERP systems, CRMs — that need to exchange data with their productivity suite. EUnifyer supports this through open protocols and APIs.

See Connect External Systems for a practical guide, and Supported Protocols for technical details.

Common integration scenarios

Coexistence with Microsoft 365

EUnifyer does not require a hard cutover. You can run EUnifyer alongside Microsoft 365 during a transition:

1. Identity federation — EUnifyer can broker authentication with Azure AD. Users keep their existing Microsoft credentials while also accessing EUnifyer.
2. Import data periodically — Run delta imports to keep EUnifyer up to date with new data from M365 during the transition.
3. Point systems gradually — As confidence grows, redirect third-party systems (education portals, HR tools) from M365 APIs to EUnifyer’s equivalent protocols.
4. Validate email internally — Import email first, then test sending and receiving between EUnifyer mailboxes using the EUnifyer domain. This proves the mail system works without touching your live domain.
5. Port email last — Only after email is fully validated do you update MX records to route your domain’s email through EUnifyer. This is the final step, not the first.
6. Complete the switch — Once all systems point to EUnifyer, decommission the M365 dependency.

This coexistence approach means there is no big-bang migration day. You move at your own pace, and email — the most critical service — is the last thing that switches over.

What is on the roadmap