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?

In large IT organizations, especially organizations that already use Office 365 applications, often the O365 global admin is a different team or admin than the SharePoint Online team or admin. The SharePoint Online admin team who would have the SharePoint Online service administrator role, but not necessary the entire O365 tenant global admin role, should be able to run the SharePoint Online Hybrid picker as well as the O365 global admin.

As described here: https://blogs.msdn.microsoft.com/ronalg/2016/11/21/hybrid-search-and-search-popularity-trend-reports/ Popularity Trend Reports are not available in hybrid scenarios as "the view events are not passed on to the search farm that is in the cloud". Include this functionality or provide an alternative in a future release

Crawled properties from on-premises farms should be added to O365 in Hybrid search (cloud index) scenario.

Being able to source taxonomies from SharePoint online and utilize them in a hybrid SharePoint 2016 on-premises situation would aid in consistency across content types, site columns, search (managed properties), etc.

If it is impossible to consume a SharePoint Online content type hub on-premises, at least provide the possibility of syncing.

Why do I spend more time entering my email address and password than accessing the many different files and actually doing some work!

Our law enforcement agency consists of over 1400 users. Probably 90% of those users use OWA .. no licenses for the client. We also have many units that use SP and have a shared calendar on the SP site. Supervisors would like to be able to see this shared calendar in OWA. At this time the calendar can only be shared in the outlook client.

I have been migrating a few 10's of Gbytes from on-premise file shares to cloud and find that the migration is so efficient, it saturates my network connection, causing problems for my users.

When I paused the task after 60 minutes to allow users to do their work, although the file system scanner paused, the package upload didn't, so the tool continued saturating my bandwidth for an additional 75 minutes.

It would be helpful if the migration tool had some throttling settings to avoid this situation, and if the pause could also affect the package uploader.

SPMT agents, specifically for local fileshare to OneDrive, is limited in that you define X agents, they are selected automatically. Adding a feature to either specify the agent pool to use, or limit it by domain. Use case: Multinational company doing migrations both in EMEA and Americas end up with agents in EMEA migrating AM users, which is essentially two ocean hops for the data.

For files, timestamps are preserved but not for folders.

SPMT has been extend to SharePoint 2016, it will be be nice to also extend to SharePoint 2019.
I have already vote for the both direction idea, but the on premise to cloud direction should be easier implement.

SPMT tool is not retaining folder permission in sharepoint online post migration. A User/users added with FULL permission on local folder when synced to sharepoint online it does not retain the permission. User/Users with Modify permission and R/W permission are getting retained as is in sharepoint online. Please look in to this issue.

I know it's in preview, but if you could add the option to Schedule a start time from within Migration Manager like Exchange Migration that would be awesome and help with throttling as we could configure a Out of Hours Start time!

Currently when SPMT creates a new site it only does a Modern site no groups. It would be beneficial to have the tool give an option of what site you would like to create. Example sometimes I might want a communication site. In order to do this today I have to first create the site in SPO then use the SPMT tool to set that as my destination. It might be good to have a few choices to pick from or let the user build a site template mapping file.

Don't immediately begin migration of files upon resuming a scan only session. I had a scan only session running for 175 shares that crashed the SPMT. Upon restarting and resuming the migration, the tool began actually migrating the files when I only wanted to scan them.