Why does a long source URL corrupt my SPO migration? #M365AMA
In this episode, the #M365AMA panel discusses the following community question:
“We recently introduced a new internal O365 environment. Now we need to transfer a lot of documents from the “external” environment. We tried to do this manually (via synchronization and then move), but almost all documents become corrupt. We think it’s due to the length of the URL of the source and destination location… does anyone have a tip for this? Thank you in advance!”
Check out the discussion here:
Participating in this discussion were:
- Christian Buckley @buckleyplanet
- Kirsty McGrath, MVP @KirstyMcGrath13
- Hal Hostetler, MVP @TVWizard
- Joy Apple, MVP @JoyOfSharePoint
Some relevant notes/links shared by the team:
- You can find a lot of unanswered questions or non-answers on how to resolve this issue, such as this one: Long Path URLs Affecting SharePoint Online Migration [https://answers.microsoft.com/en-us/msoffice/forum/all/long-path-urls-affecting-sharepoint-online/31ee9b81-c549-43cc-9fed-de061660c78d]
- If your source is OneDrive, check out: Migration Assessment Scan: Long OneDrive URLs [https://learn.microsoft.com/en-us/sharepointmigration/migration-assessment-scan-long-onedrive-urls]
- There are many migration tools on the market, depending on your source system. We mention a few in the video, but here is a quick review via TechTarget: 5 SharePoint migration tools to consider [https://www.techtarget.com/searchcontentmanagement/tip/SharePoint-migration-tools-to-consider]
