Forum Discussion
IMAP Migration from Google Workspace to Microsoft 365
Hello Team,
Greetings!!
We have recently been experiencing significant delays during IMAP migrations from Google Workspace to Microsoft 365 and would like to understand if there are any known issues or recent changes affecting IMAP migration performance.
We are aware that Microsoft provides the native Google Workspace migration method, which would generally be preferable. However, in our migration scenarios, we have split routing/coexistence configured, with the domain configured as Internal Relay in Exchange Online. Because of this setup, we are currently unable to select/configure the required target delivery domain as expected during the native Google Workspace migration process.
Could you please confirm:
Whether there are any known issues, throttling, or performance degradation with IMAP migrations from Google Workspace to Microsoft 365 recently?
Whether the Internal Relay/split-routing configuration can affect the native Google Workspace migration process or the availability of the target delivery domain option?
Is there any recommended configuration or workaround that would allow us to use the native Google Workspace migration while maintaining split routing?
Any guidance or recommended approach would be highly appreciated.
1 Reply
- BennettCrawfordCopper Contributor
Migrating emails from Google Workspace to Microsoft 365 becomes easy with a dedicated approach that preserves the emails attachments, folders, and properties. A direct IMAP to Office 365 tool can migrate mail from mailbox-only to Exchange Online without the need to export each email. The WholeClear IMAP to Office 365 Converter is a worthy tool for the conversion. It helps to transfer bulk emails from Google Workspace and many other IMAP enabled service providers, with support for email metadata. It also enables selective folder transfer without needing any extra email application. Check for migrated messages and attachments in the target mailbox.