In This Article:

    Search for and Resolve Duplicates Using the Constituent Merge Utility

    In This Article:

      The Constituent Merge Utility reports multiple instances of duplicate constituents so that they may be merged into one record. This may be necessary if duplicate records had been created or uploaded for a constituent. It is helpful to think of the two records in terms of a Source Constituent record and a Target record.  The Source record contains data that you want moved into the Target record.

      When you use this utility, you'll want to be careful about overwriting current information. Before merging, update the statuses on the Source candidate with the information that you want to keep. Step 8 of the process below provides options on some fields to merge; checked values allow Source Constituent data to overwrite the Target values.

      Access Control and My Salsa CRM information will be retained in the Source record only. Be sure to transfer information manually prior to deleting the Source record.

      Check out the Constituent Merge training course in Salsa Scholars.

      1. From the main menu bar, select Tools > Constituent MergeSearch for Duplicates. The Constituent Merge Utility will open.
      2. Choose the fields that you suspect to contain duplicate information, by selecting the checkbox next to the suspect field names. For example, if two records contain the same last name, first name, and address, that would most likely be the same person, and the two records should be combined into one record.

        NOTE: Name Suffix is not a comparable field, like Jr. or Sr., so if you have a father and son with the same name in the database, and they live at the same address, they will return in your report results as a potential duplicate.

      3. The text field located to the right of the Last or Org Name check box allows you to filter results based on the first letter of the last name or organization. If you have a lot of records, this allows you to clean your data one last name letter at a time.
      4. Select the Run Query button. Duplicate records are returned.
      5. Click to select a record, and then select the Edit Selected Candidates button. Alternately, you can double-click on any row to compare two records.
      6. Determine which record has the most correct and complete information. One or the other record may simply be deleted at this time, if there is no reason to merge them but they are complete duplicates.
      7. Choose either the Merge Left to Right or the Merge Right to Left button.
      8. The Select Information to be Moved dialog box opens. Choose the fields that you wish to move over by selecting the appropriate checkboxes and then choosing OK.
        Emails can be moved or left unmoved, as is the case with any Contact data (such as phone numbers and URLs, for example). If you choose to merge Email addresses, Salsa CRM will move the email address and give it primary status. Old emails will be designated as non-primary (and not overwritten). If the record you are merging content into contains an email address and the record you are merging from does not, the email address will not be removed or overwritten. The last option deletes the Source constituent after the merge is completed. This setting is 'sticky', meaning that whether the setting is automatically checked or unchecked is dependent on what the setting was the last time the user merged records. As with any constituent deletion from the system, this change is permanent and cannot be undone, but you are not prompted for your initials.
      9. The Select Information report opens, listing how many records from each field were merged. Click OK.
      10. Repeat steps 4-10 for each record that you wish to merge.

      NOTE: If you have the Volunteer/Human Resources module you will need to note when merging constituent records that the General tab on the Employee and Volunteer nodes will overwrite any pre-existing information in the record being merged into.

      Was this article helpful?
      0 out of 0 found this helpful
      Have more questions? Submit a request



      Article is closed for comments.