• Customermates logo
    CustomermatesDocumentation
  • Introduction
  • Comparison
Getting Started
  • Quickstart
  • Core Concepts
  • From Pipedrive
Integrations
  • Introduction
  • MCP
  • Connect Claude Desktop
  • Connect ChatGPT
  • Connect Cursor
  • Webhooks
  • OpenAPI 3.1.0
  • N8N
Self-Hosting
  • Self-Hosted vs Cloud
  • Get Started
  • Managing Your Installation
  • Architecture & Security
Reference
  • Setup AI Assistant
  • MCP Tool Catalog
  • Webhook Events
  • Filter Syntax
  • API Keys
  • Go back
  1. Introduction
  2. From Pipedrive

From Pipedrive

Migrate contacts, organizations, and deals from Pipedrive to Customermates without losing custom fields or links.

TL;DR — Export from Pipedrive as CSV, map fields, import through the UI or through the MCP surface. Custom fields become custom columns. Relationships survive. Budget an hour for a team of ten.

What moves over cleanly

PipedriveCustomermates
PersonsContacts
OrganizationsOrganizations
DealsDeals
ProductsServices
Activities (open)Tasks
Custom fieldsCustom columns (same eight types)
NotesNotes
StageSingle-select custom column on deals

What doesn't (yet)

  • Activity history (completed activities) — exported but not imported. Keep the CSV for reference.
  • Email threads attached to deals — Pipedrive-specific; no equivalent today.
  • Pipedrive automations — rewrite as webhook subscribers or n8n flows. See n8n.

Steps

1. Export from Pipedrive

In Pipedrive, Company Settings → Data → Export data. Pick the entity types you need. You will get five CSVs: persons, organizations, deals, products, activities.

2. Create custom columns first

Look at your exported CSVs. Any column that isn't in the Customermates default schema becomes a custom column. Create them up front so the import can map values.

The fastest way: ask your AI via MCP. Paste the column names at the top of a Pipedrive CSV and say "for each of these that isn't in the default schema, create the right custom column on contacts/organizations/deals". The setup prompt already tells the assistant how to pick the right column type.

3. Import

Settings → Import → upload CSV, map columns. Relationships resolve by Pipedrive IDs in the first pass, then re-resolve to Customermates UUIDs.

4. Verify

Spot-check ten records per entity type. Pay attention to:

  • Deal stage — if you converted Pipedrive pipelines to single-select, every deal should land in the right option.
  • Contact↔Org links — run search_all_entities on a few known names.
  • Custom column values — especially currency and dates, where CSV formatting is easy to get wrong.

5. Turn off Pipedrive

Do not cancel until you've exported historical activities and any email threads you want to keep. Consider keeping Pipedrive in read-only mode for a week.

Automation replacements

Pipedrive's automations roughly map to:

PipedriveCustomermates equivalent
Automation → WebhookWebhooks
Automation → ZapierSubscribe Zapier to a webhook
Automation → EmailSubscribe n8n or your email tool to a webhook
Automation → Update fieldMCP, from Claude/ChatGPT, or a direct webhook listener

Next

  • Quickstart — verify your account end-to-end.
  • Webhooks — recreate automations.
  • Custom columns — where your Pipedrive custom fields live.
What moves over cleanly
What doesn't (yet)
Steps
1. Export from Pipedrive
2. Create custom columns first
3. Import
4. Verify
5. Turn off Pipedrive
Automation replacements
Next