
Pipedrive migration
Pipedrive migration
Pipedrive is a sales CRM built around deals that travel through the stages of a pipeline, each tied to a person and an organization, with activities setting the next step. Leads sit apart from deals, and synced email sits in its own Mailbox. We move that data out of Pipedrive or into it, and scope other routes on a call.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Pipedrive migration at a glance
- Who it is for
- Sales teams that run their pipeline in Pipedrive and are moving to a larger CRM, or moving in from another one, and the consultants who run those projects.
- What moves
- Persons, organizations, deals with pipeline and stage, leads, activities, notes, files, products and custom fields, plus synced email where the plan allows it.
- What does not move as-is
- Automations, email templates, reports, dashboards and filters. No Pipedrive export route covers them, so we list each one for rebuilding.
- What sets the scope
- Deal and person counts, notes and files on each record, whether email sync is on, the custom field count, and the daily API token budget your plan and seat count give you.
What moves
What moves from Pipedrive?
MigrateX moves Pipedrive persons, organizations, deals with their pipelines and stages, leads, activities, notes, files, products and custom fields.
- Persons
- Organizations
- Deals
- Pipelines and stages
- Leads
- Activities
- Notes
- Files
- Products
What does not move
What does not move from Pipedrive as-is
Configuration, not data. We list each item in scope so your team can rebuild it in the target.
- Automations and workflows
- What we do: Rebuilt in the destination. We found no Pipedrive export route for them, so each is listed with its trigger and actions.
- Email templates, reports, dashboards and filters
- What we do: Rebuilt on the migrated fields. No Pipedrive export route for them was found.
- Files stored in Google Drive
- What we do: Pipedrive leaves them out of its global export, so they are listed and re-linked from Drive if you want them on the record.
Source: Pipedrive Knowledge Base, checked 15 Nov 2026
- Synced email history
- What we do: No export route for email is documented in the app. We read it through the Mailbox API where your plan has email sync, and treat what is missing as a gap we show you.
Source: Pipedrive Knowledge Base, checked 15 Nov 2026
- When an activity was marked done
- What we do: The v2 API returns marked_as_done_time but its update call exposes only the done flag, so the completion time is kept in a field.
Source: Pipedrive developer documentation, checked 15 Nov 2026
- Duplicate people and organizations
- What we do: Pipedrive's spreadsheet import offers a step to merge duplicates instead of creating new records. Whether duplicates merge or stay apart is agreed with you during the free sample.
Source: Pipedrive Knowledge Base, checked 15 Nov 2026
What does a Pipedrive migration have to handle?
A Pipedrive migration has to build pipelines and stages before any deal loads, keep every deal tied to its person and organization, collect notes, activities, files and email by their own routes, and stay inside the daily token budget. Your Pipedrive admin and our engineer settle each point before the free sample.
- Pipelines and stages come before deals
- A deal carries a pipeline_id and a stage_id, so both must exist in the destination before deals load. Stage names are matched in a table you approve, because two pipelines can use the same stage name.
Source: Pipedrive developer documentation, checked 15 Nov 2026
- Leads are not deals
- Pipedrive keeps leads in their own inbox, apart from the deal pipeline, and each needs a person or organization name. We agree with you whether leads stay leads or become deals in the destination.
Source: Pipedrive Knowledge Base, checked 15 Nov 2026
- Notes, activities and files are separate exports
- Pipedrive's Export data tab downloads one item type at a time. Activities, notes and files linked to deals and contacts must be exported on their own, so each type is read and rejoined to its parent.
Source: Pipedrive Knowledge Base, checked 15 Nov 2026
- Email is in the Mailbox, and only through the API
- Pipedrive's export article does not mention email. Synced messages are read through the Mailbox endpoints with the mail:read scope, and the body arrives only when include_body is set. Email sync itself needs the Growth plan or higher.
Source: Pipedrive developer documentation, checked 15 Nov 2026
- Creation dates depend on the object
- In the v2 API, persons and organizations accept add_time when created, and notes accept it too. The v2 bodies for deals and activities list no add_time, though deals do accept close, won and lost times. We confirm each date during your free sample.
Source: Pipedrive developer documentation, checked 15 Nov 2026
- Users first, or the importer owns everything
- Pipedrive advises setting up users before a migration, because data brought in is owned by whoever started the import. Owners are created and matched first, so every record lands with its real owner.
Source: Pipedrive Knowledge Base, checked 15 Nov 2026
- Load order follows the links
- Pipedrive's own guide for a HubSpot move imports organizations, then persons, deals, leads, activities and notes. We follow that order, since each later record points at an earlier one.
Source: Pipedrive Knowledge Base, checked 15 Nov 2026
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationMigration paths
Where can I move to or from Pipedrive?
Routes we run from and into Pipedrive. Open a route to see what migrates, or ask us about one that is not listed yet.
From Pipedrive
191 connectors, all live
Every connector is live, so Pipedrive can be paired with any of them. Some of the CRM platforms:
- Salesforce Sales Cloud
- Dynamics 365 Sales
- Zoho CRM
- Freshsales
- monday CRM
- Zendesk Sell
- Attio
- Copper
- Close
- Insightly
Platform not listed?
We build new connectors in 2 to 3 days. Tell us what you run and we scope the route with you.
Timeline
Your Pipedrive migration, step by step
Estimated total
About 10 business days
end to end
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Preparation
Day 1-2
Scoping call
Both0.5 dayA 30 minute call with the engineer who will run the migration, to agree the objects, date ranges and volumes in scope.
Connect both platforms
You0.5 dayYou create scoped API credentials on the source and the destination. Nothing is written until you sign off the mapping.
Field mapping review
Both1 dayWe walk through every field, pipeline stage and owner mapping with your team and note the ones that need a decision.
Migration
Day 3-7
Free sample migration of 100 records
MigrateX1 dayA sample of your real records is migrated end to end so you can see the result before the full run.
You review the sample
You1 dayYour team opens the migrated records and tells us what to adjust. We rerun the sample until it is right.
Full migration
MigrateX2-3 daysThe bulk pass runs in dependency order, paced to the destination rate limit. Your team keeps working normally.
Delta sync
MigrateX0.5 dayEverything created or changed during the bulk pass is synced at cutover so nothing falls between the two systems.
Validation
Day 8-10
Validation report
MigrateX1 dayRecord counts per object and per status on both sides, plus every record that needed a default or a placeholder.
Spot checks and sign-off
You1-2 daysYour sales managers check a random sample and sign off. We stay available for two weeks after go-live.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
See how it works in detailData model
Pipedrive data model and limits
How Pipedrive holds the records that move, and the vendor limits that set the pace of the migration.
How does Pipedrive store CRM data?
Pipedrive keeps a sale as a Deal that sits in one stage of a pipeline and links to a Person and an Organization. Leads, Activities, Notes, Files and Products hang off those records, and synced email lives apart in the Mailbox. A migration reads or writes each of these through its own route.
| Object | What it holds | How it links |
|---|---|---|
| Person | A contact, with emails, phones, labels and custom fields. | Points to an Organization through org_id and to an owner through owner_id. |
| Organization | A company, with an address, website, industry and custom fields. | Owned by one user. Persons and deals point to it. |
| Deal | A sale in progress: status, value, currency, lost reason, an archived flag, and close, won and lost times. | Points to a person, an organization, a pipeline and a stage. |
| Pipeline and stage | The path a deal travels. Stages belong to a pipeline. | Both have their own v2 endpoints, and a deal carries pipeline_id and stage_id. |
| Lead | An unqualified prospect, kept apart from deals. | Needs at least one lead field and a person or organization name. Source: Pipedrive Knowledge Base |
| Activity | A call, meeting, task or other typed action, with a due date and time and a done flag. | Links to a deal, lead, organization or project, with participants and attendees. |
| Note | Free text in HTML, with an author. | Attached to a person, deal, lead, organization, project or task. |
| File | An uploaded document. The API returns its metadata and a download URL. | Linked to a person, organization, deal, activity, product or lead. |
| Product | An item in a standalone catalogue. | Attached to deals through the deals products endpoint. |
| Custom field | Field definitions, one set per object: persons, deals, organizations, products and activities. | Written as custom_fields on a record in the v2 API. |
| Mailbox message | Synced email threads and messages, listed per deal. | Needs the Growth plan or higher. The full body comes only when include_body is requested. |
Person
- What it holds
- A contact, with emails, phones, labels and custom fields.
- How it links
- Points to an Organization through org_id and to an owner through owner_id.
Organization
- What it holds
- A company, with an address, website, industry and custom fields.
- How it links
- Owned by one user. Persons and deals point to it.
Deal
- What it holds
- A sale in progress: status, value, currency, lost reason, an archived flag, and close, won and lost times.
- How it links
- Points to a person, an organization, a pipeline and a stage.
Pipeline and stage
- What it holds
- The path a deal travels. Stages belong to a pipeline.
- How it links
- Both have their own v2 endpoints, and a deal carries pipeline_id and stage_id.
Lead
- What it holds
- An unqualified prospect, kept apart from deals.
- How it links
- Needs at least one lead field and a person or organization name.
Source: Pipedrive Knowledge Base
Activity
- What it holds
- A call, meeting, task or other typed action, with a due date and time and a done flag.
- How it links
- Links to a deal, lead, organization or project, with participants and attendees.
Note
- What it holds
- Free text in HTML, with an author.
- How it links
- Attached to a person, deal, lead, organization, project or task.
File
- What it holds
- An uploaded document. The API returns its metadata and a download URL.
- How it links
- Linked to a person, organization, deal, activity, product or lead.
Product
- What it holds
- An item in a standalone catalogue.
- How it links
- Attached to deals through the deals products endpoint.
Custom field
- What it holds
- Field definitions, one set per object: persons, deals, organizations, products and activities.
- How it links
- Written as custom_fields on a record in the v2 API.
Mailbox message
- What it holds
- Synced email threads and messages, listed per deal.
- How it links
- Needs the Growth plan or higher. The full body comes only when include_body is requested.
Pipedrive objects that hold sales data, as of 15 November 2026. Source: Pipedrive API reference and help centre.
Which Pipedrive limits set the pace?
Pipedrive limits a company by a daily token budget that scales with plan and seats, and each user by a burst window of two seconds. These are the allowances that decide how fast persons, deals, notes and files move in or out, and which export and import routes can carry a whole account.
| Limit | Allowance |
|---|---|
| Daily token budget | 30,000 base tokens times the plan multiplier times the number of seats, plus any purchased top-ups. The multiplier is Lite 1, Growth 2, Premium 5 and Ultimate 7. It resets at midnight server time. |
| When the budget runs out | Every further request is rejected with HTTP 429 until the reset. |
| Burst limit per user | Per rolling 2 seconds: API token 20 (Lite), 40 (Growth), 100 (Premium), 120 (Ultimate). OAuth apps 80, 160, 400 and 480. The Search API allows 10 on every plan. |
| Token cost per call | Get one record 2, get a list 20, update one 10, delete one 6, search 40. The v2 endpoints generally cost less than v1. |
| Pagination | Cursor paging on v2 list endpoints, up to 500 items a page and 100 by default. Older endpoints page with start offsets. |
| Files endpoints | 100 items a page since 15 January 2025, down from 500. The API documents no per-file size limit. |
| Export from the app | Excel or CSV, one item type at a time, with notes as HTML or plain text. Files stay available for 28 days. Only global admins and permitted users can export, and only the data they can see. No row limit is stated. Source: Pipedrive Knowledge Base |
| Spreadsheet import | XLS, XLSX or CSV, one tab with a header row, at most 200,000 rows and under 50 MB. Source: Pipedrive Knowledge Base |
| Mandatory import fields | A person name, an organization name, and a product name. Deals and leads need a person or organization name. Notes must link to a record. Activities have no mandatory field. Source: Pipedrive Knowledge Base |
| Why import rows are skipped | A missing deal title or name, an unknown system ID, a currency symbol instead of a code, or an unauthorised user. Source: Pipedrive Knowledge Base |
| Combined deals and leads | Beyond the plan's combined limit, imported deals and leads are diverted to the skip file or an overflow list. The article words the limit as 300,000 on all plans except Enterprise, a plan name from before the 2025 renames. Source: Pipedrive Knowledge Base |
| Custom fields per company | From 30 on Lite to 500 on Ultimate. Source: Pipedrive Knowledge Base |
| Plan names | Lite, Growth, Premium and Ultimate, which replaced Essential, Advanced, Professional or Power, and Enterprise in the 2025 repackaging. Email sync needs Growth or higher, and project exports need Premium or higher or the Projects add-on. Source: Pipedrive Knowledge Base |
| System fields on import | Every item type has owner, creation date and Pipedrive System ID as import fields, but some system fields cannot be mapped or are set automatically. Source: Pipedrive Knowledge Base |
| Pipedrive's Import2 service | Takes data in from sources such as Salesforce, HubSpot and Zoho CRM, free up to 1,000,000 records. It does not move data out of Pipedrive. Source: Pipedrive Knowledge Base |
Daily token budget
- Allowance
- 30,000 base tokens times the plan multiplier times the number of seats, plus any purchased top-ups. The multiplier is Lite 1, Growth 2, Premium 5 and Ultimate 7. It resets at midnight server time.
When the budget runs out
- Allowance
- Every further request is rejected with HTTP 429 until the reset.
Burst limit per user
- Allowance
- Per rolling 2 seconds: API token 20 (Lite), 40 (Growth), 100 (Premium), 120 (Ultimate). OAuth apps 80, 160, 400 and 480. The Search API allows 10 on every plan.
Token cost per call
- Allowance
- Get one record 2, get a list 20, update one 10, delete one 6, search 40. The v2 endpoints generally cost less than v1.
Pagination
- Allowance
- Cursor paging on v2 list endpoints, up to 500 items a page and 100 by default. Older endpoints page with start offsets.
Files endpoints
- Allowance
- 100 items a page since 15 January 2025, down from 500. The API documents no per-file size limit.
Export from the app
- Allowance
- Excel or CSV, one item type at a time, with notes as HTML or plain text. Files stay available for 28 days. Only global admins and permitted users can export, and only the data they can see. No row limit is stated.
Source: Pipedrive Knowledge Base
Spreadsheet import
- Allowance
- XLS, XLSX or CSV, one tab with a header row, at most 200,000 rows and under 50 MB.
Source: Pipedrive Knowledge Base
Mandatory import fields
- Allowance
- A person name, an organization name, and a product name. Deals and leads need a person or organization name. Notes must link to a record. Activities have no mandatory field.
Source: Pipedrive Knowledge Base
Why import rows are skipped
- Allowance
- A missing deal title or name, an unknown system ID, a currency symbol instead of a code, or an unauthorised user.
Source: Pipedrive Knowledge Base
Combined deals and leads
- Allowance
- Beyond the plan's combined limit, imported deals and leads are diverted to the skip file or an overflow list. The article words the limit as 300,000 on all plans except Enterprise, a plan name from before the 2025 renames.
Source: Pipedrive Knowledge Base
Custom fields per company
- Allowance
- From 30 on Lite to 500 on Ultimate.
Source: Pipedrive Knowledge Base
Plan names
- Allowance
- Lite, Growth, Premium and Ultimate, which replaced Essential, Advanced, Professional or Power, and Enterprise in the 2025 repackaging. Email sync needs Growth or higher, and project exports need Premium or higher or the Projects add-on.
Source: Pipedrive Knowledge Base
System fields on import
- Allowance
- Every item type has owner, creation date and Pipedrive System ID as import fields, but some system fields cannot be mapped or are set automatically.
Source: Pipedrive Knowledge Base
Pipedrive's Import2 service
- Allowance
- Takes data in from sources such as Salesforce, HubSpot and Zoho CRM, free up to 1,000,000 records. It does not move data out of Pipedrive.
Source: Pipedrive Knowledge Base
Pipedrive limits that shape a migration, as of 15 November 2026. Source: Pipedrive developer docs and help centre, linked per row.
Facts checked 15 Nov 2026. Sources: Pipedrive developer documentation and Pipedrive Knowledge Base.
Pipedrive migration questions
Still unsure? Ask us on the scoping call.
What does a Pipedrive migration cost?
The cost of a Pipedrive migration follows the persons, organizations and deals in scope, and the notes, activities, files and email attached to them. The number of pipelines, stages and custom fields to map adds work. The free sample covers 100 of your records, and the fixed quote arrives within 24 hours.
How long does a Pipedrive migration take?
The default plan is about 10 business days end to end. On Pipedrive the pace is set by your daily token budget, which is 30,000 tokens times your plan multiplier times your seats. A small Lite account can hit HTTP 429 and wait for the midnight reset. The free sample measures the real pace.
How do I export all data from Pipedrive?
From the Export data tab, one item type at a time, as Excel or CSV. Leads, deals, organizations, people, products, activities, projects, notes and files each export on their own, and the files stay available for 28 days. MigrateX reads every type through the API and rejoins each record to its parent.
Can I export notes, files and emails from Pipedrive?
Notes and files, yes: each has its own export, with notes as HTML or plain text, though files stored in Google Drive are left out. Emails are different. The export article does not cover them, so we read synced messages through the Mailbox API, which needs the Growth plan or higher for email sync.
Do Pipedrive deals keep their original created dates?
Not always, and it depends on the object. In the v2 API, persons, organizations and notes accept add_time, but the deal and activity bodies list none, although deals accept close, won and lost times. We confirm every date field during your free sample, before any deal is loaded.
Why do my Pipedrive imports skip rows?
Pipedrive writes rejected rows to a skip file. The usual causes are a missing deal title or name, a system ID it does not know, a currency symbol where a code is needed, or a user without permission. Beyond the plan's combined deal and lead limit, rows are diverted as well. We check these before the load.
Does Pipedrive's Import2 replace a managed migration?
Only for moving into Pipedrive. Import2 takes data from sources such as Salesforce, HubSpot and Zoho CRM and is free up to 1,000,000 records, but users must be set up first or the data is owned by whoever ran it. It does not move data out of Pipedrive, which is where MigrateX is used.
What access do you need to our Pipedrive account?
A global admin, or a user with export permission, because Pipedrive limits exports to those users and to the data they can see. Reading synced email also needs the mail:read scope, and email sync itself needs the Growth plan or higher. MigrateX is SOC 2 Type II, GDPR and HIPAA compliant.
Guides
Guides for a Pipedrive migration

Start with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.


