KB39274: Object modification timestamp is not preserved during migration when the option "Preserve object modification timestamp during migration" is enabled in MicroStrategy Object Manager 10.x

SYMPTOM:
In Strategy Object Manager 10.x, object modification timestamp is not preserved during migration when the option "Preserve object modification timestamp during migration" is enabled. This behavior is observed both during regular Strategy Object Manager 10.x migrations as well as with packages.
STEPS TO REPRODUCE:
Follow the steps below to reproduce the issue with Strategy Tutorial project:

• In Strategy Object Manager, enable the option "Preserve object modification timestamp during migration", as shown below: 

• In Strategy Developer, create a folder and create any objects such as reports, folders and filters in this folder.  
• Copy the folder created at step 2 and pastes it into another project.
• The timestamp of copied folder shows current timestamp instead of its modification timestamp, as shown below:
  Source Project:
  

• Destination Project:
  

 
CAUSE:
The behavior is expected, because in the whole process, the children of the folder are copied after the folder gets copied. So the folder is "touched" and the timestamp/version get changed. 
What happens in this use-case is as under: 
 - First the folder gets migrated = Time stamp is preserved 
 - Next the children get migrated = Time stamp is preserved 
 - Lastly, folder gets touched again = Time stamp changed since the folder is not copied but modified within the MD..since this was not a migration. 
ACTION:
Replace the object after the migration using Strategy Project Comparison tool to show consistent modification timestamp.