Salesforce → Pipedrive
Move Salesforce records into Pipedrive with Import2 after the users exist. Salesforce's own export is a weekly or monthly ZIP that disappears 48 hours after it finishes, and it skips the recycle bin.
Should you make this move?
Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.
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
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
Pipedrive: A sales-first pipeline and activity view that reps open every day. This removes a major source-side concern: Licensing, implementation, and ongoing administration are expensive and specialized.
What you lose: Extensive CRM customization, ecosystem, reporting, and enterprise governance support complex businesses. What you inherit: Marketing automation, custom objects, and deep cross-team reporting are thinner than a full CRM suite.
Jump to a section
Know the shape of the move.
This timeline assumes
- A Pipedrive global admin runs Import2. Salesforce is on Pipedrive's supported CRM list. Users are invited before the import, or the initiating user owns the data.
- You can run Salesforce Data Export, or you accept that a large export can take a long time and has no SLA.
- Import2's free tier covers up to 1,000,000 records. A record is one item or one CSV row. Above that, the migration is paid. Undo and redo are included.
- The site already documents Salesforce → HubSpot and Pipedrive → Salesforce if you need the other CRM paths.
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 |
|---|---|---|---|---|
| Ownership | manual | critical | Pipedrive says to create users before Import2. If you start before users are invited and pipelines exist, the initiating user owns the imported data. | Invite every rep and build the pipelines you want before Start Import. |
| Record volume | partial | high | Import2 includes up to 1,000,000 records for free and charges beyond that. You can filter record types or disable them on the Settings tab. Multiple sessions are allowed on trial and paid accounts. | Count the objects you will send. Disable history objects you do not need in Pipedrive. |
| Salesforce export window | manual | critical | Export files are available for 48 hours after completion. A new export removes the previous files even inside that window. Salesforce cannot restore a file after it leaves Setup. Weekly exports are Enterprise, Performance, and Unlimited. Monthly exports are the other editions except Database.com. A manual export is once every 7 days, or 29 days on the monthly schedule. | Download every ZIP before you queue another export. One file at a time, with 60 seconds between downloads. |
| Recycle bin and formulas | lost | high | Data Export does not include the recycle bin. Formula fields and roll-up summary fields are always excluded. Archived records are included. Sandbox export can be scheduled and is expected never to process. | Restore anything you need from the recycle bin first. Recompute formulas in Pipedrive from the stored source fields. |
| Files and attachments | partial | high | Salesforce recommends deselecting images, documents, attachments, and Files if you need a faster export. A large org is split into ZIPs of about 512 MB. A single uploaded file can make a ZIP larger than that, up to the 2 GB file size Salesforce allows. | Decide whether files are in this export. Download them inside the 48 hours if they are. |
| Rows written during the export | partial | medium | Salesforce says users can keep working, and rows added while the export is already running are not in that file. There is no SLA. A request can take longer than a week. A later scheduled run is skipped while one is still queued. | Note the start time. Plan a second pass for records created after it. |
| Pipelines and custom fields | partial | high | Import2 can create pipelines, stages, and custom fields, or you can turn that off and map fields yourself. Filters can drop record types. Pipedrive suggests allowing 24 hours and writing to Import2 if it stalls. | Review Customize Mappings before the full import. Undo and run it again if the mapping is wrong. Pipedrive says undo and redo cost nothing extra. |
| Automations and code | manual | critical | Import2 moves CRM records from Salesforce. Salesforce formula logic, Apex, and flows are not Pipedrive automations. You rebuild the behavior you still need. | List the automations reps actually use. Recreate those in Pipedrive after the records look right. |
| Permissions to run the export | manual | high | The user who scheduled the export gets the ready email. That address cannot be changed in place. Deactivating that user, or removing their export permission, can fail the job. Data Export does not run in read-only mode. | Keep that user active until every ZIP is downloaded. |
| Reports and dashboards | lost | medium | The export FAQ describes object data, files, and attachments. It does not describe a move of Salesforce report definitions or dashboards into Pipedrive. | Screenshot or export the reports you still run. Rebuild them after fields exist in Pipedrive. |
Where each thing goes.
| Source | Destination | Method | Notes |
|---|---|---|---|
| Salesforce account | Pipedrive organization | transform | Confirm the mapping on Import2's Settings tab. |
| Contact | Person | transform | Map email and phone before the full run. |
| Opportunity | Deal | transform | Let Import2 create stages, or map them to stages you already built. |
| Opportunity owner | Deal owner | manual | The Pipedrive user must exist first or the initiator owns the row. |
| Custom field | Pipedrive custom field | transform | Turn on automatic custom fields or map them yourself. |
| Formula or roll-up | No destination | unsupported | Salesforce excludes these from Data Export. They are also not stored values Import2 can copy. |
| Recycle bin | No destination | unsupported | Restore first if the row must move. |
| Attachment or File | File on the deal | manual | Include them in Data Export only if you will download the ZIPs within 48 hours. |
| Record type you do not want | No destination | manual | Disable that type in Import2 settings. |
Make the move recoverable.
Create the source-of-truth backup
Hold a Salesforce export that still exists after the 48-hour download window.
- Schedule Data Export in production, not a sandbox.
- Include only the objects you need. Add files only if you will download them immediately.
- Download one ZIP at a time. Wait 60 seconds between files.
- Do not queue a second export until the first set is copied off Salesforce.
Proof to capture: Every ZIP from that run is stored outside Salesforce, and the export user is still active.
Users, then Import2
Keep ownership on the right reps.
- Invite users and create the pipelines you want to keep.
- As a global admin, open the account menu, Tools and Apps, Import data, Import from other software.
- Choose Salesforce, test the connection, and review pipelines, stages, and custom fields.
- Start the import. Wait for Import2's email. Pipedrive suggests allowing 24 hours.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
Local Salesforce archive
Keep a copy that Salesforce will not hold.
- Run the export with the objects Import2 will not be your only copy of.
- Download each ZIP inside 48 hours.
- Check that formula columns are absent, as Salesforce says they are excluded.
- Note the start time so you can find rows created while it ran.
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.
Users are invited late
Import2 is started by one admin before the team is in Pipedrive.
- Consequence
- That admin owns the imported records.
- Mitigation
- Invite users first. Undo and redo if a sample shows the wrong owner. Pipedrive says that redo has no extra cost.
Stop if: A required rep has no Pipedrive user.
The ZIP window closes
Files sit in Setup, or someone queues another export.
- Consequence
- Salesforce removes the files. Support cannot put them back.
- Mitigation
- Download immediately, one file at a time.
Stop if: You are still inside the 48 hours and have not copied the ZIPs.
Sandbox export is treated as a backup
The job was scheduled in a sandbox.
- Consequence
- Salesforce says that job is expected never to process.
- Mitigation
- Run Data Export in production.
Stop if: The only scheduled export is a sandbox.
Do the work in this order.
- Days 1 to 3 · inventory
Objects, users, and stages
4 to 8 hours active2 to 3 days elapsedUser invites waiting- List objects that must move.
- Invite Pipedrive users.
- Sketch pipelines.
Depends on: Global admin and a Salesforce export user
Stop / go checkpointStart a sample?
Go when: Every owner has a Pipedrive user and the record count is estimated.
Stop when: You are over 1,000,000 records and have not accepted a paid import.
- Days 3 to 10 · backup
Production export
2 to 4 hours active2 to 7 days elapsedSalesforce queue waiting- Run Data Export in production.
- Download every ZIP inside 48 hours.
Depends on: Object list
Stop / go checkpointIs the archive local?
Go when: ZIPs are stored outside Salesforce and the next export is not queued.
Stop when: The ready email arrived and the files are still only in Setup.
- Days 10 to 12 · pilot
Import2 settings
3 to 5 hours active1 to 2 days elapsedImport2 waiting- Test the Salesforce connection.
- Review mappings and disabled record types.
- Check one owner and one deal.
Depends on: Users and pipelines
Stop / go checkpointRun the full import?
Go when: A sample deal has the right owner, stage, and custom fields.
Stop when: The initiator owns rows that belong to someone else.
- Days 12 to 14 · cutover
Full import
2 to 4 hours active1 to 2 days elapsedImport2, suggested 24 hours waiting- Start the full import.
- Read the completion email.
- Stop new Salesforce edits or plan a delta.
Depends on: Passed sample
Stop / go checkpointPipedrive is the CRM?
Go when: Counts and owners match the sample rules on the full data.
Stop when: Mappings are wrong and you have not undone the run.
- Days 14 to 21 · observe
A week of deals
3 to 6 hours active5 to 7 days elapsedOne sales week waiting- Watch new deals.
- Rebuild the automations you still need.
- Keep Salesforce read-only if you can.
Depends on: Full import
Stop / go checkpointClose rollback?
Go when: Reps can find their deals and the local ZIP is stored.
Stop when: Owners or stages are still wrong.
Cut over with a way back.
Cutover
Make Pipedrive the place reps edit deals, with Salesforce kept as the downloaded archive.
- Confirm users, mappings, and a sample owner.
- Start the full Import2 run and wait for the email.
- Compare deal counts and one owner per pipeline.
- Tell the team to edit in Pipedrive.
- Keep the Salesforce ZIPs offline. Do not queue another export over a set you have not downloaded.
Proof to capture: Import2's email is in, sample owners match, and the ZIPs are stored outside Salesforce.
Rollback
Put editing back in Salesforce if Pipedrive owners or stages are wrong.
- Tell reps to stop creating deals in Pipedrive.
- Undo the Import2 migration if the mapping is the problem. Pipedrive says undo has no extra cost.
- Export any deals that exist only in Pipedrive.
- Review those rows before you recreate them in Salesforce.
- Keep the downloaded ZIPs. Salesforce will not regenerate an expired export on demand.
Proof to capture: Salesforce is the only system being edited, and Pipedrive-only deals are listed.
- The initiating user owns another rep's deals
- A required record type was disabled
- Formula values you needed are missing and were not recomputed
- The 48-hour files were never downloaded
- Import2 is still running past the point you can explain to the team
Prove the migration worked.
Every blocking check must pass. Capture the evidence before cleanup begins.
| Pass | ID | Check | Method | Expected result | Evidence |
|---|---|---|---|---|---|
V-01Blocking | Invites first | Compare Salesforce owners with Pipedrive users. | Each owner exists before Start Import. | User list. | |
V-02Blocking | Global admin | Confirm who clicked Import from other software. | That person is a global admin. | Pipedrive role. | |
V-03Blocking | ZIPs local | Count files in Setup against files on disk. | Every ZIP from the run is stored outside Salesforce, and no newer export was queued. | Download log. | |
V-04Blocking | Excluded data | Look for recycle-bin rows and formula columns. | You restored anything required from the bin. You are not expecting formula columns in the CSV. | CSV header. | |
V-05Blocking | Sample deal | Open one deal per pipeline in Pipedrive. | Owner, stage, and custom fields match the Settings tab. | Sample notes. | |
V-06Blocking | Record count | Compare Import2's count with the objects you enabled. | The count is under 1,000,000 or the paid tier is accepted. | Import2 status. | |
V-07 | Rows after export start | Query Salesforce for records created after the export began. | Those rows are in a second pass or still edited in Salesforce. | Created-date report. | |
V-08Blocking | Production export | Read which org sent the ready email. | The archive came from production. | Ready email. |
Remove the scaffolding safely.
Safe after: Reps have worked a week in Pipedrive, owners match, and the Salesforce ZIPs are stored outside Setup.
- Leave Salesforce read-only if the contract allows it.
- Keep the export user until you are sure no ZIP is still only in Setup.
- Rebuild the automations you listed.
- Store the ZIPs with the Import2 completion email.
- Do not use a sandbox export as the archive.
- Schedule the next Pipedrive backup once rollback is closed.
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.
This is a SalesHusky case study, not an independent write-up. SalesHusky is a Pipedrive partner. Dick Putt, founder of Encore Land & Sea in Florida, says the company had been on Salesforce for 18 years. The pain he describes is complexity, not the license price. Custom work needed an outside programmer, and Salesforce support started over with a new person each time. He had also bought a year of a CRM called Pipeline and abandoned it in the second month. SalesHusky says Encore was live on Pipedrive within a month, with a sales pipeline and a projects pipeline. Won deals stay in a Closed Deals This Month column until a month-end automation marks them won and copies them into projects. Dick calls Pipedrive the best simple project tracker he found for that work, and he contrasts Franki at SalesHusky with impersonal Salesforce callbacks. The page is dated 20 October 2026.
- Decide which Salesforce customizations you will rebuild before the import. This account left that work to a partner after years of needing a programmer.
- Label a partner case study as the partner's account. The one-month go-live here includes SalesHusky's implementation, not only Import2.
- Encore kept two pipelines, sales and post-sale projects, joined by a month-end automation instead of a default won stage.
- The published reason for leaving was customization and support, after 18 years, not a quoted license number.
Verify against the primary material.
Platform behavior changes. Check these sources and the review dates above before executing a production migration.
- Pipedrive: Import2 from a previous CRMAccessed 2026-11-04
- Salesforce: Data Export FAQAccessed 2026-11-04