When you run the SharePoint Migration Tool, some files may be skipped without any clear error. This happens because Windows has a 260-character path limit that the tool enforces by default. Files with paths longer than 260 characters are not moved to SharePoint or OneDrive. This article explains why the tool skips these files and … Read more
When you migrate files to SharePoint using the SharePoint Migration Tool, some files may be skipped without an obvious error. The migration log shows a warning that the file path exceeds 400 characters. This happens because Windows and SharePoint enforce a maximum path length limit that the tool respects. This article explains why the SharePoint … Read more
When you run a SharePoint Migration Tool migration, some files may be skipped with a “path too long” error. This happens because Windows and SharePoint have a 400-character limit for the full file path including the file name. If any file exceeds this limit, the SharePoint Migration Tool will skip it and log it as … Read more
When you migrate files into SharePoint, the Created By field often shows the migration account instead of the original author. This happens because SharePoint writes the account that performed the upload as the creator. This article explains why the metadata is lost and provides two methods to restore the original Created By values. Key Takeaways: … Read more
When you migrate files to SharePoint, the Created By column often shows the migration account instead of the original author. This happens because the migration tool does not preserve the original author identity by default. The Modified By column may also show the migration date rather than the original modification date. This article explains why … Read more
Duplicate folders appear in SharePoint after a file share migration when the migration tool copies folder contents into a new folder instead of merging them with the existing folder structure. This problem occurs most often when the source file share has subfolders with names that match folders already created in the target SharePoint library or … Read more
When migrating file shares to SharePoint, duplicate folders often appear in the destination site. You see two folders with the same name, or a folder plus a subfolder that copies the parent name. This happens because of a mismatch between how Windows file shares handle folder metadata and how SharePoint maps paths during migration. This … Read more
When you modernize a classic SharePoint site, the navigation menu often stops working correctly. Links disappear, custom nodes fail to load, or the entire navigation bar renders as a blank area. This happens because the modern user interface uses a different navigation engine than the classic experience. This article explains why navigation breaks during site … Read more
When you modernize a classic SharePoint site, the top navigation bar and quick launch menu often disappear or stop working. Users see empty menus, missing links, or a broken site structure after the modernization process. This happens because the classic navigation provider is not replaced by the modern navigation provider during the upgrade. This article … Read more
When you modernize a SharePoint classic team site or publishing site, the navigation menu may stop working correctly. Links disappear, the menu fails to expand, or custom navigation nodes are lost entirely. This happens because the modernization process replaces the classic master page and navigation provider with a modern SharePoint framework that does not automatically … Read more