Fix Office Document Links After a ShareGate Migration
Use ShareGate for the content-migration work it is designed to perform, then use ReplaceMagic to inspect and repair supported references stored inside the migrated Office documents.
Why a successful content move can still leave broken links
A document can arrive at the correct destination while a hyperlink, OLE object, external workbook reference or data-source path inside that document still points to the old server, site, library or tenant. The content move and the internal-reference repair are separate validation tasks.
Recommended sequence
- Export the source-to-target site, library and folder mapping.
- Scan a pre-migration pilot with ReplaceMagic and classify the discovered link types.
- Complete the pilot migration with ShareGate and preserve its migration reports.
- Generate and test replacement patterns; use SmartMapper where source analysis is required.
- Repair a copy of the pilot, rescan it and obtain business-owner approval.
- Run production batches and retain both migration and link-repair reports.
What to validate
- Old and new tenant or site URLs
- UNC and mapped-drive paths embedded in documents
- Word hyperlinks and linked objects
- Excel external links, connections and Power Query paths
- SharePoint ID-based links that may require pre-cutover resolution










