If you must have versioning information included when you move a file from one SharePointlibrary to another, use theMove tocommand.For more details, read on.
Versioning is part of a SharePoint library. The versions and tracking is stored in the SharePoint data itself, and not in the files. Rather than overwrite older files when you check in a new version, SharePoint stores the older files as well as the newer ones, and differentiates between them with version numbers. The files are still separate, and are tracked in the library, but the versions are only in the SharePoint library.
File Explorer works with files which contain only the metadata that's needed for that single file, such as modified date or author. When you copy using File Explorer, it can only copy or move files and their immediate info. The additional information and other files in SharePointaren't included.
If you're using SharePoint, the Move to command does move the versioning history, as it is working inside the library. Move to retains versioning because only one copy of the file and structure exists. When SharePointmoves a file between folders or libraries with Move to, it includes versions and tracking information.
The SharePointCopy to command, however, only copies the latest file. This prevents splitting the history between two locations. You can make updates to either file, but the changes are only reflected on that file.
If you're copying files to keep a backup, and want to preserve the versioning, consider using a SharePointserver based backup rather than manually copying. That way if something happens to your current files, the backup of SharePointcan be retrieved. SeeBest practices for backing up and restoring in SharePoint Server.
