locked
Lead import RRS feed

  • Question

  • Hi All,

    I have a list of Leads for importing in CRM 4. Some Leads have more than one Contact and all information regarding that Contacts I put in  Description. My problem is while converting Leads to Opportunities I will have only one associated contact regarding that Opportunity. Can I do something for having more than one associated contacts for a Lead(or something else) and also for logical continuation of the Sales Process?

    Thanks in advance!
    Wednesday, December 2, 2009 2:15 PM

Answers

  • Leads in CRM are different than Accounts in CRM in that you have can have multiple Lead records for the same company.  You should consider creating one Lead record for each individual and then applying the same Company name. 

    I had a similar issue come up with one client.  The issue was that the client wanted to track several Lead records to one Company Name.  If you think through this a bit, generally speaking a Sales person will have one Primary person that they are dealing with to identify the Opportunity.  Keep in mind that a Lead can be considered a name in the database.  It is a Lead, just that, nothing more.  It is a person that your Sales or Marketing team can contact to see if there is an Opportunity for the company.  Therefore, most companies only need one Lead record to represent a company.  Once the Opportunity for the Lead is identified, you can then convert that Lead to an Account, Contact and Opportunity.  Once you have the Account record, then you can begin adding additional Contact records to the Account.  These Contacts, are not generally considered Leads.

    If the above does not work, another option is to use a field on the Account form to identify the Account Type.  Some examples for reference:  Accounts can be Vendors, Clients, Prospects, Leads, etc.  When you import your records, you could bypass creating a Lead and create an Account instead with the Type of 'Lead' and then add the Contact records as Contacts associated to the Account.  The only downside for this is reporting in that you will not have the ability to report on the Orginating Lead using the application default field.  If this reporting is important to the company, you will have to apply a workaround like tagging the Contact record as the Orginiating Lead and then report using that field.
    Best Regards, Donna
    • Marked as answer by Jim Glass Jr Wednesday, December 2, 2009 4:05 PM
    Wednesday, December 2, 2009 3:01 PM

All replies

  • Please take a look at this post, it will give you some ideas. You might have to use a 3rd party tool or do it through the SDK is you have some complex logic.




    Darren Liu | 刘嘉鸿 | MS CRM MVP | English Blog: http://msdynamicscrm-e.blogspot.com | Chinese Blog: http://liudarren.spaces.live.com
    Wednesday, December 2, 2009 2:24 PM
    Moderator
  • Leads in CRM are different than Accounts in CRM in that you have can have multiple Lead records for the same company.  You should consider creating one Lead record for each individual and then applying the same Company name. 

    I had a similar issue come up with one client.  The issue was that the client wanted to track several Lead records to one Company Name.  If you think through this a bit, generally speaking a Sales person will have one Primary person that they are dealing with to identify the Opportunity.  Keep in mind that a Lead can be considered a name in the database.  It is a Lead, just that, nothing more.  It is a person that your Sales or Marketing team can contact to see if there is an Opportunity for the company.  Therefore, most companies only need one Lead record to represent a company.  Once the Opportunity for the Lead is identified, you can then convert that Lead to an Account, Contact and Opportunity.  Once you have the Account record, then you can begin adding additional Contact records to the Account.  These Contacts, are not generally considered Leads.

    If the above does not work, another option is to use a field on the Account form to identify the Account Type.  Some examples for reference:  Accounts can be Vendors, Clients, Prospects, Leads, etc.  When you import your records, you could bypass creating a Lead and create an Account instead with the Type of 'Lead' and then add the Contact records as Contacts associated to the Account.  The only downside for this is reporting in that you will not have the ability to report on the Orginating Lead using the application default field.  If this reporting is important to the company, you will have to apply a workaround like tagging the Contact record as the Orginiating Lead and then report using that field.
    Best Regards, Donna
    Wednesday, December 2, 2009 2:58 PM
  • Leads in CRM are different than Accounts in CRM in that you have can have multiple Lead records for the same company.  You should consider creating one Lead record for each individual and then applying the same Company name. 

    I had a similar issue come up with one client.  The issue was that the client wanted to track several Lead records to one Company Name.  If you think through this a bit, generally speaking a Sales person will have one Primary person that they are dealing with to identify the Opportunity.  Keep in mind that a Lead can be considered a name in the database.  It is a Lead, just that, nothing more.  It is a person that your Sales or Marketing team can contact to see if there is an Opportunity for the company.  Therefore, most companies only need one Lead record to represent a company.  Once the Opportunity for the Lead is identified, you can then convert that Lead to an Account, Contact and Opportunity.  Once you have the Account record, then you can begin adding additional Contact records to the Account.  These Contacts, are not generally considered Leads.

    If the above does not work, another option is to use a field on the Account form to identify the Account Type.  Some examples for reference:  Accounts can be Vendors, Clients, Prospects, Leads, etc.  When you import your records, you could bypass creating a Lead and create an Account instead with the Type of 'Lead' and then add the Contact records as Contacts associated to the Account.  The only downside for this is reporting in that you will not have the ability to report on the Orginating Lead using the application default field.  If this reporting is important to the company, you will have to apply a workaround like tagging the Contact record as the Orginiating Lead and then report using that field.
    Best Regards, Donna
    • Marked as answer by Jim Glass Jr Wednesday, December 2, 2009 4:05 PM
    Wednesday, December 2, 2009 3:01 PM
  • Thanks very much!!!
    Thursday, December 3, 2009 7:17 AM