Fix Broken Links After Migrating to SharePoint Online

Moving your document estate to SharePoint Online is one of the most common — and most disruptive — migrations an IT team can undertake. The moment documents leave a traditional file server or on-premises SharePoint environment and arrive in SharePoint Online, every embedded link that referenced the old storage location stops working. Hyperlinks fail, Excel workbooks lose their external data connections, OLE objects become unresolvable, and Power Query refreshes throw errors. The documents themselves are intact; the invisible web of references that connected them is not. ReplaceMagic is the purpose-built tool that repairs those references in bulk, across your entire document library, without opening a single file.

Why SharePoint Online Migration Breaks Document Links

Traditional corporate document storage uses Universal Naming Convention (UNC) paths — addresses that look like \\FileServer\Departments\Finance\Report.xlsx or \\SharePoint2016\sites\Projects\document.docx. SharePoint Online does not use UNC paths. Every resource in SharePoint Online is addressed by an HTTPS URL, typically in the form https://company.sharepoint.com/sites/Finance/Documents/Report.xlsx.

When a migration tool moves documents from a file server or on-premises SharePoint to SharePoint Online, the files are copied or transferred correctly — but every link inside those documents still points to the old UNC path or the old on-premises URL. Those addresses no longer exist in the new environment. The result is broken links at scale.

In a typical enterprise migration involving 50,000 documents, each containing an average of three to five embedded references, the total number of broken links can easily reach 150,000–250,000. Manual repair is not a realistic option. ReplaceMagic processes the entire corpus in a single automated run.

Which Link Types Break After SharePoint Online Migration

The damage is not limited to clickable hyperlinks. Office documents embed path references in many places:

• Hyperlinks — in Word paragraphs, Excel cells, PowerPoint shapes, and Visio shapes
• OLE object links — embedded objects whose data source is an external file
• Excel external link sources — workbooks that pull data from other workbooks via cell references
• VBA references — macro code that opens or reads external files by path
• Header and footer embedded paths — document footers that display a file path field
• Power Query connections — data refresh queries that reference SharePoint lists or file locations
• Word field codes — INCLUDETEXT, INCLUDEPICTURE, and similar fields pointing to external resources

ReplaceMagic addresses every one of these link types in a single pass.

How ReplaceMagic Fixes Broken Links After SharePoint Online Migration

The repair workflow follows a straightforward six-step process designed to give you full visibility and control before any changes are committed to your document library.

Step 1 — Connect to SharePoint Online

ReplaceMagic connects natively to SharePoint Online using Microsoft’s SharePoint API. No drive mapping, no WebDAV, no virtual file system. You authenticate with your Microsoft 365 credentials — including modern authentication with MFA or App-Only Authentication for unattended service accounts — and ReplaceMagic has direct access to every document library in scope.

Step 2 — Scan and Inventory

ReplaceMagic scans every document in the specified libraries and builds a complete inventory of every embedded link it finds: the file that contains it, the link type, and the current link target. You can export this inventory as a report before doing anything else — useful for communicating migration scope to stakeholders.

Step 3 — Configure Path Mapping Rules

You define the mapping between old paths and new SharePoint Online URLs. For example: replace \\FileServer\Departments with https://company.sharepoint.com/sites/Departments/Documents. ReplaceMagic supports multiple mapping rules simultaneously, regular expressions for complex path transformations, and case-insensitive matching to handle inconsistent authoring conventions.

Step 4 — Preview All Proposed Changes

Before a single file is modified, ReplaceMagic shows you every proposed change: the original value, the replacement value, the file, and the link type. You can review, approve, or exclude individual items. This preview step is critical for quality assurance in regulated industries.

Step 5 — Execute the Repair

ReplaceMagic processes documents in parallel across multiple CPU threads, writing repairs directly into each file’s binary format without launching Office applications. Document metadata — last modified date, author, and editor — is preserved when running with Site Collection Administrator rights. Check-out and check-in are handled automatically; files checked out by other users are reported rather than skipped silently.

Step 6 — Verify With a Re-Scan

After the repair run, ReplaceMagic performs a verification scan to confirm that no instances of the old paths remain. The verification report serves as your completion evidence for change management and compliance documentation.

SharePoint Online–Specific Features in ReplaceMagic

• Native SharePoint API connection — no drive mapping or WebDAV required
• Metadata preservation — last-modified date and author are maintained (requires Site Collection Administrator rights)
• Automatic check-in / check-out management — files are checked out before modification and checked in afterwards; force check-in is available for abandoned checkouts
• Modern authentication support — handles MFA, App-Only Authentication, and OAuth-based modern auth flows
• Automatic throttle management — ReplaceMagic detects Microsoft 365 API throttling signals and backs off gracefully, then resumes without user intervention
• SharePoint Canvas and Wiki page support — link references embedded in modern SharePoint pages are also updated

Migration Scenarios Supported

ReplaceMagic handles the full range of SharePoint Online migration patterns encountered in enterprise environments:

• File server to SharePoint Online — UNC path references replaced with SharePoint Online HTTPS URLs
• SharePoint on-premises to SharePoint Online — old on-premises site collection URLs replaced with their SharePoint Online equivalents
• Tenant-to-tenant migration — source tenant URLs replaced with destination tenant URLs, including ID-based link conversion where applicable
• OneDrive for Business — documents stored on OneDrive for Business are accessed via the SharePoint backend and repaired in the same workflow
• Microsoft Teams document libraries — Teams stores all documents in SharePoint Online; ReplaceMagic connects to and repairs those libraries directly

In case of any questions please do not hesitate to contact us.