Fix Errors Moving OneNote Files Between SharePoint Libraries
Question details
The user is unable to move OneNote files between folders or document libraries in SharePoint, although copying the exact same files works without issues.

- Product
- Microsoft SharePoint
- Device & OS
- not provided
- Scenario
- Attempting to organize or migrate existing OneNote notebooks across different SharePoint document libraries or folders.
- Observed behavior
- SharePoint prevents the move operation from completing, either throwing an error or failing silently, while the copy operation succeeds.
Ensure you have Site Owner or Full Control permissions on both the source and destination SharePoint libraries to modify settings and successfully move files.
Use the Copy and Delete Workaround
Since copying works when moving fails, manually copying the notebook and then deleting the original is the safest and fastest immediate solution.
Select the OneNote file in the source SharePoint library, click 'Copy to' from the top command bar, and choose your destination library.
Navigate to the destination library and open the copied OneNote notebook in the browser to ensure all sections and pages have synced correctly.
Return to the source library, select the original OneNote file, and click 'Delete' to remove it, effectively completing the manual move process.

Verify Versioning Settings and Workflows
Mismatched configurations or active workflows between the source and destination libraries can block file movements.
Experience Hassle-Free Document Management with WPS Office
Tired of complex SharePoint library settings and file syncing errors? Switch to WPS Office. It provides a lightweight, unified workspace for your documents, spreadsheets, and presentations, complete with seamless cloud storage integration and high compatibility with standard file formats.

Frequently Asked Questions
Why can I copy but not move files in SharePoint?
Moving a file in SharePoint is essentially a copy-and-delete operation that also attempts to preserve version history and metadata. If the destination library has conflicting versioning rules, required columns, or if a retention policy locks the source file, the move operation will fail, whereas a simple copy (which creates a brand-new file without history) will succeed.
Does the SharePoint REST API bypass UI move errors?
Sometimes. If the issue is caused by a frontend browser glitch or a timeout in the modern SharePoint interface, using the REST API or PowerShell to move the file might succeed. However, backend permission conflicts or structural mismatches will still block the API.
Is there a tenant-level setting blocking OneNote file moves?
There is no specific tenant-wide toggle just for moving OneNote files. However, tenant-wide retention policies, eDiscovery holds, or customized Information Rights Management (IRM) settings can prevent files from being deleted from their source locations, which effectively breaks the 'move' action.




