Limitations for Folder Names and Filenames When Migrating to SharePoint
Microsoft Article Describing the Limitations
To address these limitations, you can choose to automatically shorten the path and filename to fit within SharePoint’s constraints. The original path and filename, before shortening, are preserved in the standard columns and can be assigned to any metadata column.
Additionally, in the database view Report_MigratedFiles, the column shortenedpathname indicates whether the path or filename was shortened (1 = Shortened, 0 = Not Shortened).
Note that the shortening occurs after transformations, so it also applies to custom naming.
Here’s what happens:
- We detect excessively long paths and automatically shorten them.
- At the same time, we retain a reference to the original location and name.
- In the “Migration Model,” you can view both the shortened path and the original path and name simultaneously, enabling you to decide on appropriate renaming.
ALL OF THIS IS VISUALIZED IN TEAMS, ensuring the end result is 100% correct and aligns with the document owners’ preferences and understanding.
Renaming and reorganizing is particularly challenging for IT teams, as they may not understand the logic behind folder and document naming. However, document owners do understand it. By involving them in the process, they can rename and reorganize structures to create a GREAT end result, ready before the migration takes place.