Microsoft Teams + Quest On Demand Migration
A tenant-to-tenant Teams migration is extraordinarily complicated. Why? Because this widely-adopted communication and collaboration platform isn’t a just single, standalone application. Teams actually serves as the front end to many other Microsoft 365 components, including SharePoint, Exchange and OneDrive. That’s why it’s essential that IT pros manage their tenant-to-tenant Teams migration securely, accurately and efficiently.
Quest On Demand Migration (ODM) is a solution for tenant-to-tenant Teams migration that will ensure continued collaboration, and retain valuable data stored in Teams channels, conversations and documents. You’ll be able to merge or rename Teams as they are being transferred to the target tenant. Best of all, end users will be able to continue where they have left off, even after they have been migrated, including historical data.
Consolidate Teams from multiple tenants without leaving critical files behind.
Discover all Teams on the source, including team members and Microsoft 365 groups
With the volume of Teams that likely exist in your Microsoft 365 environment, no one person or group is going to know every detail about them – or even most of them. That’s why auto discovery is so important during a tenant-to-tenant Teams migration. ODM’s Auto discovery capabilities make it easier to identify who the Team members are, which Teams have been created and how the Team is being used, thereby helping you limit sprawl and track usage.
Maximize visibility into the Teams in your environment with pre- and post-migration assessments
Ensure all content migrates accurately by boosting visibility into Teams
across your Microsoft 365 environment, including permissions, to avoid
post-migration headaches. ODM helps you determine which Teams are living in
across your environment and how the teams are used. This allows you to
prevent Teams sprawl by preventing superfluous or unwanted Teams from being
integrated into the new tenant.
Ensure coexistence for continued collaboration after a tenant-to-tenant Teams migration
Preserving important data stored in Teams channels, documents and conversations is essential to ensuring continued collaboration post migration. End users must have access to historical discussion data to continue collaboration and foster growth.
FAQ
Microsoft does not have a dedicated solution to move a Microsoft Team from one tenant to another. Moving a Team and all of the content is very complex, making a tenant-to-tenant Teams migration even more challenging. The content in a Team is stored in multiple locations. See our blog post, Microsoft Teams tenant-to-tenant migration checklist: Preparing to migrate Microsoft Teams, for a short list of Teams content and storage locations. Another blog post to review is Microsoft Teams meeting content: Where is it stored? This blog provides storage details for Teams meetings.
Typically, you need to coordinate the Teams migration planning with the content migration planning of other workloads – including SharePoint, OneDrive, and email. Thus, there is not an easy copy-and-paste solution to moving content. While you can attempt to migrate some content with PowerShell, you will soon find that it is easier to migrate all content with using a comprehensive solution for tenant-to-tenant Teams migration.
Yes, it is possible to merge content from two channels into one channel. Our On Demand Migration Teams solution for tenant-to-tenant Teams migration allows for merging of source Teams into target Teams. Merging Teams channels will move the messages and contents together.
Of course, special consideration should be given when merging content from different types of channels (standard, private, shared). Learn more details about shared channels in our blog post, Microsoft Teams shared channels/Teams Connect – Everything you need to know.
There is really just one type of Teams product for businesses; but Teams is adaptable for many business uses. The flexibility in adding components to a Team is what defines how it is used. For example, there are three types of channels:
- Standard: Available and visible to everyone
- Private: Focused, private conversations with a specific audience
- Shared: A place to collaborate with people inside and outside your team or organization
A second example is that Teams can contain Planner Plans for managing small projects. See the blog post, How to Use the Top Features of Microsoft Planner when it comes to preparing to migrate Planner plans and tasks.
A third example is that users can also use OneNote in Teams for taking notes during meetings.
These are just three examples of how to adapt a Team for business use.