Last year, we released enhancements that allow you to copy files in Office 365. Today, we're adding the ability to move files in Office 365 with full fidelity protections for metadata and version ma...
Updated Feb 15, 2018
Version 4.0
Blog Post
itsrajeshid, I totally agree with you. The fact that "Replace" when using "Move to" is different than when using "Upload" is wrong. Users must be able to trust that version history is always kept. Instead, a moved document with the same name as a document at the destination, will result in the destination document being COMPLETELY WIPED AWAY without warning. It does not even go to the recycle bin. This is unexpected and really unfortunate behaviour. We have lost very critical document history from files over 10 years old as users were expecting "Replace" to add the source document "on top" of the current versions from the destination document (just like it does for uploading). Can you imagine if happens with legal documents for which you are required by law to keep intact for X years? It is terrible...
Anyone who agrees that the "Move to" > "Replace" should move current version history "on top" of existing version history, instead of wiping the destination document completely, please go in and upvote my UserVoice item created yesterday: https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration/suggestions/41711827-stop-the-replace-option-for-document-move-to-t
Thanks!