Fix Broken Links After Network Share to Network Share Migration
Moving documents from one network share to another — whether due to server consolidation, data centre move, or storage upgrade — breaks every embedded link that references the old share name or path. This guide covers how ReplaceMagic repairs all broken file paths across thousands of documents in a single bulk operation.
- Old path:
\\OldServer\CompanyDocs\Finance\Budget.xlsx - New path:
\\NewServer\Archive\Finance\Budget.xlsx - ReplaceMagic updates every embedded path across all documents without opening a single file
Why Network Share Migrations Break Document Links
Office documents store links to other files as the exact UNC path where the linked file was located when the link was created. When a network share is renamed, consolidated onto a new server, or moved to a different folder structure, that stored path becomes invalid. Every document that links to a file on the old share now has a broken reference.
Common Scenarios That Break Links
- Server rename: \\OldServerName → \\NewServerName (all paths with the old name break)
- Server consolidation: multiple servers merged onto one (\\ServerA and \\ServerB both become \\NewServer with different subfolder paths)
- Data centre migration: UNC paths change due to new server names in the new location
- Storage upgrade: NAS or SAN replacement with a different hostname or share name
- Folder restructuring: a new parent folder inserted into the hierarchy changes all paths beneath it
What Link Types Break
- Hyperlinks to other documents stored on the old share
- OLE object links (embedded charts, linked images, linked files)
- Excel external data source references (Link Sources)
- Excel Power Queries and Pivot table sources referencing the old path
- VBA macro code containing hardcoded UNC paths
- Headers and footers with embedded file references
How ReplaceMagic Fixes Network Share Migration Links
Step 1 — Scan Before or After Migration
Run ReplaceMagic against the document library (old or new share) to get a complete inventory of all embedded links and the exact path strings they contain. This scopes the repair effort and identifies every path variation that needs a replacement rule.
Step 2 — Define Replacement Rules
Set up one or more search/replace pairs covering all path changes:
-
\\OldServer\CompanyDocs→\\NewServer\Archive
For server consolidations with multiple source servers, add a row per server in the same import file.
Step 3 — Import Rules and Preview
Import the mapping file (CSV or text). Run in Preview mode to validate all proposed changes before committing. Review the preview report to confirm all path variations are covered before executing.
Step 4 — Execute
Run the replacement. ReplaceMagic processes all documents in parallel, updating every matching link in every document. Original file dates are preserved. No documents are opened during processing.
Step 5 — Verify
Re-scan on the new share to confirm all links now resolve correctly. Export a verification report for project documentation and audit purposes.
Handling Complex Path Changes
If the folder structure changed (not just the server name), you may need multiple replacement rules. For example, if \\OldServer\Dept1 became \\NewServer\Archive\2024\Dept1, one rule covers the full path change. Import all rules in a single CSV file — they all run in one processing pass.
Performance for Large Migrations
- Batch size: up to 250,000 documents per run recommended
- Parallel processing: increase parallel threads for local/network targets (8–16 threads on fast networks)
- Backup: enable automatic document backup before the first run on production data
- Volume licensing: for very large estates, run multiple licensed copies on separate machines simultaneously, each covering a different folder
