BridgeAD migrates Gmail and Google Workspace mailboxes, IMAP hosts, on-premises Exchange, and PST/EML archives into Microsoft 365 — and back out — over one certified canonical engine. Every cross-provider job runs under a signed fidelity contract, and every item is hash-verified into a tamper-evident custody ledger you can export and verify offline.
Whether you are consolidating a Google Workspace acquisition into Microsoft 365, rescuing mailboxes from a legacy IMAP host, retiring an on-premises Exchange server, or exporting mailboxes to archives for retention — the same engine, the same evidence, the same controls.
Cross-provider migration is not a bulk copy — it is a controlled operation with disclosure up front and proof at the end.
Add source and destination connections with guided, provider-specific setup steps. Credentials stay in the platform secret store.
Before a cross-provider job starts, BridgeAD generates a signed contract listing exactly what carries losslessly, what degrades, and what drops — you approve it, hash-bound.
Baseline and delta passes with throttle-adaptive pacing, typed failure triage, and per-item outcomes.
Every item is hashed at source and verified at target into Merkle-rooted, tamper-evident custody batches — exportable as an offline-verifiable evidence pack.
Yes — the Gmail → Microsoft 365 route is certified and available now. It runs on customer-supplied Google service-account credentials with domain-wide delegation, so no third party ever holds your Google tenant keys. Mail migrates as full MIME with original dates; calendars and contacts map per the signed fidelity contract.
Any RFC-compliant IMAP host — Zimbra, Dovecot, cPanel/Plesk mail, and legacy providers. The route is mail-only by design (IMAP exposes no calendars or contacts), and the fidelity contract states that before you start.
Mailboxes export to and import from EML/JSON archives in your own storage account, with custody hashes that verify offline. Binary .pst packaging is available on request.
Nothing silently. Every route has a fidelity policy listing lossless, degraded and dropped item classes; you approve it as a contract before the job starts, and every skip is recorded against its contract line in the evidence pack.
Two things: the fidelity contract — loss disclosure you approve up front instead of a knowledge-base caveat — and the custody ledger, which hash-verifies every item into tamper-evident records you can audit offline. See the detailed comparison.