• Replies 3 replies
  • Subscribers 336 subscribers
  • Views 34 views
  • Users 0 members are here
Related

How to Handle Inactive Users for v12 Worker Migration

Christopher Short
$organization

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 

  • $organization

    Hi -

    We mapped all of ours, deceased/inactive or not if they were used in the system as a solicitor on a solicitation. This was really just so we had historic knowledge that they were at one time a host or solicitor for our organization. 

    We've found it helpful in a couple of cases of recently deceased board members because we can look at their portfolio over the last few years and see who they interacted with and make sure that we had a good transition to someone else.

    Now, we didn't have a huge amount of people to map - maybe 50 or so total so this didn't take me too much time.

    HTH,

    Heather

  • $organization

    Hi Christopher,

     

    We focused primarily on active users. One reason for that was due to limited time to get it done.  Also, I wasn’t too concerned about whether old solicitors were mapped to existing constituents as the reality is that was just there for historical purposes – and a few new constituents for old/inactive workers didn’t bother us either.  We have now been live on v12 since early January and have not had any issues or complications with that approach, at least not that we’re aware of currently.

     

    There may be some pros/cons I am not thinking of that others may point out, but I think mapping of inactive users is just a matter of preference; I don’t think you’ll find any major difference in terms of using v12 with either approach.

     

    I hope that is helpful.

     

    Thanks,

    David

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Christopher Short
    Sent: Wednesday, February 12, 2014 11:58 AM
    To: David Frederick
    Subject: [Tessitura Technical Forum] 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 




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

  • $organization

    Thank you, both!

    I talked this through with our team and I think we're going to move forward and map everyone.

     

    Cheers!
    Short