Migrating from Pipedrive: Step-by-Step Guide

Pipedrive is a beloved sales tool — genuinely focused on pipeline management, with a clean interface and a strong reputation among sales-led teams. But it's not the right tool forever. Teams outgrow it, find its marketing capabilities lacking, hit its pricing ceiling, or want more control over their data.

The good news: migrating from Pipedrive is meaningfully easier than migrating from Salesforce or HubSpot. The data model is relatively clean, the export tools are straightforward, and Pipedrive's API is well-documented. A focused team can complete the migration in 2-3 weeks.

Why People Leave Pipedrive#

Pricing Increases#

Pipedrive's pricing has increased several times in recent years. What was an affordable sales tool at $15/user/month has climbed, with meaningful features (AI assistance, workflow automation, reporting) requiring higher tiers. For small teams, the price-to-value equation has shifted.

Limited Marketing Capabilities#

Pipedrive is optimized for sales pipeline management. Its email campaign tools are basic. Its marketing automation is limited. Teams that need a single platform covering both marketing and sales often find they've outgrown Pipedrive before they've outgrown their deal count.

Reporting Constraints#

Pipeline reports in Pipedrive are good. Anything more sophisticated — cohort analysis, custom funnels, revenue attribution — requires the higher tiers or third-party tools. Teams that want richer analytics often look elsewhere.

AI Feature Expectations#

Pipedrive's AI features (Smart Contact Data, Pipedrive AI) are useful but limited. In 2026, teams expect to be able to query their pipeline in natural language, get AI-generated deal summaries, and have the system surface at-risk deals automatically. Pipedrive's current AI offering doesn't meet that bar.

Data Ownership#

Like all cloud CRMs, Pipedrive stores your data on their servers. You can't run direct SQL queries against your deal database, connect your own BI tool without CSV exports, or access the data outside the Pipedrive interface.

What to Export from Pipedrive#

Pipedrive organizes data into objects — each with its own export. You'll need to export all of them:

Core Objects#

• Contacts (People) — Names, emails, phones, company associations, custom fields
• Organizations (Companies) — Company details, addresses, custom fields
• Deals — Deal names, values, stages, close dates, contact/org associations
• Leads — If you use Pipedrive's Leads inbox
• Products — If you use product catalogs

Activity Data#

• Activities — Calls, emails, meetings, tasks with completion status
• Notes — Notes attached to contacts, organizations, and deals

Configuration#

• Pipeline stages — Your deal stages with win probability
• Custom fields — All custom field definitions

Step-by-Step Export Process#

Step 1: Export Contacts#

1. Go to Contacts > People
2. Click the ... menu > Export to spreadsheet
3. Wait for the export email
4. Download the CSV

The export includes all standard and custom fields. Make sure you're not filtering by any active view before exporting — you want all contacts, not just the ones in your current filter.

Step 2: Export Organizations#

1. Go to Contacts > Organizations
2. Click ... > Export to spreadsheet
3. Download the CSV

Step 3: Export Deals#

1. Go to Deals
2. Click ... > Export to spreadsheet
3. The deal export includes stage, value, close date, owner, and all custom fields
4. Associated contacts and organizations appear as columns

Step 4: Export Activities#

Activities require a separate export:

1. Go to Activities
2. Filter to show all activities (not just upcoming — include past and completed)
3. Click ... > Export to spreadsheet

Notes are not included in the Activity export. For notes:

1. Pipedrive's API provides note access (GET /v1/notes)
2. If you have many notes, a script or browser-based export tool is more efficient than the web UI

Step 5: Export via API (Notes + Complete History)#

Pipedrive's REST API at api.pipedrive.com/v1/ gives you programmatic access to everything.

Key endpoints:

• GET /v1/persons — all contacts with pagination
• GET /v1/organizations — all organizations
• GET /v1/deals — all deals
• GET /v1/activities — all activities
• GET /v1/notes — all notes
• GET /v1/dealFields — custom field definitions

To get all notes for export:

curl -X GET "https://api.pipedrive.com/v1/notes?limit=500&start=0" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

The API token is in your Pipedrive Settings > Personal Preferences > API.

Step 6: Document Your Configuration#

Before leaving Pipedrive, document:

• All pipeline names and stage order
• Win probability per stage
• Custom field names, types, and options
• Email template names and content
• Workflow automation rules (if on a plan with automations)
• Filter views you use regularly

Cleaning Your Pipedrive Data#

Migrations are the best time to clean your data. Common issues in Pipedrive databases:

Duplicate organizations: Pipedrive doesn't enforce unique organization names. "Acme Corp", "Acme Corporation", and "ACME" might be three separate organizations. Merge them before migrating.

Orphaned contacts: Contacts not linked to any organization. Decide if these need organizations added or can migrate as-is.

Stale deals: Deals that haven't been updated in 12+ months and aren't won or lost. Archive or move these to a "Stale" stage rather than migrating active pipeline data.

Inconsistent custom fields: If a custom field was optional and different reps used it differently, standardize the values before migrating.

Mapping Pipedrive Fields to Your Destination#

Standard Field Mappings#

Custom Field Translation#

Pipedrive custom fields by type:

• Text → Standard text field everywhere
• Number → Number field everywhere
• Date → Date field everywhere
• Single option → Dropdown/picklist
• Multiple options → Multi-select/tags
• Address → Multi-component address field (may need to split)
• Person → Relation field (many-to-one)
• Organization → Relation field

Step-by-Step Import to Common Destinations#

Importing to DenchClaw#

The fastest path: use the browser agent.

1. Install DenchClaw: npx denchclaw
2. Say: "Import my Pipedrive — contacts, organizations, deals, and notes"
3. The browser agent opens Pipedrive in your existing browser session, navigates the export flows, and imports data into DuckDB automatically

For manual import:

1. Create a people object with matching fields
2. Create a companies object
3. Create a deals object with relations to people and companies
4. Import companies CSV first
5. Import people CSV (linking to companies by organization name)
6. Import deals CSV (linking to people and companies)

Importing to HubSpot#

1. Companies: Contacts > Import > Start an Import > Import a file > Organizations CSV
2. Contacts: Map Pipedrive "Person Name" to HubSpot "First Name" + "Last Name" (split if needed)
3. Deals: Deals > Import > Deals CSV
4. Set "Associate with" to map deal-contact-company relationships

HubSpot's importer handles basic associations well. More complex multi-object associations may require the API.

Importing to Salesforce#

Salesforce Data Loader for large datasets:

1. Import Accounts (organizations) first — note the Salesforce IDs assigned
2. Import Contacts with AccountId from step 1
3. Import Opportunities with ContactId and AccountId

The Salesforce import requires you to resolve relationships manually by matching fields (e.g., using company name/domain as a lookup key).

Importing to Zoho CRM#

Zoho has a dedicated migration tool: Setup > Migration > Pipedrive. It handles the export API calls and field mapping automatically. For teams moving to Zoho, this is the fastest path.

Running Systems in Parallel#

For teams that can't do a hard cutover, run Pipedrive and the new CRM in parallel for 4-6 weeks:

1. Keep Pipedrive as the system of record for existing deals
2. New deals and contacts go into the new CRM
3. After 4-6 weeks, the existing deal pipeline will have mostly resolved (won, lost, or stalled)
4. Close out the final Pipedrive deals and cancel the subscription

The parallel run period is also useful for user training — salespeople learn the new system without the pressure of a hard deadline.

Timeline#

After the Migration#

Keep Pipedrive active for 30 days after your main migration. New issues will surface — a salesperson remembers a deal they didn't migrate, a contact has notes you missed, a custom field value needs correcting. Read-only access during this period is worth the cost.

Update integrations: Anything connected to Pipedrive — Zapier flows, email tools, reporting tools — needs to be reconnected or replaced.

Archive Pipedrive data: Before canceling, do a final full export of everything and keep it archived. Regulatory requirements in some industries require maintaining customer communication history for specific periods.

Frequently Asked Questions#

How long does a Pipedrive migration take?#

For a small team (under 10 users, clean data), 2-3 weeks with focused execution. For larger teams or messier data, 4-6 weeks is more realistic.

Can I migrate Pipedrive automations to HubSpot?#

No direct export exists. Document your Pipedrive automation workflows and recreate them as HubSpot Workflows. The trigger → condition → action logic is similar; the specific UI and options differ.

Does Pipedrive have an export for everything?#

Close. Pipedrive's CSV exports cover the major objects. Notes require the API. Email body content (for tracked emails sent through Pipedrive) is not available in exports — only the fact that an email was sent. If full email content is important, consider routing through your email provider (Gmail/Outlook) rather than Pipedrive's email tool.

Will I lose call recordings when leaving Pipedrive?#

If you used Pipedrive Calling, call recordings are stored in Pipedrive. Export or download these before canceling — they're not included in the standard data export. Go to each deal or contact with a call and download recordings individually, or use the API.

What's the easiest CRM to migrate to from Pipedrive?#

DenchClaw (browser agent handles the export automatically), Zoho (has a dedicated Pipedrive migration tool), or HubSpot (has an import wizard that works well with Pipedrive CSVs).

Ready to try DenchClaw? Install in one command: npx denchclaw. Full setup guide →