CRM Duplicate Prevention & Deduplication

This is a build-to-order module, not an instant download. Typical delivery is 2–4 weeks from the scoping workshop: we confirm your match rules and block-vs-warn policy, build against your exact Odoo version and edition, test on a staging copy of your database (UAT), then deploy to production and run an optional first bulk dedup pass. Simpler rule sets land nearer two weeks; broader cross-model matching, complex fuzzy scoring, or heavy multi-company scoping trend toward four. We give you a firm timeline in writing after scoping.

Every build includes a post-go-live support and warranty window covering bug fixes and reasonable adjustments to your matching rules. You receive the full source code, so nothing is locked behind a vendor. We also offer optional ongoing support plans and paid version-migration work when you later upgrade Odoo (for example 18 to 19). Because rules are admin-configurable from Settings, most day-to-day tuning needs no developer at all.

Both. The module is built on standard Odoo framework primitives — ORM models, @api.constrains constraints, ir.model.access.csv, record rules, QWeb and OWL — so it runs on Community and Enterprise across Odoo 17, 18 and 19. We build it specifically for the version and edition you run so there are no compatibility surprises.

Odoo's native tool is an after-the-fact cleanup that groups existing contacts by a single exact field (like email or name) and merges them. It does not stop a duplicate from being created in the first place, has no fuzzy matching, no block mode, no per-team override control, and doesn't cover crm.lead. This module adds real-time prevention at entry (warn or hard-block), configurable multi-field fuzzy rules, cross-model checks, an audit trail, and a far more capable review-and-merge wizard — while still handling the bulk cleanup the native tool does.

Yes. Because the matching runs at the ORM constraint/compute level, it applies to records created via CSV/Excel import and via XML-RPC or JSON-RPC integrations — not just the manual form. That means your web lead-capture forms, marketing tools, and third-party feeds are protected too. For high-volume imports we can configure the behavior (block, tag for review, or route to the merge wizard) so a big load doesn't stall.

Safe merging is a core design goal. The merge wizard re-parents everything attached to the losing records — chatter messages, scheduled activities, child contacts, opportunities, quotations, sale orders and invoices — onto the surviving master record before deleting the duplicate, so no history or link is orphaned. You always review a side-by-side field diff and choose the master before anything is written, and we run the first production dedup with you on approved clusters only.

Yes. Rules and modes are configurable per model and can be scoped by company or sales team, so distinct business units don't false-trigger on each other. Permissions are enforced with ir.model.access.csv and record rules: you decide which groups can override a soft warning (with a logged reason), which can run merges, and which can edit the match rules themselves. Overrides are recorded for audit and coaching.