Dec 10 2020 04:12 AM
Hello,
We are trying to migrate contents from a file share to a user's Documents place (the default one, which is created on user creation ) and once we setup the Migration Manager task, all it does is create a new Document Library and upload user files to the newly created Document Library. It does not upload content to the existing documents, which is a list BTW.
We are performing the tasks with a SPAdmin account.
Has anyone expierienced such behaviour? and solved it?
Bottomline is that we need the user files uploaded to the user Documents Folder.
Dec 10 2020 11:43 AM
Dec 11 2020 02:16 PM
Solution@Anthony_Tudor Hello Anthony and thank you for your response.
After opening a ticket with microsoft support it seems that it's a bug and it's affecting some levels of o365 licenses. Tried the same workflow with just different licenses on another tenant and it worked.
A simple workaround of the above was instead of picking OneDrive as the destination, pick SPO and insert the <tenant>-my.sharepoint.com and the Documents list afterwards.
Jan 28 2021 03:28 AM - edited Jan 28 2021 03:33 AM
@jimas_1966
I have the same problem, but your suggestion doesn't seem to do the trick. Any other suggestions? No matter what I do, OneDrive or SharePoint location, it creates a new Documents1 folder, not visible to the user. I have two options "Files" and "Documents", but the result is the same.
Feb 01 2021 11:22 PM
@jimas_1966 For me the interface trick was not the issue. I have a problem because i want to do the migration in bulk. With JSON or CSV this trick is not an option. And the same problem exists when i do the migration with JSON or CSV.
Feb 01 2021 11:25 PM - edited Feb 02 2021 12:19 AM
I have the same problem, but the suggested work around didn't help. The same problem arises, a new Documents1 folder is created.
Feb 02 2021 01:52 AM
@jorikpolhuis In reaction to my owm reply. I found the source of my problem. In my scenario there was a language difference. The document library name wasn't "documents" but was "documenten" as it calls in the Netherlands. I hope this helps someone..... And maybe Microsoft could make a simple fix for this.
Feb 02 2021 01:58 AM
Feb 02 2021 03:09 AM - edited Feb 02 2021 03:10 AM
@jorikpolhuis
Could you post an example of your JSON and/or CSV files? (Without exact file shares\locations, of course)
Feb 02 2021 04:40 AM
@dmutsaers In the attachment the example you requested.
Feb 02 2021 05:50 AM - edited Feb 02 2021 05:51 AM
Thanks @jorikpolhuis ,
But I don't see the dutch "Documenten" mentioned in your example. :)
Feb 02 2021 05:53 AM
@dmutsaers sorry, here is the dutch json. :)
Feb 02 2021 07:16 AM
@jorikpolhuis Thanks!
Jan 13 2022 05:30 AM - edited Jan 13 2022 05:43 AM
Just in case someone else reads this. This seems to be fixed in the February 2021 agent update:
https://docs.microsoft.com/en-us/sharepointmigration/mm-whats-new
Fix for non-English sites. Fixed the issue where Documents1 library was getting created for non-English sites. Requires latest version of agent.
However, I haven't been able to test this myself yet.
Apr 04 2022 02:09 AM
Dec 11 2020 02:16 PM
Solution@Anthony_Tudor Hello Anthony and thank you for your response.
After opening a ticket with microsoft support it seems that it's a bug and it's affecting some levels of o365 licenses. Tried the same workflow with just different licenses on another tenant and it worked.
A simple workaround of the above was instead of picking OneDrive as the destination, pick SPO and insert the <tenant>-my.sharepoint.com and the Documents list afterwards.