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

When your organization moves a department from one file server to another, users often lose access to recent files they opened from OneDrive for Business. The symptom appears as broken links in the “Recent” list inside Office apps like Word, Excel, or PowerPoint. This happens because the file paths stored in the Office Recent list point to the old server location, and OneDrive sync does not automatically update those references.

The root cause is that OneDrive for Business tracks files by their local path and server URL. After a department move, the new server path differs from the old one, so OneDrive cannot match the migrated files to the existing recent entries. This article explains why this occurs and provides a step-by-step method to restore access to recent files after a server migration.

You will learn how to identify the broken paths, how to rebuild the Office Recent list, and how to prevent this issue in future migrations by using Shared Links or Known Folder Move.

Why Department Server Moves Break OneDrive Recent Links

When a department is moved to a new file server, the physical location of the files changes. OneDrive for Business syncs files from SharePoint document libraries or OneDrive personal libraries, but it also syncs files from mapped network drives if you use the OneDrive sync client for SharePoint. The Office Recent list does not store the cloud link — it stores the local file path that Office used to open the file. After the migration, that local path no longer exists because the file is now at a new UNC path.

The Office Recent list is stored per user in the Windows registry under HKEY_CURRENT_USER\Software\Microsoft\Office\Version\User MRU\LiveId_####\FileMRU. Each Office app maintains its own list. When you click a recent file, Office tries to open the path stored there. If the path points to the old server, Office fails with a “File not found” error. OneDrive does not intercept this lookup because the path is local, not a SharePoint URL.

The problem is amplified when users have many recent files — up to 150 per app. Migrating a department of 50 users could result in thousands of broken recent links. The only reliable fix is to clear the broken entries and let users reopen the files from the new location, which repopulates the Recent list with the correct path.

Steps to Restore Recent Links After a Department Migration

These steps assume the files have been successfully moved to the new server and OneDrive sync is working on the new path. Do not start before confirming that users can access the new server location directly.

1. Close all Office applications
   Word, Excel, PowerPoint, and Outlook must be closed. The Recent list is cached in memory and written to the registry when the app closes. If apps are open, clearing the registry will not take effect.
2. Open the Registry Editor
   Press Windows key + R, type regedit, and press Enter. Click Yes if prompted by User Account Control.
3. Navigate to the Office Recent list key
   Go to: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\User MRU\LiveId_####\FileMRU. Replace 16.0 with your Office version: 16.0 for Office 2016 and Microsoft 365, 15.0 for Office 2013. The LiveId_#### folder name varies per user — it contains the user’s Microsoft 365 account hash.
4. Delete the FileMRU key for each Office app
   Right-click the FileMRU folder and select Delete. Repeat this step for Excel, PowerPoint, and any other Office app that shows broken recent links. The paths are:
   HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\User MRU\LiveId_####\FileMRU
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\PowerPoint\User MRU\LiveId_####\FileMRU
5. Clear the Office Upload Center cache
   Open the Office Upload Center (search for it in the Start menu). Click Settings and then Delete cached files. This removes any stale file metadata that might interfere with new recent entries.
6. Open a file from the new server location
   In File Explorer, navigate to the new server path. Open a document from there. Office will add this file to the Recent list with the correct new path.
7. Test the Recent list
   Open Word, click File > Open > Recent. The file you just opened should appear. Click it to confirm it opens without errors.

If Recent Links Still Break After the Main Fix

OneDrive sync shows a red X on migrated files

A red X in the OneDrive sync status column means the file is not syncing to the new location. This can happen if the OneDrive sync client is still pointing to the old SharePoint document library. To fix this, go to OneDrive settings > Account > Choose folders and verify that the correct library is selected. If the old library was removed, unlink and relink the OneDrive account.

Office shows “Sorry, we couldn’t find your file” when clicking a recent link

This error appears if the registry key was not fully cleared. Open Registry Editor again and confirm that the FileMRU key under each Office app is deleted. Also check the HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Internet\FileMRU key, which stores links from file dialogs. Delete that key as well.

Users want to keep some recent files but not all

The registry method clears the entire Recent list. If users need to keep specific entries, they can manually remove only the broken ones by right-clicking a recent file in Office and selecting Remove from list. This is slower but preserves the working entries.

Manual Removal vs Registry Clear: Comparison for Recent Link Repair

Item	Manual removal in Office	Registry clear
Time per user	5–15 minutes depending on number of broken links	2–3 minutes
Preserves recent files	Yes — only broken entries are removed	No — all recent entries are deleted
Requires admin rights	No	Yes — Registry Editor access needed
Risk of error	Low — user selects which items to remove	Medium — wrong key deletion can affect other Office settings

After the migration is complete, users can now open files from the new server location and see them in the Recent list. The broken links from the old server are gone. To prevent this issue in future moves, use OneDrive Shared Links instead of direct file paths. When you share a file via OneDrive, the link remains valid even if the file is moved to a different SharePoint site or server. For department moves, plan to redirect users to the new server using a Group Policy that sets the default save location in Office.

An advanced tip: use the OneDrive admin center > Sync > Known Folder Move to redirect Desktop, Documents, and Pictures to OneDrive. This eliminates server paths entirely for those folders, so future migrations will not break recent links for those files.