Would be great to be able to use SharePoint Migration Tool libraries in our own Migration solutions. For example, it's great to include "Microsoft.Sharepoint.Migrationtool.Migrationlib.dll" in the project and make small, Customer-specific migration tool based on existing SPMT functionality.

All the requirements for that - is to add a bit more comments for public members. And write some documentation of basic usage scenarios: simple site migration in .NET project, migrating simple document library etc.

We are using the SharePoint Online created by Teams and all other cool Apps like Planner, Flow and One Note. However, in order to use also Yammer we currently need to create a new Yammer group (that creates a new SharePoint and so on).

It would be great if from one O365 Group you could manage ALL apps, regardless where this group was created from. This would enable us to manage our SharePoint integration with Yammer seamlessly.

Currently the Hybrid Config Wizard is unable to accept accounts which are protected by Azure MFA, including app passwords.

Please allow the use of MFA in the Hybrid Config Wizard so we can protect all elevated access accounts in O365.

A very useful addition to the SharePoint Migration Tool from Microsoft would be support for SharePoint Online to SharePoint Online migrations. There are many scenarios where this is commonly needed for some customers who must restructure or realign and be able to migrate from one area of SharePoint Online to another. Just in general as well this would be a handy option to have.

Could this please be considered as a future improvement to the SharePoint Migration Tool including support with bulk migrations for SharePoint Online as a source. Thanks.

It would save us a lot of time and hassle if we could specify the target folder in the UI instead of having to export and edit the JSON file to do it.

Support for migrate from SharePoint 2010 to SPO

We have a few SharePoint 2016 sites that we would like to have migrated to Office365 but I'm not able to find an easy way to do this. I tried to save list as template to get some of the content there but the data didn't import correctly. There needs to be a way to migrate SharePoint 2016 to O365 fully.

While migrating from file share to SPO using SPMT, if any file "Date Created" metadata is empty, migration tools throwing error "Scan File Failure:The item created time or modified time is not supported".

I would suggest in this scenario, if "Date Created" is empty it should replace with "Data Modified" metadata and vice versa after migration time.

Avian

SharePoint Migration tool does not migration Full permission from File share to "Full Control" permission level in SharePoint Online. The mapping of Full permission to contribute is not a correct scenario because it does not provide Share folder permissions. This is a serious flaw. We hope there is a workaround or fix very soon.

Jerry Yasir
Microsoft MVP - Office Apps and Services.

Pause/resume feature of SharePoint Migration Tool is disabled.

Offer option for top navigation links to open in new tab by default.

A virus is being detected during the installation of the SharePoint Migration Tool source. Microsoft detects as PUA-Win32/Presenoker, McAfee, Avast and other engines also detect threat in file >> cefsharp.browsersubprocess.exe

"Copy path" making it possible to copy the path to a point in the file structure would help the organisation to learn "what to find where" by pointing at exact not-manually-entered locations.

It would decrease the tendency of the structure to become a "write-only-memory" with increasing size and time.

Currently, when migrating a list with a lookup field using the SharePoint Migration Tool 2.0, a failure occurs stating that the list with the GUID cannot be found. The dependency lists were migrated successfully, however, when migrating the list with the lookup fields, it is looking for a list with a GUID that doesn't exist. When the dependency lists are migrated over, they get new GUIDs.

The PowerShell cmdlets for copying Taxonomy Groups and Content Types (Copy-SPTaxonomyGroups, Copy-SPContentTypes) only support passing credentials in a legacy method, this blocks copying these items to SPO if you have conditional access (or have disabled legacy auth) enforced for your tenant.

You will get some interesting features from the community. Also stop SharePoint customers from paying tons of money for migrations

Allow ADFS users to search on premise on their Online AND Onpremise content. ADFS is the only way to provide SSO between Online and OnPremise environment but cannot be used because of the ACL mapping in the Cloud SSA when returning results OnPremise.

Our team has been using Sharepoint for years. Recently, we decided to move to 365 Platform as it has better user interface:

Having said that we were disappointed to see that Sharepoint 365 does not show html pages, instead it opens up the html in a text editor.

And if we wish to share the link as a read only, then the link will download a html file (on each time when the link is clicked). Really annoying !!!