OneDrive Admin Checklist: file server migration breaks recent links for remote users

When you migrate files from an on-premises file server to OneDrive for Business, remote users often find that their recent document links stop working. These links, which point to file server UNC paths such as \\Server\Share\Document.docx, become invalid after the migration because the target location has changed. This article explains why file server migration breaks recent links, provides a step-by-step checklist to prevent and fix the issue, and covers related problems such as broken shared links and offline file conflicts. You will learn how to use OneDrive sync, Known Folder Move, and sharing link migration to maintain seamless access for remote users.

Why File Server Migration Breaks Recent Links for Remote Users

When a remote user opens a document from a file server, Windows records the file’s UNC path in the Recent Items list and in Office applications’ Recent Documents lists. After you migrate that file to OneDrive, the UNC path no longer points to a valid location. The file server share may be decommissioned, renamed, or restricted, leaving the link broken.

Two technical factors make this problem worse for remote users. First, remote users connect through VPN or DirectAccess, and if the file server is taken offline during migration, they cannot access the old path to open the file even temporarily. Second, OneDrive stores files at a URL like https://tenant-my.sharepoint.com/personal/user/Documents/File.docx, which is completely different from the UNC path. Office applications do not automatically replace UNC paths with OneDrive URLs. Without intervention, every recent link created before migration becomes a dead shortcut.

How Office Stores Recent Links

Office 365 apps store recent documents in the Windows registry and in a local database file. The path stored is the exact path used when the file was last opened. If the file was opened from a file server, that path is the UNC path. Office does not check whether the path still works until the user clicks the link. At that point, the application tries to connect to the file server, fails, and shows an error message such as “We can’t find this file. It may have been moved, renamed, or deleted.”

Why Remote Users Are Affected More Than On-Site Users

On-site users on the corporate LAN can sometimes access the old file server during a migration cutover window. Remote users, however, rely on VPN connectivity to reach the file server. If the file server is decommissioned before the migration is fully validated, remote users lose all access to the old paths. Additionally, remote users often have slower VPN connections, making it impractical to re-open every file to rebuild the recent links manually.

Admin Checklist to Prevent and Fix Broken Recent Links

Use this checklist before, during, and after the file server migration to OneDrive. Each step targets a specific cause of broken recent links.

Before Migration: Configure OneDrive Sync and Known Folder Move

1. Enable Known Folder Move for all users
   In the OneDrive admin center, go to Sync > Known Folder Move. Select Desktop, Documents, and Pictures. This redirects the user’s local folders to OneDrive. After migration, any file the user saves to these folders automatically appears in OneDrive, and the recent link points to the OneDrive path.
2. Turn on Files On-Demand
   In OneDrive Settings > Sync and backup > Advanced settings, enable Files On-Demand. Remote users can see all OneDrive files as placeholders without downloading them. This prevents sync conflicts that could overwrite migrated files and break recent links.
3. Audit current recent links with a script
   Run a PowerShell script to export each user’s Office recent documents list from the registry and the Office file database. Save this list. After migration, you can compare it with the new OneDrive paths to identify which files still have broken links.

During Migration: Use SharePoint Migration Manager

1. Run SharePoint Migration Manager
   In the Microsoft 365 admin center, go to SharePoint > Migration Manager. Select your file server as the source. The tool copies files to OneDrive and SharePoint and can optionally update file references. Enable the option “Update file links in Office documents” to replace UNC paths with OneDrive URLs inside the file metadata.
2. Keep the file server online during migration
   Do not decommission the old file server until all users have confirmed that their recent links work. Set the file server share to read-only during the cutover so remote users can still open files from the old path while you validate the new OneDrive paths.
3. Use a DNS alias for the file server
   Create a CNAME record that points the old file server name to a placeholder. After migration, update the CNAME to redirect to a web page that explains the new OneDrive location. This prevents remote users from seeing a generic “server not found” error.

After Migration: Fix Existing Broken Links

1. Deploy the Microsoft Support and Recovery Assistant
   Run the SaRA tool on remote user machines with the “OneDrive for Business” scenario. SaRA can scan for broken Office recent links and replace them with OneDrive URLs. This tool requires the user to have the migrated files already synced to OneDrive.
2. Use a Group Policy to clear and rebuild recent links
   Create a Group Policy Object that runs a logon script. The script deletes the Office recent documents registry keys under HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\File MRU and then triggers a one-time sync of the user’s OneDrive. After the sync, the user’s recent links will only show OneDrive files they open going forward.
3. Train users to use the OneDrive web interface
   Show remote users how to access their migrated files through https://portal.office.com/onedrive. The web interface does not rely on recent links from the file server. Users can pin frequently used files to the Quick Access section in the browser.

If Recent Links Still Break After Migration

Remote users see “We can’t find this file” when clicking a recent link

This error means the UNC path in the recent link points to a file server that is no longer accessible. The quickest fix is to run the SaRA tool as described in the post-migration steps. If SaRA does not resolve the issue, open the file manually from OneDrive and then close it. Office will create a new recent link with the correct OneDrive URL. Repeat this for each file the user needs to access.

OneDrive sync shows a red circle with a white minus sign on migrated folders

This icon means the folder is excluded from sync. Remote users may have set up OneDrive sync before the migration, and the old sync relationship conflicts with the new OneDrive folder structure. To fix this, go to OneDrive Settings > Account > Stop sync on the old library. Then start sync on the new OneDrive library. After resyncing, the user’s recent links will point to the new local OneDrive folder path, which mirrors the cloud path.

Shared links that were sent before migration now return a 404 error

File server migration does not automatically update shared links that were sent via email or chat. If you migrated files from a file server to OneDrive, any shared link containing the old URL will break. To prevent this, use the SharePoint Migration Manager option to generate new sharing links during migration. For links already sent, ask users to resend the file using the OneDrive Share button, which creates a link with the new OneDrive URL.

Item	File Server (UNC Path)	OneDrive (URL Path)
Link format	\\Server\Share\Folder\File.docx	https://tenant-my.sharepoint.com/personal/user/Documents/Folder/File.docx
Access method for remote users	VPN required	Internet connection, no VPN required
Recent link storage in Office	UNC path stored in registry	OneDrive URL stored in registry
Link migration tool support	Not applicable	SharePoint Migration Manager can update links
Offline access	Available if file server is online	Available via OneDrive Files On-Demand sync

Now you can plan a file server migration to OneDrive without breaking recent links for remote users. Start by enabling Known Folder Move and Files On-Demand before migration. Use SharePoint Migration Manager to update file references during the cutover. After migration, deploy the SaRA tool to fix any remaining broken links. For advanced protection, configure a Group Policy logon script that clears old recent links and forces a OneDrive sync on first login.