The Move command is expected to retain the versions. The Copy command will create a new file at the destination with no versions.
I can't answer why you didn't get all versions, though.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I recently ran into a situation where I was moving an excel file (1.5MB) that had about 800 versions. I used the SharePoint Online Move To command to move it to another site collection's document library. What I noticed is that when the file showed up at the target site collection it was as the original first version of the file and over time, more recent versions of the file became available (I was simply watching the version history to see the file version increment). More concerning was that when I opened the target version, the content was the old content (in this case I was missing all of the 2020 updates to the sheet since the last version moved was dated 12/26/2019). I've escalated this to MS but not sure if others have also seen this or not.
The Move command is expected to retain the versions. The Copy command will create a new file at the destination with no versions.
I can't answer why you didn't get all versions, though.
Whether all versions of your file been restored until now?
I think due to your file has more than 800 versions, so when your file is moved, the version will be restored slowly.
You could open a service request with Microsoft for further help.
I am finding that this happens when I move the file to a location with a deeper file structure (i.e., buried under more folders). I suspect I'm running into the URL character limitation, which must include some additional characters for the version history/metadata. Try moving the file first to a primary folder and see if that helps. Good luck! (My staff don't listen when I ask them to minimize characters and especially spaces!)