Bitrix24 to BI: Automated Data Export Setup

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.

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1361
  • 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

Every week, managers spend up to 4 hours manually exporting reports from Bitrix24. The head of sales expects a funnel summary — but data has to be gathered from Excel, CRM, and email. We automate this process: we set up a direct ETL pipeline from Bitrix24 into your BI system. Dashboards update automatically, saving significant time and resources for a sales department. Typical savings: $2,000 per month in manual reporting time.

Problems We Solve

Manual data export and transformation. One request from a manager takes 1–2 hours to prepare. If breakdown by managers or periods is needed — another hour. Typical loss: up to 4 hours per week per manager. We automate the entire process, achieving 80% reduction in reporting time.

Limitations of the built-in BI connector. It is available in the "Professional" plan and above, but has a fixed set of fields — no custom fields, no derived metrics. Updates are once per hour. This is insufficient for real-time dashboards. For Bitrix24 Power BI integration, we recommend REST API.

Complexity with custom data. Custom fields in Bitrix24 have technical IDs (UF_CRM_1678901234), and stage/assignee IDs need to be replaced with names. During transformation, we convert everything to a readable format and compute required metrics.

Incremental Loading: How It Works

Incremental loading is key to performance. Instead of fetching all records each time, we only request those with DATE_MODIFY later than the last successful sync. For the initial load, we do a full fetch with pagination of 50 records (REST API limit). Typical volume: up to 50,000 deals per sync, execution time under 5 minutes. Incremental loading is 10x faster than full loading for large data volumes.

Why REST API Over BI Connector?

Let's compare export methods for Bitrix24 BI connector:

Method Flexibility Speed Update Cost
REST API Full control: any fields, any transformations Depends on volume (up to 2 requests/sec) Configurable (from 5 minutes) Free, but requires developer
BI connector Only fixed set of fields Instant for available datasets Once per hour Included in Professional plan
Webhooks Only events, no history Instant Real-time Free

REST API gives 3x more available fields than the BI connector and allows building any reports. We use it in 80% of projects.

ETL Pipeline: Extract, Transform, Load

Extract. A PHP (8.1+) script calls methods crm.deal.list, crm.lead.list, crm.activity.list. We use date-modified filter — only updated records are fetched. Error handling: retry on timeouts, logging.

Transform. Raw data contains IDs, dates in different formats, and multiple fields. At this stage:

  • Replace stage/assignee IDs with names from reference tables;
  • Normalize dates to ISO format;
  • Unfold multiple fields (e.g., contacts) into separate rows;
  • Compute derived metrics: deal duration, stage-to-stage conversion.

Load. Transformed data is written to PostgreSQL or ClickHouse. Table structure: fact tables (deals, activities) and reference tables (managers, stages). For deleted records — periodic ID reconciliation.

Example pipeline configuration via cron
# Every hour: incremental load deals
0 * * * * php /path/etl/deals.php --incremental >> /var/log/etl.log 2>&1
# Every Sunday at 3:00: full sync of reference tables
0 3 * * 0 php /path/etl/dictionaries.php --full >> /var/log/etl.log 2>&1

How to Set Up Export in 5 Steps

  1. Audit of current reports and data sources.
  2. Selection of the optimal export method (REST API / BI connector / combination).
  3. Development of ETL pipeline with incremental loading and error handling.
  4. Design of warehouse structure for required reports.
  5. Connection of BI system and creation of basic dashboards.

Update Frequency

The pipeline runs on a schedule: cron, Airflow, or Bitrix24's built-in scheduler. Typical frequency is every 30–60 minutes for operational dashboards, once per day for analytics. We configure failure monitoring and notifications via Telegram/Slack.

Typical Dashboards and Metrics

Dashboard Metrics
Sales funnel Stage conversion, average deal size, deal duration
Manager activity Calls, emails, meetings per period
Plan vs fact Revenue plan fulfillment by department

These sales metrics dashboards provide real-time insights.

What's Included

  • Audit of current reports and data sources
  • Selection of optimal export method (REST API / BI connector / combination)
  • Development of ETL pipeline with incremental loading and error handling
  • Warehouse structure design for required reports
  • Sync schedule and monitoring setup
  • BI system connection and basic dashboard creation
  • Field mapping and data structure documentation
  • Team training (optional)
  • 30-day post-launch support

Timelines and Guarantees

A standard project takes 5 to 15 business days. Pricing is individually assessed after audit. We guarantee stable pipeline operation: automatic retries on failure, monitoring, configuration backups. Our experience includes over 50 Bitrix24 integrations, including with 1C, CommerceML, and REST API. Significant cost savings after implementation — over $2,000 per month for mid-size sales teams.

Checklist of Common Mistakes

  • Ignoring deleted records (need ID reconciliation)
  • Exceeding REST API limits (need request queue)
  • No monitoring: failures can go unnoticed
  • Skipping custom fields in transformation

From Bitrix24 documentation: "REST API allows exporting up to 50 records per request, but with pagination you can get up to 50,000 records per sync."

Request a consultation — we'll assess your Bitrix24 data export to BI scenario within a day and provide a roadmap. Write to us, and your Bitrix24 data will speak the language of your business.

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Type Purpose Key Feature
Intranet Internal communications and services News, phone directory (sync with AD), meeting room booking, IT requests via BP
HR portal HR management and development Profiles, KPI/OKR on custom HL blocks, training, electronic document flow
Knowledge portal Documentation and regulations Categorization, tags, ratings, subscriptions to updates
Extranet Work with partners and contractors Granular permissions via CGroup and extranet module, access without VPN
Holding portal Management of multi‑company structure Separate workspaces, consolidated reporting, cross‑cutting BPs

Additional integrations that deliver real value:

  • Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
  • IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
  • Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
  • EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

  • role model via CGroup and section‑level permissions;
  • two‑factor authentication (OTP, Yandex.Key, SMS);
  • audit of all actions (b_event_log);
  • TLS encryption for transmission and disk encryption;
  • full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

Stage Duration What we do
1. Audit 2–3 weeks Interviews, process analysis, architecture, integration plan
2. Setup and customization 3–6 weeks Structure, roles, BPs, branding (CSS template)
3. Integrations 2–4 weeks 1C, AD, email, telephony, EDI
4. Data migration 1–2 weeks Documents, directories, employees from current systems
5. Training and pilot 1–2 weeks Administrators, key users, pilot of 20–30 people
6. Scaling 2–4 weeks Connecting departments, fine‑tuning based on feedback
  1. Audit — we record current processes, measure time losses.
  2. Design — choose portal type, plan integrations.
  3. Implementation — configure business processes, permissions, interface.
  4. Test — pilot group tests scenarios, we fix issues.
  5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

  • Project documentation: architecture, integration scheme, business process diagrams.
  • Configured portal with all integrations (1C, AD, telephony, EDI).
  • Business process descriptions and instructions for administrators and users.
  • 30 days of technical support after launch.
  • Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.