Tracking/ Storing Archived Data

​@marie.krueger - hi - I am sorry you are running into this. I used to run into this more in another life, but I will offer some advice.

A question - anyway you can preserve their original account and not transform it as it goes from one business unit to the next? An option B - can you tranform that original account and not add another and then move it? Essentially “rename” it?

At a high level, transforming identities in any system forces merge operations and almost invariably make for a type of conflict. Even with clever tools like Merge User being supported, there are corners to it - and you called out one of them. Archiving enrollments came after the merge user operation - so I can see where this can feel like an oversight.

Going one step further, we have a use case where agency workers become employees. This drives us to bring them into another branch and essentially transform their identity. It forces a Merge User operation but with the wrong timing in the year, we can land up mapping people to another version of the same training = a hot mess.

It is not the same situation as yours. But worse? Is when the same email address is being used and both accounts are left active in error. We have found in certain situations, that the system will not fire off a notification to a person IF they have the same email address in two accounts...sigh another hot mess - all related to this transformation of identity.