Automated Duplicate Merging in Bitrix24 CRM

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Showing 1 of 1All 1626 services
Automated Duplicate Merging in Bitrix24 CRM
Simple
~1 day
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1362
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    949
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    695
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    834
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    733
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1076

Automated Duplicate Merging in Bitrix24 CRM

A CRM with 12,000 contacts and 40% duplicates takes weeks to clean manually. Automated merging via the API on PHP reduces the process to a few hours. But without proper rule configuration and relation handling, you risk losing activity history and deals. The mechanism uses the CCrmEntityMerger class, which transfers related objects and removes absorbed records. The order of operations is critical — the wrong sequence leads to broken references. Our engineers configure merges to keep history intact. On a recent project with 15,000 contacts and 35% duplicates, we cut merge time from two weeks to three hours, achieving 98% data integrity. Proper rules save up to 80% of the time, and the fix pays for itself within a month.

What do default merge rules do?

In CRM → Settings → Duplicates → Merge Rules, you define the logic for choosing values when fields conflict:

Rule Behavior
Primary record Takes the value from the selected 'main' card
More filled Takes a non-empty value; on conflict, from the primary
Merge Applicable for multiple fields (phones, email)
Last modified Takes the value from the record with a later modification date

For most tasks, set key identifiers (INN, phone, email) to 'merge'; status fields (responsible, stage) to 'primary record'; text notes to 'more filled'. If you are unsure, our engineers will help tailor the configuration to your CRM.

Programmatic merge via API

For mass cleanup, manual mode is not feasible. The REST method crm.contact.merge allows automatic merging of thousands of contacts:

// Merge: record 1001 absorbs 1002 and 1003
CRest::call('crm.contact.merge', [
    'id'      => 1001,
    'victims' => [1002, 1003],
    'fields'  => [
        'PHONE' => 'merge',
        'EMAIL' => 'merge',
        'ASSIGNED_BY_ID' => 'primary',
    ],
]);

For companies, use crm.company.merge analogously. The method is synchronous; when merging more than 5 victims, it may time out — split into pairs. In the on-premise version on PHP:

$merger = new CCrmEntityMerger(CCrmOwnerType::Contact);
$merger->Merge(
    1001,
    [1002, 1003],
    $fields,
    $errorMessage
);
Steps for a successful merge
  1. Create backups of tables b_crm_contact, b_crm_company, b_crm_deal, b_crm_activity, b_crm_timeline.
  2. Identify the primary record (most complete or with the highest number of deals).
  3. Run the merge for small victim groups (2-3 records) first.
  4. After completion, check related objects: deals, activities, tasks.
  5. For smart processes, update bindings via crm.item.update.

What does automation transfer?

The merge automatically transfers:

  • Deals (the CONTACT_ID field is updated)
  • Activities: calls, emails, meetings from b_crm_activity
  • Tasks via the b_tasks_member link
  • Timeline (b_crm_timeline)

What is NOT transferred automatically?

  • Links through user-defined smart process blocks (SPAs) — a separate update script is needed
  • External links from third-party integrations (data in custom tables)
  • Chat history in Open Lines — history is bound to the line, not the contact

How to minimize data loss risks?

Always back up the relevant tables before a mass merge. There is no built-in rollback — after a merge, absorbed records are marked deleted (DELETED=Y in b_crm_contact) but remain physically in the database for a few days until the recycle bin is cleared. The recovery window is: CRM → Settings → Recycle Bin — absorbed cards are available for restoration for 30 days (configurable). After restoration, links to the main record are not recreated — you must reassign them manually.

Manual vs. API merge comparison

Criterion Manual merge API merge
Speed ~2 minutes per pair 10 pairs per second
Volume Up to 50 records per session Thousands of records
Accuracy High but operator-dependent Predictable, rule-based
Control Full visual control Automatic, requires verification

API merging is 10× faster than manual and can handle up to 95% of duplicates in one pass. If your database exceeds 10,000 records, API merging is the only reasonable option. Order a merge setup from our engineers — they will adapt the rules to your business.

Why is testing the merge important?

Gartner notes that data cleaning improves forecast accuracy by 60%. Testing on live data with a backup uncovers problems before go-live. We always check activity transfer on a cloned database. Get a consultation on CRM optimization — our specialists will show you how to avoid data loss.

What is included in duplicate merge setup

  • Analysis of the current database for duplicates and their types
  • Configuration of merge rules according to your business processes
  • Testing on live data with a backup
  • Training your staff on duplicate handling
  • Documentation of the recovery procedure
  • 30-day post-setup support

We have been working with Bitrix24 for over a decade and have delivered more than 100 CRM cleanup projects. Our certified engineers guarantee data safety. Contact us for a free consultation — we will advise and select a strategy.

How to ensure CRM implementation success?

We have been working with Bitrix24 for over 10 years — during that time we have completed 500+ projects. Every second one starts with the same problem: a company buys CRM, sets it up "by the book," and three months later managers fill two out of twelve fields, deals stall at "Negotiations" for months, and management cannot extract analytics. The root is not bad software — it's the approach. CRM is configured without auditing real processes, without considering staff objections, and without a step-by-step automation plan. In this article — a step-by-step guide on how we avoid this.

All specialists are certified by 1C-Bitrix, the methodology is proven on hundreds of cases. 1C-Bitrix is a platform that, when paired with Bitrix24, provides real end-to-end analytics if configured correctly.

Reality of CRM implementations: 80% fail to deliver results

Why do employees sabotage CRM?

Managers are accustomed to Excel and notepads — they perceive CRM as total control. Our solution: involve key employees at the design stage, show personal benefits — automatic reminders, ready-made proposal templates, less routine. We train on real scenarios, not abstract examples. Resistance drops 4 times faster than with "command" implementation.

How to prevent incomplete data entry?

Mandatory fields are filled, others are ignored — familiar picture? We solve it on three levels:

  • Set mandatory fields per funnel stage (only relevant data at each stage).
  • Implement auto-fill from UTM tags, email parsing, data from open databases.
  • Remove redundant fields — fewer fields, higher quality.

According to our practice, field optimization reduces omission rates by 70% within the first month.

How to design funnels correctly?

Too many stages, no transition criteria, duplicate stages — typical mistakes. We design the funnel based on reality: how sales actually work, not as written in textbooks. We use CRM data from the first 2 weeks of audit to identify real stages and loss points. This shortens the deal cycle by 25–40%.

What automation should be done first?

We set up robots and business processes from day one — so the team immediately feels the difference. For example, lead distribution, sending emails after status changes, creating tasks for colleagues. Companies that implement automation at the start achieve plan targets 3 months faster.

What Bitrix24 features accelerate sales?

  • Inquiries from all channels (phone, email, messengers, forms) are captured automatically.
  • Leads are created and distributed without manual intervention.
  • Visual kanban with custom stages — drag a card to the next stage, an email is sent automatically, a task is created.
  • Omnichannel: unified window for telephony, email, WhatsApp, Telegram, Viber, VK, Instagram, online chat.
  • Robots and business processes: mailings, document generation, reminders, escalations — no coding required.
  • Analytics: funnel, conversions, lead sources, manager workload, average handling time.

What does integrating a 1C-Bitrix website with Bitrix24 CRM provide?

Synergy of the two products yields measurable results, and we implement it through direct data exchange. Site forms transfer leads to CRM instantly with full UTM markup — you see where the client came from. Online chat connects via open lines: a visitor writes on the site, the manager responds from CRM. Orders in the store based on infoblocks v2.0 become deals with full purchase history, enabling cross-selling. Call tracking with number substitution links calls to advertising channels. We use CommerceML to exchange data with 1C Trade Management/ERP: nomenclature, stock balances, prices — synced via agents without manual intervention. End-to-end analytics collects advertising costs, visits, leads, sales in one report — ROI per channel. For non-standard logic, we use REST API and high-load blocks to store arbitrary data (e.g., tech support interaction history). In one project, we configured this bundle for a retail chain: 1C cash register integration with CRM created contacts automatically upon loyalty card purchase, and CRM marketing via Bitrix24 increased repeat purchases by 18% in six months.

How we set up CRM: the process

  1. Audit. We analyze how sales work currently. Where are leads lost? Which channels bring clients? We form recommendations before technical implementation.
  2. Design. Multiple funnels for different directions, custom fields, mandatory stages and transition conditions. Structure reflects the real process.
  3. Integrations. Connect to website, telephony, email, messengers, Yandex.Direct, Google Ads, 1C.
  4. Custom modules. When standard is not enough — applications for Bitrix24: specific reports, non-standard business logic, integrations with industry systems.
  5. Migration. Transfer databases from amoCRM, Megaplan, Salesforce, HubSpot, Excel. Relationships, communication history, attachments — everything intact.
  6. Training. Trainings tailored to your configuration, video instructions, documentation.

What is included in the work?

Deliverable Description
Technical documentation Funnel scheme, robot settings, field structure, integration plan
Access and configurations List of integrations, API keys, logins/passwords (provided under NDA)
Team training 2–3 webinars tailored to your configuration, video instructions, cheat sheets
Post-implementation support 2 weeks of incident management + regular usage audits

Cloud or on-premise: which to choose?

Parameter Cloud (SaaS) On-Premise
Time to start 1–2 days 1–2 weeks
IT requirements None Server and admin required
Data control Limited Full
Customization Standard limits Unlimited
Best for Teams up to 100 people, standard processes Large companies, strict security requirements

Comparison: the cloud version is 2–3 times cheaper initially, but for B2B companies with large data volumes, on-premise pays off in 1.5–2 years due to no per-user subscription fee.

Metrics we track for your business

  • Funnel stage conversion. If 80% are lost at the proposal stage — the problem is pricing, not managers. Norm: 5–15% for B2B, 1–5% for high-ticket B2C.
  • Lead response time. A 5-minute response increases conversion 10x compared to a 30-minute response. We set alerts — if a manager doesn't respond within 15 minutes, the lead is reassigned.
  • LTV. CRM segments clients by lifetime value — managers focus on the most valuable.
  • Average deal cycle. If it increases, something is broken. Reasons for rejections are gold for product and script adjustments.

Our case studies

Manufacturing company (B2B). A plant with high annual turnover. Leads were lost in email; management only learned about large deals post-factum. We set up automatic inquiry capture, a funnel "qualification → calculation → proposal → approval → contract → payment," and robots that generate proposals from templates. Conversion increased by 23%, lead processing time dropped from 4 hours to 20 minutes. Manager payroll savings exceeded $1,000 per month due to reduced routine.

IT service company. Three funnels: new clients, upselling, tenders. Auto-generation of contracts and invoices, integration with Jira — after signing, tasks automatically appear in the development department. Management received a weighted revenue forecast with 90% accuracy. The project paid off in 4 months.

Implementation timeline and cost

Scale Timeline What's included
Basic 1–2 weeks Funnel, telephony, email, database import
Standard 1–2 months Custom funnels, automation, website and 1C integrations
Comprehensive 2–4 months Multiple funnels, custom modules, training, end-to-end analytics

The cost is calculated individually based on your scope of work. After implementation — tech support with SLA (response from 1 hour), regular usage audits, and feature development.

Ready to discuss your situation? Contact us — we'll conduct a free audit of your current CRM within 2 days and propose an implementation architecture with a result guarantee. Request a consultation — we'll show you in numbers how much you'll save with proper setup.