How to "force" only associations during V11 Constituent Migration

Thanks.

Do you know when the determination of Like to Like is made.  Before or after the accounts with N1 and N2 are broken up.  See my further comments in this thread.

You mentioned:

“The only thing you can do is make sure your current associations won't migrate to one of the unlike type pairs.”

How is this controlled?  I thought that the unlike pairs would become an affiliation and that was out of our control.

--Tom

From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Heather Kraft
Sent: Friday, November 18, 2011 4:32 PM
To: Thomas Brown
Subject: Re: [Tessitura Next Generation Forum] How to "force" only associations during V11 Constituent Migration

Tom -

It's my understanding that you can't force a pair to be only association because the association/affiliation determination is completely dependent on the type of the two accounts it is linking.

The means like type to like type (e.g. individual to individual, corporate/household to corporate/household) will always be an association and unlike type to unlike type (e.g. individual to corporate/household) will be an affiliation. There's no getting around that. The only thing you can do is make sure your current associations won't migrate to one of the unlike type pairs.

Don't take my answer for law, but I *think* that's what I've been told multiple times as I've tried to work through relationships myself.

HTH,

Heather

Heather,

I think that the key point here for us is

“You'd just make sure your associations are set up indicating N1/N2 and never use "both" in the association.”

And I’m fairly sure that both is what has been used?

Then the questions is:

To “Cleanup” or Not to “Cleanup” what is the cost and what is the benefit?

--Tom

From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Heather Kraft
Sent: Friday, November 18, 2011 5:57 PM
To: Thomas Brown
Subject: Re: [Tessitura Next Generation Forum] How to "force" only associations during V11 Constituent Migration

Hi Tom -

I think this is dependent on several things - some you can control and some you can't.

A) v10 Corporate type of account associated with v10 individual

- Nothing you can do about this, if left, it will turn into an affiliation. The only way you could change this would be to change the Corporate side of the association to use an individual contact if that existed.

B) v10 account 1 with N1/N2 associated with v10 account 2 with N1

- If you want the relationship in v11 to be on the household of account 1, again it will be an affiliation between account 1 and account 2.

- If you want the relationship in v11 to be with N1 or N2 individual accounts linked to account 1 (I hope that makes sense) then you can assure that the relationship will migrate as an association by cleaning up your v10 associations. You'd just make sure your associations are set up indicating N1/N2 and never use "both" in the association. You'd also NOT check the 'Force Both' checkbox in the migration table as this would force the association to go to the household (if it existed). If 

Does that make sense? I'm not nearly as coherent in my explanation as the Next Gen Team so maybe I should just let them answer this. :P 

The really short answer is: If you have v10 organization types in the mix or want this relationship to be with the v11 household you are going to end up with both associations and affiliations for that particular v10 association.

- Heather