[MUSIC PLAYING] Hey. My name is Malte Schoch. I'm a principal product manager at Quest, and I'm here together with Randy Rempel, also a principal product manager at Quest, and we both work on the On Demand Migration platform. And we want to talk about Teams migration today. So Randy, looking at the growth of Microsoft Teams over the last years-- not only from a number of active users, but also the volume of chat messages, the volume of data that is stored there-- it is really one of the most critical workloads but also one of the more complex workloads to migrate.
I'm interested in what is your recommendation on planning for a successful Teams migration.
Yeah. Teams has really grown rapidly over the last two years. And so we always recommend that you want to scan your team's environment, find out how many Teams you have, but also what kind of content makes up your Teams. Look at the SharePoint content, basically, your channels, the number of messages that you have in there, and also your Planner plans, and also private chat messages too.
Yeah. Let's split this up. So let's talk about the chat migration first. So obviously, chat migration is something very critical because it impacts the user directly and the user just wants to have access to their chats. I think the challenge for a lot of organization is the volume of chat messages is growing so quickly.
And if you want to migrate everything but you have a tight schedule, you might run into the situation that you [? can't ?] migrate everything. And I think for this situation, you recently released two new features, which is archiving private chats but also merging private chats. Can you tell us a bit about that?
Yeah. So it's really critical. When you're doing your private chat migration, you want to save it for right near the end. And we recommend migrating the last 30 days of messages that you have over to your target tenant and migrate it with the merge messages settings because that will run a lot faster.
So it just takes your messages, combines them together, and migrates it as a single message over to the target. But also you want to archive all the remaining messages over. And so we have a solution that just stores that into an HTML file and puts it over into your private chat also. So it runs very fast, very efficient, very good for planning purposes.
OK. But as I said-- I mean, the chat migration is one part. The other part, obviously, is the migration of Teams, of channel. And here, we have to deal with data that is stored maybe in SharePoint, but also in OneDrive. We have other applications like Planner coming into the place.
So having a tool that supports all of these workloads seems to be necessary or makes this migration easier for customers. I mean, would you agree with that?
Absolutely. You really need a product that covers everything. It has to be able to handle the SharePoint content of the conversations that occur in the channels, the Planner plans. You need something that handles everything. So one issue that we often face is, what do we do with the Teams meetings that are stored? And how do we handle the links that are in those meetings?
Yeah. That's a very good point. And that is, obviously, something you have to consider in the post-migration period. So when you decide, OK, we move now to the target tenant. Then it means that all the users have to recreate their Teams meeting links because they still point to the source, they become invalid, and you have to recreate these Teams meeting links.
And a solution can definitely help here to automate the whole process. Because if you have a lot of users, it's really a fundamental amount of work. Thank you so much, Randy, for sharing your insights. And I think we still realize that Teams migration are complex, but there are solutions available that can help customers to be successful with their migration.