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.

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.

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.

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.

I noticed that when doing an incremental migration with the SPMT tool that the tool will bring over the setting from the source and overwrite the Destination. Example after migration I enable versioning in SPO but versioning if off in SP2013. When I do a incremental migration versioning will be disabled on the SPO library. It might be useful for people to pick if they want to migrate all setting or leave the destination setting like versioning.

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.

Currently uploading files to onedrive is limited to 15GB.
With an increasing file size, especially with 4k content, the 15GB limit causes some inconveniences
Please
Increase limit of the uploaded file to 50GB or the highest possible level

Seems that SPMT versione 3.2.114.0 has an issue migrating from OnPremises file system. Look at this: https://social.technet.microsoft.com/Forums/en-US/eb5c2b7a-0da8-46dd-9d45-abcb6716ff4a/sptm-version-321140-quotseveral-packages-failed-to-upload-pause-the?forum=SharePointMigrationTool
Any solution or workaround?

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.

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?

Migrated Web parts from SP13 to SPOnline don't include the chrome type attribute as it is and set to "Default".
So, if I have a web part that its Chrome type is set to "None", it's set online as "Default" instead.

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.

migrazione da sito sharepoint 365 ad altro sito sharepoint 365 (altro account)

HI,

I have been testing migration tool and experienced extremely slow speed, even for a list of 100 items, it takes couple of hours to even initiate the migration.

1 - Is there anything we can do to increase the speed
2 - when using a csv file, connection is made for every source and destination url. Can we authenticate once and it can used for all the source sites and destination sites.

Would be nice to have the ability to move sites and content between SharePoint 2019 and SharePoint online with SPMT tool in both directions

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.

Support for migrate from SharePoint 2010 to SPO