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.

We currently have to maintain on-prem OWA server(s) to handle on-prem document previews (even in new Hybrid search), and of course in-browser document editing/viewing. This experience will undoubtedly become fragmented from Office Online as MS adds features to the cloud platform.

I would really like to leverage the Office 365 Online apps to preview/view/edit documents hosted on-prem. This is really the last piece of the hybrid puzzle for us.

I would like the Delve UX in my SharePoint onprem environment and also have my onprem events from SharePoint, Lync, Exchange and custom sources added to my company's Office graph. The solution may be Hybrid, but integration should be easy to setup and configure.

Third party tools such as ShareGate and Metalogix allows the customer to migrate libraries with an option (setting) to leave behind the content. This is very common request from our customers needing to cleanup sites/content before migration but allows the migration of site structure. I have been asked if this is possible many time and I can only recomment using a 3rd party tool. This would be a great addition to our migration tool.

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.

add custom mime-type (such as .svg file) to IIS so that it can open directly in browser other than download it

The LastItemModifiedDate property of the site object in Office 365 reports the last time an item in the site was modified by either the system or a user. This causes a problem for anyone or any tool trying to do activity reporting to determine the last time a site was modified by a user. Please create a LastItemModifiedByUserDate and/or LastItemModifiedBySystemDate to allow us to distinguish the two.

Bring the App launcher ribbon form O365 to on Prem and allow use to administer what icons/links appear form central admin.

This would allow the use of SharePoint as a landing page company wide with links to all corporate applications on SharePoint and external.

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 default emails that are sent for an approval workflow are broken. The idea is that users can click on the "Open this Task" button directly within Outlook. But this button is broken (since 2010?)
Beside that there is no such button when using Outlook Web Access.

Therefore there is no way direktly hup into the according task to edit this approval workflow.

This issue should be fixed and the email itself should contain a link to approve or reject this wf directly.

Currently, custom properties from an on-prem farm, like site columns in a site, are only visible to the search service account in O365. Global admins, SharePoint admins, cannot see these properties and cannot access them until they are added to managed properties.

At present, you need Full Control to view Site Usage Reports. This seems unnecessary to view what is an on-demand obfuscated report. It should be a case of granting someone ‘View Web Analytics Data - View reports on Web site usage’ permission rather than resorting to Full Control just so a VIP can see how his site is used.

The current migration tool works well in transferring metadata already attached to the files (date/time, last user, etc.). There is currently no way to assign metadata required in the destination library to the files during migration, and the migration tool also ignores any default metadata assigned to the destination library (those values added automatically when files are added). You have to either update the values manually or use another tool like PowerShell.

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.

Include timebased information like CreationDate,ModifiedDate and LastAccessedDate in the scan reports to gain insights on data in fileshares or SharePoint that might require archiving or disposition opposed to migration. By including this in the reports, these can be used for further processing.

We as SharePoint administrators cannot see how many email SharePoint sends (when sharing sites for example) and are email colleges are complaining that our farm sends to much email. Make it more insightfull

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.