Completed

Converting Leads to Contacts (& Organizations)

When I convert a Lead to a Contact/Organization, ALL of the information I keyed into the "leads" fields should migrate over.

Otherwise, setting up all the info in Leads is a waste of time if it just disappears when I convert the Lead to a new Contact & new Organization.

And only the Organization name migrated during the conversion.  Insightly should at least ask "Which fields do you want to convert to the new Contact record?" and "Which fields do you want to convert to the new Organization record?". 

And it would be even better if Insightly asked "Do you want to create a new Opportunity from this Lead?"

17

Comments

45 comments
  • Thanks for your feedback!

    All your Lead information except your Custom Fields and attachments should convert over. The Custom Fields you have under Contacts may be different than those you have set up under Leads which is why those will not transfer.

    Can you provide me an example of what isn't transferring over?

    0
    Comment actions Permalink
  • The Lead has the following fields completed:

    Insightly Fields:  Lead Name, Organization, Lead Status, Lead Source, Responsible User, Lead Rating, Email Address, Industry, Phone, Address, Number of Employees, and Description.

    Custom Fields:  Thank You Note and Webinar Date

    When I select CONVERT LEAD from the Actions drop-down menu:

    The first thing that happens is an OPPORTUNITY is created.  I disregard those fields, because I'm going to delete the 'opportunity' anyway, but I have to hit save in order to finish the conversion.

    When I find the organization's information, the only fields that are completed are Organization Name and Organization Created.I needed the address and phone number to convert over ... 

    And it would be awesome if the other fields that are only available in the LEADS section (number of employees, industry, etc) would convert over too ... I mean that information applies to the Organization that is created from converting a lead ... 

     

    4
    Comment actions Permalink
  • I agree. It would be nice to have the Lead info updated to the Organization after converting the lead. Even better, if it would update to the Organization and Contact not just part of the information to the Contact.

    In addition, I love how the custom fields from Leads can be updated to your Opportunity if you have the same custom field names/format.  But it would be awesome if those custom fields could also update across to the Organization and Contact as well.

    We are re-typing in so much information across the board and having an option to transfer the data across it would save so much time and be greatly appreciated!

    7
    Comment actions Permalink
  • Thanks for the additional details. The Lead information once converted will transfer over to the Contact and not the Organization. Its a great suggestion for it to transfer over for the Organization as well.

    2
    Comment actions Permalink
  • It is really ridiculous that all information doesn't sync from lead to contact. Old school CRMs were doing that 20 years ago. This is really frustrating.

    6
    Comment actions Permalink
  • How is this not a given?  Why create any custom fields in Leads if they're just lost upon conversion to Contacts?

    6
    Comment actions Permalink
  • My apologies for any misinformation above. Custom Fields in Leads will not transfer to Contact or Organization records.

    However, the custom fields will travel over into the new Opportunity record  if the exact same Custom Field exists for both record types (Leads and Opportunities).

    @Keith - This has not been added as a function at this time. The reason it's set up this way is, Custom Fields are limited in each plan type and most users do not want to take up all their Custom Fields with duplicate data. Please add your vote to this at the top of the original post to show your support for a possible feature addition.

    0
    Comment actions Permalink
  • @Lyla, you say "most users do not want to take up all their Custom Fields with duplicate data."  That makes no sense.  Who said I want to use "all" of my custom fields allotment?  I do want to use some, though. Isn't that what they're for?  How am I "duplicating" data?  My Leads, once converted, are no longer the key source of information for that person; the Contact record is. Am I "duplicating" a Lead field (e.g., first name) when the converted Contact also has a "first name" field? Perhaps, but it would be counterproductive not to retain that information in a "duplicate" field in the Contact record.  

    6
    Comment actions Permalink
  • Thanks for adding additional time to add more detail to the request @Keith.

    0
    Comment actions Permalink
  • Is there a plan to include any of the following in a future release?  And if yes, when?

    • Allow ALL fields from a Lead to travel over to a Contact upon conversion - or - at a minimum, ask the user which fields they would like to travel over to the new Contact record.
    • Ask the user which fields they would to have travel over from a Lead to a new Organization upon conversion (i.e. address, city, state, zip, phone, etc.)
    • Ask the user if they want to create an Opportunity when converting a Lead to a Contact.  (A simple yes or no would suffice).

    The answers to these requests are primary drivers in my decision whether or not to renew my account.

    4
    Comment actions Permalink
  • Hi Trish:

    These are items are not part of our road map however, our product team is aware of these needs and is always looking into making improvements.

    Adding your comments and votes in our community is a great way to show what is wanted so thanks for adding additional specifics for this.

     

    1
    Comment actions Permalink
  • Is there an update on that feature? Is it still not possible to pull customer fields over from a lead to a contact? 

    1
    Comment actions Permalink
  • Yes please!  We need our custom fields to carry forward from the Contact to the Opportunity.  We have had to duplicate the custom field names, and duplicate data entry.  Please add this functionality.

    3
    Comment actions Permalink
  • UPVOTE - 100% agree with Trish on presenting some dialogue to the Insightly user when converting Leads to  Contacts and Opportunities.  And presumption is that we have created identical custom fields in both Leads and Contacts.  

    2
    Comment actions Permalink
  • Completely agree.. using Leads is a waste of time if it doesn't convert to Contacts.  This is a huge flaw in a really good CRM.

    4
    Comment actions Permalink
  • I'm adding MY BIGGEST REASON for needing Custom Fields to transfer when you change from lead to a contact (thought I'm certain I am not alone!).

    When we enter a new lead (either manually or via web form on our website) we ask them to OPT IN TO OUR NEWSLETTER this is a Custom Field I have in both lead and contact. It is imperative that we keep that information accurate (opting into email is not something you want to mess around with!) and right now we need to manually check the box once we have changed a Lead to a Contact. I have voted (and would vote again if possible, I am in Chicago and we vote early and vote often here!). Thanks!!

    2
    Comment actions Permalink
  • I am a new user using the Trial Period for an evaluation. I'm currently a SalesForce client/user. Converting seamlessly from lead to contact is a deal breaker for me. Even though I've only been trying this out for a day, Insightly is way more friendly than SF. Please please make this work. If I switch over and then dump this on my business development folks with this limitation, they will have a fit. Thanks for reading my request.

    4
    Comment actions Permalink
  • This would be a great addition. If Custom Fields in both Leads and COntacts were exactly the same, Insightly should map them across in the conversion - or at least give you the option. Thanks!

    5
    Comment actions Permalink
  • Many of these custom fields will follow a contact from prospecting, through the selling process and even onto future and repeat sales. Why would we NOT need the information to follow along. I understand the concern about "using up" your custom fields, but that is an issue related to your business model and actually contrary to the selling cycle. Making it a choice during the conversion process would eliminate that issue, either way it need to be added.

    3
    Comment actions Permalink
  • I agree with everyone... giant, frustrating lack of functionality here.

    The only reason given for why this feature doesn't exist is because 'some users don't want to use up multiple fields per their plan restrictions.'

    SOLUTION: why not just count an identically named field that exists in both leads and contacts as 1 custom field? Worst case scenario, just count the fields as 2 custom fields and make it a quicker path for us to upgrade plans. 

    You would make more money and we get this desperately needed functionality. 

    3
    Comment actions Permalink
  • We need this feature fixed soon. Frustrating and a real timeconsumer..

    3
    Comment actions Permalink
  •  We appreciate your added thoughts. This unfortunately doesn't have a spot on the immediate roadmap. With enough additional interest it can be considered in the future.

    0
    Comment actions Permalink
  • Layla,  how much interest needs to be there to get it on the roadmap?  This feature (and the lack of tags transferring over) is lead management 101...It really is a time killer...

     

    2
    Comment actions Permalink
  • Hi there Casey:

    We'll be posting something soon to give everyone an idea of what the life cycle of a Feature Request looks like. 

    0
    Comment actions Permalink
  • Definitely support the ability to enable custom fields to be carried forward from Lead records on conversion. Admin user should have the option to specify whether a Lead custom field can also be seen against a Contact, Organisation and/or Opportunity. This is a basic requirement to ensure important information captured during the Lead process remains visible throughout.

    2
    Comment actions Permalink
  • Hi Andy,

    Thank you for taking the time to add your feedback to our Community.

    0
    Comment actions Permalink
  • Please add the ability to transfer custom fields from leads when converting.  This is basic Sales 101 and should be at the TOP of the priority list.

    3
    Comment actions Permalink
  • Clearly you'll want some fields from the Lead to go to Contact (like job title) some to go to Organisation if you are creating a new one, and some to go to the Opportunity.  In fact, mapping from lead to opportunity is the least important of the three for me.

    Yeah, I think you've lost me as a potential customer over this.

    3
    Comment actions Permalink
  • I'm sorry to hear that, Tim. Thank you for taking the time to provide your feedback.

    0
    Comment actions Permalink
  • I'd like to ask this same question to the Insightly team the other way around.

    I have just created a lead and captured lots of information in the process, including several custom fields.

    Please can you give me some examples of information that you feel I would NOT want to carry forward into the Contact or Organization as I progress my relationship with a lead who has become a really good prospect?  What data would I throw away?

    So far, I don't think I've created any fields that I don't want to keep for the long term.   If you can think of some, maybe we can have a discussion.  If you cannot, then maybe you should cave on this one and fix it so it works?

    Keen to hear your thoughts team.  Thanks

     

     

    0
    Comment actions Permalink

Post is closed for comments.