Where do CRM duplicates come from?
Duplicates come from repeated touches: a client submits a website form, then calls, then writes in a messenger — and every channel creates a new lead. Add an imported legacy base, integrations and manual entry with differently spelled phones and emails, and an active CRM accumulates repeats fast. Managers call the same client twice, pipeline stats get skewed, and the conversation history spreads across several cards.
What does the built-in duplicate control cover — and where does it fall short?
Bitrix24's built-in duplicate control matches names, phones and emails when a card is created and can bulk-merge from the list view. But it does not check duplicates when a card moves through the pipeline, does not block work on a repeated entity, compares only near-identical values, and offers no custom matching rules. A duplicate that slips past the creation check lives on in the base unnoticed.
How does the Duplicates No More app work?
The app embeds into day-to-day CRM work: the check runs when a manager moves a card through the pipeline or edits it. When a duplicate is found, the entity does not move on until the duplicate is deleted or merged. It supports bulk scanning of the whole base and two merge modes: automatic for records without conflicts, and manual review when a person should decide.
What is inside
- Duplicate checks on pipeline moves and on card edits
- Stage transitions blocked until the duplicate is merged or deleted
- Bulk scanning of leads, deals, contacts and companies
- Automatic merging without conflicts plus manual review of disputed records