Custom Fields while converting lead to account

[smallbiz]

when lead is converted to account, values of custom fields do not move. possible solution suggested in suppor wiki says

Create the custom fields in the target (Account, Contact, Oportunity) module exactly as they appear in the originating (Leads) module before converting data.

---------------
What is the meaning of custom field being exactly in target module as in originating module.? is it data type, field name, system label. I have tried several combination, none works !!

[sugarcane]

Hello,

this means that the database name and the type need to be the same in both the leads module and the Accounts or Contacts module.

Ex: if you create a custom dropdown field in the Leads module with a database value of budget_c and you want this to convert to the Contacts module, then you also need to create a custom dropdown field in the Contacts module with the exact same database name of budget_c.

Because custom fields you create automatically add '_c' to the database name of the custom field, if you wanted to add a field in the Leads module which already exists in Accounts or Contacts (ex: website), then in order for this field to convert, you would have to either hard code the website field in the Leads module (since creating a custom field would create a database name of 'website_c' instead of 'website'), OR if you did not want to hard code anything, then in this example, you could just create a new field in both Leads and Accounts and remove the original website field from the Accounts

Make sense?

[consultsales]

We have the same issue. Both custom fields in the Accounts and Leads module have the same name in the database and are of the same type but yet when the lead is converted to account, the information is not passed over. We have several custom fields that need to be copied over.

HELP!

[jkliza]

How is this accomplished? We do a lot of qualification up front, and have about 10 custom fields that we would like to be copied over to the account when we convert the lead to an opportunity.

Any ideas?

- Jesse

[tobydz]

I'm attempting to do the same thing as above, make custom "leads" fields populate the contact form that also has custom fields. I noticed the post was dated 2005, so I'm wondering if anyone has any further, up to date, info on this.


Thanks!

[Angel]

Same process. So long as the names of the custom fields (and data type) match each other in both modules, the data will automatically carry over during the conversion process.

[flockswatter]

No none of that works! This is so frustrating. I've spent the last 5 hours banging my head against a wall!!

I have the exact same custom field in leads and contacts. Same exact field name car_notes_c, same exact display label Car Notes, same exact system label LBL_CAR_NOTES_C. I hit convert and it shows up on the conversion things but when I hit save....nothing is transferred!

I've created about 120 custom fields in leads that need to convert to contacts. WTF!?

On another note, I've created about 600 additional custom fields in the contacts module and the custom field creation and layout is ABSOLUTELY HORRIBLE! What should have taken me a few hours has taken me over 2 days and I'm still not even close to where I need to be!!!!

Sugar is great in a lot of ways but it SUCKS in this way!

[jmertic]

No none of that works! This is so frustrating. I've spent the last 5 hours banging my head against a wall!!

I have the exact same custom field in leads and contacts. Same exact field name car_notes_c, same exact display label Car Notes, same exact system label LBL_CAR_NOTES_C. I hit convert and it shows up on the conversion things but when I hit save....nothing is transferred!

I've created about 120 custom fields in leads that need to convert to contacts. WTF!?

On another note, I've created about 600 additional custom fields in the contacts module and the custom field creation and layout is ABSOLUTELY HORRIBLE! What should have taken me a few hours has taken me over 2 days and I'm still not even close to where I need to be!!!!

Sugar is great in a lot of ways but it SUCKS in this way!

Just to answer that last bit, why are you creating so many custom fields? While doing mass field creation does take a bit of time, I'm not sure on the use case of so many fields on one module.