🇷🇺 A product of the Russian company 1C-Bitrix

Bitrix24 in Ukraine:
we do not implement it

Bitrix24 is developed by 1C-Bitrix, a company registered in Russia. WDP deliberately stopped any new implementations of this product in February 2022. But if you already run Bitrix24 — we help you exit.

Migration to Uspacy / Pipedrive / NetHunt / KeyCRM
Consulting on architecture and business processes
Audit of your current Bitrix24 before the migration
New Bitrix24 implementations — we do not do them
TL;DR

Bitrix24 and the WDP position —
in short

System facts first, our position second. No evasive maneuvers.

In short
  1. Bitrix24 is an all-in-one suite: CRM, tasks and projects, chats and video calls, a website builder, HR tools. The vendor claims 15 million organizations and roughly 600 marketplace apps.
  2. A product of Russian origin: 1C-Bitrix was founded in Russia in 1998; international distribution via US and Cyprus entities (the Alaio rebrand, 2025–2026) does not change the origin.
  3. Since April 2023 — under Ukrainian state sanctions until 2033 (Decree No. 227/2023); on June 1, 2023 bitrix24.ua officially ceased operating in Ukraine.
  4. WDP has done no new Bitrix24 implementations since February 2022. No partner status. A matter of principle, reinforced by sanctions compliance.
  5. What we do: migrations from Bitrix24 to Uspacy, Pipedrive, NetHunt, or KeyCRM — from 3 weeks. History moves via the REST API: the standard CSV export loses comments, entity links, and files.
Strengths

What Bitrix24 has —
and why companies leave it

Analysis without marketing: the real capabilities of the system and the lock-in mechanics. We know it well enough to get your data out.

01
A genuinely broad all-in-one

CRM, tasks and projects, chats with video calls, online docs, a website and online-store builder, HR tools — in one product, in 18 languages. This breadth is exactly why companies buy Bitrix24 "just in case" — and then use a fraction of what they pay for.

From WDP practice From our pre-migration audits: deals, contacts, and tasks are what actually lives in a portal — the other modules are dead weight. A custom field filled in less than 10% of records is a candidate for the trash bin, not for transfer.
02
Free plan with unlimited users

Unique among major CRMs: the Free plan has no user cap. It is heavily gated though: chat history is kept for 30 days, the REST API and webhooks (instant system-to-system notifications) are unavailable, automation rules do not run. Critical for an exit: API-based data export requires temporarily returning to a commercial plan.

03
BP Designer — a full business-process engine

The visual process designer goes deeper than the automations of most CRMs; fall 2025 added a no-code (no-programming) Workflow Automation Studio. The flip side is lock-in: templates export only to the .bpt format, readable solely by another Bitrix24. Processes transfer to no other system — we rebuild the logic with the target CRM's native tools.

04
Mature REST API: batch and an offline event queue

The batch method runs 50 calls as 1 request — with list methods that is up to ~2,500 records per hit. Rate limits follow a leaky-bucket model: a 50-request burst, then 2 req/s (Enterprise — 250 and 5); exceeding it returns HTTP 503. The migration takeaway: a full export of tens of thousands of deals is feasible, but it needs pacing, not a naive script.

From WDP practice Via the REST API we transfer what the standard CSV export does not carry: deal comments and timelines, contact ↔ company ↔ deal links, files. Active deals plus those closed within the last 1–2 years move into the new system; the rest goes to a cold archive outside the CRM.
05
Aggressive AI rollout: CoPilot → Bitrix24 Intelligence

CoPilot transcribes and summarizes calls, fills CRM fields from conversations, scores sales-script adherence; the fall 2025 release added AI agents, MCP support, and voice-to-task creation. These are shipping features, not announcements — an honest trade-off we weigh before any migration.

06
On-premise edition and a high customization ceiling

A self-hosted edition is rare among SaaS CRMs — which is why some Ukrainian companies still run legacy instances (on limited licenses after June 1, 2023). Up to 1,016 custom fields per CRM entity: field inventories at migration are large, so we transfer via mapping triage, not 1:1.

Кому підходить

Who should exit now —
and whom we will not help

Honest segmentation, no universal answers. If this is not your case — we say so upfront.

Migrating off Bitrix24 is due if

  • You are under Ukrainian jurisdiction: state sanctions until 2033 and the official service shutdown on June 1, 2023 make this a compliance risk, not just an ethical question
  • You pay for the whole bundle but actually use only the CRM — the classic "10% of capacity" picture from our audits
  • Your data is effectively locked in: a Free plan without API access, processes in BP Designer, history in chats — you need a designed exit, not a CSV
  • You need deal and communication history preserved in the move — the standard export does not carry it; we transfer it via the REST API

Not our case

  • You are looking for a contractor to implement a new Bitrix24 — we have not done that since February 2022, no exceptions
  • You want to "improve" Bitrix24 and stay on it for years — we only consult within an audit and an exit plan
  • You are choosing a new CRM from scratch rather than leaving Bitrix24 → start with the Uspacy, Pipedrive, NetHunt, or KeyCRM profiles
Architecture

The architecture of
a Bitrix24 exit

An export is a project with a data model, API limits, and triage. Four nuances that define the budget and the timeline.

"Dump a CSV" and "design a migration that keeps the history" are two different projects. We do the second one.

EXIT One-way export
Stock migration tools only work into Bitrix24
Bitrix24's own migration apps are one-directional: they bring data into the system, never out. An exit is mostly REST API work: an entity inventory, field mapping, pacing under rate limits; for Uspacy, a native importer covers part of the entities. The API is unavailable on the Free plan, so an exit plan often includes temporarily reactivating a commercial plan.
API Leaky-bucket limits
Exporting 30,000+ deals is a pacing problem, not a feasibility one
A 50-request burst, then 2 req/s (Enterprise — 250 and 5); exceeding it returns HTTP 503 QUERY_LIMIT_EXCEEDED; a method gets blocked if its cumulative execution time exceeds 480 s within 10 minutes. Batch packs 50 calls into 1 request — up to ~2,500 records per hit via list methods.
DATA What stays behind
Chats, task comments, and BP processes stay inside
The internal messenger is effectively not exportable; the standard task export does not include comments; BP Designer templates are readable only by another Bitrix24 (.bpt). We design for this upfront: what gets archived, what gets rebuilt in the target system, what is consciously left behind.
SCOPE Data triage
A migration is a chance to clear data debt, not to move the mess
Up to 1,016 custom fields per entity means large field inventories. The triage rule: active deals plus those closed within the last 1–2 years move into the new system; the rest goes to a cold archive (Excel, BigQuery, a portal backup) outside the CRM.
FAQ

Frequently asked questions
about Bitrix24

Answers to what people actually ask — on calls, in Telegram, in emails. No fluff.

Not ready for a call?

Take the Bitrix24 migration checklist with you

18 steps that save your data: inventory, field mapping, the three classic loss points, day X. A 2-page PDF, print-friendly.

The PDF opens right away. The email just tells us who found it useful — no newsletters.

Planning to leave Bitrix24?

Free 30-minute consultation. We'll define where to migrate, what survives the move, and how long it takes.