Moving files en-masse to Sharepoint
-
It's amazing how much better the personal version of OneDrive handles this kind of stuff. It's faster and can take multiple files.
/rantoff
-
Furthermore, you often cant use the online version of excel to open old school xls files. You should convert them to xlsx if possible first, I'm sure the same is true for old word doc files.
-
@thwr said in Moving files en-masse to Sharepoint:
Yepp, mass file ops are a bit buggy, at least in 2010. Maybe due to WebDAV behind the scenes.
Used a PowerShell script to upload and verify each file. Slow but worked as expected.
From what I can tell, the site is on 2016 (16.0.0.1203).
-
Found lots of products for sale that will assist in migrating the files. So far, I have found two free ones:
-- https://spbulkdocumentimport.codeplex.com/
-- https://gallery.technet.microsoft.com/ScriptCenter/f538c34c-4f74-4645-9649-fd25e49805d6/ -
Another one:
-
Christmas come early... we used to get around this with SharePoint 2007 by mounting a virtual drive and dumping hoards of documents in there, which then shows up on the front end. Essentially you're not using the front end. You are just doing a massive dump directly onto the server.
Kept using that method with SP13 even though now you can upload multiple docs but not open and share certain file types that GIS uses.
I can't remember the path to the repository we dump stuff in. Let me look...
-
@BBigford said in Moving files en-masse to Sharepoint:
Christmas come early... we used to get around this with SharePoint 2007 by mounting a virtual drive and dumping hoards of documents in there, which then shows up on the front end. Essentially you're not using the front end. You are just doing a massive dump directly onto the server.
Kept using that method with SP13 even though now you can upload multiple docs but not open and share certain file types that GIS uses.
I can't remember the path to the repository we dump stuff in. Let me look...
Ultimately it ends up looking something like this...
https://community.spiceworks.com/how_to/4133-office-365-sharepoint-map-network-drive
-
There's also another one that would look something like \devdep\WWW\share\front
But I can't remember the exact verbiage so I'll have to look tomorrow...
-
@BBigford Thanks... I look forward to your response. To clarify, this is different than the "Open In Exploer" option I mentioned earlier with the zero byte resulting files?
-
@BBigford said in Moving files en-masse to Sharepoint:
There's also another one that would look something like \devdep\WWW\share\front
But I can't remember the exact verbiage so I'll have to look tomorrow...
Did you ever come up with anything further on this?
Thanks, Dan
-
This doesn't answer your problem specifically, but something to be aware of when moving fileshares over to SPO is that there is a 5,000 item limit to file views. If you get close to that, SPO starts behaving oddly. What we did to get around this limitation was converting our top level folders into separate Document Libraries.
-
File views? or files per site in SPO? I found it to be files per site several years ago... sad to see that hasn't been fixed/upped.
-
@Dashrender said in Moving files en-masse to Sharepoint:
File views? or files per site in SPO? I found it to be files per site several years ago... sad to see that hasn't been fixed/upped.
The 5k limit was per view. There might also be an upper limit for files per site, but I've not tested it.
-
@Danp said in Moving files en-masse to Sharepoint:
@BBigford said in Moving files en-masse to Sharepoint:
There's also another one that would look something like \devdep\WWW\share\front
But I can't remember the exact verbiage so I'll have to look tomorrow...
Did you ever come up with anything further on this?
Thanks, Dan
WebDAV is underlying technology.. if my SP site and domain is site.domain.com, knowing that SharePoint is going to use a flat file share in this example, then my mapped drive would be \site.domain.com\repository ... If you get a permissions error (the user needs to be able to upload there) use the following link: https://www.lucidica.com/help/mapping-sharepoint-as-a-network-drive/A Google search for some more key content would be "SharePoint mapped drive Windows". I found lots and lots of links for all kinds of setups from 2007 to hosted online and 2013.
-
@BBigford Not sure that this solves the issue that I encountered where the resulting file was corrupt / zero bytes.
-
@Danp said in Moving files en-masse to Sharepoint:
@BBigford Not sure that this solves the issue that I encountered where the resulting file was corrupt / zero bytes.
What version of SharePoint are you on? That method is what we've used for 2007 & 2013...
-
@BBigford This is on O365. The version is 2016 (16.0.0.1203).
-
This post is deleted! -
@Danp said in Moving files en-masse to Sharepoint:
@BBigford This is on O365. The version is 2016 (16.0.0.1203).
Ah, yeah ours is not hosted. A few things...
*We had issues where the path exceeded 255 characters, have you addressed that?
*The user did not have the proper permissions on SharePoint, or permissions on the file(s) being uploaded. Have you checked that you can copy files to the upload location, as well as at least read permissions on the file(s)?
*There is a limit on amount of files to be uploaded. I think it is something like 5000, are you exceeding 5000?
*There is sometimes a file size limitation, have you already checked out this link? https://support.microsoft.com/en-us/kb/925083
That's about all I have for now as I'm not a SharePoint expert...
-
@BBigford I don't believe that our issue was due to any of the restrictions / limitations you listed. When copying a group of files, occasionally one of them would get corrupted and have zero bytes. There were no errors or warnings.
I was using Explorer to move files between the network drive and SP document library. All of the files were moved, but one of them was empty and had to be restored from backup.
