We’re Excited to Announce the Teams Private Chat Rehydration Release
MigrationWiz is the industry-leading SaaS solution for streamlining migrations across mailboxes, documents, public folders, personal archives, hybrid exchange management, and Microsoft Teams. Our platform enables users to easily discover and select items at the Source, map and sync the Destination, verify, test, pre-stage, and identify potential issues before a full migration. With detailed post-migration reports, MigrationWiz ensures a thorough review of the end results. Our solution offers a fully automated, accessible anytime/anywhere, enterprise-grade security experience through a single centralized interface.
What’s New in MigrationWiz?
Teams Private Chat Rehydration
The ‘New’ Teams Private Chat ‘Collaboration’ Project enables users to migrate 1:1 chats, group chats, chat titles, long texts, rich content and styling, chat replies/threads, as well as emojis, GIFs, and stickers. Microsoft has announced that Teams Private Chat History is no longer available as part of Mailbox migrations due to their restriction on Teams data access through EWS. Accordingly, MigrationWiz users are now able to easily migrate their Teams Private Chat due to the transition from EWS API to Graph API.
Important
Please note that this feature is currently excluded from the Teams to Teams ‘Collaboration’ Project and is set as a standalone ‘New’ Teams Private Chat ‘Collaboration’ Project.
Product Enhancement Highlights
Teams Private Chat 'Collaboration' Project
MigrationWiz users can now migrate their Teams Private Chat, transferring essential components such as 1:1 chats, group chats, chat titles, long texts, rich content and styling, chat replies/threads, as well as emojis, GIFs, and stickers. Additionally, users have the flexibility to easily specify their migration preferences and parameters, requiring fewer steps to initiate and manage a migration project, allowing the migration of various components with minimal complexity.
Teams Private Chat API Enablement
MigrationWiz users should enable read-only access to Teams-protected APIs in the Azure Cloud Platform Console before initiating their MigrationWiz document migration project.
Authentication Requirements for Teams Private Chat
To have the ‘Collaboration’ project setup performed correctly, MigrationWiz users should select the following application permissions options and follow the steps to enable permission levels at the source and destination as described in the Teams Private Chat Migration Guide.
- Grant the MigrationWiz-PCH-FullControl permission level at the source tenant.
- Grant the MigrationWiz-PCH-DelegateAccess permission level at the destination tenant.
Multi-pass Migration and Post-Migration Steps
When performing the Teams Private Chat migration, a temporary ‘Migration User’ is added to the chat. If needed, multi-pass migrations can be carried out before running the ‘Clean-Up’ process. The ‘Clean-Up’ feature removes the temporary ‘Migration User’ account from all migrated chat threads, and can no longer migrate new messages in subsequent passes.
Error Handling
The Teams Private Chat feature incorporates an improved error-handling mechanism for easier issue resolution across all stages of the migration process. In cases where errors are encountered MigrationWiz users can refer to the Collaboration Error List and Troubleshooting articles to follow the listed steps.
Licensing
The current Teams Private Chat feature will not require MigrationWiz users to consume a license. However, as part of a future feature release, using Teams Private Chat migrations will require a MigrationWiz User Migration Bundle (UMB) license.
Important
Please note that this is the Teams Private Chat Replacement feature as Teams Private Chat History is no longer available as part of Mailbox migrations due to their restriction on Teams data access through EWS.