Hi all, I’m doing a migration from eTapestry into SF NP template.  I haven’t worked with the NP template up until now.  Some import/design questions: 1.      I understand it is good practice to create a household for every contact in the db.  What is the best way (is there a way) to generate them en mass for my imported records (simply one per record at this point). 2.      Their Org records do not have any (people) contact info with them right now.  The sf import wizard wanted to import email address into a contact record related to the Account, so I went ahead and let it make a “dummy” contact records for all Accounts for ease of mail and email list mgmt.  Is this the right way to go?  It seems potentially confusing for the client, since most of the salient info on organizations is in the Account record – or of course they could now start gathering contact info for their orgs! 3.      Next I need to import donations (connected to donors by the old system ID number)  … is this a stupid question – but what _link_s the Opportunity to the Donor?  When I run the data loader Account/Org (not Contact) appears to be the only _object_ available to _link_ the donation/opportunity to through AccountID.  What am I missing here? Thanks in advance Jenny No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Data_base_: 269.8.16/849 - Release Date: 6/14/2007 12:44 PM

          st1:*{behavior:url(#default#ieooui) }                     Hi all,   I’m doing a migration from eTapestry into SF NP template.  I haven’t worked with the NP template up until now.  Some import/design questions:    I understand it is good practice to create a      household for every contact in the db.  What is the best way (is      there a way) to generate them en mass for my imported records (simply one      per record at this point).    Their Org records do not have any (people) contact      info with them right now.  The sf import wizard wanted to import      email address into a contact record related to the Account, so I went      ahead and let it make a “dummy” contact records for all Accounts      for ease of mail and email list mgmt.  Is this the right way to go?  It      seems potentially confusing for the client, since most of the salient info      on organizations is in the Account record – or of course they could      now start gathering contact info for their orgs!    Next I need to import donations (connected to      donors by the old system ID number)  … is this a stupid      question – but what _link_s the Opportunity      to the Donor?  When I run the data loader Account/Org (not Contact) appears      to be the only _object_ available to _link_ the donation/opportunity to      through AccountID.  What am I missing here?   Thanks in advance   Jenny   No virus found in this outgoing message.  Checked by AVG Free Edition.  Version: 7.5.472 / Virus Data_base_: 269.8.16/849 - Release Date: 6/14/2007 12:44 PM

Hi all, I'm doing a migration from eTapestry into SF NP template.  I haven't worked with the NP template up until now.  Some import/design questions: 1.      I understand it is good practice to create a household for every contact in the db.  What is the best way (is there a way) to generate them en mass for my imported records (simply one per record at this point). 2.      Their Org records do not have any (people) contact info with them right now.  The sf import wizard wanted to import email address into a contact record related to the Account, so I went ahead and let it make a dummy contact records for all Accounts for ease of mail and email list mgmt.  Is this the right way to go?  It seems potentially confusing for the client, since most of the salient info on organizations is in the Account record - or of course they could now start gathering contact info for their orgs! 3.      Next I need to import donations (connected to donors by the old system ID number)  ... is this a stupid question - but what _link_s the Opportunity to the Donor?  When I run the data loader Account/Org (not Contact) appears to be the only _object_ available to _link_ the donation/opportunity to through AccountID.  What am I missing here? Thanks in advance Jenny No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Data_base_: 269.8.16/849 - Release Date: 6/14/2007 12:44 PM

Hi all, I'm doing a migration from eTapestry into SF NP template.  I haven't worked with the NP template up until now.  Some import/design questions: 1.      I understand it is good practice to create a household for every contact in the db.  What is the best way (is there a way) to generate them en mass for my imported records (simply one per record at this point). 2.      Their Org records do not have any (people) contact info with them right now.  The sf import wizard wanted to import email address into a contact record related to the Account, so I went ahead and let it make a dummy contact records for all Accounts for ease of mail and email list mgmt.  Is this the right way to go?  It seems potentially confusing for the client, since most of the salient info on organizations is in the Account record - or of course they could now start gathering contact info for their orgs! 3.      Next I need to import donations (connected to donors by the old system ID number)  . is this a stupid question - but what _link_s the Opportunity to the Donor?  When I run the data loader Account/Org (not Contact) appears to be the only _object_ available to _link_ the donation/opportunity to through AccountID.  What am I missing here? Thanks in advance Jenny No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Data_base_: 269.8.16/849 - Release Date: 6/14/2007 12:44 PM

 Hi all,  I'm doing a migration from eTapestry into SF NP template.  I haven't worked with the NP template up until now.  Some import/design questions:  1.      I understand it is good practice to create a household for every contact in the db.  What is the best way (is there a way) to generate them en mass for my imported records (simply one per record at this point).  2.      Their Org records do not have any (people) contact info with them right now.  The sf import wizard wanted to import email address into a contact record related to the Account, so I went ahead and let it make a dummy contact records for all Accounts for ease of mail and email list mgmt.  Is this the right way to go?  It seems potentially confusing for the client, since most of the salient info on organizations is in the Account record - or of course they could now start gathering contact info for their orgs!  3.      Next I need to import donations (connected to donors by the old system ID number)  . is this a stupid question - but what _link_s the Opportunity to the Donor?  When I run the data loader Account/Org (not Contact) appears to be the only _object_ available to _link_ the donation/opportunity to through AccountID.  What am I missing here?  Thanks in advance  Jenny  No virus found in this outgoing message.  Checked by AVG Free Edition.  Version: 7.5.472 / Virus Data_base_: 269.8.16/849 - Release Date: 6/14/2007 12:44 PM