Allow WIki Page LIbrary to be selected from the list of things to migrate from OnPrem to Online.
Currently, even though we can successfully migrate WIki Page LIbraries by selecting "Migrate All Lists, LIbraries, Pages and Webparts", it does not allow you to specifically select WIki page libraries from the drop down to migrate just that libraries instead of migrating everything.6 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 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
The file size limit in Migration Manager seems to be 15GB, which we have confirmed through our testing and also consulting with Microsoft support. Please increase this limit from 15GB to the file size limit for SharePoint/OneDrive.5 votes
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.
While migrating from file share to SPO using SPMT, if any file "Date Created" metadata is empty, migration tools throwing error "Scan File Failure:The item created time or modified time is not supported".
I would suggest in this scenario, if "Date Created" is empty it should replace with "Data Modified" metadata and vice versa after migration time.
SPMT needs a silent installation option and should be allowed to run by any user other than the one who installs the tool5 votes
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.5 votes
We are migrating the files form local machine to sharepoint site using sharepoint migration tool and running the incremental migrations after completing the migration. Now we want our local machine and sharepoint site are in sync and if i delete/move file on my local machine same should be reflected in sharepoint site after running the incremental migration. Currently its not possible. is there anyway to fix it?4 votes
*English follows Japanese
About the transfer speed of objects/list items in the SharePoint migration tool
If carrying out a migration via the SharePoint migration tool, objects and list items are moved more slowly than files.
Please improve the speed at which objects and list items can be migrated.4 votes
*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.
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.
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.
Provide a way to export/import the migration jobs so that incrementals or resume tasks are not lost/or can be moved to another client/server3 votes
We have recently found that any user can create a new SharePoint site collection using the SPMT tool. It doesn't seem to reference any of our tenant settings. We have a strict governance process and have disabled self-service site creation so that only the SP Admin role can create sites, however the SPMT does not respect any of these tenant level settings. I have logged a ticket with support but they are saying this is expected behaviour. So we would like to see SPMT require SP Admin role permissions to create a new site.2 votes
Please add a setting to remove the source data after it successfully copies to the destination - effectively a "move" operation instead of a "copy" operation.2 votesthinking about it · AdminSharePoint UserVoice Admin (SharePoint UserVoice Admin, Microsoft SharePoint) responded
Thank you for sharing your feedback. Your input is valuable for us in informing our future roadmap. Thanks
-Migration Manager team.
Support for Sharepoint 2019 on premise would be nice.2 votes
I have been migrating a few 10's of Gbytes from on-premise file shares to cloud and find that the migration is so efficient, it saturates my network connection, causing problems for my users.
When I paused the task after 60 minutes to allow users to do their work, although the file system scanner paused, the package upload didn't, so the tool continued saturating my bandwidth for an additional 75 minutes.
It would be helpful if the migration tool had some throttling settings to avoid this situation, and if the pause could also affect the package uploader.2 votes
For Migration agents, offer opportunity to pool agents logically and select specific pools to control bandwidth usage and data flow.
SPMT agents, specifically for local fileshare to OneDrive, is limited in that you define X agents, they are selected automatically. Adding a feature to either specify the agent pool to use, or limit it by domain. Use case: Multinational company doing migrations both in EMEA and Americas end up with agents in EMEA migrating AM users, which is essentially two ocean hops for the data.2 votes
Preserve "date modified" for folders when using SharePoint Migration Tool (to migrate File Shares to OneDrive)
For files, timestamps are preserved but not for folders.2 votes
- Don't see your idea?