Everything you need to know about migrating your mailboxes.
No. Migrations run in the background while everyone keeps using their current mailbox. Mail is copied continuously, and you choose when to cut over to the new platform — usually after hours or over a weekend. A short delta sync catches any messages that arrived during the switch.
Google Workspace, Microsoft 365, on-premises Microsoft Exchange (2010–2019), and any standards-based IMAP or POP provider, plus legacy suites like Zimbra and IceWarp. We also handle Microsoft 365 tenant-to-tenant moves after mergers and rebrands.
There are no size limits imposed by us. We migrate mailboxes of any size, including large archives, shared mailboxes, and public folders. Transfer speed is governed only by the throttling limits of the source and destination providers.
Mail (all folders, labels, flags, read/unread state, and attachments), calendars (including recurring events and shared calendars), contacts and address books, tasks and notes where supported, and public or shared folders. Duplicate messages are automatically detected and skipped.
All transfers are encrypted in transit, and we use OAuth or least-privilege service accounts rather than storing user passwords wherever the platform allows it. Every migration produces an audit trail and per-mailbox report, which helps you meet privacy and compliance obligations.
Failed or throttled items are retried automatically. Anything that still cannot be moved is logged in a per-mailbox error report, so you know exactly which message was affected and why — nothing fails silently.
Sign in to the migration console, connect your source and destination accounts, and run a pre-flight check. The check validates access, folder mappings, and throttling limits before any data moves. From there you can schedule the migration on your own timeline.
Still have questions?
Contact our migration team →