Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant M&A/D Migration Expert Lead)

  Teams Personal Chat Migration   The largest challenge I have been facing is migrating 1:1 chats from one Teams tenant to another . 1:1 Chat Migration is extremely slow. Guess you have experienced this while using Teams App. If you scroll within a chat and reached the non-cached messages, they are pulling very slow. This is what you will experience upon execution of Chat messages. Additionally complex is the availability of shared files. If OneDrive isn’t fully sync’ed, placing the sharing information is impossible. This indicates the sequence for user service migration. Let’s list the three major challenges in personal chat migrations:   1.       Counting the Private Messages Teams has no out-of-the-box possibility counting the personal/ group chat messages. You could write a script using the GraphAPI:   getTeamsUserActivityCounts method A limitation exists here, it can only return the number of messages in a specified perio...

  Teams Migration for Tenant to Tenant   The Microsoft Teams Tenant to Tenant Migration Guide I have separated into the several chapters. ·        Enterprise Voice ·        Team/Channel Migration ·        Personal Chat Migration Why Teams Migration in a tenant to tenant scenario is so complex? First, Teams makes extensive use of other M365 service, considered as shared services. Teams uses Enterprise Voice, with might be using Direct Routing, Calling Plans and Operators Connect. The shared part of Teams can get very planning extensive if you need to identify Channels and migrate them along with users. You can imagine how complex the web of Teams channel user can get. The initial advise is, you have to setup a team of experienced teams consultant for voice, devices and channels. This team of experts need to work very closely with the experts of other T2T migration streams, ...