Bitrix24 vs amoCRM (Kommo) vs a Custom CRM: Which One Fits a Business in Uzbekistan

When a company in Tashkent outgrows spreadsheets and a shared Telegram group, the shortlist usually comes down to Bitrix24 vs amoCRM. A third option, a CRM built around your own process, appears in few comparisons. There is no single best CRM for business in Uzbekistan, only a better fit: Bitrix24 typically suits a company that wants one workspace for sales, tasks and internal communication; amoCRM, sold internationally as Kommo, typically suits a sales team that works in messengers; and a custom CRM suits a process neither models well, or work where integration is the main job. Below, the three are compared on facts checked on the vendors' pages at the time of writing, on what changes in Uzbekistan (1C configurations, Telegram, the March 2026 personal-data rules) and on implementation effort. For pricing, see how much a CRM system costs.

Three different kinds of tool

The first two are products you configure; the third is a project you commission.

• Bitrix24 is a workspace with a CRM inside it: tasks, projects, chats and a contact centre sit alongside the sales pipeline. It comes as a cloud service and as an on-premise (self-hosted) edition installed on your own server; the official Uzbekistan site, bitrix24.uz, presents both.
• amoCRM is a cloud CRM built around the sales pipeline and conversations in messengers. As for amoCRM vs Kommo: in October 2022 the international version, whose accounts sat at amocrm.com, was renamed Kommo, and the vendor said the platform itself would stay the same. amoCRM still operates under its own name at amocrm.ru, so ask a partner which of the two they sell, and check features against that one.
• A custom CRM is software built around your own process, data model and integrations, hosted where you choose.

Bitrix24: where it fits and where it falls short

Bitrix24 typically suits companies that want one tool for more than sales. Its strengths:

• Breadth. One system for sales, the contact centre, tasks and internal chat.
• Cloud or on-premise. According to the Bitrix24 helpdesk, the cloud edition needs no installation, updates automatically, keeps data in the vendor's data centres and is customised through the REST API. The on-premise edition keeps data on your servers and opens the source code, with the REST, Bitrix and D7 APIs, but needs installation, server administration and an annual licence renewal for updates and support. That is the Bitrix24 on-premise vs cloud trade-off: control against upkeep.
• Telegram. It connects through an Open Channel (Open Lines in the Russian interface): create a bot with @BotFather and paste its token into the channel settings.
• Telephony. Calls connect through a rented virtual number, a SIP connector to a cloud or office PBX, or a telephony app. It is not on every plan, so check yours and ask which options work with your operator in Uzbekistan.

Where it falls short:

• Complexity. The same breadth makes it a lot to learn, so onboarding usually takes longer.
• 1C in Uzbekistan. The official 1C connector lists supported configurations for Russia, Belarus and Kazakhstan only. If you run a 1C configuration localised for Uzbekistan, check with your 1C specialist whether the connector works with it, or plan custom integration work; see 1C integration with a website and CRM.

In the cloud edition each user picks their interface language; check which languages, including Uzbek, are offered.

amoCRM (Kommo): where it fits and where it falls short

amoCRM typically suits a sales team that works in conversations. Its strengths:

• A quick start. The product centres on the pipeline, so a sales team can usually start sooner than in a broader workspace.
• Messengers. Kommo's integrations include Telegram, WhatsApp Business and Instagram, some built in and some from third-party developers.
• Telephony, API and widgets. Calls connect through VoIP integrations, an API and widgets extend the product, and there is a mobile app.

Where it falls short:

• Cloud only. There is no self-hosted edition, so your data sits wherever the vendor keeps it; ask where that is for your account.
• Narrower scope. Projects and internal work are not its focus.
• 1C through widgets. Exchange with 1C comes from widgets and third-party modules. The ones we found are built for Russian 1C, such as a widget for the cloud version of 1C:Accounting 8, so check any module against your configuration.
• Dependence on add-ons. Many functions arrive as paid widgets from other developers, each a supplier to vet, pay and keep up to date.

When a custom CRM is the better choice

Bitrix24 or a custom CRM, amoCRM or a custom CRM: the answer depends on whether the ready-made model matches how your business works. A custom build usually wins when:

• The CRM is really an operations system. Dispatch, field service and installations revolve around jobs, crews and schedules rather than deals.
• Most users are light-touch. Drivers or technicians who only update a status need a narrow screen or a Telegram bot, not a full CRM.
• Integration is the core requirement. Deep exchange with your 1C configuration, Telegram or local payment providers matters more than standard features.
• You need the data on servers you control.

The cost is effort as well as money: discovery, build time before first use, someone to maintain the system and a budget for later changes. See CRM development and the CRM cost guide. If a bought CRM fits the sales side but not the rest, you can keep it and connect or automate around it through business process automation and system integration.

CRM and personal data in Uzbekistan: what the law asks in 2026

A CRM is mostly personal data, and in Uzbekistan the rules on where it may be stored changed in March 2026.

The 2021 rule. Law ZRU-666 of 14 January 2021, in force from April 2021, added Article 27-1 to the Law 'On Personal Data'. It required personal data of Uzbek citizens processed using information technologies to be stored on servers physically located in Uzbekistan and registered in the State Register of personal data bases. Many companies moved to local hosting or on-premise CRMs as a result.

The rule since 27 March 2026. Law ZRU-1125 of 26 March 2026 rewrote Article 27-1 and took effect on publication, on 27 March 2026. Only biometric data, genetic data and data of users of telecom operators working in Uzbekistan must now be stored in Uzbekistan, and databases holding these categories must be registered in the State Register. Other personal data, which usually includes typical CRM contacts, may be stored and processed abroad if one of three conditions is met:

1. the foreign country is recognised as providing adequate protection;
2. standard contractual clauses or binding corporate rules meet requirements approved by the authorised body;
3. the processing complies with international standards from a list approved by the authorised body.

The list of countries with equivalent protection is set by the Cabinet of Ministers: Resolution No. 415 of 29 July 2026, in force since 3 August 2026, lists 49 countries and territories. The requirements for standard contractual clauses and binding corporate rules, and the list of international standards, come from the authorised body; the resolution gave three months for them, so check their current status. Many pages online still describe the 2021 rule.

In practice:

• Ask the vendor where your account's data is stored.
• With on-premise Bitrix24 or a custom CRM hosted in Uzbekistan, where the data sits is your decision.
• Ask a lawyer which of the three conditions you would rely on, and whether any data in your CRM falls into a localised category. This is a plain-language summary, not legal advice.

Integrations that decide the choice in Uzbekistan

• Telephony. Your operator or PBX, with call recordings attached to the client record.
• Telegram. A bot or an account, with the history in the client card rather than on a manager's phone; see Telegram bots for business.
• 1C. Which configuration and version you run, and which system owns which data; see the 1C integration guide.
• Local payment providers. Check whether a ready integration exists for your provider and CRM; if not, it is API work.
• Website forms and marketplaces. Leads and orders should arrive without retyping.

For each, ask: is it a ready connector, a third-party widget or custom work, who supports it, and what happens after a 1C or CRM update? Scope this system integration work before you choose, not after.

Bitrix24 vs amoCRM vs a custom CRM: decision table

Based on vendor pages at the time of writing; check anything decisive before you sign.

For the cost side, see the CRM cost guide.

• Choose Bitrix24 cloud if you want one vendor-run workspace for sales, tasks and internal communication.
• Choose Bitrix24 on-premise if you want the same with data on your servers, and have someone to run the server and renew the licence.
• Choose amoCRM (Kommo) if your CRM is mainly a sales pipeline fed by messengers and calls, and the integrations you need exist.
• Choose a custom CRM if the process is operations rather than sales, most users need a narrow screen, or integration is the core of the job.

Migration and implementation: where the effort goes

Whichever option you choose, effort goes into:

• Process mapping, exceptions included, before configuring anything.
• Cleaning data: duplicates, phone numbers in several formats, names in both Latin and Cyrillic. Using the taxpayer identification number (STIR, or INN in Russian) as the company key removes many duplicates.
• Rebuilding pipelines and automations, which rarely transfer intact.
• Permissions: who sees which clients, deals and reports.
• Integrations, each tested with real data.
• Training for managers and occasional users.
• A parallel run until old and new numbers agree.
• An internal owner accountable for how the CRM is used.

Migration tools help but have limits. One Bitrix24 Market app for moving from amoCRM states that it cannot guarantee the transfer of automations, roles and access rights, telephony, chat histories and complex custom fields, and that it does not load files directly. Plan to rebuild or move those separately.

Checklist: before you sign up or start a build

• A written list of must-have functions.
• Who the users are, and how many need full access.
• Which interface languages, including Uzbek, your staff need.
• Which messengers and telephony the CRM must work with.
• Your 1C configuration and version.
• Where the data must or may be stored, with the legal check done.
• The export format, and a test export including history and files.
• A trial or pilot with your own data.
• A named internal owner.
• A migration rehearsal.
• A plan for changes after go-live.

How BITS can help

Through IT consulting we help companies choose between a ready-made platform and a custom build, and recommend a ready-made one when it fits. We build custom CRMs as CRM development projects, with process mapping, data migration and a parallel run, and we connect CRMs with 1C, telephony and Telegram as system integration work. See all our solutions. After a discovery call we send a quote; contact us to start.