How to Handle Inactive Users for v12 Worker Migration

Good morning Tessiturians!

Like many of you out there we're going through the steps to Map our current Tessitura Users with their Consituent IDs and assigned Worker Types for the v12 Upgrade.  Our Team has come back with some questions regarding mapping inactive or deceased users and I thought I'd check in with the community to see how other organizations are handling this.

One option that was floated out was that we not map these users and simply inactivate the constituent records that are created as a result of the upgrade.

Personally, I don't see why we wouldn't map them but perhaps there's a reason that I just can't see.  How did or are your organizations handling these inactive users?


Thanks!
Short 

Parents Reply Children
No Data