Four practical paths exist for moving or copying files between SharePoint Online sites. Each makes a different trade-off between ease of use, bulk capability, and metadata fidelity.
| Method | Bulk support | Metadata preserved | Version history | Cross-tenant | Skill needed |
|---|---|---|---|---|---|
| SharePoint native Move To / Copy To | No | Within site only | Within site only | No | None |
| SharePoint admin centre site move | Site-level only | Yes | Yes | No | Low (admin UI) |
| PnP PowerShell | Yes | Yes (configurable) | Yes (configurable) | No | High (scripting) |
| ShareMaster Copy To / Move To | Yes | Yes | Yes | No | Low (GUI) |
Cross-tenant migration (moving content between entirely separate Microsoft 365 tenants) is a distinct scenario not covered by any of the methods above. For that, see the cross-tenant migration tools comparison.
Method 1: SharePoint native Move To and Copy To
SharePoint Online's modern file browser includes Move To and Copy To commands accessible by selecting a file or folder and clicking the toolbar command, or via the right-click context menu. No setup or licensing is required beyond your Microsoft 365 subscription.
What it does well
- Available immediately in any modern SharePoint experience, no installation needed.
- Supports moving files to any library in the same tenant, including across site collections.
- Within the same site collection, version history and metadata (Created By, Modified By, dates) are preserved.
- Works for any user with Contribute or Edit access to the destination library.
Where it falls short
- No bulk operation beyond what is visible on the current screen. Moving thousands of files is not practical through the browser interface.
- When moving across site collection boundaries, created date and modified date metadata may be reset to the transfer date and the moving user's account.
- No resume capability. A failed partial transfer leaves you with no progress record and no way to continue from where it stopped.
- Not scriptable through a supported command-line equivalent that replicates the same metadata preservation behaviour.
Method 2: SharePoint admin centre site move
The SharePoint admin centre includes a site move feature that lets administrators relocate an entire site collection to a different URL within the same tenant. This is a site-level operation, not a file-level one.
Because the admin centre move relocates the whole site object rather than copying individual files, it preserves all content, metadata, permissions, and version history. The operation runs as a background job and is tracked in the admin centre. The constraint is that it is all-or-nothing: you cannot use it to move a specific library from Site A to Site B while leaving the rest of Site A in place. It is the right tool only when you need to reorganise site URLs, not when you need to selectively move content between sites.
Method 3: PnP PowerShell
PnP PowerShell provides Move-PnPFile and Copy-PnPFile commands that can move files between sites and site collections within the same Microsoft 365 tenant. These commands accept parameters that control whether metadata and version history are preserved.
Strengths of the PowerShell approach
- Handles bulk operations: a loop over a list of file paths is easy to write.
- Highly configurable through parameters (overwrite behaviour, metadata preservation, version carry).
- No additional licensing cost beyond Microsoft 365.
- Integrates with automation pipelines, scheduled tasks, and larger admin scripts.
Challenges
- Requires PowerShell authoring skill and familiarity with the PnP module's API to write correctly. A script that does not explicitly request metadata preservation will silently drop it.
- Error handling, retry logic, and throttle management (HTTP 429 responses from SharePoint) must be coded manually. Without them, a large transfer can fail partway through with no clear recovery path.
- No GUI progress view. You work from console output or log files, which makes status reporting to stakeholders awkward.
- PnP module updates occasionally introduce breaking changes that require script maintenance.
Method 4: ShareMaster Copy To and Move To
ShareMaster's Copy To and Move To tools are designed for within-tenant file and library moves where metadata fidelity and reliability on large file sets matter. Connect to SharePoint Online, browse the source and destination, configure what to carry across, and run the transfer as a managed job.
The key differentiator from the native browser experience is resume safety. If the transfer is interrupted - by a network drop, a SharePoint throttle window, or a system restart - it picks up from where it stopped rather than starting over. On transfers of tens of thousands of files, that is not a nice-to-have: restarting from zero is not a recovery plan.
For scenarios involving full-site moves or transfers between separate Microsoft 365 tenants, Clone Master handles the complete migration including site structure, content types, permissions, and version history.
Decision matrix: which method for which scenario?
| Scenario | Recommended method | Reason |
|---|---|---|
| Move 5 to 20 files, same site collection, metadata not critical | Native Move To | No setup required; metadata is preserved within the site collection |
| Reorganise a site's URL without changing its content | SharePoint admin centre site move | Moves the whole site object cleanly; no file-by-file work needed |
| Scripted bulk move, integrated into an existing automation workflow | PnP PowerShell | Flexible, scriptable, no additional tooling license |
| Bulk move libraries or thousands of files across site collections, with metadata and version history preserved | ShareMaster Copy To / Move To | GUI-driven, resume-safe, no scripting required, handles throttling automatically |
| Move a full site or migrate content between separate Microsoft 365 tenants | ShareMaster Clone Master | Designed for full-site and cross-tenant scenarios, carries permissions and structure |
Frequently Asked Questions
Does SharePoint preserve metadata when moving files between sites?
It depends on the method. Native Move To preserves metadata within the same site collection but may reset created and modified dates when crossing site collection boundaries. ShareMaster's Copy To and Move To are built to preserve metadata during within-tenant moves.
Can you move files between different Microsoft 365 tenants?
None of the native SharePoint tools support cross-tenant transfers. Cross-tenant migration requires a purpose-built tool. ShareMaster's Clone Master handles full cross-tenant migrations of sites, libraries, files, and permissions between separate Microsoft 365 tenants.
What happens to version history during a file move?
Native Move To preserves version history within the same site collection. Across different site collections, version history preservation depends on the tool used. PnP PowerShell and ShareMaster's tools include options to carry version history as part of the operation. See the version history trim guide if you want to reduce version count before moving large file sets.
What is the difference between Copy To and Move To?
Copy To leaves the original file in place and creates a copy at the destination. Move To removes the file from the source after writing it to the destination. Both commands are available in the native SharePoint browser experience and in ShareMaster's tools.