New file storage causing broken links in Office documents
When an organisation replaces its file storage hardware or changes its storage architecture, the network path to every stored document changes — even when the folder structure and file names remain identical. Every Office document that contains an embedded path to the old storage will immediately have broken links. ReplaceMagic scans the new storage, identifies all affected documents, and repairs every broken path in bulk.
What triggers a new file storage migration
File storage migrations happen for several infrastructure reasons:
- NAS replacement — an ageing network-attached storage device is replaced with new hardware. The new device has a different hostname or IP address, changing all UNC paths
- SAN upgrade — a storage area network upgrade changes volume names or the way volumes are presented to the network
- Cloud storage adoption — documents are moved from a local NAS or file server to a cloud-based file platform. All UNC paths are replaced by URLs or a new path convention
- Data centre move — a physical move to a new data centre often results in new server hostnames, new IP addresses, or a new network architecture, all of which change the paths documents use
Why links break even when folder structure is preserved
The folder structure and the documents themselves may be copied perfectly to the new storage. Every file is present and intact. But the stored paths in Office documents contain the name of the old storage device, not the new one. A link to \\NAS-OLD\Storage\Finance\Q1Report.xlsx cannot resolve after the migration because NAS-OLD no longer exists. The file is now at \\NAS-NEW\Storage\Finance\Q1Report.xlsx but no document knows this automatically.
Typical storage migration examples
Two common path change patterns:
- NAS hostname change:
\\NAS-OLD\Storage\→\\NAS-NEW\Storage\ - Drive letter to UNC:
Z:\Documents\→\\NewSAN\Vol1\Documents\
In both cases the folder structure beneath the root is unchanged, so a single search/replace rule per variant fixes every broken link.
Scanning the new storage to generate an inventory
After the files have been copied to the new storage, point ReplaceMagic at the new root path. It will crawl every subfolder, open every Office document, and extract all embedded paths — producing a complete inventory of every document and every link it contains. This inventory is the foundation of the repair process. It also confirms that all documents were successfully copied and are accessible on the new storage before any replacements are made.
Verifying link validity before and after
ReplaceMagic can check whether each embedded path actually resolves to an existing file. Running a validity check before the migration confirms the baseline state: which links are currently valid on the old storage. Running it again after the replacements confirms that all previously valid links now resolve on the new storage, and flags any that do not for further investigation.
Using Preview mode before committing
Before executing replacements, Preview mode shows exactly which documents will be modified and which strings will be substituted. This allows you to verify that the replacement rule is correct and complete before any file is changed. For a storage migration affecting thousands of documents, this review step is an important safeguard.
Handling multiple path variants
If the document estate contains both UNC paths and mapped drive letter paths referencing the old storage, both variants can be configured as separate replacement rules and run simultaneously in a single pass. This ensures all path forms are updated consistently regardless of how individual users had their drives mapped when the documents were created.
In case of any questions please do not hesitate to contact us.
