Forums
How Leads V2 Work - Confirmation, measure twice, cut once, questions (a) - (e)
Greetings Everyone,
We are re-designing our internal processes to use LeadV2. Below is my understanding of how this will (i.e., should) function:
Step 1 - Create the LeadV2 object - Associated UDFs are displayed for the Lead. These UDF values can be updated for the Lead.
Step 2 - Decision is made to continue, and LeadV2 object is converted to an "Individual" or "Company". Questions: (a) I assume that the UDF values for the Lead are not transferred to the converted object? Can these values be transferred automatically, or (b) must they be transferred manually or thru an API call?
Step 3 - We need to create a web hook and update the data for the "Individual" or "Company" after conversion from a Lead. Thinking (c) that this web hook subscription should be defined for the "Individual" or "Company" object (this is a key change as we are converting from a Lead to an new entity: "Company" or "Individual" in this case, and the web hook will fire based on a defined filter)? The payload (d) will contain a reference to the Lead and the newly created "Individual" or "Company"?
After conversion, (e) is a reference and the original Lead object retained with all the Lead's original information (assume that it is)?
Please confirm and / or advise on items (a) - (e) above.
Onward, Upward, thanks, Joe