Forum Discussion
File Share Migration to SP Online using SharePoint Migration Tool
Hi All,
I have been tasked with finding a resolution to documents in SPO Team Sites not being able to be shared using the in built Share option.
Essentially when a user goes to share using the Send Link option, no email is sent or received if the user in in the tenancy when using any of the sharing options (Anyone, Only people in the company, Specific People). If the link is to go to an external recipient and the option of 'Specific User' is selected, the email goes out fine.
All the documents were uploaded to individual Team Sites using the SharePoint Migration Tool as recommended by Microsoft in the SharePoint Online Deployment Advisor.
Currently they have come back with 3 options for us to resolve, none of which are viable given the amount of data (1.1TB) and the quantity of Team Sites (149).
1. sync all document libraries down using OD4B and re-upload the files
2. raise a case with the SharePoint On-Premises team
3. Migrate the documents again using a 3rd party tool - not an option given the original migration was carried out back in March 2018.
Has anyone experienced a similar issue and found a feasible resolution other then having to download all data and re-upload?
4 Replies
If you create a new file in the same document library that the files were migrated into, can you share the file? Could you also try, dragging a file from Windows Explorer into the document library and then try sharing.
1. If I download the file and upload it to the same location (overwriting the existing file) it does not share
2. If I create a new file in the library through the SPO WI it shares successfully.
3. If I create a new folder and upload the existing file to it, it shares successfully.
4. If I drag and drop an existing file to a new folder in the document library it does not share.
- You mean the problem is due to the migration? Sounds strange to my knowledge...migration tool is moving files, no changing your sharing settings
O365 Support have come back with the problem being caused by the SP Migration Tool.
I said the same thing but apparently the tool changes some sort of metadata on the file but they do not know what.
