The SharePoint Migration tool should being over Workflow Definitions from SP2010 and SP2013 workflows. While we understand inflight workflows can not be migrated customer with workflows should see the definitions migrated to SharePoint Online.

Having solid documentation allows for detailed understand and self troubleshooting.

The protocol documents that were done for SharePoint 2010 should be repeated for SharePoint 2016.

SharePoint Products and Technologies Protocols - https://msdn.microsoft.com/en-us/library/jj633112.aspx

SharePoint Back-End Technical Specifications - https://msdn.microsoft.com/en-us/library/jj633109.aspx

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.

As is, the profile picture displayed in SharePoint Online contents to mirrors the availability status of the user with a mark, but does not connect with Skype for Business or Exchange Online.
I would like for you to change this, so that SharePoint Online contents also gets interlinked with the availability status of Skype for Business and / or Exchange Online.

While Search with hybrid SSA is getting to a prett neat hybrid story, for UPS and MMS there has been (besides maybe the PnP Metadata synch workaround) no attempts to provide a proper hybrid story. Please work on that if you really want to have a well understood and implemented hybrid story as a differentiating factor compared to other providers

With the new Hybrid search options it would be nice if we could make one eDiscovery center that will cover both on-prem SharePoint and O365 and be able to do holds.

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.

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.

Add support for Wiki Page Library to SharePoint Migration Tool v2

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

Pretty much as per the title - add the functionality to create a migration job, and have it start at a particular time of day, pause when required, and then continue. The SPMT can use a lot of resource on the device it's installed on, and consumes bandwidth, so have it start after working hours, pause for the next day, and then continue, all automatically, would be very useful.

For the most part the migration tool is good and easy to use, however, if possible it would be great to have the estimated time remaining displayed on the app just to give an idea of how long it will take

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.

With introduction of Office 365 groups - which are very nice as starting point - please consider to provide an migration path / integration in Teamsite (OnPrem and SharePoint Online)

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.