Keep Dynamics 365 free of duplicates – without slowing your team down
- Run duplicate checks on Leads, Contacts, Accounts and any custom entity. so you’re not limited to just core CRM tables.
- Combine exact logic (e.g. email, VAT number) with fuzzy matching (company name, address, phone) in flexible scenarios per entity.
- Find Leads that already exist as Contacts or Accounts, and other cross‑entity overlaps that would otherwise stay hidden.
- Use filters for territory, record type, status or custom fields so searches focus on the data that matters now.
- Decide per field which value wins in a merge – latest update, specific source system, or a fixed master. Protect key fields while still consolidating data.
- Review complex duplicate groups in a guided merge screen, or enable auto‑merge for straightforward cases so they’re cleaned up in the background.
- Use Direct Merge flows to resolve duplicates coming from imports or list views in fewer clicks, while still applying your merge rules.
- As users create or edit a record, Deduplicate checks your scenarios and suggests existing matches to reuse.
- On Save (including Quick Create), Deduplicate warns or blocks users based on your settings for that entity.
- Screen API and import records so potential duplicates are flagged or queued instead of created.
- Prevent creating a Lead when the same person already exists as a Contact or Account with cross‑entity scenarios.
- Configure per standard and custom entity which scenarios, prevention hooks, and merge rules apply.
- Combine exact and fuzzy matching, weighting, and merge rules to fit your own data model.
- Exclude test data, segments, or low‑value entities so dedupe runs stay focused.
- Use the audit log to see who merged, deactivated, or deleted what and when.
- Process duplicates across entities and automated flowsUse cross‑entity scenarios to catch overlaps like Leads that already exist as Contacts or Accounts.
- Apply the same cross‑entity logic in real‑time prevention and DC Jobs for both day‑to‑day and batch cleanups.
- Use Direct Processing on automated sources (imports, API inserts) to auto‑handle high‑confidence duplicates. based on your thresholds, while leaving edge cases for review.
Yes. You can enable Deduplicate on both standard and custom entities. For each entity you decide which scenarios apply, which prevention features are active, and how merges should behave. That way, dedupe rules match your actual data model, not just core CRM tables.
No. Real‑time checks are optimized via the search index so users see fast suggestions while they work. For heavy clean‑up, DC Jobs run on Plauti Cloud or DC Local, processing large volumes outside Dynamics 365 and only sending back results, so everyday usage stays responsive.
Yes. You can configure per entity if Deduplicate should only warn users, block them from saving, or route records into a job for later review. For batch clean‑ups you can choose to merge, deactivate, or delete duplicates, with optional auto‑merge for straightforward matches.
Records created via API or imports are screened using the same scenarios you configure for manual entry. Potential duplicates are detected and handled according to your prevention settings, so new data from marketing, other CRMs, or custom apps doesn’t silently create duplicate records.
Yes. Deduplicate keeps an audit log that records merges, deactivations, and deletions, including who performed the action and when. This makes it easier to investigate issues, answer user questions, and meet compliance or auditing requirements.