Convert to Household/Move Transactions

So I'll weigh in here - we don't have any fully written standards yet, but the thing to look at/think about is if any of the individual accounts have non-transactional information on them. You'll want to look at tabs like: Constituencies, Relationships, Research, Attributes, History, Connections, and Custom. Any information on these tabs will *not* move with the Move Transactions functionality.

So when you are looking at accounts you have to make a judgement call about whether that particular account has information that is best left on the individual or if it can be 'household' owned information. How much information is on the current individual account? If they are a basic account with just transaction info then it won't matter much if you do a convert to household or create a new household account and move the transactions up to it.

Where you run into trouble is when you have accounts with a lot of non-transaction historical information - then you have to ask yourself where should that information live? Is it stuff that is directly related to the individual (like a school or employment affiliation) or is it information you'd be happy to live on the household like a customer service CSI?

I've often found that the information is split - some wants to live on the individual and some on the household. This requires me to do some back-end canoodling unfortunately. (Shhh) In my ideal pony world we could move information around from any tab similar to the email moving functionality. (She says as she hides from the Tessi developers)

So that's my 2 (or more) cents. 

Heather

Unknown said:

I wish that it was as easy to move constituencies, attributes, postal addresses, and other such information among members of a household the way you can move eaddresses…

I agree: the "transfer owner" button would be very handy to have under all the radio buttons under Contact Details, as well as Attributes, Consts, Relationships; basically almost anywhere that the "group by constituent" functionality exists.

I've been meaning to post this little bit of list SQL - and this thread seems like a good place. This is only useful if your business rules are to push all transactions to the household and you want to check to find people where this hasn't happened. (This could be the result of a merge or someone forgetting to move transactions to household when affiliating them to a household account)

I put this SQL in a list via manual edit - it looks for anyone who is in a household but has orders or contributions still on their account (it doesn't check for everything, but these are the big guns for us).

Then I scheduled the 'Generate a List' report which is mailed to my box office who goes through and checks the accounts and cleans them up. It helps keeps our data consistent so we don't have random orders on an A1 or A2 until we actually WANT them there in later Tessi versions.

Anywho - just in case it is useful to someone out there!

select distinct(ch.customer_no)

from

(SELECT distinct(customer_no) from V_CUSTOMER_WITH_PRIMARY_AFFILIATES 

where name_ind in (-1,-2)

and cust_type = 1 ) as ch

JOIN dbo.T_ORDER o on ch.customer_no = o.customer_no

UNION

select distinct(ch.customer_no)

from

(SELECT distinct(customer_no) from V_CUSTOMER_WITH_PRIMARY_AFFILIATES 

where name_ind in (-1,-2)

and cust_type = 1 ) as ch

JOIN dbo.T_CONTRIBUTION c on ch.customer_no = c.customer_no

Just to second what Heather was saying earlier - we've actually stopped "Converting to Household" because we have a lot of non-transactional data on individuals (attributes, interests, emails, etc etc). It is so easy to create a new household that making a household and filling it with people has not been an issue. If transferring details between affiliates was more readily available (and more than just eaddresses), we might change our tune. But for now, no "Convert to Household" allowed.

Another thing we've noticed with Move Transactions though is that history/activities and history/events do not move to the household, either. It hasn't negatively impacted us as of yet, but it might for some.  Also had a little trouble initially with how our custom reports pull benevolent (donated) seats. They also continue to exist on the individual in the database table.

Also, like Heather, we have a dynamic list that pulls households that need transactions moved - though we did it without custom SQL. (Though the custom is more comprehensive, most likely).

Tickets - Season In (all seasons selected)
Constituent Type In Individual
Relationship Type In Adult Member
OR
Contribution Amount >= $1.00
Constituent Type In Individual
Relationship Type In Adult Member 

-------------
Beth

Hi Heather,

We just went live on v11 today.  I copied your SQL query and setup a list.  Do you find a high number of accounts on a regular basis where ticket history needs to be moved to the household?  I'm just wondering how prevalent of an issue we can expect this to be. 

Thanks,

Chuck

Charles,

We went through the same thing when we converted to V11.  From our experience, once you get things cleaned up initially, you shouldn't see that many records on an ongoing basis.  We also have a custom report running to check for this situation (Individuals affiliated to a household who still have some kind of transactional history on their record) but the only time someone new pops up is if an existing individual with history is affiliated to a household and someone missed the step of moving transactions.  Since that circumstance is against our business rules we want to know about it quickly.  But the actual number of records after initial cleanup has been pretty low.

Hi Levi,

Thank you for the feedback.  We are also adding this as a business rule in merges but it will be helpful to keep a watch for accounts that slip through the process (hopefully not many).

Hey Chuck -

The biggest place we see this issue is when merging accounts. I'm working on adding something to my custom merge tab, but haven't finished it yet.

For normal day-to-day stuff we rarely see them. As Levi says, it is only if someone forgets and that is few and far between. We run the list once a week to check and usually it is blank.

HTH,

Heather

Unknown said:

[...] my custom merge tab, [...]

You have a custom merge tab? As person that works on and thinks about merges a lot, this sounds interesting to me. Please describe, and - sorry if you did that at some point and I missed it!

Erg. Sorry, mis-typed. Should have said customized merge procedure. Nothing special - just tweaks and twonks related to our business practices trying to make our merged accounts needing as little actual manual massaging/cleanup as possible.

Didn't mean to get your hopes up!