Skip to main content
Adam_Benitez1
Adam_Benitez1
Level 3
March 28, 2017
New

Keep Populated Field Data for Custom Fields When Merging Leads

  • March 28, 2017
  • 4 replies
  • 4846 views

I was just told by support, "For custom fields, the values from the winning lead will take precedence over the losing lead's values - even if the winning lead's value is currently null. This behavior is expected and there is not currently a plan for us to change that."

I suggest that when the winning value has a custom field value of null and the losing value is populated, Marketo should retain the populated field data instead of purposefully decreasing the data quality of our database by nulling out the data.

I'm sure there are some fields where a blank value is the better value, but in the vast majority of cases a populated field is better than an empty one.

    4 replies

    Grégoire_Miche2
    Grégoire_Miche2
    Level 10
    March 30, 2017

    Voted.

    In the meantime, there is one absolute rule when merging fields: create a backup first

    -Greg

      Adam_Benitez1
      Adam_Benitez1Author
      Level 3
      April 7, 2017

      Great advice. When I've used RingLead in the past, I made sure to keep an export so I could fix some not-so-ideal data populations. We now use LeanData for Routing and they also have an incoming merge feature that we're using so it's more systematic. They probably have records of the old data. I'll have to look into it, but this creates a lot more work for sure.

      Jamie-Carey
      Jamie-Carey
      Level 4
      March 30, 2017

      Wow. That's really unexpected behavior. Surprised that this is how it was designed.

        SanfordWhiteman
        SanfordWhiteman
        Level 10
        March 30, 2017

        The default behavior must not be changed, as it would be a colossal backward compatibility break.

        Can see adding the option to merge case-by-case and field-by-field. But there are just as many problems going in the other direction. Until we have a notion of field groups which always move together, someone will always lose.  I shudder at what we would have lost had blank fields blindly taken a value from source fields without regard for context.

          Adam_Benitez1
          Adam_Benitez1Author
          Level 3
          April 7, 2017

          Yes, there would absolutely need to be conditions. This is especially true for source fields.

          K
          kh-lschutte
          February 6, 2020
          No text available
          Terms & ConditionsAccessibility statement

          Loading footer...