OneDrive for Business file server migration breaks recent links for department moves: Fix Guide

When your organization migrates files from a legacy file server to OneDrive for Business, users often lose access to recent document links shared via email or Teams. This happens because the original file server paths become invalid after the move, and the new OneDrive URLs are not automatically mapped to the old links. The broken links cause confusion, lost productivity, and repeated requests for re-sharing. This guide explains why file server migration breaks shared links and provides a step-by-step fix for restoring access to recently shared documents.

Why file server migration breaks recent shared links

File servers use Universal Naming Convention (UNC) paths such as \\fileserver\shared\project.xlsx. When users share files from the file server, email clients and Teams embed these UNC paths as hyperlinks. OneDrive for Business uses HTTPS URLs like https://contoso-my.sharepoint.com/personal/user/Documents/project.xlsx. The migration tool copies the file content and metadata, but it does not rewrite existing email or chat messages. Any link that was sent before migration still points to the old UNC path, which no longer resolves after the file server share is decommissioned. Additionally, if the migration tool does not preserve file-level sharing permissions, users may see access denied errors when they click the newly generated OneDrive link.

Steps to fix broken recent links after migration

Use these steps to restore access to recently shared files. Complete the steps in order for best results.

1. Identify the affected files and users
   Open the Microsoft 365 admin center. Go to Reports > Usage > OneDrive. View the Most used files report. Note the file names and the users who shared them recently. Cross-reference with your migration log from the SharePoint Migration Tool to confirm which files were moved.
2. Generate new OneDrive sharing links for each affected file
   Ask the file owner to open the file in OneDrive on the web. Select the file, click Share, and choose Copy link. Select the appropriate permission level: Anyone with the link (if the file is public), People in your organization, or Specific people. Click Copy and send the new link to the original recipients via email or Teams.
3. Use SharePoint Migration Tool to remap links (advanced)
   If you have many broken links, use the SharePoint Migration Tool (SPMT) with the Preserve file share permissions option enabled. During migration, SPMT can update file URLs in SharePoint lists but cannot rewrite links inside email messages. For email links, you must re-share manually. Run SPMT again on the same source folder with the Incremental migration option to detect any newly shared files.
4. Update shared links in Microsoft Teams channels
   If the broken links appear in Teams chat or channel posts, the user who shared the link must delete the old message and post a new message with the OneDrive link. To find all messages containing the old file server path, use Teams search: type the old UNC path in the search bar and filter by the relevant channel or chat.
5. Notify users about the change
   Send a company-wide email or Teams announcement. Include instructions for recipients: If you receive a broken link, request the file owner to re-share using OneDrive. Provide a link to your organization’s migration FAQ page.

If links remain broken after re-sharing

Recipients see Access Denied on the new OneDrive link

This occurs when the file owner chose Specific people in the Share dialog but did not include the recipient’s email address. The file owner must open the file in OneDrive, click Share, and verify that the recipient’s email appears in the Shared with list. If not, they must re-share with the correct email address.

The file server path appears in the URL bar of SharePoint

This happens when the file was not fully migrated or the migration tool left a redirect shortcut. Open the SharePoint Migration Tool and run a full scan on the source folder. If the file shows as Not migrated, re-run the migration with the Replace option. After migration, delete any leftover shortcut files on the file server.

Multiple users reported the same broken link

Use the Microsoft 365 admin center to create a shared link for the entire department. Go to SharePoint admin center > Policies > Sharing. Create a sharing policy that allows Anyone with the link for the target OneDrive library. Apply the policy to the affected site. Then generate a single sharing link for the parent folder and distribute that link to all recipients. This reduces the number of individual re-share requests.

File server path vs OneDrive URL: Key differences for link stability

Item	File server path (UNC)	OneDrive URL (HTTPS)
Format	\\server\share\folder\file.ext	https://tenant-my.sharepoint.com/personal/user/Documents/folder/file.ext
Dependency	Requires active file server and network drive mapping	Requires valid user license and OneDrive site
Link durability after migration	Breaks immediately after file server decommission	Persists as long as the file exists in OneDrive
Permission inheritance	Uses NTFS permissions on the server	Uses SharePoint permission inheritance and sharing links
Maximum link length	260 characters (Windows path limit)	4000 characters (modern browser limit)

File server migration to OneDrive breaks recent shared links because the underlying path format changes completely. By re-sharing files through OneDrive’s Share dialog and using the SharePoint Migration Tool for bulk operations, you can restore access for all affected users. For future moves, enable Known Folder Move in OneDrive sync settings before migration so that files are stored in OneDrive from the start. As an advanced tip, configure a SharePoint site collection app catalog and deploy a custom link rewriter web part that automatically replaces UNC paths with OneDrive URLs in SharePoint pages.