Posted on
microsoft teams

Are you currently get yourself ready for moving to Office 365 and want some guidance? Download our free web seminar on-demand “Planning Office 365: Managing Content On Your Migration” today!


This is actually the sixth inside a seven-part blog series about moving to Microsoft Teams. Discover the others below:

In the last articles within the series, I’ve spoken about moving TO Microsoft Teams and it is connected components. However, how about the scenario where you need to migrate FROM Microsoft Teams?

No, I am not speaking about moving to Slack or any other platform. I’m speaking about when a company really wants to migrate in one Office 365 tenant to a different. This usually exists within the situation of acquisitions and mergers, and it is something I’ve were built with a lot of expertise with while running these business (Paradyne–a firm that specialised at work 365 migrations) so when that business itself was acquired so we needed to migrate right into a new tenant.

Which was almost four years ago, however, and Office 365 would be a lot simpler in those days. Office 365 Groups and Sway remained as new, PowerApps had been released, Forms, Planner and Flow weren’t in preview yet, and rumours of Microsoft Teams (or “Skype Teams” because it was known as) were a lengthy way away.

In those days, a migration between Office 365 tenants was relatively straightforward:

  • Migrate mailboxes
  • Migrate OneDrives
  • Migrate SharePoint sites
  • Migrate Yammer systems
  • Cut over email routing
  • Reconfigure finish-user devices
  • Place your ft up

It was not always easy and simple, but there is much less emigrate than there’s today. And just like a glitch within the Matrix, you’re sure you’ve seen the items in your tenant before it’s difficult to shake the sensation that there’s something wrong about this.

Need assistance working out O365 tenant-to-tenant migration? Read this publish: Click To Tweet

Flash toward today, and Office 365 is really a behemoth of the platform with several core workloads and a lot of smaller sized apps and services that interconnect between one another. We have Exchange Online for mailboxes, OneDrive, SharePoint, and Yammer. However, we currently also provide Bookings, Flow, Forms, Kaizala, MyAnalytics, Office 365 Video (still), Planner, Power BI, PowerApps, Stream, Sway, and (obviously) Microsoft Teams. To-Do can also be there, but that’s operated by Exchange Online there aren’t any major issues.

Office 365 Groups straddles across several of these services, so although it itself need not be migrated, the constituents it connects to complete.

There are all of the interconnected services for example Azure Active Directory and Microsoft Intune (along with the Home windows 10 and cellular devices linked to both of them), Microsoft Information Protection, and so forth.

However , there isn’t any good way to migrate many of these in one Office 365 tenant to a different. Although some applications like Sway permit you to duplicate sways between accounts, this is accomplished on the per-sway basis and may simply be transported by the finish user. Flows and PowerApps could be exported as packages after which imported again, but forms of individually performed.

Now let’s bring this to the main focus of the blog series: Microsoft Teams. Can Microsoft Teams be migrated between Office 365 tenants?

Technically, no, there isn’t any out-of-the-box or good way to do that.

A few of the underlying components could be moved, though, for example Exchange, OneDrive and SharePoint. For individuals, there’s a variety of third-party tools that may lift and shift your articles in one tenant to a different. Anything else (e.g. Forms, Video/Stream, Planner, etc.), however, will probably be untidy or must be left out.

There’s a couple of firms that provide a full fidelity migration of Microsoft Teams, but you have to be careful when selecting which to utilize. Microsoft doesn’t openly present an API that enables content migration of chat and channels, so that all solutions available are heavily customized. Structure could be programmatically replicated, and content in the underlying SharePoint document library and OneDrive could be introduced across too, however the chats and funnel conversations can’t be transferred because they are. These may rather be exported and “migrated” as HTML files therefore the conversations can effectively be replayed in to the new tenant.

The idea of moving Microsoft Teams between tenants is comparatively new, so it’s essential that you’re ready to walk an costly and potentially unstable path if you choose to pursue it.


Need to know once the next entry within the series opens up? Sign up for our blog!