Forum Discussion
Document not retaining version history on Move To
I've added new document libraries to my sharepoint site to effectively use as "Archives". The problem I am facing is when i move files to my "Archive", which resides in the same SharePoint site all of the metadata changes in previous versions are pushed to the top (the latest version) whether it's a draft or published version it doesn't matter everything is pushed to the top. How can I avoid this? The structure of the document libraries are identical. I have the same versioning settings and advanced settings and both are using the exact same content type.
This is known behaviour with SharePoint and your use case is a very common one, particularly where you are using SharePoint as a document management system. The only solution that I am aware of is to build a flow in power automate that would have the the following send an http request action. It will move the document to the specified library & folder and retain the versions.
Rob
Los Gallardos
Microsoft Power Automate Community Super User.
Principal Consultant, SharePoint and Power Platform WSP Global (and classic 1967 Morris Traveller driver)Hi davidlongswe
The “Move To” feature in modern SharePoint Online doesn’t perform a true move. Instead, it copies the file to the destination library and then deletes it from the source library. As a result, version history isn’t retained during the process.To preserve version history, you might consider using Power Automate to create a custom flow for moving files, or alternatively, use PowerShell for more control over the transfer.
