CMP42 // USE CASES // LEAVING HUBSPOTUSE CASE 04 OF 04
// Use case 04 · Anyone leaving HubSpot

NOT ANOTHER
PLATFORM.

You want lean data plus a real API, not another platform to migrate onto next year. CMP42 is deliberately small, deliberately obvious, deliberately headless.

// Why teams reconsider

THE ASSUMPTION CHANGED.

HubSpot, Salesforce and Pipedrive were designed around an assumption that made complete sense when they were built: a human would open the UI. Every field, every pipeline view and every dashboard exists because someone was going to click on it. For teams that work that way, a UI-first CRM remains a sound choice.

What changed is the workflow. A sales manager who once opened the CRM to check the pipeline now asks an agent to summarise it — and opens the CRM only when the summary looks off. When the agent reads a schema designed for people clicking through screens, it struggles: it invents fields, fabricates stages, fills gaps with guesses.

If that describes your team, the question is not which platform to move to next. It is whether you need a platform at all — or a well-structured graph and a boring, fast API that every agent can use.

// What you get instead

LEAN DATA. A REAL API.

Lean

Lean defaults

Contact, company, deal, task, activity — with sensible, small defaults. Extension is explicit: if a field is not in your ontology, it is not on your contact. Lean defaults →

API

MCP, REST and GraphQL

Every model becomes MCP tools automatically — in the style of get_contact or list_deals_at_stage. Every operation is also exposed through REST and GraphQL, with the same auth and audit trail. API →

Git

Your ontology in git

Models are declared in TypeScript-shaped YAML, reviewed like code and migrated with one command. Your schema is a product artefact you own, not a configuration spread across settings pages. Models →

Hosting

Your hosting choice

Managed by us in the EU, or run yourself on your Postgres and object store. Same binary, same models. Your data, your call. Self-hosting →

// What a move looks like

FOUR STEPS, CONCEPTUALLY.

Every CRM move is different. This is the shape of one onto CMP42 — what happens in which order, and why.

  1. Inventory what you actually use. Long-lived CRM instances accumulate properties, pipelines and objects nobody reads any more. Before moving anything, list the objects, fields and relationships your team — and your agents — genuinely rely on. That list is the first draft of your ontology.
  2. Map your objects to Models. Contacts, companies and deals map onto CMP42’s lean defaults. The custom objects and fields that survived your inventory become explicit model declarations, versioned in git and reviewed like code. Relationships you used to encode in free-text fields become typed edges. Design Partners do this in a first-model mapping session during onboarding week.
  3. Import. Bring the records across. Because every write is validated against your Models, malformed data surfaces as clear errors instead of silently becoming part of the graph an agent will read.
  4. Point your agents at MCP. Connect Claude Desktop, Claude Code, Cursor, Cline or your own agent on the MCP SDK to the generated tools. Point the rest of your stack at REST or GraphQL. Your team keeps working where it already works — in its agents, in Slack, in the apps you build.

In the Alpha, CSV import for the standard objects — contacts, companies, deals and notes — ships as a built-in mapper, and everything beyond it (custom properties, historical timelines, attachments) is migrated with founder support at no extra charge as part of the Design Partner Program. The one-click HubSpot API connector with OAuth arrives with the Beta in Q1 2027; until then, working directly with the founder tends to be faster than a generic connector would be for the shape of migration Design Partners actually run.

The sketch illustrates the mapping idea — legacy objects on the left, CMP42 models on the right, and a deliberate decision about everything else. It is not an importer configuration.

mapping · sketchIllustrative
# illustrative — the mapping idea, not a tool
contact  ← contacts        # lean default, extend explicitly
company  ← companies
deal     ← deals           # stages declared in your model
note     ← call notes      # linked by typed edges
doc      ← proposals, briefs

# everything else: keep it only if a reader uses it
// An honest fit check

IS CMP42 RIGHT FOR YOUR MOVE?

The founder has spent fifteen years wiring companies to HubSpot, Salesforce, Pipedrive and the CRMs before those. The honest lesson: the best CRM is the one that fits how your team actually works. Here is when CMP42 fits — and when it does not, yet.

A good fit

  • Your team reaches CRM data mainly through agents — or wants to.
  • You want your ontology in git, reviewed like code.
  • You have engineers, or a partner, who are comfortable with an API.
  • You need EU hosting or self-hosting for your customer data.
  • Your team is fast on a keyboard and would rather filter a million rows than click through screens.

Not a good fit (yet)

  • Your team wants a point-and-click CRM — drag-and-drop pipelines, forms, a mouse-first screen for every field. CMP42 gives you the Podma Workbench, a keyboard workbench over your records, and a migrations CLI.
  • You need marketing automation today — sequences, sending, opt-out handling. CMP42 checks who may be contacted and why, and refuses a list that breaks the rules; the sending module is not in the Alpha.
  • You need a production system today. CMP42 is in Alpha with weekly releases — things will break.
  • You cannot run a real workload during Alpha. Then wait for Beta, which opens in Q1 2027 with a waitlist.

Bring your CRM mess to the call

The application asks what CRM or spreadsheet you are on today and what the messiest part of your CRM-to-AI workflow is. Fifteen minutes, no slide deck.

→ Apply to be a Design Partner
// Questions on this

What people ask here

The same answers as in the CRM FAQ, next to the case they belong to.

DAT-01

What are CRM objects, properties and associations called in CMP42?

The concepts stay; the implementation becomes stricter and readable for agents:

Glossary term Classic CRM CMP42
CRM object contacts, companies, deals, custom objects Model, declared in a file, versioned in Git
Property / field a field on a settings page typed field in the Model, validated on write
Association a link, often without meaning typed edge with a meaning (knows, owns, authored) and a validity period
Activity / note an entry on a timeline versioned record with an author (person or agent)

Prompts and sources for this question

DAT-04

How does a data migration to CMP42 work?

In four steps:

  1. Inventory: list the objects, fields and relationships your team and your agents actually use. That is the first draft of your ontology.
  2. Mapping to Models: contacts, companies and deals land on the standard Models. Whatever survives the inventory is declared explicitly. Relationships hidden in free-text fields become typed edges.
  3. Import: because every write is validated, bad data shows up as clear errors instead of slipping quietly into the graph.
  4. Connect the agents: Claude and other MCP clients use the generated tools; the rest of your stack uses REST or GraphQL.

The Alpha has a CSV import for contacts, companies, deals and notes. Custom fields, histories and attachments are migrated by the founder at no extra cost as part of the design-partner programme. A HubSpot connector with OAuth arrives with the Beta in the first quarter of 2027.

Prompts and sources for this question

HUB-06

Who is a good fit for moving from HubSpot to CMP42, and who is not yet?

A good fit Not a fit (yet)
Your team mainly reaches CRM data through agents, or wants to Your team wants a click CRM with drag-and-drop pipelines and forms
You want your ontology in Git, reviewed like code You need marketing automation with sending today
You have developers or a partner who can work with an API You need a production system today; the Alpha ships weekly releases
You need EU hosting or self-hosting You cannot run a real workload in the Alpha; then the Beta from Q1 2027 is the right time

Prompts and sources for this question

HUB-01

What corresponds to a HubSpot custom object, and when do you need one instead of a property?

In HubSpot a custom object is a user-defined object type and a property is an additional field. In CMP42 both are declarations in the Model. The rule of thumb stays the same: if something has fields of its own, relationships of its own and a lifecycle of its own, it is a Model of its own. If it is only an attribute of an existing object, it is a field.

An example from CMP42 itself: what applies after the close (contract, data processing agreement, data categories, retention period) is not three extra fields on the deal but a project record of its own, with its own edges to the deal, the contracting party and the people involved.

Prompts and sources for this question

HUB-02

What is the difference between lifecycle stage, lead status and deal stage?

The three terms describe different perspectives and should never be used as synonyms. CMP42 keeps them apart on purpose:

Term The question it answers Belongs to In CMP42
Lifecycle stage Where does the relationship stand overall? contact, company seven fixed stages for every tenant planned, each change with a reason
Lead status How far has work on this lead progressed? contact in sales result of a qualification record, e.g. qualified, nurture, rejected
Deal stage Which phase is this sales opportunity in? deal stages declared in the deal Model, validated on write

The benefit for agents: because every stage is typed, Claude cannot invent one. Ask “Which stage is the deal in, and where is the contact in the lifecycle?” and you get two separate answers, each with its source.

Prompts and sources for this question

Decided1
HUB-03

What corresponds to a HubSpot workflow and a HubSpot sequence?

A HubSpot workflow automates CRM processes through triggers and actions. Its counterpart is the CMP42 Process: steps by agents and people, with approvals, run history and cost per run (see chapter 3).

A HubSpot sequence is a series of e-mails and tasks for personal follow-up. CMP42 has no counterpart for it in the Alpha, because it does not send. A sensible pattern: the agent drafts each message from the real contact history, a person approves it, and your existing tool sends it.

Prompts and sources for this question

Decided1

Decided and on the way. Say which one you need first:

  • Open - you decide1Products and line items on deals
  • Open - you decide1Follow-up sequences

All 43 questions in the CRM FAQ

¹ Planned for a future release.