whats-best.ai
Search Sign in

CRM

Zoho CRM

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 4 dimensions proven

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

by Zoho Corporation · www.zoho.com

Compare with HubSpot Sales Hub → Compare with Odoo CRM → 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 Data Protection Officer

Weighted verdict

Knows a CRM is a database of other people's personal data before it is a sales tool. Optimizes for GDPR posture: EU hosting, DPA, subprocessor hygiene, consent fields, retention and deletion that actually delete. Rejects US-default hosting and enrichment features that scrape contacts from the open web.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Data Protection Officer

Contact & data model

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 Data Protection Officer

Leads and deals reach even the free tier, and teamspaces, wizards, custom functions, territory management, time-stamped audit logs and Vaults for private business data give the record layer substance. We found no public information on deduplication, field validation or field-level permissions, so the hygiene of a database full of other people's personal data rests unproven. 1 2 5

Report an error

Pipeline & forecasting

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 Data Protection Officer

Revenue forecasts, reports and dashboards ship in the standard tier and CPQ arrives at Professional, so a reporting layer exists. We found no public information on required fields per stage, stage gates, quota tracking or weighted forecast views — nothing evidences a process the pipeline enforces rather than merely displays. 2 5

Report an error

Automation & workflows

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 Data Protection Officer

Workflows and assignment rules are present from the free tier, cadences and AI agents sit in standard, and process automation, journey orchestration and custom functions arrive tier by tier, so multi-step sequences and routing are evidenced. The automation story is structured as a ladder of paid tiers, and we found no public information on webhooks as steps, round-robin routing, error handling or per-step logs. 1 2

Report an error

Integrations & API

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 Data Protection Officer

A marketplace of over 1,000 applications, a named Google Ads integration, widgets and the right to share service data through supported third-party integrations evidence a broad native directory. We found no public information on two-way email and calendar sync, API scope, rate limits or webhooks — precisely the seams through which contact data leaves the controller's grip. 1 2 4

Report an error

European sovereignty

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 Data Protection Officer

A German GmbH in Essen, a data protection officer in the Netherlands, selectable EU datacenters, a DPA offered by form and group-company standard contractual clauses form a genuine EU posture, with no third-party trackers and no ad-derived revenue. It stays short of signable: no subprocessor list is published, the captured pages state both that data is stored in an EU datacenter and that personal information is processed in the USA, the EEA and other countries where Zoho operates, every footer names the Indian parent company, and deletion after cancellation takes six months in the active database plus three more in backups — under a policy last updated in March 2022. 1 3 4 5

Report an error

Import, export & exit

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 Data Protection Officer

Access, export and deletion of service data are stated rights, but they read as request-based rather than self-serve, and migration support appears only as a top-tier Ultimate feature. We found no public information on self-serve import with mapping, export formats, or whether notes, activity history and attachments survive the trip out, while the six-plus-three-month post-cancellation deletion clock sets the floor on how long contacts' data lingers. 2 4

Report an error

Pricing transparency

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 Data Protection Officer

The public pricing pages state a permanently free tier for 3 users, annual and monthly billing, EUR and GBP pricing, a 15-day trial without credit card, and that local taxes are added on top of listed prices. The per-seat figures for the paid tiers do not appear in the captured pages, and Ultimate is described only as extended function limits plus consulting, so the real invoice at renewal is not computable from what is public. 2 5

Report an error

European sovereignty — proven facts

2 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 optional ⚠ unverified 1/3 pts 5 Report an error
Subprocessors Not determined — 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 (5)

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

  1. 1 Vendor product page www.zoho.com Checked 17 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
  2. 2 Vendor pricing page www.zoho.com Checked 17 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
  3. 3 Imprint — found from the homepage www.zoho.com Checked 30 Sep 2026 Details →
  4. 4 Privacy policy — found from the homepage www.zoho.com Checked 30 Sep 2026 Details →
  5. 5 Security / trust page — found from the homepage www.zoho.com Checked 30 Sep 2026 Details →