At my IT company we are frequently working on Office 365 migration projects. We're also working on some merger / carve-out projects so we frquently need to move data out of tenant no 1 and re-import that data to tenant no #2.
Currently this cannot be done by the existing graph api, as there is no support to access several data like chat conversation etc.
Unfortunately, a support request answered that it's also not possible to get that from the support right now.

I'd like to request some export-team and import-team functionality
• Export should be possible to an Azure storage account or local file.
• Import should be possible from an Azure storage account or local file.
• all data from the team site should be included in the export, such as sharepoint content incl. item history information, chat history, etc
• On import, it must be able to set a new team owner in the target tenant
• Users that are listed in the last modified content, but are not present in the target tenant, should be shown as string with some "not existent" information tag
• It's not required for the data export to be readable on-premises, as we want to move it between tenants, we do not want to do Offboarding at that step.
• A short howto for use by powershell (or graph api) must be included at the resulting functionality

Ideally I would like to have an export cmdlet like that
Export-MicrosoftTeam -team name -tenant mytenantname -credential sourcecred -outputtarget storagetype -targetlocation somepathtomystopragetarget
Ideally I would like to have an import cmdlet like that
import-MicrosoftTeam -team targetname -tenant mytargettenant -credential targetcred -inputstorage storagetype -inpputlocation somepathtomystopragetarget -newtargetowner newownerinmytenant

I know there are already a lot of requests for federation. This is a different type of request though, as it is more specific:

Similar to how true email federation uses open source federated protocols like IMAP, SMTP, POP3, true federated banquet style chat applications should also use open source federated protocols to allow other clients & hosts.

The Matrix protocol (which is managed by a non-profit organization) is the most popular way to do this. I would love if Microsoft Teams added support for this to allow it to truly replace email, and communicate with customers, vendors, etc. that may not have Microsoft Teams.

https://matrix.org/

At my company, we have Skype for Business (SFB) and Teams enabled. Teams allows you to message people exclusively using SFB, but you cannot send an SFB message to someone exclusively using Teams. To make matters worse, at my company many people (ie. managers) exclusively use SFB, and another set (ie. developers) use Teams. So there are effectively two options to communicate with everyone:

1) Only use SFB, and both groups can message you.
2) Keep BOTH SFB and Teams open. Use Teams to send new messages, and keep SFB open to respond to Managers that do not use Teams.

This unfortunate scenario has made it so people *prefer* Skype for Business, even though Teams is a superior choice in terms of features. So to better facilitate a full transition to Teams, there needs to be complete and total interoperability between Skype and Teams. SFB users should be able to send direct messages to Teams users such that Teams users do not need to keep both clients open at the same time.

(NOTE - This is the second time I am posting this as the last time it was inappropriately merged into https://microsoftteams.uservoice.com/forums/555103-public/suggestions/17137732-hyperlink-any-text-in-chat which has nothing to do with this request. It is a little frustrating that I can't even get to my original post in order to copy and paste - I need to recreate it from scratch.)

It would be very helpful to have the ability to hyperlink INTO a chat with a given user. We relied on this heavily while using Skype and it is a very nice feature to be able to embed into other internal applications.

E.g. in Skype we could use:
<a href="skype:myuser?call">Call User</a>
<a href="skype:myuser?chat">Chat with User</a>

Could we please allow for the same linking INTO Teams from 3rd party applications?

Please see related discuss here: https://techcommunity.microsoft.com/t5/Microsoft-Teams/Hyperlinking-from-a-web-page-into-Teams-Chat/m-p/134506#M9672