Skip to main content

Move and Copy

Move to and Copy to are the built-in SharePoint commands for relocating and duplicating files, folders, and items between folders, libraries, and even different sites. The crucial difference is version handling: Move to carries the document's full version history to the destination, while Copy to creates a fresh copy that includes only the latest version. Used well, these commands let you restructure libraries, archive completed work, and distribute templates without third-party tools or manual downloads and uploads.
Related Features
Folder, Metadata, Recycle Bin, Version History

Common Use Cases

  • Library reorganizations: move files into a cleaner folder or library structure as a site matures
  • Archiving completed projects: move finished documents to an archive library or site while preserving their full history
  • Template distribution: copy a master template into project sites so each team starts from the same baseline
  • Departmental handoffs: move a document from a working library to the official records library once it is finalized
  • Site consolidations: relocate content from retired sites into the sites that replace them
  • Working copies: copy a published document into a draft area to rework it without touching the original

Benefits

  • Version history preserved on move: Move to carries the complete version history, keeping audit trails intact
  • No download and re-upload: content travels between libraries and sites directly in the browser
  • Cross-site reach: files can be relocated to other sites and even to OneDrive, not just within the current library
  • Clean duplication: Copy to produces a tidy single-version copy, ideal for templates and working drafts
  • Folder-level operations: entire folder structures move or copy in one action
  • Built in: everyday restructuring needs no migration tools or scripts

How It Works

  • Choose a destination: both commands open a destination picker covering the current library, other libraries, other sites, and OneDrive
  • Move transfers the original: after a move, the file lives only at the destination, with its full version history intact
  • Copy creates a sibling: after a copy, two independent files exist, and changes to one never affect the other
  • Metadata comes along: column values are kept when the destination has matching columns to receive them
  • Folders work too: moving or copying a folder brings its contents along in one operation

Limits and Nuances

  • 500 MB per copy: Microsoft documents that you can copy up to 500 MB of files and folders at one time
  • Copy takes only the latest version: earlier versions must be restored and copied one at a time if they are needed at the destination
  • Moved files linger in the source recycle bin: after a move completes, the file remains in the source site’s recycle bin on its normal recycle schedule
  • Unsupported columns lose values: when the destination lacks a column from the source, the information in that column does not carry over
  • Managed metadata depends on the term store: managed metadata values carry over only when source and destination use the same term store
  • Enforced unique values can block moves: a move across libraries fails when the destination enforces unique values on a column
  • Site Pages are different: the Move to option is not available on the Site Pages library
  • Cross-site availability is configurable: if other sites do not appear as destinations, the organization has moving and copying across sites turned off

Common Questions About Move and Copy in SharePoint

What is the difference between Move to and Copy to in SharePoint?

Move to relocates a file so it exists only at the destination, and it brings the document’s full version history along. Copy to creates an independent duplicate that contains only the latest version, leaving the original untouched. Choose Move when restructuring or archiving and Copy when you want a starting point you can change freely.

Does moving a file keep its version history?

Yes. When you use Move to, the history of the document travels to the new destination, so every prior version remains available there. This is the key reason Move to is the right command for archiving and reorganizing official documents, where the trail of who changed what and when needs to stay intact.

Why does my copied file have only one version?

That is by design. Copy to brings only the latest version of a document, which keeps the full history in a single authoritative place instead of splitting it across locations. If you genuinely need earlier versions at the destination, each one has to be restored as the current version and copied separately.

Can I move files between different SharePoint sites?

Yes, the destination picker includes other sites and OneDrive in addition to libraries on the current site. If other sites do not appear, the organization has moving and copying across sites turned off, which an administrator can change. A move across libraries can also fail when the destination enforces unique values on a column.

What happens to metadata when I move or copy a file?

Column values carry over when the destination has matching columns. If the destination lacks a column from the source, the information in that column is not retained, so it pays to align library columns before a big move. Managed metadata values carry over only when both locations use the same term store.

How should I plan a large library reorganization?

Start with the structure you want: libraries, folders, metadata, and permissions. Then move content into it in planned batches, verifying version history and column values as you go. Greg Zelfond, the SharePoint consultant behind LookBook 365, designs and builds document management structures entirely out of the box, so reorganizations like this land cleanly the first time.