Current Release Notes


New Endpoints: Google Groups to Microsoft 365 Shared Mailbox 

MigrationWiz now supports a new mailbox migration scenario from Google Groups (Source) to Microsoft 365 Shared Mailbox (Destination)

What items are migrated?

  • Conversations

    • Message body and attachments

    • Metadata (Dates, Subject, Recipients)

    • Labels

  • Members

    • Email addresses

    • Roles

Ensure the following prerequisites are met before setting up a Google Groups to Microsoft 365 Shared Mailbox migration project.

  1. Enable APIs for the Service Account

  2. Google Vault license is required for the source endpoint administrator (only 1 required)​.

  3. Shared Mailbox and member users must be provisioned by the customer at the destination tenant​.

  4. Enable Conversation History on Google Groups settings​.

  5. MigrationWiz Mailbox or User Migration Bundle (UMB) licenses are required.


  • MigrationWiz leverage PowerShell to migrate the project line items, hence, there is an inherited PowerShell concurrency limitation of 3 line items per run per administrator user.

    • It is recommended that user select only 3 line items to prevent encountering this limitation. Selecting more than 3 line items may result in a timeout error.

Refer to the Google Groups to Microsoft 365 Shared Mailbox migration guide for more info.


Teams: OneNote 

  • Old Behavior:

    • If site asset document library did not exist at source (i.e. no default OneNote), migration would fail.

    • In such scenario, adding the TeamsSkipSiteAssets advanced option would help skip migration of Site Assets document library.

  • New Behavior:

    • If site asset document library does not exist at source, the migration will not be failed. Instead, an error will be logged and migration of Site Assets document library will be skipped. (This is the same behavior as when the advanced option is used).

    • Add the TeamsSkipSiteAssets advanced option to explicitly skip migration of Site Assets document library.


Teams: Dark mode compatibility 

Previously, Teams conversations that were migrated to the destination with dark mode setting were not rendered correctly and appeared unreadable. MigrationWiz has modified the solution to resolve this issue and now Teams conversations migrated to destination with dark mode will be rendered readable.

Teams: Channel tabs 

If there is a change in the source channel tabs (tab name or tab link) after the initial migration pass, users can now run another pass of the migration selecting channel tabs to get the tab changes migrated to the destination.

Note: For the destination tab link to work, the associated document must be migrated/must exist before migrating channel tabs.

Documentation Updates

New articles

Error: Unable to decode message

Article updates

Exchange Migration Setup & Planning FAQ - Broken links replaced

SharePoint & OneDrive Migration FAQs - Non-English tenant details added

MigrationWiz: the Migration Process - Migration details added

Folder Filtering & Mapping in MigrationWiz - Google Shared Drive details added

Was this article helpful?
0 out of 0 found this helpful