The output of Start-SPMTMigration is in sentence form, and while you can capture it, you still have to parse it, which is exactly what you're NOT supposed to have to do in PowerShell.

Instead the Output of Start-SPMTMigration should be something like this
GUID Status Reason

c3cc7804-7164-4a2b-8996-7e51f319dea9 Passed
efd127ce-68f4-4d85-960d-5384ba561bef Failed The Target Site <URL> does not exist

I mean, you still have to parse the Reason, if you want, but at least you have fewer hoops to jump through just to remove tasks that are destined to fail from your migration.

I hear that MS is committed to moving o365 functionality to the on-prem version yet nothing is ever mentioned about social. We've had to implement a 3rd party social platform because a decent one is not provided out of the box.

After you run a migration and you saved it, you can only run an incremental migration or delete the session. It would be great to edit the migration settings or maybe also add or remove a task from the review migration.

Being able to host an on-premise Share Point Server (2019), that synchronizes real time bidirectionally with Office 365 Share Point. (To Improve Performance / Business continuity)

Also, it would need to have the options of cloning the sites and other pages from Share Point Office 365 to the on-premise Share Point Server (2019). With offering as much full functionality as possible.

Offline Mode for SharePoint Migration Tool - The SharePoint Migration Tool requires the end user to enter in credentials to an O365 instance. In my scenario, we are currently blocked from accessing login gateways related to O365, but are currently working towards migrating to O365 as a solution. It would be nice to get the insights that the SharePoint Migration Tool provides in its reports without a set of O365 credentials. I.E. if credentials to O365 are not provided, place the Migration Tool into a REPORT ONLY state.

I noticed that the Suite Bar in Office 365 and in SP2016 doesn't display the user in the top right the same way. SP2016 displays the name where Office 365 shows the picture.
Would be better to do the same as Office 365 in SP2016 no? Better UX when in Hybrid.

*English follows Japanese

■Title(件名)：
SharePoint 移行ツールについて
About the transfer speed of objects/list items in the SharePoint migration tool

■Description(内容):
SharePoint 移行ツールで移行する際に、オブジェクトとリストアイテムは、ファイルより移行速度が低くなります。
オブジェクトとリストアイテムも移行速度が速くなるように改善を希望します。

If carrying out a migration via the SharePoint migration tool, objects and list items are moved more slowly than files.
Please improve the speed at which objects and list items can be migrated.

Allow WIki Page LIbrary to be selected from the list of things to migrate from OnPrem to Online.

Currently, even though we can successfully migrate WIki Page LIbraries by selecting "Migrate All Lists, LIbraries, Pages and Webparts", it does not allow you to specifically select WIki page libraries from the drop down to migrate just that libraries instead of migrating everything.

Currently the SPMT tool does a lot more than it should when migrating only lists or libraries. For example - it changes the site title, activates features (web & site scoped) that are completely unrelated to list data that's being migrated.

It's rather frustrating when having spent considerable time setting up a site where features need to be deactivated and other settings reverted. The incremental process does the same too. The tool also resets and removes views, as well as surprisingly deletion of indexes that were put in place to assist with filtering in views.

Thanks,

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

We will be happy to send the following important\urgent feedback to Microsoft:

It's important to allow users to access documents online only!
If other users can edit in excel (client application) so we have conflicts and any other error messages will pop-up while someone else is trying to work offline (with client application).

In other words, block users to work with client application on documents on cloud.

We cannot leave google cloud services yet!

Thanks,
Avichai

Search integration should be seamless between O365 and local installation. A method for combining navigation would also be a plus. With search integration I'd like to see a better hybrid discovery story similar to what we get with exchange. Even better if I can add a 2016 server and great a hybrid endpoint without uplifting 2010/2013 farms even a bigger plus.

Hello team,

is there any feature planned for setting maximum single file upload limit for migration to OneDrive or SharePoint.

With current update from OneDrive, it now allows 100GB of file upload, while our requirement is to not migrate files greater than 15GB.

Thanks and regards,
Rupali Kothawade

We are migrating the files form local machine to sharepoint site using sharepoint migration tool and running the incremental migrations after completing the migration. Now we want our local machine and sharepoint site are in sync and if i delete/move file on my local machine same should be reflected in sharepoint site after running the incremental migration. Currently its not possible. is there anyway to fix it?

*English follows Japanese

■Title(件名)：
オンプレミスのファイルサーバーから、SharePoint Online へ移行について
Regarding file migration from on-premise file server to SharePoint Online

■Description(内容):
オンプレミスのファイルサーバーから、SharePoint Online へ ファイルをドラッグ アンド ドロップ、もしくは、サイト上のアップロードボタンで移行した際に、ファイルに破損などなく移行できたか確認できる機能の追加を希望します。
When I migrate files by uploading or drag and drop from on-premise file server onto SharePoint Online, I want to check if the file has been moved successfully without any damages, so please implement such a feature.

Currently it gives an "Access denied" error, but it doesn't really make any sense why O365 Team Sites would not be supported as a destination. There are many scenarios where this is commonly needed for some customers who have Sharepoint sites setup as O365 Team Sites and not as an SPO Site Collection. Just in general as well this would be a handy option to have.

Please consider this as a future improvement to the SPMT. Thanks

The SharePoint Migration Tool should have a well documented, silent and scriptable installation process. The GUI portions of this product have interest to me, and yet, I'm stuck with 3 or four clicks to get it installed just so I can automate data migrations.

Maybe a Nuget Package? Chocolatey?