When you migrate files from an on-premises file server to OneDrive for Business over a weekend cutover, users often find that their recent document links stop working on Monday morning. These broken links appear as error messages like “File not found” or “This item might have been moved or deleted” when clicked from Microsoft 365 apps, Windows File Explorer Recent lists, or email attachments. The root cause is that the original file paths stored in the operating system and application caches no longer point to valid locations after the migration. This article explains why the links break and provides a step-by-step fix to restore access without re-uploading files.
Key Takeaways: Restoring broken recent links after a file server to OneDrive migration
- Windows Recent Items cache: Clears stale file references from the user profile, forcing the OS to rebuild links based on the new OneDrive sync location.
- OneDrive Known Folder Move: Redirects Desktop, Documents, and Pictures to OneDrive, which restores shortcuts that relied on the old server path.
- Microsoft 365 admin center > SharePoint Migration Tool: Preserves file metadata and sharing links during bulk transfers, reducing link breakage at the tenant level.
Why File Server Migration Breaks Recent Links in OneDrive
When users open files from a network share, Windows and Office applications store the file path as a Universal Naming Convention path such as \\fileserver\shared\report.docx. After migration, that file now lives in the user’s OneDrive under a local sync folder path like C:\Users\username\OneDrive - Company\shared\report.docx. The old UNC path no longer exists because the file server is decommissioned or the share is removed.
The Recent Items list in Windows File Explorer and the Recent Documents list in Office applications store these UNC paths. When a user clicks a recent link, the operating system tries to resolve the UNC path. If the server or share is offline, the link fails. Additionally, email signatures, SharePoint document library links, and Teams file tabs that pointed to the old server path will also break.
Weekend cutovers worsen the problem because users have no opportunity to update their local caches during the migration. When they return Monday morning, all cached paths from the previous week are invalid. The fix requires clearing stale caches on each client machine and re-establishing the file location through OneDrive sync.
Steps to Fix Broken Recent Links After a Weekend Cutover
Perform these steps on each affected user’s Windows 10 or Windows 11 computer. Run the steps in the order listed.
- Clear the Windows Recent Items cache
Press Windows + R to open the Run dialog. Typeshell:recentand press Enter. Select all items in the folder by pressing Ctrl + A. Press Delete and confirm the deletion. This removes all shortcuts stored in the Recent Items folder without affecting the actual files. - Clear the Office Recent Documents list
Open any Office application such as Word or Excel. Go to File > Options > Advanced. Scroll to the Display section. Set Show this number of Recent Documents to 0. Click OK. Reopen the same settings and restore the value to your preferred number, for example 25. This forces Office to rebuild the list from the new OneDrive sync path. - Run a quick OneDrive sync to refresh file pointers
Right-click the OneDrive cloud icon in the system tray. Select Settings > Account. Click Choose folders and verify that the migrated folders are selected. Click OK to trigger a full sync. Wait for the sync to complete. OneDrive updates the local file pointers and makes the files accessible from the new path. - Redirect Desktop, Documents, and Pictures to OneDrive
Right-click the OneDrive cloud icon and select Settings > Sync and backup > Manage backup. Turn on the toggle for Desktop, Documents, and Pictures. Click Start backup. This moves the user’s personal folders to OneDrive and updates all file shortcuts that reference these folders. - Recreate file shortcuts in email and Teams
Open any email or Teams chat that contains a broken link to an old server path. Delete the existing link. Navigate to the file in OneDrive using File Explorer. Right-click the file and select Share > Copy link. Paste the new OneDrive link into the email or chat. Send the updated message to recipients.
If OneDrive Still Has Issues After the Main Fix
OneDrive shows a red X or sync error after migration
A red X on a file or folder in the OneDrive sync status indicates a sync conflict. This often happens when the migration tool copies files with modified timestamps that conflict with existing local copies. To resolve this, right-click the file with the red X and select View sync conflicts. Choose Keep both files or Keep the server version. After resolving all conflicts, run a manual sync by right-clicking the OneDrive icon and selecting Sync.
Users cannot find migrated files in OneDrive
If files are missing from OneDrive after migration, check the SharePoint Migration Tool log for errors. Open the SharePoint Migration Tool from the Microsoft 365 admin center. Go to Migration > Review logs. Look for entries with a status of Failed or Warning. Common causes include file names longer than 256 characters, special characters in file names, or files larger than 250 GB. Rename or compress the problematic files and rerun the migration for those items.
OneDrive does not start after the cutover
If OneDrive fails to launch after the migration, the service may be blocked by a group policy or the client version is outdated. Press Windows + R, type onedrive, and press Enter. If nothing happens, download the latest OneDrive sync client from the Microsoft 365 admin center. Install the client and sign in with the user’s work account. Ensure that the Allow syncing OneDrive accounts to only specific organization group policy is not blocking the connection.
Broken Links Before and After Migration: Key Differences
| Item | Before Migration (File Server) | After Migration (OneDrive) |
|---|---|---|
| File path type | UNC path (\\server\share\file.docx) | Local sync path (C:\Users\…\OneDrive – Company\file.docx) |
| Recent Items storage | Stored in %AppData%\Microsoft\Windows\Recent | Rebuilt from OneDrive sync after cache clear |
| Link sharing method | Manual email attachment or network shortcut | OneDrive Share link with permissions |
| Access from outside office | Requires VPN or DirectAccess | Accessible from any internet-connected device |
| Backup and versioning | Manual file server backup | Automatic version history up to 500 versions |
After completing the steps above, users can access their migrated files through OneDrive without broken recent links. Run the cache-clearing steps on every machine that was connected to the old file server. For future cutovers, schedule a dry run one week before the weekend to identify and fix link issues early. Use the SharePoint Migration Tool with the Preserve file permissions option enabled to minimize link breakage at the tenant level.