Pipedrive → Salesforce
Move Pipedrive organizations, people, and deals into Salesforce accounts, contacts, and opportunities. Salesforce will not invent your stages, record types, or custom booking fields. Load a sandbox first.
Should you make this move?
Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.
Pipedrive
- A sales-first pipeline and activity view that reps open every day
- Structured ownership, status, and workflow views improve operational visibility
- Marketing automation, custom objects, and deep cross-team reporting are thinner than a full CRM suite
- Custom fields, automations, history, and reporting are difficult to reproduce exactly
Salesforce
- Extensive CRM customization, ecosystem, reporting, and enterprise governance support complex businesses
- Structured ownership, status, and workflow views improve operational visibility
- Licensing, implementation, and ongoing administration are expensive and specialized
- Custom fields, automations, history, and reporting are difficult to reproduce exactly
Salesforce: Extensive CRM customization, ecosystem, reporting, and enterprise governance support complex businesses. This removes a major source-side concern: Marketing automation, custom objects, and deep cross-team reporting are thinner than a full CRM suite.
What you lose: A sales-first pipeline and activity view that reps open every day. What you inherit: Licensing, implementation, and ongoing administration are expensive and specialized.
Jump to a section
Know the shape of the move.
This timeline assumes
- You are moving a sales pipeline into Sales Cloud, not Service Cloud cases or a full CPQ catalog.
- The site already documents Pipedrive → HubSpot and Salesforce → HubSpot as nearby routes.
- A Salesforce admin has built record types, stages, and required fields in a sandbox before any production load.
- Pipedrive exports are run by a global admin. Visibility groups hide records from everyone else.
- Pipedrive stays available until the first Salesforce forecast cycle is signed off.
What survives the move.
“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.
| Item | Outcome | Impact | What happens | Mitigation |
|---|---|---|---|---|
| Organizations | partial | critical | Pipedrive organizations become Salesforce accounts. You choose the account name and the external id you will match on later. Parent companies are only there if you exported that relationship. | Add a Pipedrive organization id column and mark it as an external id in Salesforce. |
| People | partial | critical | People become contacts. Salesforce wants an account for each contact in the usual business-account model. A person with no organization needs a rule. | Create a holding account for unaffiliated people, or exclude them in writing. |
| Deals | partial | critical | Deals become opportunities. Stage names, forecast categories, and required fields are yours to define. Pipedrive will not populate them. | Map each Pipedrive stage to a Salesforce stage and forecast category before the load. |
| Custom deal detail | manual | critical | Flyer Club told Salesforce they left Pipedrive because bookings needed passport, flight, supplier, and commission fields Pipedrive's flexibility did not cover. Those fields exist only after you build them. | List the custom fields reps type every week. Create them in the sandbox and put them on the page layout. |
| Activities | manual | high | Pipedrive exports activities separately from deals. They can become tasks or events. Completed and open activities need different mappings. | Load activities after accounts, contacts, and opportunities so the who and what ids exist. |
| Notes and files | partial | medium | Notes export as HTML or plain text. Files are a separate export, and Google Drive files are not in the global export. | Attach notes with the parent external id. Keep Drive links as URLs. |
| Products on deals | partial | high | Pipedrive can export products linked to deals. Salesforce opportunity products need a price book entry. | Load products and price book entries first. Skip line items until that load is clean. |
| Leads versus deals | manual | high | Pipedrive leads are not Salesforce leads unless you decide they are. Many teams import only open deals and leave old leads behind. | Sign a rule for archived leads, open leads, and lost deals. |
| Automations | lost | high | Pipedrive workflows do not become Flow. Insights chart exports are PDF or PNG snapshots. | Rebuild the automations you still run. Store the PDFs with the project notes. |
| Users and visibility | manual | critical | The user export lists emails and visibility groups. Salesforce roles, profiles, and sharing are a different model. A non-admin Pipedrive export is incomplete. | Export as a global admin. Create Salesforce users before you set opportunity owners. |
| Multiple pipelines | manual | high | Pipedrive pipelines do not become record types or sales processes on their own. | Pick one sales process, or one record type per pipeline, and test both in the sandbox. |
| Export lifetime | manual | medium | Pipedrive keeps generated exports for 28 days. | Download and store them outside Pipedrive the day they finish. |
Where each thing goes.
| Source | Destination | Method | Notes |
|---|---|---|---|
| Organization id | Account external id | transform | Use it for every later match. |
| Organization | Account | transform | Map name and domain. |
| Person | Contact | transform | Require an account or a holding account. |
| Deal | Opportunity | transform | Stage and close date need a rule. |
| Pipeline | Sales process or record type | manual | Decide before the sandbox load. |
| Activity | Task or event | manual | Separate export. Load after parents. |
| Note | Content note or a long text field | transform | Plain text is the safer file. |
| Product on a deal | Opportunity product | manual | Needs a price book entry. |
| Owner email | Salesforce user | manual | Create users first. |
| Workflow | No destination | unsupported | Rebuild in Flow. |
Make the move recoverable.
Create the source-of-truth backup
Keep admin exports that can rebuild accounts, contacts, and opportunities if the sandbox load is wrong.
- Export organizations, people, deals, activities, notes, products, and users.
- Export the data-field setup so custom fields have names and API keys.
- Download the files before day 28.
- Save a stage-to-stage map signed by sales.
- Hash the files.
Proof to capture: The manifest names each file, its count, its hash, and the admin account that exported it.
External ids
Make the Salesforce load matchable and repeatable.
- Add external ids for organization, person, and deal.
- Load accounts, then contacts, then opportunities in a sandbox.
- Upsert. Do not insert a second time without the external id.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
Stage and required-field map
Stop opportunity rows failing on validation rules.
- List every Pipedrive stage.
- Write the Salesforce stage, forecast category, and close-date rule.
- Fill required custom fields before the production load.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
The things most likely to hurt.
These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.
Required fields reject the load
A validation rule or required field is empty on the opportunity file.
- Consequence
- The batch fails or opportunities land half-empty.
- Mitigation
- Run the same file in a sandbox with production validation rules copied.
Stop if: The sandbox load has unreviewed errors.
Contacts have no account
People exported without an organization.
- Consequence
- Those contacts fail in a business-account model.
- Mitigation
- Assign a holding account or drop the rows in the signed exclusions.
Stop if: The contact error file is larger than the agreed threshold.
Reps keep using Pipedrive
Edit rights remain after the opportunity load.
- Consequence
- New deals exist in only one system.
- Mitigation
- Remove edit rights before the final delta.
Stop if: A rep login can still create a Pipedrive deal.
Do the work in this order.
- Days 1–6 · inventory
Objects and stages
10–18 hours active4–6 days elapsedSales sign-off waiting- List pipelines, custom fields, and required Salesforce fields.
- Sign the stage map and the lead rule.
Depends on: Pipedrive global admin and a Salesforce admin
Stop / go checkpointBuild the sandbox?
Go when: Every open stage and required field has a rule.
Stop when: Custom booking fields are still unnamed.
- Days 5–9 · backup
Export
4–8 hours active2–4 days elapsedExport jobs waiting- Run admin exports.
- Store them outside Pipedrive.
Depends on: Signed stage map
Stop / go checkpointLoad the sandbox?
Go when: Counts match and files are downloaded.
Stop when: The export was not run as a global admin.
- Days 9–25 · pilot
Sandbox load
20–50 hours active8–16 days elapsedValidation-rule fixes waiting- Upsert accounts, contacts, and opportunities.
- Read the error file and fix the map.
Depends on: Stored exports
Stop / go checkpointProduction?
Go when: Sandbox counts and a rep walkthrough pass.
Stop when: Error rows are unexplained.
- Days 22–32 · cutover
Production upsert
8–18 hours active2–5 days elapsedWrite freeze waiting- Freeze Pipedrive.
- Upsert the final delta into production.
- Point reps at Salesforce.
Depends on: Passed sandbox
Stop / go checkpointOpen production?
Go when: Open opportunity totals match the freeze file.
Stop when: Pipedrive still accepts edits.
- Days 30–45 · observe
Forecast cycle
8–16 hours active5–12 days elapsedFirst forecast waiting- Compare the first forecast with the Pipedrive pipeline you froze.
- Keep Pipedrive readable.
Depends on: Production load
Stop / go checkpointClose rollback?
Go when: Forecast and activity logging hold for the agreed cycle.
Stop when: Reps reopen Pipedrive for daily entry.
Cut over with a way back.
Cutover
Upsert the frozen Pipedrive pipeline into production Salesforce and stop Pipedrive edits.
- Remove Pipedrive edit rights.
- Export the final delta and download it.
- Upsert accounts, contacts, then opportunities with external ids.
- Load in-scope activities.
- Have a rep open five live opportunities and confirm stage, amount, and account.
Proof to capture: Production opportunity counts match the freeze file. Pipedrive is read-only.
Rollback
Return daily entry to Pipedrive and keep any opportunities created only in Salesforce.
- Stop Salesforce edits by the sales team.
- Restore Pipedrive edit rights.
- Export Salesforce opportunities created after the freeze.
- Add reviewed rows back to Pipedrive with the external id so you do not duplicate them later.
- Recount open deals.
Proof to capture: Pipedrive is writable. Salesforce production is not receiving new sales edits.
- Sandbox errors repeated in production
- Opportunity totals do not match
- Contacts without accounts
- Owners pointing at inactive users
- Reps logging the same deal in both systems
Prove the migration worked.
Every blocking check must pass. Capture the evidence before cleanup begins.
| Pass | ID | Check | Method | Expected result | Evidence |
|---|---|---|---|---|---|
V-01Blocking | Admin counts | Match organizations, people, and deals to list views. | Counts agree, exclusions are signed. | Count sheet. | |
V-02Blocking | Error file | Read every failed row from the sandbox upsert. | Failures are fixed or accepted in writing. | Error CSV. | |
V-03Blocking | External ids | Query duplicate external ids. | One account per Pipedrive organization id. | SOQL result. | |
V-04Blocking | Account link | Count contacts with a null account id. | Zero, unless the holding-account rule says otherwise. | Contact query. | |
V-05Blocking | Stages | Pivot stage and amount against the freeze file. | Open pipeline amount matches within the signed tolerance. | Stage pivot. | |
V-06Blocking | Custom fields | Open a booking-style opportunity as a rep. | The fields they type every week are on the layout. | Walkthrough notes. | |
V-07 | This week's tasks | Compare open activities due in seven days. | In-scope tasks point at the right contact and opportunity. | Task sample. | |
V-08Blocking | Pipedrive is read-only | Try to create a deal with a rep login. | Pipedrive rejects the edit. | Permission check. |
Remove the scaffolding safely.
Safe after: One forecast cycle and stored copies of the Pipedrive exports.
- Archive exports, the error file, and the stage map.
- Remove sandbox credentials from laptops.
- Keep Pipedrive read-only through the rollback window.
- Disable Pipedrive automations that still notify customers.
- Deactivate the Pipedrive plan only after finance agrees.
- Review Salesforce validation rules that were relaxed for the load.
When the plan met reality.
First-hand accounts are preferred. Vendor case studies are labeled, and every note below is an editorial paraphrase—follow the link for the full context.
Salesforce's customer story says Flyer Club tracked leads in spreadsheets and Google Docs, adopted Pipedrive, and then moved to Salesforce because each booking needed passport details, flight numbers, stopovers, costs, supplier data, and commissions paid at different times. General manager Josh Burt says customization is why they left Pipedrive. Chief growth officer Victor Kerman describes custom features across marketing, sales, and operations. Salesforce reports a 30 percent revenue increase, a 10 percent conversion increase, 20 percent less time managing new leads, and 24/7 coverage with Agentforce Voice. Those results are Salesforce's.
- List the booking fields a pipeline cannot hold before you assume a deal import is the whole job.
- Read the revenue, conversion, and time figures as Salesforce's claims about this customer.
- The reason they give for leaving Pipedrive is custom booking data, not a failed export.
- Agentforce and the percentages are part of the vendor story. They are not a cutover checklist.
Verify against the primary material.
Platform behavior changes. Check these sources and the review dates above before executing a production migration.
- Pipedrive: exporting dataAccessed 2026-11-01
- Salesforce: Data Import WizardAccessed 2026-11-01
- Pipedrive API: dealsAccessed 2026-11-01