ReplaceMagic vs Manual Link Repair
After a SharePoint migration or server rename, broken links in Office documents are inevitable. The question is: do you fix them manually or automate?
Every Office document that contains embedded paths — hyperlinks, OLE links, Excel external references, Word field codes — will have broken links after a migration. The only variables are how many documents are affected and how you choose to repair them. This page compares the two approaches across every relevant dimension.
Feature comparison
| Capability | Manual repair (opening each document in Office) |
ReplaceMagic |
|---|---|---|
| Time per document | 3–10 minutes | Seconds |
| Documents processed per hour | 6–20 | Thousands |
| Accuracy | Prone to human error; easy to miss occurrences | Consistent; every occurrence of the search string is replaced |
| Requires Office to be installed and open | Yes | No |
| Handles OLE object links | Not via Find & Replace | Yes |
| Handles VBA path strings | Requires manual code editing | Yes |
| Handles headers and footers | Often overlooked | Yes |
| Handles Excel link sources and named ranges | Partial | Yes |
| Scales to 10,000+ files | Not feasible | Yes |
| Audit trail and reporting | No | Full report of all changes |
| Pre-migration scanning and baseline report | Not available | Yes |
| Preview changes before committing | No dry-run capability | Full Preview mode |
| Multiple replacement rules in one pass | One rule per run | Yes, unlimited rules simultaneously |
The maths
Manual repair assumes a trained person opens each document, runs Find & Replace in the main document body, checks headers and footers separately, reviews any linked objects, and saves. A realistic estimate is 3 minutes per document for a straightforward hyperlink-only case, rising to 10 minutes or more for documents with OLE links or VBA code.
Example calculation: 100,000 documents at 3 minutes each
- 100,000 documents × 3 minutes = 300,000 minutes
- 300,000 minutes ÷ 60 = 5,000 hours
- 5,000 hours ÷ 8 hours per working day = 625 working days
- At one full-time person: approximately 2.5 years of work
- At 10 people working in parallel: approximately 63 working days = 3 months
ReplaceMagic processes the same 100,000 documents in hours, not months, and without requiring a single person to open a document.
What manual repair misses
Even with unlimited time, manual repair using Office's built-in Find & Replace dialog cannot reach all link types:
- VBA references — path strings hard-coded in macro modules are not surfaced by Find & Replace. They require opening the VBA editor for each document and searching through code manually
- OLE links — the source path of an embedded OLE object is accessible only through the Edit Links dialog, which must be opened for each object in each document. It cannot be changed by Find & Replace
- Headers and footers — Office's Find & Replace does not reliably reach hyperlinks or field codes in headers and footers unless you switch into header/footer editing mode first
- Link sources in Excel — external cell references use a different storage mechanism than standard hyperlinks and are not found by the standard Find & Replace dialog
- Field codes in Word — INCLUDETEXT, INCLUDEPICTURE and similar fields require the field code to be displayed and edited directly, which Find & Replace does not do automatically
The consequence is that even after a careful manual repair pass, a significant proportion of broken links remain in the document estate, invisible until a user encounters them.
When is ReplaceMagic the right choice?
Any migration involving more than approximately 50 documents makes automation the more practical choice. Below that threshold, manual repair may be acceptable if the documents are simple and contain only hyperlinks. Above 50 documents, the combination of time cost, risk of missed link types, and lack of an audit trail makes manual repair unsuitable for a professional migration project.
ReplaceMagic is appropriate for:
- Server renames or consolidations affecting any number of documents
- SharePoint migrations (on-premises to Online, or tenant-to-tenant)
- Folder restructuring affecting document cross-references
- NAS or SAN replacements where storage paths change
- Network infrastructure changes (platform migrations, domain renames)
- Any situation where you need a documented, auditable record of all link changes made
Stop repairing links manually
Download the free trial and scan your document estate. No documents are modified in scan-only mode.
Download Free Trial Buy Now
