How to Move Documents Between SharePoint Libraries
Reorganising content is sometimes necessary. Moving files between libraries (correctly) preserves history and keeps the team functional.
What it is
Moving documents between libraries — or between sites — happens for legitimate reasons: a project closes and content moves to archive; content was uploaded to the wrong library and needs to relocate; an org restructure means a department’s content moves to a new site. SharePoint has built-in move and copy functions that handle this without losing version history (in most cases) or breaking permissions structurally.
The catch is that moving content can break things downstream: links in emails, references in documents, bookmarks people have saved, integrations with other systems. The move itself is fine; the broken connections are the problem. Plan moves carefully and communicate them clearly.
For small moves (a few files), use the built-in Move to command. For larger moves (hundreds or thousands of files), consider migration tools that handle metadata and links more reliably. Avoid drag-and-drop between libraries when you can — it sometimes copies rather than moves, and the resulting orphan copies cause confusion.
When to use this
- When content was uploaded to the wrong library and needs to be in the right place.
- When a project closes and you’re moving content to an archive library.
- When you’re reorganising a site and content needs to redistribute.
- When merging or splitting libraries to align with a new structure.
How to do it
- Confirm the target library exists and is configured (permissions, versioning, metadata).
- Select the file(s) in the source library.
- Use Move to in the toolbar.
- Choose the destination (different library, folder, or site).
- Confirm the move — SharePoint preserves version history when moving within the same site.
- Check that metadata is intact — some columns may not exist in the destination.
- Update any external references (links in emails, wiki entries, bookmarks).
- Notify users of the new location.
Best practices
- Prefer Move over Copy. Move keeps version history; copy creates duplicates.
- Update navigation and links after moving. Broken links are the most common post-move complaint.
- Move in batches and verify. 50 files, check results, repeat. Don’t move 5,000 in one go without testing.
- Document the move. Record what moved where and when, so you can answer ‘what happened to that file?’ later.
Common mistakes
- Drag-and-drop between libraries. Sometimes copies, sometimes moves. Use the Move To command instead — it’s deterministic.
- Moving content without warning users. Their bookmarks break, they panic, they recreate copies. Communicate first.
- Constant reshuffling. If you’re moving content every quarter, your structure is the problem, not the content.
The File Sanity Kit gives you the Container Method™ — audit, restructure, and future-proof SharePoint without IT admin. The complete methodology, full workbook, and 8-tab Excel planner.
Get the File Sanity Kit — $27 →FAQ
How do I move files between SharePoint libraries?
Select the files in the source library, click Move to from the toolbar. Pick the destination library (any library you have edit access to, in the same tenant). Click Move. Version History travels with the files; permissions reset to inherit from the destination library.
Does moving SharePoint files preserve version history?
Yes — Move (not Copy) preserves the file’s complete version history, including who edited what and when. This is one of the most underused features in SharePoint — many teams Copy when they should Move, ending up with duplicates and broken audit trails. Default to Move unless you genuinely need two copies.
What happens to SharePoint sharing when I move a file?
Sharing links to the original location continue to work — they redirect to the new location automatically. Permissions reset to inherit from the destination library, which may broaden or narrow access. After moving sensitive files, review Manage Access to confirm the new permissions match the intended audience.
Can I move files between SharePoint sites?
Yes — Move to works across libraries on the same site, across sites in the same tenant, and (with some limits) across tenants. Cross-tenant moves use the SharePoint Migration Tool or Mover. Within a tenant, Move to handles most cases cleanly while preserving history.