Hi gabrielav2004072 ,
The below was posted by someone in this forum. Not able to get hold of that post. Content as below:
"The "_msm_moved" is created when the a rollout action is triggered and content is being rolled out to a livecopy where an identically named resource is located and that resource is identified as being detached.
A relationship is determined to exist between a resource in the livecopy and a resource is in the blueprint by a mixin type on the livecopy resource called cq:LiveRelationship. If that mixin type is not present the assumption is that that content was created directly in the livecopy or there was a desire to treat that resource like it was created directly in the livecopy and a detach command was executed on the resource through the MSM Control panel.
When a rollout is triggered for that blueprint resource, the application understands that it's being told to put this new content into that livecopy, however, since the mixin doesn't exist it doesn't know how to handle that existing resource, so it renames it and puts the current blueprint resource in it's place.
The interesting thing with your problem is that new resource should have that mixin applied as soon as the rollout takes place. The fact that you have so many of these instances would seem that either there is a rollout configuration in place that is preventing this mixin being applied to this resource OR you have some secondary process in place that is removing the mixin for that resource after the fact.
I would check your Rollout Configurations, any automated workflows or processes that are focused on that path"
