Your custom fields, your history, your relationships. Not only the fields both apps happen to have in common.
Start free assessmentWe run Salesforce CRM to Pipedrive CRM migrations. The assessment is free and comes before any commitment.
Running this for a client? Explore partnership options.
Salesforce CRM
Pipedrive CRM
Keep deals linked to contacts and companies, and activities linked to their records in Pipedrive CRM.
We find your custom fields in Salesforce CRM and plan how their values will travel to Pipedrive CRM before migrating their records.
Your activity history arrives on the record it belongs to. This page names which types transfer and any limit on them.
We match them to your Pipedrive CRM users and stages.
The plan flags values that change during migration. The original value comes across beside the converted one.
Where possible, we create a field in Pipedrive CRM for data with no matching field.
Each row explains a limit and what you can do about it. Open the details for the reason and supporting source.
How many deals your Pipedrive plan will hold is capped
View detailsHide detailsPipedrive counts your active leads and deals against a limit set by your plan, 2,500 per user on Lite, 5,000 per user on Growth and 15,000 for the whole company on Premium. A Salesforce org with more opportunities than your plan holds cannot bring them all across.
Verified against support.pipedrive.comWe count yours first, so you see that before you commit.
A field that holds a date and a time keeps the date
View detailsHide detailsPipedrive's custom field types are date and time as two separate kinds, with no combined one. So a Salesforce date/time field we create in Pipedrive keeps the day and not the time of day.
Verified against support.pipedrive.comThe assessment names the fields this affects before anything is written.
Your logged emails stay in Salesforce CRM
View detailsHide detailsPipedrive fills its inbox by syncing a mailbox, and its mail API reads, updates and deletes the messages that arrive there. It publishes nothing that creates one. So a Salesforce email that was sent years ago has no route in.
Verified against developers.pipedrive.comYour calls, events and tasks come across, and the email stays where it is.
Your Salesforce custom objects have no home in Pipedrive
View detailsHide detailsPipedrive's items are the seven it ships, leads, deals, people, organizations, activities, products and projects, and an account cannot add one of its own. So the records of a Salesforce custom object have nowhere to land.
Verified against support.pipedrive.comWe say which ones that affects during the assessment rather than after the run.
One action removes the records we wrote to Pipedrive CRM. Review what will remain before you undo and retry.
A paused run resumes where it stopped, without losing progress or duplicating records.
We only read Salesforce CRM. Nothing is written back to it.
Keep working in Salesforce CRM while you check the results. Then bring across the latest changes before switching over.
In Pipedrive CRM after the migration
After you undo
Covers up to 20,000 records. Larger migrations use higher tiers. You pay once per migration, with no recurring charge.
Connect Salesforce CRM to see your record count and price before you commit.
Ask for a refund within 30 days of your migration being marked complete. We reverse the migrated data out of Pipedrive CRM and refund you.
Yes. The free assessment finds them in Salesforce, and they are created as custom fields on the matching Pipedrive item before records are migrated. Review the plan and choose whether to leave unused fields behind.
Both land as Pipedrive people. Accounts become organizations and Opportunities become deals, so the shape of your pipeline comes with you, and a lead arrives as a record your team can work rather than one waiting to be converted.
Your tasks land as Pipedrive to-dos, a task logged as a call lands as a call activity, and your events land as meetings, each one on the record it belongs to and with its owner and its date. The files on your Salesforce records come across onto the record they were attached to.
They stay in Salesforce. Salesforce keeps notes as files rather than as activities, so we cannot read them the way we read your calls, emails and tasks. This is on your plan before you commit.
Your product catalogue comes across as Pipedrive products. The lines priced on each opportunity do not yet, and that one is our limit rather than Pipedrive's, so it is on your plan before you pay rather than a surprise after the run.
Your deals are routed onto the pipelines your Pipedrive account already has rather than into new ones we create, matched by what each stage meant. A stage with nowhere to go is named before the run rather than discovered during it.
No. We work out what each value becomes, so nobody builds a field map. You review the plan before the migration runs. A Salesforce field with no native home in Pipedrive can be brought along as a new field instead of being left behind.
We run the migration and stay reachable. Connect Salesforce for the free assessment and price, then Pipedrive to complete the plan. Nothing moves until you ask.
Yes. We only read Salesforce and never write back to it. Keep working while you check the results, then bring across the latest changes before switching over.
You can undo the migration, correct the issue and run again. Created fields, shared catalogue data and any other items listed as retained stay in place.
One payment, based on the records that move. The free assessment of Salesforce gives you the exact count and price before you commit. Payment is by invoice, with no subscription.
Next step
Create an account and connect Salesforce CRM for your free assessment. See your record count and price before you commit. Nothing moves until you ask.
Start free assessment