We often have the case where an individual who is part of an existing household goes to the web and creates a new record, in order to make a purchase or donation. To clean this up now, we need a two-step manual process:
1) merge the two individual accounts (one part of the household, the other stand-alone)
2) After the merge completes, move the transactions from the individual to the household.
We are thinking about customizing our merge process to do this automatically, since at this point we expect all transactions to be on the household.
Has anyone tried this, or considered it and rejected it for some reason?
Jane,
We considered it, but decided it was safer to manually move the transactions after the merge. We are a consortium, so there are several invested organizations and we felt it was safer to have someone verify the transactions should be moved. Like you, all transactions should be on the household, but we’re afraid there might be some extenuating circumstances once in a while. I went the route of creating a custom report that is scheduled to run after the weekly merge process that shows accounts with tickets, subscriptions, contributions or history on individual accounts that are affiliated with a household. I have a data integrity person who then manually does the transaction moving. So far the process has been great and really doesn’t take a lot of extra time for the second manual step.
Teresa L. Dean
Tessitura Systems Director
AT&T Performing Arts Center
Right now we do it manually as well - simply because I don't completely trust my own coding skills with v11 and would hate to move something to the wrong household. So far we just manually move 'em which is a slight pain, but I just haven't set aside the time to really dig into something that would make it automatic.
If someone else does it'd be a lovely thing to share! ;)
Heather