CRM

Copper

Rest of world 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 Copper CRM, Inc. · www.copper.com

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The Solo Seller v1.2 · The Data Protection Officer v1.0 · The Sales Ops Lead v1.0 · The RevOps Integrator v1.0 · The Migrator v1.1 · The Skeptic v1.2 · rubric v1 · evaluated 16 Sep 2026

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 Migrator

Weighted verdict

Has moved a company off a CRM twice and remembers every scar. Optimizes for clean import with dedupe, full export of every object including notes and activity history, and contract terms that permit leaving. Rejects export behind support tickets and per-record API metering that makes exit a project.

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

Scored by The Migrator

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 Migrator

The evidence confirms contacts exist — tiered contact caps of 2,500 and 15,000 are the pricing page's loudest data-model fact — plus lead capture from LinkedIn, but says nothing about companies, deals, custom fields, required fields, or any dedupe or merge tooling. No dedupe evidence means duplicates accumulate unchecked, which is rubric level 3 territory, and the contact caps make data volume a billing event. 1 2

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 Migrator

Complete silence on pipelines, stages, required fields, win/loss capture and forecasting — the only deal-adjacent fact in the entire sheet is multi-currency on the Business plan. I can't credit a process the vendor's own pages don't describe, so this scores just above the bare-kanban anchor. 2

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 Migrator

The automation story is a Zapier checkbox ('5,000+ apps for workflow automation') — third-party if-this-then-that, not a native builder. No evidence of multi-step sequences, branching, routing or workflow analytics, and automations living in a connector mean they don't survive a migration. 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 Migrator

Genuine Google Workspace depth ('add leads, track conversations, find files or manage tasks directly in Gmail and Google Calendar') plus an API & embedded SDK, Okta SSO and Zapier. But sync is evidenced for Google only, and the API is a checkbox with no documented limits, webhooks or UI parity, so it sits just under the two-way-sync-for-major-providers anchor. 1 2

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 Migrator

Copper CRM, Inc., San Francisco, US, provenance rest of world, and 'no sovereignty attributes on record' — no DPA, no subprocessor list, no EU region anywhere on either captured page. That is the anchor-0 case verbatim; anyone with EU personal data here has no documented story on where it sits or under whose law. 1 2

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 Migrator

The entire exit story is one pricing-page boolean — 'Data import & export: available' — with nothing on which objects export covers, whether notes, activity history and files ride along, whether import dedupes, or whether it's self-serve. A bare checkbox next to an existing API earns just enough credit to clear the support-ticket floor, but I've seen too many of these checkmarks to believe activity history survives them; scope is unproven, and unproven is unscoreable. 2

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 Migrator

All three tiers carry real per-seat numbers with the annual/monthly split published ($23/$29, $59/$69, $99/$134), taxes explicitly excluded, and capacity limits stated up front (2,500/15,000/unlimited contacts) so capacity pricing is visible before you commit. No seat minimums, overage meters or hidden tiers appear on the page — only the fuzzy 'up to 26% off' keeps it short of full computability. 2

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.

Legal entity	Not determined	—	uncited Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	US by default ⚠ unverified	0/3 pts	3 Report an error
Subprocessors	Not determined	—	uncited Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 16 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Data residency. This is stricter than a default — Copper states it cannot store data anywhere else, so the US is the only available region, and hosting runs on unnamed third-party cloud services.
AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.

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.

9 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
7 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
7 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
6 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
5 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
2 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us

Do you know more about Copper? Tell us Report an error on this page

Sources (13)

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

1 Vendor homepage www.copper.com Checked 16 Sep 2026 Details →
2 Vendor pricing page www.copper.com Checked 16 Sep 2026 Details →
3 Privacy policy www.copper.com Checked 30 Sep 2026 Details →
4 Terms of service www.copper.com Checked 30 Sep 2026 Details →
5 Contact & data model — found from sitemap support.copper.com Checked 1 Oct 2026 Details →
6 Contact & data model — found from sitemap support.copper.com Checked 1 Oct 2026 Details →
7 Pipeline & forecasting — found from sitemap support.copper.com Checked 1 Oct 2026 Details →
8 Pipeline & forecasting — found from sitemap www.copper.com Checked 1 Oct 2026 Details →
9 Automation & workflows — found from sitemap support.copper.com Checked 1 Oct 2026 Details →
10 Automation & workflows — found from sitemap support.copper.com Checked 1 Oct 2026 Details →
11 Integrations & API — found from sitemap www.copper.com Checked 1 Oct 2026 Details →
12 Integrations & API — found from sitemap www.copper.com Checked 1 Oct 2026 Details →
13 Import, export & exit — found from sitemap www.copper.com Checked 1 Oct 2026 Details →