SharePoint Migration Scenarios — How ReplaceMagic Fixes Broken Links
Broken links are an almost inevitable byproduct of SharePoint migrations. The moment a file moves to a new URL, every hyperlink, OLE object reference, and embedded path in every document that pointed to the old location stops working. ReplaceMagic addresses five distinct SharePoint migration scenarios, each with its own pattern of link breakage and its own repair strategy.
Scenario 1: File Server to SharePoint Online
What happens: An organization migrates documents from a Windows file server to SharePoint Online. Files that previously lived at UNC paths like \\FileServer\Shared\Reports\Q4.xlsx are now accessible at HTTPS URLs such as https://company.sharepoint.com/sites/finance/Shared%20Documents/Reports/Q4.xlsx.
What breaks: Every document that contained a hyperlink or OLE reference to a UNC path on the old file server now has a broken link pointing to a location that no longer contains the file.
How ReplaceMagic fixes it: You define a replacement rule that maps the old UNC root (\\FileServer\Shared) to the new SharePoint Online base URL. ReplaceMagic applies this rule across every document in the target library, updating all matching links in a single pass. Microsoft Teams files and OneDrive for Business files are covered by the same native SharePoint integration, so no separate processing step is needed for those locations.
Scenario 2: SharePoint On-Premises to SharePoint Online
What happens: An organization lifts its on-premises SharePoint farm to Microsoft 365. The base URL for every site changes from an intranet format (http://intranet/sites/team) to a cloud format (https://company.sharepoint.com/sites/team).
What breaks: Documents stored on the new SharePoint Online site still contain links formatted with the old intranet URL. These links resolve to a server that is either decommissioned or no longer holds the files.
How ReplaceMagic fixes it: ReplaceMagic connects natively to the SharePoint Online destination, processes every document, and replaces all occurrences of the old intranet base URL with the new cloud URL. Metadata — last-modified date, author, content approval status, and version history — is preserved throughout. Teams channel files and OneDrive for Business files that were migrated from the same on-premises source are handled through the same SharePoint API connection.
Scenario 3: SharePoint Tenant-to-Tenant Migration
What happens: Two organizations merge, or a company restructures its Microsoft 365 tenancy. Documents are migrated from one tenant (company-a.sharepoint.com) to another (company-b.sharepoint.com).
What breaks: Not only does the base URL change, but SharePoint’s internal item IDs — used in organizational links and shared links — are reassigned in the new tenant. ID-based links that worked perfectly in the source tenant are permanently broken in the destination because the IDs no longer correspond to the same documents.
How ReplaceMagic fixes it: ReplaceMagic first converts ID-based SharePoint links to absolute URL format, which is stable across tenant boundaries. It then applies the base URL replacement rule. This two-step approach ensures that even organizational links embedded in documents are repaired correctly after a tenant-to-tenant move.
Scenario 4: SharePoint Farm-to-Farm Migration (On-Premises to On-Premises)
What happens: An organization migrates from one on-premises SharePoint farm to another — due to hardware refresh, data center consolidation, or disaster recovery activation. The web application URL or server hostname changes.
What breaks: All documents containing links to the old farm URL, including cross-site links within documents, have broken references. Wiki pages and navigation items pointing to the old server are also affected.
How ReplaceMagic fixes it: ReplaceMagic connects directly to the new farm and applies find-and-replace rules targeting the old farm hostname or base URL. Processing runs without throttling constraints, allowing higher parallelism and faster completion than a cloud-based migration. Quick Launch and Top Navigation bar URLs can also be updated in the same processing pass.
Scenario 5: SharePoint Online Library Restructuring
What happens: Documents are reorganized within SharePoint Online — moved between site collections, between document libraries, or into new folder hierarchies. This may happen as part of a governance initiative or to align with a new information architecture.
What breaks: Both relative and absolute paths embedded in documents change whenever a file is moved to a different library or site collection. Cross-document links, OLE references, and hyperlinks all break simultaneously.
How ReplaceMagic fixes it: ReplaceMagic scans the affected libraries and constructs replacement rules that reflect the new path structure. Because it processes files in place via the native API, there is no need to download and re-upload the entire library manually. Microsoft Teams and OneDrive for Business files hosted in restructured SharePoint libraries are covered automatically.
Complex Projects: Replacements Preparation Package
For migrations involving multiple simultaneous scenarios — for example, a tenant-to-tenant move combined with a library restructure — ReplaceMagic offers a professional Replacements Preparation Package service. Our team analyzes your source and target environments, maps old paths to new paths, and delivers a ready-to-use replacement ruleset that you can import directly into ReplaceMagic. This eliminates the manual effort of building complex multi-rule configurations and reduces the risk of errors on large, high-stakes migration projects.
