Twenty vs amoCRM: Which CRM Should an IT Company Choose in 2026

If an IT company sells B2B projects with a long cycle, Twenty is usually the better fit: an open CRM with a flexible data model, an API and the option to keep the database on a server in Kazakhstan. If sales are built on a high inbound flow through WhatsApp, Instagram and calls, amoCRM is stronger: messengers and telephony work out of the box. Most borderline cases come down to one question: how many inquiries arrive per day, and through which channels.

This article is for founders, sales directors and heads of sales at IT companies in Kazakhstan. We compare the two CRMs across ten criteria, explain when to choose each and show how to migrate data from amoCRM to Twenty via CSV and the API.

In short: the fundamental difference

amoCRM and Twenty solve the same problem in different ways.

amoCRM is a cloud CRM built around the sales pipeline and communications. Its strength is speed: connect WhatsApp and telephony, set up the stages, and managers are working the same day. In Kazakhstan, it has many integrators and ready-made solutions.

Twenty is an open source CRM under the AGPL-3.0 license. It is a construction kit: custom objects, fields, views, workflows, an API and webhooks. You can deploy it on your own server or use it in the vendor’s cloud. It shines where the sales process is non-standard and the CRM needs to be part of the company’s overall system.

A detailed review of Twenty, with its data structure and cost of ownership, is in a separate article on Twenty CRM for IT companies in Kazakhstan.

Comparison across ten criteria

Criterion	amoCRM	Twenty
1. Delivery model	Cloud only	Cloud or self-hosted
2. Data storage	Vendor servers outside Kazakhstan	Your own server in Kazakhstan when self-hosted
3. Messengers	WhatsApp, Instagram, Telegram out of the box	Via an external service and the API
4. Telephony	Ready-made PBX integrations	Via webhooks and the API, nothing built in as of version 2.1
5. Automation	Automated actions at pipeline stages	Workflows on events and on a schedule
6. Data model	Deals, contacts, companies, custom fields	Custom objects, fields and relationships
7. API and extensibility	API and widgets	API, webhooks, a TypeScript apps framework
8. License price	Per user, in tenge through partners in Kazakhstan	Free self-hosted; cloud $9–19 per user as of October 2026
9. Administration	Vendor, with setup by an integrator	Cloud: vendor; self-hosted: your engineer
10. Ecosystem in Kazakhstan	Many integrators and ready-made solutions	Market expertise is still forming

The table shows that the choice is almost never made “on average”. Usually one or two criteria outweigh everything else: for some it is WhatsApp, for others it is storing data in the country or connecting to a task tracker.

Messenger sales and telephony

This is the main argument for amoCRM. If customers write in WhatsApp and Instagram, a manager needs to reply from a single window, see the conversation history in the deal card and not lose inquiries at night. amoCRM handles this natively.

In Twenty, you can build such a setup, but it is a project: a WhatsApp Business service receives messages, creates or finds a contact via the API and writes the activity to the card. It works, but it requires development, testing and maintenance. For an IT company with a few dozen B2B leads a month, this is overkill. For an online school or a service with a mass inbound flow, it is critical.

The story is similar with telephony. In amoCRM, integrations with popular PBXs are installed from a catalog. In Twenty, a call reaches the CRM through the PBX webhook and the API.

Data model and flexibility

Here Twenty has the advantage. IT companies rarely sell a “product”. They sell projects, retainers, licenses, pilots and support. A single client company may have several parallel deals, contracts and projects, and a partner may bring in some of the leads and earn a commission.

In Twenty, you create separate objects with relationships for this: “Project”, “Contract”, “Partner”. You can filter them, show them on a kanban board and build workflows around them. In amoCRM, the core unit is a deal in a pipeline, and everything else is described with custom fields and tags. For a simple process that is enough; for a complex one, workarounds appear. A typical example: a manager creates a second deal for the same client to reflect a support upsell, and six months later a revenue report cannot be built without manual reconciliation. In Twenty, an upsell is a separate deal linked to the same contract and project, and the report is built on relationships rather than on team conventions.

The second point is integrations. Twenty is open: API, webhooks, code on GitHub. If the CRM needs to exchange data with a task tracker, billing and an internal service, that is easier to do on an open system. We covered how such a setup works in our article on integrating a CRM and a task tracker.

Where data is stored and how you pay

Kazakhstan context. A CRM almost always contains personal data: names, phone numbers, emails and conversations with customer contacts. amoCRM stores data on the vendor’s servers outside the country. Self-hosted Twenty is deployed with a Kazakhstani hosting provider, and the database stays in Kazakhstan. If the company wants to store data in Kazakhstan, this is a strong argument. Payment differs too: amoCRM is sold through Kazakhstani partners in tenge, Twenty Cloud is paid by card in dollars, and self-hosted Twenty needs no license, only hosting under a contract in tenge.

Cost: what it is made of

Comparing only the per-user price is misleading. The two CRMs have different cost structures.

Cost item	amoCRM	Twenty Cloud	Twenty self-hosted
Licenses	Per user, price from a partner in Kazakhstan	$9 Pro or $19 Organization per user per month	$0
Infrastructure	Included in the subscription	Included in the subscription	Server and S3 storage in tenge
Implementation	Usually an integrator, separate from licenses	In-house or by a contractor	Deployment plus setup
Integrations	Many available in the catalog	Via the API, webhooks and development	Via the API, webhooks and development
Support	CRM administrator	CRM administrator	CRM administrator plus an engineer

Twenty prices are from the vendor’s website as of October 2026 with annual billing. As a benchmark, amoCRM in Russia costs about 599 ₽ for the Basic plan and 1,200 ₽ for the Professional plan per user per month; check tenge prices with a Kazakhstani partner.

The practical takeaway: amoCRM is cheaper at the start if you need ready-made messengers and telephony. Self-hosted Twenty shifts costs from licenses to engineering time, which pays off when you already have an engineer.

When to choose amoCRM and when Twenty

amoCRM, if

• Your main sales channel is messengers, inquiries are numerous, and first response speed is decisive.
• You need telephony with call recording in the first week.
• The team has no engineer, and sales need to launch quickly.
• The process is simple: one or two pipelines with standard stages.
• Storing data outside Kazakhstan is acceptable for your company.

Twenty, if

• Sales are B2B with a long cycle, and deals are large and few.
• You need to keep the customer database in Kazakhstan or in a closed environment.
• The data model is complex: projects, contracts, partners, several deals per client.
• The CRM needs to be connected to the task tracker, billing and internal systems.
• You have an engineer or contractor willing to maintain the system.

Hybrid setup

Sometimes companies keep both systems: amoCRM takes the mass inbound flow from messengers, while qualified B2B deals move to Twenty via the API. The setup works, but only with a strict rule: each deal has one home. As soon as a deal is managed in two places, you get duplicates, mismatched amounts and arguments about whose client it is. If you go hybrid, assign an owner for the integration and document at which stage and on which event a deal moves over.

Migrating from amoCRM to Twenty via CSV and the API

Moving from amoCRM to Twenty is first and foremost about migrating the structure, and only then the data. The process we use:

1. Audit. Export the list of pipelines, stages, custom fields and tags. Mark the fields that are actually filled in, and do not migrate the rest.
2. Model in Twenty. Create custom fields and objects before importing. amoCRM pipeline stages become values of the deal’s “Stage” field.
3. Trial import. Export companies, contacts and deals from amoCRM to a file, save it as CSV and load it into a test workspace in Twenty. Check relationships and duplicates.
4. A script for the complex parts. Notes, tasks and “deal with several contacts” relationships are easier to migrate with a script: it reads the amoCRM API and writes to the Twenty API, saving the original IDs in a separate field.
5. Final migration. Freeze changes in amoCRM for a day, run the migration and reconcile record counts.
6. Parallel operation. Keep amoCRM read-only for a month as an archive.

amoCRM	Twenty	Comment
Company	Company	The duplicate key is the BIN or domain
Contact	Person	Phone numbers in a single +7 format
Deal	Deal	Amount and currency as separate fields
Pipeline and stages	“Stage” field, plus a “Pipeline” field if there are several pipelines	Worth revisiting stage names
Custom fields	Custom fields	Migrate only the ones that get filled in
Tags	Multi-select field	Clean up before migrating
Tasks and notes	Tasks and notes	Via the API
Messenger conversations	Cannot be fully migrated	Keep a separate archive

After migration, check five things:

• The number of companies, contacts and deals matches the amoCRM export, adjusted for removed duplicates.
• Open deal amounts by stage match the amoCRM report as of the freeze date.
• Every deal has an owner, and that owner is a current employee.
• Phone numbers and emails are normalized to a single format, and search on them works.
• The original amoCRM ID is saved on every record so it can be found in the archive.

The most common migration mistake is moving everything as is, including fields nobody has filled in for five years and stages deals have not passed through in ages. Migration is a convenient opportunity to clean up the database and rebuild the pipeline around your current sales process.

How we help you choose and implement

During the diagnostic we look at channels and inbound volume, data model complexity, storage requirements and whether you have an engineer. Usually that is enough to make the choice obvious. Then we run a two- to four-week pilot with one sales team, migrate the data and only then onboard everyone else.

Details about the process are on our Twenty and amoCRM implementation page.

---

Sources. Twenty: twenty.com and the GitHub repository. amoCRM: amocrm.ru. Prices as of October 2026 and subject to change.

Terms in plain words

B2B

Selling to companies rather than individuals. For IT companies, such deals are usually large and few in number, and the path from first contact to contract is long.

Open source (AGPL-3.0)

Open code under the AGPL-3.0 license: Twenty can be installed on your own server for free and modified. amoCRM is not distributed this way; it is available only as a cloud service.

Self-hosted

An option where Twenty runs on your server, for example with a Kazakhstani hosting provider. The customer database stays in the country and the license is free, but you need an engineer for updates and backups.

Data model

The set of record types and the relationships between them: deals, companies, projects, contracts. In amoCRM, the core unit is a deal in a pipeline; in Twenty you can create your own objects.

PBX

A company phone system, these days usually cloud-based. In amoCRM, integrations with popular PBXs are installed from a catalog; in Twenty, calls reach the CRM through webhooks and the API.

API

An interface for exchanging data between programs. Twenty's open API is used to connect it to the task tracker, billing and internal services.

CSV

A simple table file used to export data from one system and load it into another. This is how companies, contacts and deals are moved from amoCRM to Twenty.

Migration

Moving from one system to another: first the structure, then the data, reconciliation, and a month during which the old system stays open read-only as an archive.