A Pipedrive to Salesforce migration moves organizations, people, deals, leads, activities, notes, products and files into Salesforce objects. Pipelines, automations, forms and reports are then rebuilt around them. Records transfer well. Stage-change history, email threads and automation logic need a plan of their own. Keep the parts reps liked about Pipedrive, especially a fast deal board, and the switch lands far more smoothly.
Why do sales-led teams leave Pipedrive, and what should survive the move?
They usually leave because sales now shares customers with other teams, and the CRM has to serve all of them. What should survive is the rep experience: few clicks, a visual pipeline and an obvious next step.
If you are still deciding whether to switch, our Sales Cloud vs. Pipedrive comparison covers that choice. This guide assumes the decision is made and focuses on how to execute it.
Pipedrive teams are used to activity-led selling. Every open deal has a scheduled next activity, and stale deals turn red on the board. Write those habits down before design starts, because they are the features reps will compare Salesforce against on launch day.
How does each Pipedrive record map to a Salesforce object?
Most Pipedrive items have a direct Salesforce counterpart. The decisions sit in the details: how pipelines become sales processes, where old leads go and which history is worth loading.
| Pipedrive concept | Salesforce equivalent | Migration note |
|---|---|---|
| Organizations | Accounts | Load first; keep the Pipedrive ID in an external ID field for matching |
| People | Contacts | People with no organization need a rule: a holding account, or leave them out |
| Deals | Opportunities | Map open, won and lost status to stages; carry lost reasons into a picklist |
| Leads (Leads Inbox) | Leads | Load only live leads; archived ones need a separate API call and a keep-or-drop decision |
| Pipelines and stages | Sales processes, record types and the Stage picklist | One sales process and record type per pipeline that genuinely differs |
| Activities (calls, meetings, tasks) | Tasks and events | Set owner, due date and status; link to the matching contact and opportunity |
| Notes | Notes or a long text field | Keep the author and date, and link each note to its parent record |
| Products on deals | Product records, price books and opportunity products | Build price books before loading deal line items |
| Custom fields | Custom fields | Audit each one for use; many will not deserve a place in Salesforce |
| Files | Salesforce Files | Check storage needs; files kept in Google Drive are not in Pipedrive's export |
Load in dependency order: users, accounts, contacts, opportunities, then products, activities, notes and files. Each later object points at records loaded before it, so the external IDs carry the relationships across.
What should happen to multiple Pipedrive pipelines?
Give each pipeline that sells differently its own Salesforce sales process and opportunity record type. Merge pipelines that only differ by name or territory.
Pipedrive keeps each pipeline and its stages separate, with no combined board across them. In Salesforce, every stage lives in one shared Stage picklist. A sales process then selects which stages a given record type may use.
That structure lets a renewals pipeline and a new-business pipeline share reports while keeping different stages. Teams that tracked territory with a pipeline per region usually fold those into one process and use a field or the role hierarchy instead. Our record types and page layouts guide explains the trade-offs.
Agree on a probability and forecast category for every stage before loading. Pipedrive deals store won or lost as a status, while Salesforce expresses both as closed stages.
How do you get data out of Pipedrive?
Pipedrive offers spreadsheet exports from its settings and from filtered list views, plus a REST API. Most migrations use the API or a migration tool built on it, with exports kept as a reference copy.
According to Pipedrive's help center, global admins can export leads, deals, organizations, people, products, activities, projects, notes and files as CSV or XLSX. List views export filtered records with chosen columns. Pipedrive notes that activities, notes and files linked to deals and contacts are exported separately.
Watch for two gaps. Emails are not among the export types Pipedrive lists, and files stored in Google Drive are excluded. Since mid-2025, Pipedrive's API also leaves archived deals and leads out of standard endpoints, so they need dedicated archived endpoints.
Can deal history and stage changes come across?
Current values and dates can come across. The click-by-click change history cannot be recreated as native Salesforce history, which starts fresh from go-live.
Pipedrive's deal changelog records stage moves, value changes, close date edits and custom field updates. The API exposes those updates per deal. Salesforce history tables, including opportunity stage history, are written by the platform and cannot be loaded directly.
- Load original created and closed dates. With the Set Audit Fields upon Record Creation permission, Salesforce lets API tools set created dates on insert.
- Store won and lost dates, and the date each deal entered its current stage, in custom fields if reports need them.
- Export the full changelog to a file or a simple custom object if stage-velocity analysis really matters.
- Turn on field history tracking for key opportunity fields before go-live. Salesforce allows up to 20 tracked fields per object by default.
What about email sync and attachments?
Treat old email as reference history, not live data. Reconnect email and calendar in Salesforce for everything going forward.
Pipedrive links synced emails to deals and contacts, but its export list leaves emails out. If older threads matter, pull them through the API and load key ones as completed activities. Otherwise, keep an archive that sales leadership can search.
Attachments become Salesforce Files linked to the same records. Total up file size early, because file and data storage have separate allowances in Salesforce. Confirm your allowance with your Salesforce account team.
How do Pipedrive automations translate to Salesforce?
Every Pipedrive automation gets rebuilt by hand, mostly as record-triggered or scheduled Flows. Nothing converts automatically, so inventory them before design.
Each Pipedrive automation pairs a trigger, such as a deal being added or updated, with actions. Typical actions create an activity, send an email or call a webhook. List each one with its owner, trigger, conditions and actions. Retire those nobody can explain.
Rotting deals deserve special attention, since reps rely on that red warning. A list view of deals with no recent activity, or a scheduled Flow that alerts the owner, can replace it.
What needs re-pointing on your website and booking tools?
Anything that creates leads or deals in Pipedrive must be switched to Salesforce on cutover day, or new inquiries go missing.
Pipedrive's LeadBooster add-on includes Chatbot, Live Chat, Prospector and Web Forms, and its Scheduler books meetings. Replace web forms with Web-to-Lead or a form tool connected to Salesforce. Choose replacements for chat and scheduling, then test each one end to end.
- Website and landing page forms
- Chatbot and live chat widgets
- Meeting booking links in email signatures and sequences
- Marketplace apps and Zapier-style connectors that write to Pipedrive
- Webhooks that other systems call
How do Pipedrive visibility groups become Salesforce sharing?
Pipedrive visibility groups become a combination of org-wide defaults, the role hierarchy and sharing rules. Pipeline visibility becomes record type access.
Pipedrive's visibility groups control which records users can see, and higher plans add subgroups and per-pipeline access. Each user belongs to one group. Salesforce separates what a user can do, through profiles and permission sets, from which records they can see.
Start with private opportunity access if regions must not see each other's deals, then open access with roles and sharing rules. Our sharing model guide walks through the layers. Map every Pipedrive user to a Salesforce role and permission set before the first test load.
Which reports have to be rebuilt first?
Rebuild the handful leaders actually used in Pipedrive Insights: pipeline by stage, activity by rep, conversion and won revenue. Everything else can follow.
- Pipeline value by stage and owner, matching the Pipedrive board totals at cutover.
- Activities completed and scheduled per rep, so activity-led managers keep their usual view.
- Lead-to-opportunity and stage-to-stage conversion, with history starting from go-live.
- Won and lost deals by reason, product and source.
Reconcile each report against Pipedrive on the final extract. Matching totals are the quickest way to win trust in the new system.
How should cutover and parallel running work?
Run a short, defined overlap with Pipedrive set to read-only, rather than letting reps update both systems. Dual entry breeds conflicting data.
- Run at least two full test loads into a sandbox and have reps check their own open deals.
- Pick a cutover point, take a final delta extract and load changes made since the last test.
- Switch forms, booking links and integrations to Salesforce in the same window.
- Restrict Pipedrive editing and keep it available for lookups until reconciliation is signed off.
- Keep the final export files as an archive before the Pipedrive subscription ends.
How do you keep Salesforce as simple for reps as Pipedrive was?
Design the rep screens deliberately. Short layouts, the Kanban view on opportunities and a strong mobile setup cover most of what reps miss.
Salesforce Lightning includes a Kanban list view that shows opportunities as cards by stage, close to the Pipedrive board. Add a compact opportunity layout, a path showing stage guidance and a quick action to log a call. Train on real deals from the migrated data, not demo records.
Watch login and activity logging closely after launch, and fix friction fast. Our guides to the Salesforce mobile app and to low adoption cover what to check.
What belongs in a phase-one Pipedrive migration plan?
Phase one should replace what Pipedrive did well and fix the gaps that triggered the move. New capability can wait until reps trust the data.
- Accounts, contacts, leads and opportunities, with each sales process documented.
- Open deals, recent activities, notes and files, plus closed deals within an agreed lookback.
- Rebuilt automations that reps depend on, starting with next-activity reminders.
- Web forms, booking and key integrations re-pointed and tested.
- Roles, permission sets and sharing that mirror today's visibility groups.
- Pipeline, activity and conversion reports reconciled against Pipedrive.
We have worked as a Salesforce Select partner since 2017, and we handle moves like this from field mapping through cutover. We scope the data, history and rep experience together so nothing important is left behind.
