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.
| Pipedrive | Customermates |
|---|---|
| Persons | Contacts |
| Organizations | Organizations |
| Deals | Deals |
| Products | Services |
| Activities (open) | Tasks |
| Custom fields | Custom columns (same eight types) |
| Notes | Notes |
| Stage | Single-select custom column on deals |
In Pipedrive, Company Settings → Data → Export data. Pick the entity types you need. You will get five CSVs: persons, organizations, deals, products, activities.
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.
Settings → Import → upload CSV, map columns. Relationships resolve by Pipedrive IDs in the first pass, then re-resolve to Customermates UUIDs.
Spot-check ten records per entity type. Pay attention to:
search_all_entities on a few known names.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.
Pipedrive's automations roughly map to:
| Pipedrive | Customermates equivalent |
|---|---|
| Automation → Webhook | Webhooks |
| Automation → Zapier | Subscribe Zapier to a webhook |
| Automation → Email | Subscribe n8n or your email tool to a webhook |
| Automation → Update field | MCP, from Claude/ChatGPT, or a direct webhook listener |