Move member from one parent to another without impacting historical data
It is my understanding that the best practice to move members from one parent to another without impacting historical data is to create a new member under the new parent and retire the old member.
There are callouts around following this practice as this would create a very large amount of members as time continues, making the FCCS dimension editor harder to manage. As well as the example of moving a member to a different parent, a year from now the need to move it back. Essentially would create 3 of the same members but in different locations within the hierarchy. This would involve remapping, renaming, and training users on updated adhocs to select the correct member after the multiple moves.