Merging duplicates
      Back to home
      1. Knowledge Base
      2. Merging duplicates

      Salesforce Best Practices

      Best practices for using Dedupely with Salesforce, covering sync setup, merge stages, rules, permissions, object control, and safety settings.

      Using Dedupely with Salesforce can greatly enhance your data quality by automating and simplifying your deduplication process. This guide shares strategic best practices to help you make the most of Dedupely’s features while working within Salesforce’s structure.

      1. Understand how Dedupely works with Salesforce

      • Dedupely uses Salesforce’s native merging engine.
      • All merges happen inside Salesforce; Dedupely does not override platform logic.
      • Your data integrity remains intact, merging behaves the same as doing it directly within Salesforce.

      2. Start with a full sync

      When you connect Salesforce to Dedupely:
      • You’ll authorize access through your Salesforce login.
      • Dedupely will begin syncing standard objects (e.g., Leads, Contacts, Accounts) and supported custom objects.
      • Resyncs happen in the background every 10–30 minutes.
      For more information, see: Syncing Records

      3. Use strong matching fields first

      When creating your Search Pads:
      • Begin by matching on fields like Email, Full Name, or Account Name.
      • Avoid starting with fuzzy logic. Use exact matches for initial testing.
      • Combine filters to narrow your results and prevent false positives.

      4. Merge in stages for better control

      We recommend merging in three stages:
      1. Single merge: Start small to observe behavior.
      2. Bulk merge: Once you’re confident in the results.
      3. Auto merge: For automated cleanup at regular intervals.

      5. Use merge rules for precision

      Set Merge Rules to ensure specific values win or lose during merging:
      • Create rules by object and field.
      • Use conditional logic to define outcomes.
      • Rules apply automatically across Search Pads or specific ones.
      Details: Merge Rules

      6. Pay attention to field permissions

      • Dedupely cannot write to read-only fields.
      • Merges are limited by your Salesforce user’s access and field visibility.
      • Ensure your integration user has sufficient permissions to perform merges on key fields.

      7. Monitor merge history for auditing

      • Use Merge History to review all completed merges.
      • Each entry shows the merged records and resulting values.
      • Use the export function to save a CSV of merged data.

      8. Manage which objects sync

      In Dedupely’s App Management:
      • Choose which Salesforce objects to sync (standard or custom).
      • View how many records are syncing to monitor your plan usage.
      • You can disconnect or re-sync objects at any time.

      9. Merge safety settings

      Set limits in each Search Pad to:
      • Restrict how many records can match in one group.
      • Prevent mass merges beyond a threshold.
      If a group exceeds your settings, it will be skipped for safety.
      Review: Merge Safety

      10. Support when you need it

      We offer unlimited support via:
      Our team is available to assist with implementation, strategy, or troubleshooting at any stage.