With introduction of Office 365 groups - which are very nice as starting point - please consider to provide an migration path / integration in Teamsite (OnPrem and SharePoint Online)7 votes
While our integration with Microsoft Teams and Groups in the SharePoint Migration tool is not fully complete. You Should be able to point the tool to Any existing Teams or Group connected team site to migrate content into it. I would love to understand more what are the specific parts you would like to see in the tool
While Search with hybrid SSA is getting to a prett neat hybrid story, for UPS and MMS there has been (besides maybe the PnP Metadata synch workaround) no attempts to provide a proper hybrid story. Please work on that if you really want to have a well understood and implemented hybrid story as a differentiating factor compared to other providers7 votes
With the new Hybrid search options it would be nice if we could make one eDiscovery center that will cover both on-prem SharePoint and O365 and be able to do holds.7 votes
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
Currently you can create an Office 365 Group for a project and it comes with a "Files" section to share files. Well, the group's project is done and you want to move or copy those files to a more public repository on Office 365 Sharepoint. However, there is no may to multi-select files/folders and move/copy from the Groups to Sharepoint. This is a huge need as it exposes the file to the whole company for discovery whereas Groups are usually a limited audience. If you are a Mac user, you don't have the Windows Explorer option either. This should be easy and all web based on every browser.
Currently you can create an Office 365 Group for a project and it comes with a "Files" section to share files. Well, the group's project is done and you want to move or copy those files to a more public repository on Office 365 Sharepoint. However, there is no may to multi-select files/folders and move/copy from the Groups to Sharepoint. This is a huge need as it exposes the file to the whole company for discovery whereas Groups are usually a limited audience. If you are a Mac user, you don't have the Windows Explorer option either. This should be…6 votes
I hear that MS is committed to moving o365 functionality to the on-prem version yet nothing is ever mentioned about social. We've had to implement a 3rd party social platform because a decent one is not provided out of the box.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
I noticed that the Suite Bar in Office 365 and in SP2016 doesn't display the user in the top right the same way. SP2016 displays the name where Office 365 shows the picture.
Would be better to do the same as Office 365 in SP2016 no? Better UX when in Hybrid.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
Block users to work with client application on documents on cloud - i.e. allow only editing in excel online!
We will be happy to send the following important\urgent feedback to Microsoft:
It's important to allow users to access documents online only!
If other users can edit in excel (client application) so we have conflicts and any other error messages will pop-up while someone else is trying to work offline (with client application).
In other words, block users to work with client application on documents on cloud.
We cannot leave google cloud services yet!
Search integration should be seamless between O365 and local installation. A method for combining navigation would also be a plus. With search integration I'd like to see a better hybrid discovery story similar to what we get with exchange. Even better if I can add a 2016 server and great a hybrid endpoint without uplifting 2010/2013 farms even a bigger plus.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.
- Don't see your idea?