# Move your Salesforce CRM data into Pipedrive CRM Your custom fields, your history, your relationships. Not only the fields both apps happen to have in common. Migratez runs Salesforce CRM to Pipedrive CRM migrations. The assessment is free and comes before any commitment. Canonical page: https://migratez.com/migrations/salesforce-to-pipedrive-crm-migration ## What lands in Pipedrive CRM - Accounts → Organizations - Contacts → People - Leads → People (so what arrives is a record your team can work) - Person Accounts → People - Products → Products - Opportunities → Deals - Tasks → To-do activities - Tasks logged as calls → Call activities - Events → Meeting activities - Salesforce Files → Pipedrive files, on the record they were attached to - Opportunity stages → Matched to the stages your Pipedrive account already has (with any stage that has nowhere to go named before the run) - An opportunity won or lost → Marked won or lost on the Pipedrive deal itself (Pipedrive keeps that on the deal rather than at the end of the funnel) - Custom fields → Created as custom fields on the item they belong to - Users → Matched to your Pipedrive users by email (and you name who inherits the records of anyone with no match) - Links between records → Pipedrive's own links between people, organizations, deals and activities ## What comes across Comprehensive by default, customizable on request. - **Relationships, not just records.** The graph survives. Deals stay attached to the right contacts and companies, activities stay on the record they belong to, and the links between them are rebuilt in Pipedrive CRM rather than left behind. - **Your custom fields come with you.** They are found in Salesforce CRM and created in Pipedrive CRM before a single record is written. Not flattened into a notes field. - **History, not just the current state.** Notes, calls and meetings arrive on the record they belong to, with their owners and timestamps intact. - **Owners, pipelines and stages are reconciled.** Matched to your Pipedrive CRM users and stages rather than reset to a default. - **Nothing is silently rewritten.** Where a conversion is genuinely lossy, the original value comes across alongside the converted one, so you can always see what the data was before we touched it. - **A field with no home is brought along.** If Pipedrive CRM has no native place for something you use, we can create one for it rather than drop it. ## What happens to the rest - **Your logged emails stay in Salesforce CRM** (unsupported). Pipedrive 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. Instead: Your calls, events and tasks come across, and the email stays where it is. Verified against https://developers.pipedrive.com/docs/api/v1/Mailbox - **How many deals your Pipedrive plan will hold is capped** (requires_action). Pipedrive 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. Instead: We count yours first, so you see that before you commit to anything. Verified against https://support.pipedrive.com/en/article/new-pipedrive-plans - **Your Salesforce custom objects have no home in Pipedrive** (unsupported). Pipedrive'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. Instead: We say which ones that affects during the assessment rather than after the run. Verified against https://support.pipedrive.com/en/article/data-fields-in-pipedrive - **A field that holds a date and a time keeps the date** (degraded). Pipedrive'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. Instead: The assessment names the fields this affects before anything is written. Verified against https://support.pipedrive.com/en/article/what-types-of-custom-fields-are-there ## If it goes wrong - **Undo the records we wrote.** Every write into Pipedrive CRM is recorded, so one action takes the records we wrote back out again, in reverse. If it is not what you expected, restore and retry. - **Paused, not lost.** A stop, an error or an API limit pauses the run at its last checkpoint rather than killing it. Nothing is lost and nothing is written twice. - **Read-only in Salesforce CRM.** Nothing is ever written back into Salesforce CRM. It is the system you are leaving, and we only read it. - **A last catch-up before you switch over.** After the main load, one action brings across everything that changed in Salesforce CRM since, so you can verify with both systems live and then switch over. ## What it costs One price, one time, set by how many records you move. - **From $399.** That covers up to 20,000 records. The price steps up with volume and it is for the migration, not a subscription. Nothing recurs. - **The free assessment settles the number.** It reads Salesforce CRM and reports what is actually in it, so your price comes from your real record count rather than a sales call. You see it before you commit to anything. - **A 30-day money-back guarantee.** 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. ## Questions about moving Salesforce CRM to Pipedrive CRM ### Will my Salesforce custom fields come across? Yes. The free assessment finds them in Salesforce, and they are created as custom fields on the matching Pipedrive item before a single record is written. You see that mapping before anything runs, and you can drop the fields nobody fills in any more rather than carry them over. ### What happens to my Leads and Person Accounts? 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. ### What happens to my activity history? 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. ### What about my Salesforce notes? 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 to anything. ### What about the line items on my opportunities? 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. ### Do my opportunity stages survive? 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. ### Do I have to build a field map? No. The mapping is written for this one direction and shown to you before anything runs, so your part is reviewing it rather than assembling it. A Salesforce field with no native home in Pipedrive can be brought along as a new field instead of being left behind. ### Who actually runs the migration? You create an account and connect Salesforce, and the free assessment tells you what is in it and what it costs. Pipedrive is connected next, so we can check it against what your account can hold. I run the migration itself and stay reachable while it does. Nothing moves until you ask for it. ### Can I keep working in Salesforce while this happens? Yes. Nothing is ever written back into Salesforce, we only read it. After the main load, one action brings across everything that changed in Salesforce since, so you can verify with both systems live and switch over when you are ready. ### What if the result is not what I expected? Every write into Pipedrive is recorded, so one action takes the records we wrote back out again. You can sort out what was wrong and run it again. ### What does it cost? One price, one time, based on how many records the migration moves. The free assessment counts them in your Salesforce and gives you the exact price before you commit to anything. There is no subscription and no card form.