What happens when you merge in Dedupely for Salesforce

Many teams expect Salesforce merges to behave the same way across instances. But merge logic in Salesforce isn’t fixed, it depends on your setup. Matching rules, duplicate rules, and field-level behavior vary. That flexibility is useful, and also what makes it harder to predict merge outcomes.

Dedupely doesn’t override your logic. It applies it at scale.

When connected to Salesforce, Dedupely mirrors your existing merge configuration:

• Matching and duplicate rules already in place continue to apply
• Native and custom objects are both supported
• Field-level behavior, including read-only and calculated fields, is respected
• The CRM still controls what’s editable, but you define what gets prioritized

You get more visibility and control over which values stay and when. Merge rules work on all editable fields. As in Salesforce, locked fields will skip rule application and retain native values.

Those patterns stay intact if your setup defines merge behavior by object or object type. Dedupely doesn’t flatten that logic; it scales it, using the structure you’ve already built.

To take control of Salesforce merge outcomes:

• Review your existing duplicate rules, Dedupely will follow them
• Apply merge rules only to editable fields, read-only values are skipped
• Use custom merge to preview and adjust values when needed manually
• Run bulk merges safely once logic has been validated against your config

Salesforce lets you build your CRM your way, and your merge logic should reflect that. With Dedupely, you gain continuous control over duplicates without disrupting your structure. Custom objects, matching rules, and workflows stay intact. What you get is scalable merging with consistent results, no manual cleanup, no per-user charges.

If you want to see how Salesforce handles merges natively, this guide explains their built-in logic.