How to Move Files in SharePoint: Methods, Gotchas, and What to Know First
Moving files in SharePoint sounds straightforward — and often it is. But depending on how your organization has set up SharePoint, which version you're using, and where you're moving files to, the experience can vary quite a bit. Here's what's actually happening under the hood, and how to do it correctly so you don't lose metadata, break links, or confuse your colleagues.
What "Moving" a File Actually Does in SharePoint
Unlike a simple drag-and-drop on your desktop, moving a file in SharePoint involves more than just relocating bytes. SharePoint files carry metadata — properties like who created the file, when it was modified, what version it's on, and any custom columns your library uses. How much of that survives a move depends entirely on how you move it.
There are also shared links to consider. If someone has a direct link to a file and you move that file to a different library or site, that link may break. SharePoint handles this better within the same site collection, but cross-site moves are a different story.
Understanding this upfront saves a lot of cleanup work later.
The Main Methods for Moving Files in SharePoint
Method 1: Move To (The Recommended Built-In Option)
SharePoint's native "Move to" command is the cleanest option for most users. It preserves version history and metadata when moving within the same site or site collection.
How to use it:
- Navigate to the document library containing your file
- Hover over the file and check the checkbox that appears to the left
- Click the three-dot menu (⋯) or right-click the file
- Select "Move to"
- Choose your destination — another folder, library, or site — from the panel that appears
- Click "Move here"
📁 This method keeps the version history intact when moving between libraries on the same site. When moving to a different site collection, version history is typically not carried over — only the current version moves.
Method 2: Drag and Drop
You can drag files between folders within the same document library. This works well for simple reorganization within one library, but it has limitations:
- No cross-library drag and drop in the browser interface
- Metadata and version history behavior varies depending on destination
- Easy to accidentally drop files in the wrong folder, especially with deep nested structures
Drag and drop is fine for quick folder tidying. For anything more significant, use "Move to."
Method 3: Using File Explorer (Synced Libraries via OneDrive)
If you've synced your SharePoint library to your local machine using the OneDrive sync client, you can move files through Windows File Explorer or macOS Finder just like any other folder on your computer.
This approach feels familiar and works well, but carries some caveats:
- Sync has to be fully up to date — moving a file that hasn't finished syncing can cause conflicts
- Large moves (hundreds of files) can take time and may occasionally stall
- Cross-library moves via File Explorer may not preserve SharePoint-specific metadata columns
Method 4: SharePoint Admin or Power User Tools
For bulk moves or migrations between site collections, tools like SharePoint Migration Tool (SPMT), SharePoint Designer, or third-party migration utilities are better suited. These are typically used by IT administrators rather than everyday users.
Microsoft 365 admin tools can also manage large-scale file moves while preserving more metadata — but this falls outside typical end-user territory.
Key Variables That Affect Your Move
Not every move is equal. Here are the factors that determine what actually happens:
| Factor | Why It Matters |
|---|---|
| Same library vs. different library | Version history usually preserved within same library, less so across libraries |
| Same site vs. different site collection | Cross-site moves often strip version history and may break shared links |
| File size and quantity | Large or numerous files slow down browser-based moves; sync client handles these better |
| Custom metadata columns | May not transfer if the destination library doesn't have matching columns configured |
| Active shared links | Links may break if file moves to a new location, especially cross-site |
| Permissions | Moving a file doesn't automatically move unique permissions set on it |
What Happens to Shared Links After a Move
This catches a lot of people off guard. 🔗
If a file has been shared via a direct link and you move it:
- Within the same library or site: SharePoint usually redirects the old link automatically
- Across site collections: The original link will likely break, and anyone using it will hit a "file not found" error
If your file has been widely shared — in emails, Teams messages, or embedded in other pages — note those links before moving and consider notifying recipients afterward.
Moving Files in SharePoint Mobile or Teams
If you're working through the SharePoint mobile app or accessing files through Microsoft Teams, the "Move" option is available but more limited in where it lets you navigate. The Teams interface in particular focuses on the libraries associated with that specific team, so cross-site moves typically require switching to the browser version of SharePoint.
Factors That Depend on Your Specific Setup
Whether a move is simple or complicated depends heavily on:
- How your organization has structured its sites and libraries — some companies have dozens of site collections; others keep everything in one
- What permissions you have — you need write access to both the source and destination
- Whether custom content types or metadata are in use — highly structured libraries require more care
- Your SharePoint version — Microsoft 365 (SharePoint Online) behaves differently from older on-premises SharePoint 2019 or 2016 installations
- Whether files are checked out — checked-out files can't be moved until checked back in
A move that takes 10 seconds in one organization's SharePoint environment might require IT involvement in another.