Migrating files from on-premises file servers to SharePoint Online is a common step in modern Microsoft 365 projects. However, one issue consistently causes delays, user frustration, and broken reporting: Excel links that stop working after a SharePoint migration.
Organisations that rely heavily on Excel for financial reporting, forecasting, or operational dashboards often discover that once their files are moved to SharePoint, previously stable workbooks suddenly display broken links, missing data, or constant “Update Links?” warnings. Understanding why this happens is the first step to solving it properly.
Why Excel Links Break During a SharePoint Migration
Excel was designed long before SharePoint Online existed. In many organisations, Excel workbooks have grown organically over years, forming complex dependency chains between files stored on local drives or Windows file shares.
Most of these workbooks use absolute file paths or UNC paths to reference other Excel files. A typical example looks like:
\\fileserver01\Finance\Budgets\2024.xlsx
This path relies on SMB (Server Message Block), the traditional Windows file-sharing protocol. When files are migrated to SharePoint Online, they are no longer accessed using SMB. Instead, they are accessed via HTTPS URLs, such as:
https://tenant.sharepoint.com/sites/Finance/SharedDocuments/Budgets/2024.xlsx
From Excel’s perspective, these two locations are completely unrelated. Even if the file names and folder structures appear identical, Excel can not automatically translate an SMB file path into a SharePoint URL. This is why links that worked perfectly on a file server often fail immediately after a SharePoint migration.
Why URL Redirects Do Not Fix Excel Link Issues
A common assumption during SharePoint migrations is that a URL redirect or rewrite rule can solve broken Excel links. Unfortunately, this approach only works in very limited scenarios.
URL redirects function at the HTTP or HTTPS level. They are designed for web traffic. If an Excel workbook contains links that already use HTTP-based URLs, a redirect can sometimes forward the request to the new SharePoint location.
However, most legacy Excel links do not use web URLs. They use UNC paths, which are accessed via SMB, not HTTP. When Excel opens a link such as:
\\server\share\file.xlsx
it never makes a web request. There is no HTTP traffic to intercept, and therefore no redirect server is ever involved. This means that URL rewrite rules simply cannot affect SMB-based Excel links.
This is why organisations often deploy redirect infrastructure only to discover that Excel links remain broken.
Practical Ways to Fix Excel Links in SharePoint
There is no single solution that works for every environment, but several proven approaches can significantly reduce link breakage during a SharePoint migration.
Using SharePoint and Microsoft 365 Migration Tools
Microsoft and third-party migration tools increasingly understand Excel dependencies. Some tools are capable of scanning workbooks, identifying linked files, and updating references during the migration process. This is often the safest option for large environments, as it reduces manual effort and scales well across thousands of files.
However, results vary depending on how complex the Excel models are, and critical financial workbooks should always be validated after migration.
Mapping SharePoint as a Network Drive Using WebDAV
SharePoint Online can be accessed through Windows File Explorer using a WebDAV-based UNC path that includes @SSL, such as:
\\tenant.sharepoint.com@SSL\sites\Finance\Shared Documents\
The @SSL component instructs Windows to use a secure HTTPS connection rather than SMB. From Excel’s point of view, this still appears as a network path, which means some legacy Excel links can continue to function if the folder structure is kept consistent.
This approach can be very useful as a temporary bridge during migration projects. It allows users to continue working while links are gradually remediated. However, it is not recommended as a permanent replacement for file servers due to performance and reliability limitations.
Programmatically Updating Excel Links
In controlled environments, Excel links can be rewritten using automation. PowerShell scripts, VBA macros, or Excel automation libraries can scan workbooks, detect external links, and update them to point to new SharePoint URLs.
This method provides precision and control, but it requires careful testing. Poorly written scripts can easily corrupt formulas or break complex models. For organisations with standardised folder structures and strong technical skills, this can be an effective solution.
Using Dedicated Excel Link Management Tools
For organisations where Excel is business-critical, specialised Excel link management tools offer the most reliable approach. These solutions are designed specifically to analyse workbook dependencies, manage cross-file links, and perform bulk link rewrites when moving content to SharePoint or Microsoft 365.
While this approach involves additional tooling, it significantly reduces risk for finance, accounting, and operational teams that depend on accurate Excel data.
WorktreeX is well positioned to address the challenges of SharePoint migrations by mapping Excel dependencies and giving users full control over link structures, making it easy to repoint links to their correct locations. 👉 Learn more about WorktreeX
Final Thoughts on Excel and SharePoint Migrations
Broken Excel links are one of the most common — and most disruptive — problems encountered during SharePoint migrations. They are not caused by SharePoint itself, but by the fundamental difference between SMB file paths and cloud-based URLs.
The most successful migrations treat Excel link remediation as a core workstream, not an afterthought. Whether you choose migration tooling, WebDAV-based access, scripted updates, or dedicated link management software, the key is to plan for Excel early.
Handled correctly, organisations can move to SharePoint without losing trust in their spreadsheets — and without turning migration day into a reporting crisis.