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.12 votes
Thanks for the feedback we are keeping an eye on the votes for this to compare to other requests.
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.47 votes
Include timebased information like CreationDate,ModifiedDate and LastAccessedDate in the scan reports
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.12 votes
This is a great feedback we are keeping an eye on the votes for this and comparing priority to the rest.
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
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.6 votes
Have the SharePoint Migration Tool label its errors correctly. Currently an error in spelling of the Destination results in an error that states that the source folder is not accessible1 vote
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.5 votes
Thanks for the feedback. we are considering on how we might make that experience better.
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. Thanks3 votes
Every 0365 teams sites are connected to a SPO site collections You can therefore go to that site and migrate to it if you are the site admin.
We are working on new improvements to make moving to Teams even easier.
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.
*English follows Japanese
オンプレミスのファイルサーバーから、SharePoint Online へ移行について
Regarding file migration from on-premise file server to SharePoint Online
オンプレミスのファイルサーバーから、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.3 votes
The SharePoint migration tool does all that validation for you. i would recommend looking at the reports generated.
I know it's in preview, but again similar to Exchange Migrations, could you add email notification when registering a task so we could get email notification, when completed, progress, etc without then needing to sign back in to check.1 vote
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!1 vote
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.2 votes
Would be nice to have the ability to move sites and content between SharePoint 2019 and SharePoint online with SPMT tool in both directions8 votes
Currently uploading files to onedrive is limited to 15GB.
With an increasing file size, especially with 4k content, the 15GB limit causes some inconveniences
Increase limit of the uploaded file to 50GB or the highest possible level5 votes
Thank you for the feedback, This is a request for SharePoint in general. we are looking at this in general for SharePoint and the SharePoint migration tool will support it once SharePoint supports greater size
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.4 votes
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?2 votes
Thanks for the feedback, we are definetly interested in making the automated process better.
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.2 votes
SharePoint Migration Tool Migration Support for Lists Import from CSV or Excel
It would be great to have support for loading list data from files - especially large lists!1 vote
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.10 votes
Great suggestion. Would love to see the votes\interest in this topic.
A useful addition to the SharePoint Migration Tool would be to support the option for excluding paths in a file share to SharePoint migration scenario. It would be very useful to put an exclude symbol "-" in front of a mapping while building the .csv. In this way you are able to migrate the only what you really need. Example: a library with 50 folders and you need 48 of them. In the current version you migratie everything and in a post migration step you need to manually find and delete these 2 folders. Or I need to add 48 mappings within the .csv.
A useful addition to the SharePoint Migration Tool would be to support the option for excluding paths in a file share to SharePoint migration scenario. It would be very useful to put an exclude symbol "-" in front of a mapping while building the .csv. In this way you are able to migrate the only what you really need. Example: a library with 50 folders and you need 48 of them. In the current version you migratie everything and in a post migration step you need to manually find and delete these 2 folders. Or I need to add 48…12 votes
- Don't see your idea?