whats-best.ai
Search Sign in

CRM

Bitrix24

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Bitrix, Inc. · www.bitrix24.com

Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Bitrix24's clearest strength is integrations, 4 to 5: the page names an API with developer and Google API services, a marketplace, and WhatsApp, Instagram, Telegram and telephony channels; the judges found no public information on API rate limits or two-way email and calendar sync. Pricing transparency runs 3 to 5: a flat model — fixed price per plan, user limit, monthly or annual billing, one example of 144 € per month — discounted where judges found no public tier prices, VAT treatment or crossing-the-limit costs. Data portability and sales pipeline carry the lowest scores on the table, 2 to 4 and 2 to 3: exit evidence is an API and self-hosting alone, and judges found no public information on export coverage or on stage enforcement and forecasting. Sovereignty spans 3 to 5: region selection and a self-hosted edition against a GDPR claim resting on a customer testimonial; judges found no public data processing agreement or subprocessor list, and the pages give different entity names, the vendor Bitrix, Inc. against a copyright line of Alaio. The flagged splits flag none of them.

Report an error

Speaks for it

  • Integrations, the strongest criterion at 4 to 5, credit a public API with developer and Google API services, a marketplace, and mobile and desktop apps
  • Messaging channels including WhatsApp, Instagram, Telegram and telephony are named natively on the page
  • Pricing transparency reaches 5 on a flat model stated as a fixed price per plan with a user limit, billed monthly or annually
  • A fully customizable self-hosted edition hosted on your own server is published
  • Workflow automation, approvals and Vibecode AI-built apps, agents and chatbots hold automation at 3 to 4

Report an error

Held against it

  • Data portability scores 2 to 4, with the API and the self-hosted edition the only exit evidence
  • Judges found no public information on a data processing agreement or a subprocessor list, leaving the GDPR claim at a customer testimonial
  • The captured pages give different names for the accountable entity, the vendor Bitrix, Inc. against a copyright line of Alaio
  • Public pricing amounts to one 144 € example plus a claimed 48.072 € annual saving against a 4.150 € competitor figure for a 50-user team
  • Sales pipeline scores 2 to 3, with no public information on stage requirements, win/loss capture or forecasting

Report an error

Best for

  • You rely on WhatsApp, Instagram, Telegram or telephony as front-door channels and want them named natively alongside a marketplace and API
  • You want a flat price with a user limit, like the captured 144 € example, instead of per-seat billing
  • You can run the self-hosted edition on your own server and want the personal-data database under your own roof

Report an error

Avoid if

  • You need documented export formats, import mapping or contractual data-return terms before committing — ask the vendor: the public pages we read do not show it
  • Your finance team requires evidenced forecasting, quota tracking or per-stage enforcement — sales pipeline scores 2 to 3
  • You cannot sign without a published data processing agreement and subprocessor list — the GDPR claim on the pages is a customer testimonial
  • You need tier-by-tier prices, VAT treatment and the cost of crossing the user limit to budget — only the 144 € example is public

Report an error

The scores

Contact & data model

Show reasoning
How this is scored

Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.

0 — A flat address book; no relations between people, companies and deals.

3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.

5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.

8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.

10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.

Report an error

The Solo Seller

The captured pages name contacts, leads, pipelines and a product catalog, so the standard records exist. We found no public information on custom fields, deduplication, merge tooling or field validation, so I can only credit the standard object set at surface depth. 1

Report an error

The Data Protection Officer

The feature list names contacts, leads, pipelines and access rights, so the core record objects exist, but we found no public information on custom field types, required fields, deduplication or merge tooling — the hygiene that decides whether a database of other people's personal data stays clean. 1

Report an error

The Sales Ops Lead

The captured page names the core objects — contacts, leads, orders, pipelines — in a feature list, which clears the address-book floor. We found no public information on custom field types, validation, required fields, or any deduplication and merge tooling, so I cannot verify the hygiene layer a 40-seat team depends on. 1

Report an error

The RevOps Integrator

The feature pages name contacts, leads, orders, invoices and a product catalog alongside access rights — more than a flat address book — but the capture shows nothing on deduplication, merge tooling, custom field types or record history. I found no public information on data hygiene or field customization, so I hold this below the customization-and-dedupe bar. 1

Report an error

The Migrator

Contacts, leads and access rights are named across the feature lists, so the standard objects exist and permissions get a mention. We found no public information on custom field depth, validation, dedupe or merge tooling — and duplicate-laden imports are the scar tissue I score hardest. 1

Report an error

The Skeptic

The captured page names contacts, leads, access rights and pipelines in its feature list, and that word list is the whole of the evidence. We found no public information on custom field types, required fields, deduplication, merge tooling or company-record relationships — for a data-hygiene judgement that is testimonial-grade. 1

Report an error

Pipeline & forecasting

Show reasoning
How this is scored

Whether the pipeline enforces a process and produces reporting a finance department accepts.

0 — A kanban of deals with amounts; nothing is enforced, nothing rolls up.

3 — Multiple pipelines and stage probabilities exist, but no required fields per stage and only canned reports.

5 — Stage requirements, win/loss capture and standard forecast views; custom reporting is limited or an add-on.

8 — Enforceable process (required fields, stage gates, routing), custom report builder, forecast by team and period with quota tracking.

10 — Forecasting a CFO signs: weighted and commit-based views, historical snapshots, attainment tracking, and reporting composable enough to answer questions the vendor never anticipated.

Report an error

The Solo Seller

Pipelines, kanban boards, analytics and KPI features are all listed, which is the shell of a sales process. We found no public information on stage requirements, win/loss capture, forecasting or quota tracking, so nothing here shows the pipeline enforces a process or produces a forecast I could trust. 1

Report an error

The Data Protection Officer

Pipelines and Kanban boards appear alongside analytics and KPI features, which reads as the canned-reporting end of the scale. We found no public information on stage requirements, win/loss capture, quota tracking or any forecast view a finance department could accept. 1

Report an error

The Sales Ops Lead

Pipelines, kanban, analytics and KPI appear as words in a feature list, and that is the entire pipeline story on this page. We found no public information on stage requirements, required fields per stage, win/loss capture, forecast views, quota tracking or a custom report builder — nothing here evidences a process being enforced or a forecast a CFO would sign. 1

Report an error

The RevOps Integrator

Multiple pipelines, kanban boards, analytics and KPI features are named, but nothing in the capture shows stage requirements, required fields per stage, win/loss capture or forecast views. I found no public information on forecasting or quota tracking, so this reads as a kanban with reporting claims rather than a process a finance department signs off on. 1

Report an error

The Migrator

Pipelines, a kanban view, KPI and analytics, invoices and recurring sales are all named, which is more than a bare deal board. We found no public information on required fields per stage, stage gates, win/loss capture or forecasting views, so I cannot evidence a process a finance department would sign. 1

Report an error

The Skeptic

Kanban boards, pipelines, analytics and KPI appear as feature words, which puts a pipeline of some sort on the record. We found no public information on stage requirements, win/loss capture, forecasting views or quota tracking — nothing here says a finance department would sign the output. 1

Report an error

Automation & workflows

Show reasoning
How this is scored

Triggers, sequences and routing that remove manual work without a consultant.

0 — No automation beyond email templates.

3 — Simple if-this-then-that on records; no multi-step sequences, no branching.

5 — Multi-step workflows with delays and branching, email sequences, basic lead routing — capped by tier or count.

8 — Full workflow builder across objects with webhooks as steps, round-robin routing, sequence analytics.

10 — Automation as infrastructure: versioned workflows, error handling, per-step logs, and limits generous enough that the feature is not its own upsell.

Report an error

The Solo Seller

Workflow automation, approvals, AI agents and no-code chatbot creation are each named features, so automation clearly exists in some form. We found no public information on multi-step sequences, branching, delays or lead routing, so I cannot credit more than the basics from feature-list mentions alone. 1

Report an error

The Data Protection Officer

Workflow automation, approvals and an AI builder that promises apps, agents and chatbots from a chat prompt are named on the page. We found no public information on multi-step sequences, branching, delays, routing or per-step logs, so the depth of the automation is a marketing bullet rather than a documented capability. 1

Report an error

The Sales Ops Lead

Workflow automation and approvals are named as features, and Vibecode promises apps, agents and chatbots built from chat prompts with hosting included. We found no public information on multi-step sequences, branching, delays, lead routing or sequence analytics, so I cannot confirm this goes beyond simple record-level triggers. 1

Report an error

The RevOps Integrator

Workflow automation and approvals are advertised, and Vibecode promises AI-built apps, agents and chatbots with hosting included, but the capture gives no builder detail — nothing on delays, branching, sequences or webhooks as steps. Named automation without builder evidence sits between simple record triggers and real multi-step workflows. 1

Report an error

The Migrator

Workflow automation, approvals, AI agents and a chat-prompt app builder are published, so automation is more than email templates. We found no public information on multi-step branching, delays, lead routing or per-tier automation limits — which is exactly where the upsell usually hides. 1

Report an error

The Skeptic

"Workflow-Automatisierung" and approvals are claimed by name, so automation exists at some level. We found no public information on branching, delays, sequences, routing, or the workflow limits by tier — with flat plans carrying user limits, an automation cap hiding behind a tier boundary would be invisible from these pages. 1

Report an error

Integrations & API

Show reasoning
How this is scored

Two-way email/calendar sync, native connections, and an API that treats external systems as first-class.

0 — No API, no sync; data enters by CSV and leaves never.

3 — One-way email logging (BCC), a handful of Zapier triggers, a read-mostly API.

5 — Two-way email and calendar sync for the major providers, a documented REST API with sane limits, a modest native directory.

8 — Deep native integrations for the revenue stack, webhooks, OAuth apps, API parity with the UI for core objects.

10 — An ecosystem: public API covering everything the UI does, event streams, a marketplace, and sync so reliable the CRM can be the system of record without being the only system.

Report an error

The Solo Seller

An API with developer tools and Google API services, a marketplace, mobile and desktop apps, and native WhatsApp, Instagram and Telegram channels are all evidenced, which is a real connection story. We found no public information on two-way email and calendar sync or on API documentation and rate limits, which is what I would need before trusting it as my hub. 1

Report an error

The Data Protection Officer

An API, a marketplace, and named channels for Google services, WhatsApp, Telegram and Instagram give this a genuine integration surface, with mobile and desktop apps besides. We found no public information on two-way email and calendar sync, webhooks or API limits, so parity with the interface remains unproven. 1

Report an error

The Sales Ops Lead

An API and developer area, a marketplace, and Google API services are shown, alongside named channels including WhatsApp, Telegram, Instagram, telephony and email marketing. We found no public information on two-way email and calendar sync, webhook behaviour or API limits, so I cannot confirm external systems are first-class rather than checkbox-deep. 1

Report an error

The RevOps Integrator

An API and developer offering, a marketplace, Google API services, MCP, and native WhatsApp, Instagram, Telegram and telephony connections are all named — a real native directory, not CSV-and-Zapier territory. But I found no public information on two-way email and calendar sync, webhooks, or API documentation and rate limits, which is exactly where the CRM-as-system-of-record question gets decided. 1

Report an error

The Migrator

A developer API, Google API services, a marketplace, MCP and native messaging channels including WhatsApp, Instagram and Telegram are published. We found no public information on two-way email and calendar sync, outbound webhooks, or API rate limits — and with my exit maths, an API without published limits is a metering risk I cannot rule out. 1

Report an error

The Skeptic

The page names an API with developer and Google API services, a marketplace, mobile and desktop apps, and channels including WhatsApp, Instagram, Telegram and telephony — a modest native directory claim with an API behind it. We found no public information on API rate limits, webhooks, or two-way email and calendar sync, so it sits at the middle of the road. 1

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Where other people's personal data actually lives and under whose law — entity, hosting, subprocessors, DPA.

0 — US entity, US-default hosting, no public DPA or subprocessor list.

3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad and undocumented.

5 — EU hosting selectable at signup, published DPA and subprocessor list; core processing still touches US entities.

8 — EU entity or EU-default hosting with published subprocessors, consent-friendly fields, retention and deletion controls; residual US exposure named and narrow.

10 — European entity, EU-only processing including subprocessors, deletion that provably deletes — sovereignty a DPO can sign off without a caveat file.

Report an error

The Solo Seller

Region selection is offered, and a fully self-hosted on-premise edition is available, which is the strongest form of data control on the page. We found no public information on a data processing agreement or a subprocessor list, and the GDPR claim shown is a customer testimonial rather than a documented legal commitment. 1

Report an error

The Data Protection Officer

The self-hosted edition — a fully customisable version hosted on the customer's own server — is the strongest fact here: an operator can keep the entire personal-data database under their own roof. The cloud story is thinner: the region is changeable, but we found no public information on a published DPA, a subprocessor list, EU-default hosting, or retention and deletion controls, and GDPR compliance appears only as a customer testimonial. The copyright line names Alaio while the vendor record names Bitrix, Inc., so the processing entity is not clear from the captured page. 1

Report an error

The Sales Ops Lead

Hosting region is selectable, a fully self-hosted edition on your own server is offered, and a customer testimonial claims GDPR-compliant usage. We found no public information on a data processing agreement, a subprocessor list, or where the processing entity sits — the copyright line names Alaio while the vendor of record is Bitrix, Inc. — so residual exposure cannot be judged from these pages. 1

Report an error

The RevOps Integrator

Region selection at signup and a fully self-hosted edition you host on your own server are both evidenced, and a customer testimonial claims GDPR-conformant use — a testimonial, though, not a DPA. I found no public information on a DPA, subprocessor list, retention or deletion controls, and the captured pages give different names for the accountable entity (the vendor listed as Bitrix, Inc. against a footer copyright of Alaio), so the legal picture stays unclear. 1

Report an error

The Migrator

The page publishes hosting region selection and a fully self-hosted on-premise edition, which materially helps a European deployment. But we found no public processing agreement and no subprocessor list, GDPR compliance appears only as a customer testimonial, and the copyright line names a different entity than the vendor, so where responsibility for personal data sits is undocumented. 1

Report an error

The Skeptic

The GDPR claim rests entirely on a customer testimonial ("fast wie bei WhatsApp - aber eben DSGVO-konform"), hosting region is selectable, and a self-hosted edition exists — but we found no public information on a published DPA, a subprocessor list, or the processing entities' locations. The vendor is recorded as Bitrix, Inc. while the page copyright names Alaio, and with the entity itself unresolved a DPO has nothing to sign yet. 1

Report an error

Import, export & exit

Show reasoning
How this is scored

Getting in with history intact, and out with everything — the anti-lock-in criterion.

0 — Import is a support ticket; export is contacts-only CSV missing notes, activities and files.

3 — Self-serve CSV import with mapping; export covers main objects but drops activity history, attachments or relations.

5 — Guided migration from major competitors, full-object CSV export, API access sufficient to rebuild the database elsewhere with effort.

8 — Complete export (all objects, history, files) self-serve in open formats, import with dedupe and dry-run, no API metering that prices exit out of reach.

10 — Exit as a feature: documented full-fidelity export, migration tooling both directions, and contractual data-return terms — leaving is a weekend, which is exactly why you can stay.

Report an error

The Solo Seller

We found no public information on import, export or migration tooling anywhere in the captured pages. The only sign data can leave is the named API and marketplace, and that is thin comfort when the whole exit story is unevidenced. 1

Report an error

The Data Protection Officer

An API and the self-hosted edition give a determined operator some path to their own data, but we found no public information on import mapping, export coverage of activities, attachments and relations, or migration tooling from other CRMs — the exit path is undocumented from the public pages. 1

Report an error

The Sales Ops Lead

An API and developer offering exist, which is the only portability evidence the page provides. We found no public information on guided or self-serve import with mapping, export coverage of notes, activities and files, or migration tooling in either direction, so I cannot size what an exit would actually take. 1

Report an error

The RevOps Integrator

Self-hosting on your own infrastructure plus a public API are the only portability signals in the capture, and self-hosting genuinely changes the exit question. But I found no public information on import tooling, export formats and coverage, or contractual data-return terms, so I cannot credit guided migration or full-fidelity export. 1

Report an error

The Migrator

The page names an API, a marketplace and a self-hosted edition — a theoretical path out — but we found no public information on import tooling, dedupe on import, export of any object including notes and activity history, or contractual data-return terms. I plan the way out before the way in, and I cannot price this exit from a marketing feature list. 1

Report an error

The Skeptic

An API and a self-hosted edition are the only exit-relevant facts on the record, and both are single-line claims. We found no public information on export formats or completeness, import tooling, migration from competitors, or contractual data-return terms — the anti-lock-in story is entirely untested here. 1

Report an error

Pricing transparency

Show reasoning
How this is scored

Whether a buyer can compute the real invoice — per seat, per month, at renewal — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — An entry price exists, but the tiers most buyers need are unpriced, or per-seat maths is obscured by bundles, minimums or mandatory onboarding fees.

5 — Most tiers carry real numbers with billing period and VAT treatment stated, but at least one commonly needed capability hides in an unpriced tier or usage-metered add-on.

8 — Every tier priced publicly including annual/monthly split; limits, seat minimums and overage rules stated; only genuine enterprise contracts are custom.

10 — Complete price computability: every tier, add-on, usage meter and renewal rule public, with a calculator or table that makes the invoice at 3 and 30 seats a two-minute exercise.

Report an error

The Solo Seller

The flat model is genuinely refreshing for a small team: every plan carries a fixed price with a user limit, adding users within the limit costs the same, and monthly or annual billing is stated, with an example of 144 € per month for a team. The captured pages show only that one example figure, though, and we found no public information on the full tier table, per-tier user limits or VAT treatment, so I cannot yet compute my real invoice. 1

Report an error

The Data Protection Officer

The model is stated plainly — every plan has a fixed price and a user limit, billed monthly or annually, with a captured example of 144 € — and the flat structure makes the maths less obscure than per-seat ladders. We found no public information on the prices of the remaining tiers, VAT treatment or renewal terms, and the savings claim of 48.072 € pro Jahr against a 4.150 € competitor figure is comparison marketing rather than a price list. 1

Report an error

The Sales Ops Lead

The model is stated plainly — fixed price per plan with a user limit, billed monthly or annually, adding users within the limit at the same amount — with one example of 144 € per month for a team. We found no public information on the remaining tiers' prices, the per-tier user limits, VAT treatment or renewal rules, and the claimed saving of 48.072 € per year sits beside a competitor comparison of 50 users at 4.150 € per month rather than a price table. 1

Report an error

The RevOps Integrator

The flat model is stated plainly — "144 €" per month for a plan with a user limit, the same amount as you add users within the limit, monthly or annual — which makes the monthly invoice easy to reason about. But the capture shows a single example price and a competitor comparison ("4.150 €" monthly for a 50-user team, "Sparen Sie 48.072 € pro Jahr") rather than a priced tier table, and I found no public information on VAT treatment or what sits in the higher tiers. 1

Report an error

The Migrator

One concrete figure is published — 144 € per month under a fixed price per plan with a user limit, billed monthly or annually — alongside a 50-user comparison of 4.150 € per month for competitor toolsets and a claimed saving of 48.072 € per year. We found no public information on individual tier prices, VAT treatment, seat minimums or renewal rules, so the real invoice at 30 seats is not computable from the captured page. 1

Report an error

The Skeptic

The flat model is stated unusually clearly — a fixed price per plan with a user limit, billed monthly or annually, same amount as users are added within the limit — with one example team price of 144 € and a vendor comparison of 4.150 € for 50 users against a claimed saving of 48.072 € per year. That savings figure is the vendor's own comparison maths, and we found no public information on a tier-by-tier price table, VAT treatment, or the cost of crossing the user limit — which in a limit-based model is exactly where renewal invoices are made. 1

Report an error

European sovereignty — proven facts

1 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency EU only ⚠ unverified 3/3 pts 4 Report an error
Subprocessors Not determined ⚠ unverified — uncited Report an error

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (12)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page www.bitrix24.com Checked 22 Sep 2026 Details →
  2. 2 Terms of service — found from the homepage www.bitrix24.de Checked 30 Sep 2026 Details →
  3. 3 Privacy policy — found from the homepage www.bitrix24.de Checked 30 Sep 2026 Details →
  4. 4 Security / trust page — found from the homepage www.bitrix24.de Checked 30 Sep 2026 Details →
  5. 5 Pipeline & forecasting — found from sitemap www.bitrix24.com Checked 1 Oct 2026 Details →
  6. 6 Pipeline & forecasting — found from sitemap www.bitrix24.com Checked 1 Oct 2026 Details →
  7. 7 Automation & workflows — found from sitemap www.bitrix24.com Checked 1 Oct 2026 Details →
  8. 8 Automation & workflows — found from sitemap www.bitrix24.com Checked 1 Oct 2026 Details →
  9. 9 Integrations & API — found from sitemap www.bitrix24.com Checked 1 Oct 2026 Details →
  10. 10 Integrations & API — found from sitemap www.bitrix24.com Checked 1 Oct 2026 Details →
  11. 11 Import, export & exit — found from sitemap www.bitrix24.com Checked 1 Oct 2026 Details →
  12. 12 Import, export & exit — found from sitemap www.bitrix24.com Checked 1 Oct 2026 Details →