Duplicate Management (Generally Available)

Maintaining clean and accurate data is one of the most important things you can do to help your organization get the most out of Salesforce, so we’re excited to introduce Data.com Duplicate Management. Now you can control whether and when you allow users to create duplicate records inside Salesforce; customize the logic that’s used to identify duplicates; and create reports on the duplicates you do allow users to save.
Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions



Duplicate Management uses Data.com technology, but does not require a Data.com license.

Preventing Duplicate Flow

For more information about Data.com Duplicate Management, including detailed information about matching rules, see Managing Duplicate Records in Salesforce. Also, check out the video: Watch Video Demo Understanding Matching Rules (4:32).

Key Improvements from the Winter ’15 Beta Release

  • Custom objects are supported by duplicate rules and matching rules.
  • Cross-object matching is supported by duplicate rules. For example, set up a rule so that when users attempt to save contact records, they’ll see a list of possible duplicate contacts and leads.
  • When your duplicate rules are set up to match across objects, you can decide how the matching rule fields map to each other. For example, you might map the Account Name field for a contact to the Company name for a lead.
  • When your matching rule includes custom fields, you can decide how the fields map to each other. For example, you might map a custom field called Work Email to the standard Email field.
  • You can use fields with picklist values in your custom matching rules.
  • We’ve improved how duplicate rules work when converting leads. If your organization has the “Use Apex Lead Convert” permission and a user converts a lead to a new or existing contact or account, the action specified in the duplicate rule will determine whether the lead can be converted.
  • We’ve improved how duplicate rules work with Data.com. Now, if your organization uses Data.com and the Data.com duplicate preference option is set to allow duplicate records to be added from Data.com:
    • The action specified in the duplicate rule will determine whether the user can add the record.
    • Users can click Save (ignore alert) on the comparison page when manually cleaning a record to ignore duplicate alerts and save the record.
  • We’ve added a bunch of new APIs and Apex classes for duplicate management. See the API and Apex sections of these release notes for more information.

Duplicate Management Limitations

  • Duplicate management is available for accounts, contacts, leads, and custom objects. All other objects, including Opportunities and Person Accounts, are not currently supported.
  • Duplicate rules don’t run when records are created in following ways.
    • When records are created using Quick Create.
    • When leads are converted to accounts or contacts and your organization doesn’t have the “Use Apex Lead Convert” permission.
    • When a record is restored with the Undelete button.
    • When records are added using Exchange Sync.
    • When records are manually merged.
  • In some cases, if duplicate rules are set for an alert to show when potential duplicates are found, users will always be blocked from saving records and will not see a list of possible duplicates. Examples of this include the following.
    • When records are added using the data import tools.
    • When a person account is converted to a business account (and the newly created business account matches existing business accounts).
    • When records are added or edited using Salesforce APIs.
  • Standard and custom matching rules that use fuzzy matching methods only support Latin characters, and, if you’re using international data, we recommend you use the Exact matching method with your matching rules.
  • If a field on an object is no longer available to your organization, it may cause matching rules with mappings to this field to be ignored. This could affect your duplicate detection. Make sure you check all duplicate rule field mappings for an object if there is a change to the fields available to your organization. For example, the Clean Status field is only available to customers with a Data.com license. If your organization no longer has a Data.com license, this field is no longer available and matching rules with mappings to this field will be ignored.
  • The customizable alert text in duplicate rules isn’t supported by the Translation Workbench.