Fix Broken Links When Migrating Network Drives to SharePoint
Moving documents from a file server (UNC paths) to SharePoint Online transforms all embedded paths from Windows-style references (\\Server\Share\...) to HTTPS URLs (https://company.sharepoint.com/...). Every embedded link in every document becomes invalid the moment files land in SharePoint. This guide explains how to repair them all in bulk.
- Files on file servers use UNC paths like \\FileServer\Dept\Reports
- SharePoint uses HTTPS URLs like https://company.sharepoint.com/sites/Dept
- ReplaceMagic maps every old UNC path to the new SharePoint URL across thousands of files
Why Network-to-SharePoint Migration Breaks Document Links
Office documents store links to other files as the full path where the file lived at the time the link was created. A Word document linking to an Excel file stored at \\FileServer\Finance\Budget.xlsx has that exact UNC path embedded. After migration, that Excel file lives at https://company.sharepoint.com/sites/Finance/Budget.xlsx — the old path is completely invalid.
Affected link types include: hyperlinks, OLE object links, link sources (Excel external data), Power Queries, VBA macro references, header and footer embedded paths.
Scale of the problem: a typical migration of 50,000 documents with an average of 5 embedded links each = 250,000 broken links. Manual repair is not an option.
How ReplaceMagic Fixes Network-to-SharePoint Links
Step 1 — Pre-Migration Scan (recommended)
Run ReplaceMagic against the file server before migration. This identifies all documents with embedded links and their current paths — giving you the exact strings you will need to replace and scoping the repair effort for project planning.
Step 2 — Define Path Mappings
Create a simple mapping list of old UNC paths to new SharePoint URLs. ReplaceMagic supports unlimited mapping pairs in one run, so all departments can be covered simultaneously:
-
\\FileServer\Finance→https://company.sharepoint.com/sites/Finance -
\\FileServer\HR→https://company.sharepoint.com/sites/HR
Step 3 — Import Mappings and Preview
Import the mapping file into ReplaceMagic’s Search and Replace tab. Run in Preview mode to validate all proposed changes before committing. Review the preview report to confirm all path variations are covered.
Step 4 — Execute on SharePoint
Connect ReplaceMagic natively to SharePoint Online and run the replacement. Documents are processed in parallel without being opened; SharePoint metadata (last-modified date, author) is preserved with Site Admin rights.
Step 5 — Verify
Re-scan on SharePoint to confirm all links resolve correctly. Export a verification report for project documentation and user acceptance sign-off.
Supported Scenarios
- File server to SharePoint Online (most common)
- File server to SharePoint on-premises
- File server to Microsoft Teams document library (SharePoint backend)
- File server to OneDrive for Business (SharePoint backend)
- Multiple source servers to one or more SharePoint sites in a single run
Important Considerations
- Absolute vs relative links: absolute UNC paths are straightforward to replace; relative paths may need additional rules if folder depth changes during migration
- Password-protected documents: supported — provide passwords in bulk via import file
- SharePoint throttling: use 3–5 parallel threads for SharePoint Online; enable automatic throttling management in Configuration
