Module
Mail
Loomigrate's most mature module — full transfer of messages, folders and mailbox structure.
- Any IMAP server — a direct source↔destination connection, with no intermediate copy of the content on disk.
- “Sign in with Google” — standard consumer OAuth to a Gmail mailbox, no Workspace admin rights needed.
- Microsoft Graph and Gmail API — a narrower, safer access scope than the full mailbox password, wherever possible.
- PST archive import — a single file or a whole batch at once, straight into the destination mailbox.
- Post-migration verification — a live recount of messages on the destination side, compared with what the migration reported.
Module
Calendars and contacts
Migration within a single platform and between Google Workspace and Microsoft 365.
- CalDAV / CardDAV — the standard protocols, working with any compatible server.
- Native Google and Microsoft APIs — fuller field mapping than generic CalDAV/CardDAV.
- Cross-platform migration — fields (attendees, visibility, busy status) translated between the Google and Microsoft formats.
- Recurring events — common patterns (daily/weekly/monthly/yearly, with an interval) translated in full, including individually modified occurrences of a series.
- Calendar sharing — sharing permissions replicated wherever both APIs have an equivalent role.
Honest about the limits: very complex or non-standard recurrence rules (e.g. several rules at once) are safely imported as a single event rather than risk a wrong mapping — we'd rather leave a clear note than a silent error in someone's calendar.
Module
Files
Personal and team drives, within one platform and across platforms.
- Google Drive · OneDrive — personal files, including exporting Google documents to Office formats in cross-platform migrations.
- SharePoint and Google Shared Drives — team spaces, keeping the folder structure.
- Dropbox · Box — whole team accounts migrated, no manual export/import file by file.
- Resuming interrupted migrations — state is saved per file, so an interrupted migration carries on instead of starting from scratch.
- File count verification — for personal files (Drive/OneDrive/Dropbox/Box) Loomigrate recounts the files on the destination and compares them with the number reported during the run.
Honest about the limits: transferring the “owner” role of a file towards SharePoint isn't always possible (a Microsoft Graph API limitation), and file count verification doesn't cover team spaces (SharePoint/Shared Drives) yet — personal files only.
Module
Microsoft Teams
A narrower scope than the other modules — we say so plainly.
- M365 → M365 migration — creates a new team in the destination tenant.
Honest about the limits: the new team is created without chat/channel message history — the Microsoft Graph API currently offers no way to move the conversations themselves. We don't promise what can't be done.
Module
Automation and scale
From a single account to hundreds, with full control over the pace.
- Migration waves — group accounts and start them automatically at a scheduled time.
- Concurrency limits — set per organisation, so neither the source nor the destination server gets overloaded.
- Time estimator — for mail, based on real throughput history rather than a generic guess.
- On-premise agent mode — the whole migration runs inside the client's network instead of the Loomigrate cloud.
Module
Billing
Simple rules, written into the terms and shown in the wizard before you start.
- Fee per account — one price for a mailbox (mail, calendar and contacts together), separate prices for drives, Teams and PST; credits are bought in advance and you see the total cost in the wizard before anything is charged.
- Free resyncs for 30 days after migration — the fee covers the whole migration, even one that runs for weeks, and 30 days after it finishes — re-runs and catch-up runs before cutover cost nothing.
- Refund on total failure — if an account's migration ends in error having moved nothing, the credits go back to your balance automatically; a partial failure is fixed with a free resync.
- Different account = new migration — changing the username or server means migrating a different mailbox and ends the paid window; changing only connection settings keeps it.
Module
Security
The technical details behind the promise on the home page.
- Credentials encrypted at rest — passwords, OAuth tokens and service account keys encrypted with a separate key, never in plain text in the database.
- Full audit log — every configuration change and administrative access recorded and searchable.
- Two-factor authentication — a TOTP code, an email code or a U2F/WebAuthn hardware key.
- Continuous monitoring — independent, automated end-to-end tests of the whole migration process, running around the clock and catching failures before a client notices.