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.22 votes
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.6 votes
Thanks for the feedback. we are considering on how we might make that experience better.
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?3 votes
Thanks for the feedback, we are definetly interested in making the automated process better.
Explain about the need to check the box to Migrate a OneNote folder as a file versus a library option
Please write a post explaining the need to select the option for Migrating a OneNote as one file, versus a document library with many folders.1 vote
Hi, thanks for the feedback, we are in the mist of doing some changes to this feature and we will consider your suggestion
- Don't see your idea?