Convert and merge in one router after Lead to Contact duplicate match
M
Maxim Kalenik
When a Distro lead router hits a Lead-to-Contact duplicate match and converts the lead, Salesforce creates a
second
contact instead of merging into the matched existing contact. The Merge Records node is only allowed when the trigger object type equals the duplicate match target (Lead-to-Lead or Contact-to-Contact), so it cannot be used on the Lead-to-Contact path.Requested behavior: allow match -> convert -> merge in a single path/router, so an incoming lead that matches an existing contact ends up merged into that contact instead of producing a duplicate.
Current workaround (2 routers required):
- Lead-triggered router that converts the lead after a Lead-to-Contact duplicate match.
- Contact router with a "Record is created" trigger, a Contact-to-Contact duplicate path, and a Merge Records node.
Walkthrough video: https://share.cleanshot.com/1Z7CgR0K
Why it matters: LeanData does this in one node (Merge Dupe Contact — internally match, convert, merge: https://leandatahelp.zendesk.com/hc/en-us/articles/360041790634-Routing-Merge-Dupe-Contact-Node-Guide). Every LeanData displacement that relies on dedupe hits this gap and needs a second router plus SFDC duplicate-rule tuning to work around it. Per-customer context is captured in the insights below.