Fix Broken Links After Migrating to SharePoint Online

Migrating documents to SharePoint Online converts every embedded UNC file path (\\Server\Share\...) into an HTTPS URL (https://company.sharepoint.com/...). Every hyperlink, OLE link, link source and VBA reference that used the old path breaks the moment files land in SharePoint Online. This guide explains how ReplaceMagic repairs them all in bulk.

Old path: \\FileServer\Dept\Budget.xlsx
New URL: https://company.sharepoint.com/sites/Dept/Budget.xlsx

Every embedded link in every Office, PDF and text file referencing the old path becomes broken simultaneously

ReplaceMagic maps old paths to new URLs across thousands of files — natively connected to SharePoint Online, no drive mapping needed

Why SharePoint Online Migration Breaks Document Links

Office documents store links to other files as the exact path where the linked file lived when the link was created. A Word document linking to an Excel file at \\FileServer\Finance\Budget.xlsx has that UNC path hard-coded inside it. After migration to SharePoint Online, that Excel file now lives at https://company.sharepoint.com/sites/Finance/Budget.xlsx — a completely different format. The old UNC path no longer resolves.

The scale of breakage is typically enormous. A migration of 50,000 documents averaging 5 embedded links each produces 250,000 broken references — all occurring simultaneously at cutover.

Which Link Types Break

Hyperlinks (web URLs and file path links)
OLE object links (embedded charts, linked images)
Link Sources (Excel and Word external data references)
Power Queries and Pivot data sources (Excel)

VBA macro code referencing old server paths
Headers and footers with embedded file paths
SharePoint Canvas and Wiki page content (ASPX)

How ReplaceMagic Fixes Broken Links After SharePoint Online Migration

Step 1 — Connect to SharePoint Online

In ReplaceMagic, select SharePoint Online as your target. Authenticate using Microsoft 365 credentials, MFA app password, or App-Only Authentication. ReplaceMagic connects via the SharePoint API — no drive mapping or WebDAV required. See the authentication guide for full details.

Step 2 — Scan and Inventory

Select your SharePoint Online document libraries and run a scan. ReplaceMagic builds a complete inventory of every document and every embedded link — showing the current link value, link type and validity status. This also serves as your pre-repair audit baseline.

Step 3 — Configure Path Mapping Rules

Define the replacement mapping for your migration. For a file server to SharePoint Online migration, the core rule is typically:

\\FileServer\CompanyDocs → https://company.sharepoint.com/sites/CompanyDocs

Add additional rows for each department or share that maps to a different SharePoint site. Import all rules from a CSV file for complex migrations with many mappings. See the import data guide.

Step 4 — Preview All Proposed Changes

Run in Preview mode. ReplaceMagic reports every change it would make — document by document, link by link — without writing anything to disk. Review the grid to confirm the replacement rules are correct before committing.

Step 5 — Execute the Repair

Run the replacement. ReplaceMagic processes documents in parallel across CPU cores, updating all matching links in all files. No documents are opened. SharePoint metadata (last-modified date, author) is preserved with Site Admin rights. SharePoint throttling is managed automatically — keep parallel threads at 3–5 for Online targets.

Step 6 — Verify With a Re-Scan

Re-scan the SharePoint Online libraries after the replacement run. Confirm all links now resolve correctly. Export a verification report for project documentation and stakeholder sign-off.

SharePoint Online–Specific Features in ReplaceMagic

Native API connection: no WebDAV or drive mapping required — faster and more reliable
Metadata preservation: keeps last-modified date and modified-by author (Site Admin rights required)
Check-in/check-out management: auto-manages document locking during processing
Throttling protection: automatically reduces parallel processing if HTTP 429 errors occur
Canvas & Wiki pages: repairs links embedded in SharePoint ASPX page content
Teams & OneDrive: supported via their SharePoint backend