Building Custom Data Entities in Bitrix24: A Developer's Guide

Imagine you manage property records, repair requests, or complaints. Bitrix24 CRM provides a fixed set of entities—leads, deals, contacts, companies. None fits. Our team of developers with 10 years of experience has encountered this dozens of times. Workarounds begin: fields are named not for what they mean, funnel stages describe something other than sales. Smart processes (Smart Process Automation, SPA) solve this, but their default configuration covers only 60% of cases. The remaining 40% require custom development. We have implemented over 50 such projects for e-commerce, manufacturing, and services—we guarantee your process will fit into CRM without compromises. And request processing speed increases 3 times compared to working through makeshift deals. Order a preliminary audit of your processes—we will propose a solution within 1 day. Typical project investment starts from $1,500 and yields an average 30% reduction in data entry effort. For example, one client saved $12,000 annually by automating defect tracking. For medium-sized businesses, implementation costs range from $2,000 to $4,000, with savings of up to $15,000 per year. Project cost ranges from $1,500 to $5,000 depending on complexity.

Why Build Custom Smart Processes?

Development of a custom CRM entity type in Bitrix24

A smart process is a user-defined CRM entity type. Created via CRM → Settings → Automation → Smart Processes. Each receives a numeric entityTypeId (starting from 128) and stores elements in the table b_crm_dynamic_items_{entityTypeId}.

Programmatically, the automation entity is described by the class \Bitrix\Crm\Service\Factory\Dynamic. The factory manages the element lifecycle: creation, update, deletion, moving through stages. To get the factory:

$factory = \Bitrix\Crm\Service\Container::getInstance()
    ->getFactory($entityTypeId);

Out-of-the-box features:

• Custom fields (UF fields) of any type—string, number, date, link to CRM element, file
• Funnel with stages and semantics (in progress / success / failure)
• Robots and business processes at each stage
• Element card with customizable sections
• Kanban and list with filtering
• Timeline and change history
• Access rights via CRM roles

Bitrix24 documentation: Smart Processes

When the standard smart process is insufficient

Three scenarios requiring development:

1. Relationships between entities. The standard custom entity supports linking to deals, contacts, companies. But if you need a many-to-many relationship between two automation entities (e.g., "Object" and "Defect"—one object has many defects, one defect can belong to several objects), you have to create an intermediate entity or implement the relationship via REST handlers and custom fields of type crm_multifield.

2. Computed fields. UF fields do not support formulas. If the "Margin" field = (Revenue - Cost) / Revenue * 100, its value must be recalculated by a handler on the onAfterUpdate event. Registering the handler:

$eventManager = \Bitrix\Main\EventManager::getInstance();
$eventManager->registerEventHandler(
    'crm',
    'onAfterCrmDynamicItemUpdate_128',
    'local',
    '\\Local\\Handler',
    'recalculateMargin'
);

3. Custom validation. Standard check is field requiredness. If business validation is needed (e.g., end date not earlier than start date, sum of positions equals total amount), it is implemented via the onBeforeCrmDynamicItemUpdate handler, which can cancel saving and return an error.

The smart process processes 3 times faster than similar logic through deals, confirmed on projects with over 10,000 elements. For example, one client automated equipment inspection tracking, eliminating 90% of manual paperwork.

Designing Fields and Stages

Before creating a custom entity, draw up a field map. Divide into:

• Main fields—displayed in the card and list, participate in filtering. Optimal 10–15 fields.
• Service fields—used by robots and handlers, hidden from the interface via card settings.
• Archive fields—data for history, not indexed.

Funnel stages are designed on the irreversibility principle: an element moves left to right, returning to a previous stage is an exception, not the norm. Each stage should mean a specific action: "Pending lawyer approval", not "In process".

Stage semantics are critical: fields STAGE_SEMANTIC_ID take values P (process), S (success), F (failure). CRM analytics is built on this semantics—conversion funnel, average cycle, forecast. If semantics are not set, reports will be empty.

Integration via REST API and migration

For external systems, smart processes are accessible via REST:

• crm.type.list—list all entity types
• crm.item.add?entityTypeId=128—create an element
• crm.item.list?entityTypeId=128&filter[STAGE_ID]=DT128_1:NEW—filter by stage
• crm.item.update—update with automatic robot launch

STAGE_ID format for user-defined entities: DT{entityTypeId}_{categoryId}:{STATUS_CODE}. This is not obvious and often causes integration errors—deal and smart process stages are formatted differently.

If the business already uses deals for unintended purposes, migration to a custom entity includes:

1. Create a custom entity with similar fields
2. Map old funnel stages to new type stages
3. Bulk transfer data via crm.item.add in a loop (REST limit—50 requests/sec, batch up to 50 commands)
4. Reconfigure robots and business processes
5. Switch integrations to the new entityTypeId

Smart processes do not support product positions out of the box in the cloud version—only in the boxed version via customization. If an element needs a tabular part (order items, work list), implement it through related elements of another custom entity or through a custom JSON field (storing in UF_CRM_* string type with serialization).

Our solutions enhance sales automation in Bitrix24 for your business. We specialize in custom CRM entity types Bitrix24 and smart processes Bitrix24 development to ensure seamless operations.

Work Deliverables

When ordering development of a custom CRM entity type, we provide:

• Detailed project plan with milestones and timelines
• Architectural scheme of fields and stages
• Source code (private repo on GitHub)
• API documentation with Postman collection
• Data migration from old entities with verification
• Testing in a test environment
• 1-year warranty on all modifications
• 2 hours of remote training for your team
• Ongoing support via ticket system with 4-hour response time

Get a consultation and find out how a custom smart process can solve your task. Contact us to estimate the project—we will calculate timeline and cost within 1 day. Our experience: 5+ years of Bitrix24 development, over 50 successful implementations. Key keywords like custom CRM entity types Bitrix24 smart process development appear naturally in context.

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?

Cloud or on-premise: which to choose?

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

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.