How to Move SharePoint Files Without Breaking Sharing Links
Question details
The user needs to move files across different SharePoint sites while ensuring that all existing sharing links remain functional for external applications.

- Product
- SharePoint
- Device & OS
- not provided
- Scenario
- Migrating documents or reorganizing folders between SharePoint sites where existing links are actively used in external systems like Qualio and Jira.
- Observed behavior
- Moving files to a new site changes their URLs, which breaks the original sharing links and causes integrations to fail or users to lose access.
Before initiating any large-scale file migration, audit your currently shared documents and create a backup list of critical external links used in workflows (such as Jira or Qualio) to verify them after the move.
Use a Migration or Link-Management Tool
Since standard SharePoint features do not guarantee link preservation for bulk file moves, using a specialized link-management tool is the most reliable method.
Moving entire folders or multiple documents between sites will change their underlying URLs. To keep integrations intact, a third-party migration or link-management tool (such as LFA or ShareGate) is highly recommended. These tools can automatically map old URLs to new destinations or maintain link integrity during the transfer.
Evaluate and install a SharePoint-compatible migration tool that explicitly supports link preservation or URL redirection.
Set up your source and destination sites within the tool, ensuring you enable settings that preserve sharing permissions and map existing links.
Run a pilot migration with a small batch of files. Click the original links from external apps like Jira to confirm they successfully route to the new file location.
Once verified, proceed with moving the remaining files and folders. Always perform a post-migration link audit.

Use Native SharePoint Options for Individual Files
For moving a small number of individual files, SharePoint's native move feature offers a checkbox that can help preserve sharing permissions.
Develop a Custom Power Automate Flow
If third-party tools are not an option, you can create a custom Microsoft Power Automate workflow to handle URL redirection and permission mapping.
Looking for a Simpler Document Management Alternative?
If navigating complex SharePoint permissions and broken links is slowing down your workflow, consider using WPS Office. It provides a highly compatible, easy-to-use alternative for managing, editing, and sharing documents seamlessly.
- 1. Install WPS Office: Download and install the free WPS Office suite on your device.
- 2. Save to WPS Cloud: Open your document and save it directly to WPS Cloud for secure, centralized storage.
- 3. Generate a permanent link: Click the 'Share' button to generate a stable collaboration link that remains intact even if you reorganize your cloud folders.

Frequently Asked Questions
Why do SharePoint sharing links break when files are moved?
Moving a file across different SharePoint sites changes its physical URL path. Unless specifically redirected by a migration tool, the old sharing link still points to the previous location, resulting in a 404 'File Not Found' error for users or integrated apps.
Does the 'Keep sharing with the same people' option work for folders?
The native 'Keep sharing with the same people' feature is generally effective for preserving user access on individual files, but it does not reliably preserve all permissions or functional URLs when moving bulk files or entire folders.
Will copying files instead of moving them preserve the links?
Copying files creates an entirely new version in the destination site with a new URL. The original links will still point to the original files in the source site. If you delete the source files after copying, the original links will break.
How can I test if my SharePoint links survived the migration?
Before deleting any source files or finalizing a migration, manually click the existing external links from your applications (like Qualio or Jira) to verify they successfully redirect to the new document location.




