The Definitive Guide to Migrating to Pipedrive

Pipedrive was founded in Estonia in 2010 and is headquartered in New York City; Vista Equity Partners took a majority stake in 2020 at a reporting valuation near US$1.5 billion ¹. The product is a pipeline-first sales CRM: the deal Kanban is the home screen, and every other object — Persons, Organizations, Activities, Leads — exists to push deals from stage to stage.

The typical Pipedrive customer is a sales-led team of 5 to 200 reps. Compared with HubSpot Sales Hub, Pipedrive positions on a flatter price curve (no contact-tier billing) and a sales-only feature surface; compared with Salesforce, it positions on faster setup and the absence of an admin function; compared with Zoho or Freshsales, it positions on UI simplicity and Marketplace breadth.

The shapes of migration that actually land on Pipedrive cluster into four patterns. First, HubSpot exits triggered by contact-tier billing as the lead list grows ³. Second, Salesforce downsizes, where a smaller team that never used Apex or Flow walks away from the seat cost and the admin overhead. Third, legacy replacements — PipelineDeals, ACT!, Insightly, homegrown spreadsheets — where the source schema is loose and the project is really a re-architecture.

Fourth, consolidation projects where a multi-tool stack (spreadsheets plus inbox plus quoting tool) collapses into a single Pipedrive account with Smart Docs and Campaigns. Each shape has a different difficulty profile: a HubSpot move usually has clean object parity but messy custom-property internal values, while a Salesforce move has rich automation that does not transfer and must be rebuilt in Pipedrive's Workflow Automation ¹¹.

What makes migrating *to* Pipedrive easier than the category average is the spreadsheet importer — it accepts CSV, XLS and XLSX, covers eight item types in a single mapping screen, and ships a 48-hour Revert button that undoes the most recent import in a click ²⁷.

What makes it harder than the average is the option-field model: single- and multiple-option custom fields store internal IDs rather than display labels, so any update path that sends labels instead of IDs is rejected without a useful field-level hint ¹². Throughput on the platform also favours one-record-at-a-time loaders, so very large datasets need careful pacing ⁴⁵.

Workflow Automation rules, Smart Docs templates, Insights reports and lead-scoring logic do not import — they are rebuilt from documentation. Teams that scope for that work up front finish on time; teams that assume parity do not.

Teams that scope for the workflow rebuild up front finish on time; teams that assume parity do not.

Pipedrive's CRM is built around a small set of standard items, each with default and custom fields, and a shallow set of relationships that connect them. Unlike Salesforce or HubSpot, Pipedrive does not currently offer Custom Objects — every record you bring in must fit one of the eight first-class item types.

Before you can map a field on the source side, you need to know exactly which destination item the row belongs on, what fields it requires, and which value will serve as its upsert key on re-import. The table below summarises the items you will touch in a Pipedrive migration ¹³.

People use name as the only hard-mandatory field — but Pipedrive will silently create duplicates if you do not include an email or phone number for dedup matching during import ¹³. Organizations use organization name as their required field. Deals and Leads must be linked to either a Person or an Organization in the same row, otherwise the import skip file rejects them with Deal title must be given ¹⁴.

Pipedrive does not expose external-ID custom field types the way Salesforce or HubSpot do. The closest equivalent is the Pipedrive System ID — the platform-assigned integer for each record. To re-import an existing item (update rather than create), include a column mapped to *Pipedrive System ID* and the upsert finds the target by that ID ⁷. If the ID does not exist, the row is skipped with Person not found or Deal not found ¹⁴.

The practical pattern is: export each item type from Pipedrive once after the first load, capture the System IDs back into the source database, and use them as the upsert key on every subsequent delta. Custom field types determine validation and storage; the catalogue below covers what you can model and the limits you need to plan around ¹⁵.

Relationships in Pipedrive are modelled as direct links between item types, not as named association objects with labels. A Deal links to one Person (the *deal contact person*) and one Organization; a Person links to one Organization (its *primary organization*) but can also be a *participant* on multiple deals. There is no junction object, no master-detail cascade-delete, and no many-to-many association schema ¹³³⁰.

Custom objects do not exist as a first-class concept. Teams that depend on them in their source CRM typically work around the gap by repurposing Organizations as pseudo-objects, loading extra custom fields onto an existing item type, or syncing the data to an external tool via Zapier — every workaround has trade-offs in reporting cleanliness and maintenance.

The single best predictor of a clean Pipedrive migration is how much work you do on the source side before the first import button is pressed. Pipedrive's own guidance is explicit: clean the spreadsheet first, structure it to match Pipedrive's field shape, and only then upload — every minute spent pre-processing is a minute saved chasing duplicates after the cutover ²²⁰.

The single best predictor of a clean migration is how much work you do before the first import button is pressed.

Treat the source export as raw material to be shaped to Pipedrive's expected formats — currency stripped of symbols, phone normalised, option-field values converted to existing option IDs or labels, dates rewritten, owners resolved to Pipedrive users that already exist in the destination.

Source-side prep

• Audit and dedup the source database before export — Insycle, Dedupely and Scoop run native Pipedrive-bound dedup and can find email-case-only and phone-format-only duplicates that the spreadsheet importer will otherwise merge silently.
• Normalise emails and phones — lowercase emails, trim whitespace, convert phone numbers to E.164. Pipedrive's importer uses these as soft dedup keys when the *Merge similar records* option is checked.
• Strip currency symbols and special characters from monetary columns — Pipedrive rejects rows where currency is written as $ or € and accepts only the ISO code (USD, EUR) in a separate column ¹⁴.
• Decide your option-field strategy for every dropdown — either pre-create every Single/Multiple option field in Pipedrive with the exact label set from the source, or map source values to the destination labels in the spreadsheet before upload. Mismatches go to the skip file ¹².
• Decide what is in scope for historical activities and notes. Both can be imported via spreadsheet with backdated due dates, but native CSV imports from many source CRMs do not include engagement history at all — third-party tools like Import2 are usually needed to bring email and call history across.

Destination-side prep

• Spin up a test account — Pipedrive offers a 14-day free trial that doubles as a sandbox, and a Developer Sandbox is available for partners building integrations ²³. Run the full import end-to-end in the sandbox before pointing at production.
• Add users first under Settings → Manage users → Users. Owner assignment during import works only if the owner's Pipedrive user email matches a column value exactly — rows whose owner cannot be resolved default to the user initiating the import ³³.
• Pre-create every custom field under Settings → Data fields, on the right item type, with the right field type — Text vs Large text vs Single option matters because Pipedrive does not let you change a field's type after creation.
• Build pipelines and stages under Settings → Pipelines before importing any deals. Pipedrive will auto-create stages from a spreadsheet column if you let it, but the result is rarely the stage structure you actually want — define them first ³³.
• Activate the Pipedrive System ID feature under Settings → Data fields → System fields so the System ID column is visible on exports. Without it, re-import upsert by ID is not possible ⁷.

People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours — and communicate it to every department that touches the CRM. Train sales reps on Pipedrive's deal Kanban, activity logging and pipeline drag-and-drop before go-live, not after. A spreadsheet-only migration of under 10,000 records runs two to three weeks elapsed; a multi-pipeline project with deal history and Workflow Automation rebuilds runs eight to twelve weeks. Build the human runway accordingly.

Pipedrive exposes two main load paths and the right one depends on dataset size and source platform. The spreadsheet importer covers most one-shot migrations under a hundred thousand records. The native migration tool (powered by Import2 inside the Marketplace) handles HubSpot, Salesforce, Zoho and a longer list of source CRMs with relational context preserved.

Spreadsheet importer

The native import lives at account menu → Tools and apps → Import data → Get started, with a quick alternative path on any list view via (More) → Import data → From a spreadsheet ²²⁰. It accepts CSV, XLS and XLSX. The mapping screen is one of Pipedrive's strongest surfaces — it auto-matches column headers against default and custom fields, and any column it cannot map is highlighted for manual placement.

Pipedrive does not publish a hard row-cap, but very large files time out before processing finishes — the pragmatic ceiling is around 100,000 rows per file; split anything larger into sequential uploads. Unmappable rows land in a skip file you download, fix and re-upload ¹⁴. A Revert button in import history undoes the most recent run within 48 hours ².

Native migration tool (Import2 / SyncMatters)

Under Settings → Tools and apps → Marketplace there is an Import2 app that ships as Pipedrive's recommended one-click migration path from HubSpot, Salesforce, Zoho CRM and roughly 20 other sources ²⁵. The flow: install the app, connect both source and Pipedrive, choose which objects and how to handle pipelines, click migrate. Import2 preserves notes-to-contact relationships, deal-to-organization links and activity history that CSV imports often drop.

SyncMatters (formerly Trujay) is a paid Pipedrive partner offering the same shape with deeper field-mapping control, priced $299–$2,999 self-serve plus $750 guided. Both inherit Pipedrive's per-file size cap.

Mapping is where every migration earns its scars. The schema decisions you make in your mapping spreadsheet determine whether Insights reports work on day two, whether Workflow Automation rules fire correctly on day five, and whether your sales team trusts the deal Kanban on day thirty.

Work item by item, top to bottom of the import order: Organizations first (so deals and people can link to them), then People, then Deals, then Activities, then Notes, then Products. Leads can come at the start or the end — they do not block other items.

People (Persons)

Organizations

Deals and pipelines

Recreate every pipeline and every deal stage in Pipedrive before importing deals. Each stage is a named string scoped to a single pipeline — there is no internal-value-versus-label split as in HubSpot, but stage names are matched case-sensitively on import. Build the mapping table source-stage → Pipedrive-pipeline + Pipedrive-stage-name. Deals whose stage name does not exist on the named pipeline either get rejected or, if you let the importer auto-create, land in a fresh stage with no probability set ³⁵.

If you are consolidating multiple source pipelines, the cleanest approach is to keep them as separate Pipedrive pipelines for at least 90 days post-migration, then merge once Insights reports have stabilised. Deals can be moved between pipelines later from the deal detail view or via bulk edit ³⁵.

Custom-field mapping strategy

Resist the urge to map every source custom field one-to-one. Pipedrive's plan tier scopes the count of custom fields per item type — 30 on Lite, 100 on Growth, 200 on Premium, 300 on Ultimate — and required-field enforcement is only available on Professional/Power and Ultimate ¹⁷¹⁸. Migrate only the custom fields used by an active sales process or Insights report in the last 12 months; archive the rest.

For Single option and Multiple option fields whose source values do not match the destination, either: (1) extend the destination field with the missing option labels via Settings → Data fields → [field] → Add option, (2) collapse adjacent values during the transform step, or (3) introduce a parallel custom Text field that holds the legacy verbatim value. Formula custom fields (the formula field type) do not import — Pipedrive recomputes them on-platform from the source numeric/monetary fields ¹⁵.

Historical activities, notes, and engagement

Pipedrive supports importing Activities and Notes with backdated values via the spreadsheet importer — the *Due date* on Activities and the linked-item ID on Notes are honoured, so timeline order on a contact reflects the original sequence ¹³. Activity *Type* (call, meeting, task, email, lunch, deadline) is a controlled vocabulary plus admin-defined custom types — pre-create custom activity types under Settings → Company → Activity types before importing rows that use them.

For email and call history specifically, the native CSV import from many source CRMs (HubSpot, Salesforce) does not include the engagement bodies. The supported paths are: (a) Import2 or SyncMatters, which pull thread bodies and create matching Activities ²⁵; (b) Pipedrive Email Sync for live mail going forward, set up under Personal preferences → Email sync; (c) a custom loader that creates Notes carrying the email body, linked by source email address.

Note limits matter at scale — each Note is capped at roughly 100 kB of body content, and a single deal can hold up to 100 notes before further attempts are rejected. Long email threads should be summarised or split rather than dumped wholesale into a single Note.

Files and attachments

Attachments do not import in bulk via the spreadsheet importer. The supported path is the Files upload flow, which uploads a binary linked to a Person, Organization, Deal or Activity. Individual file size is capped at roughly 50 MB per file, with no overall storage cap published but a soft ceiling that scales with plan tier ³².

For large attachment estates (hundreds of GB), the pattern is: keep originals in Google Drive, OneDrive or S3, store a deep link in a custom Text field, and only inline-upload the most recent subset. Pipedrive's Google Drive and OneDrive integrations surface external files on the deal panel without consuming Pipedrive storage ³².

Audit trail, ownership, and original timestamps

Standard *Add date*, *Update time* and system audit columns are Pipedrive-managed — they stamp to the import moment and cannot be overwritten via the spreadsheet importer ³³. If you need to preserve the original audit trail, the pattern is to create two custom Date fields per item, *Legacy Created Date* and *Legacy Modified Date*, and populate them from the source export.

Owner assignment during import works only if the owner email matches an existing Pipedrive user at the moment of import; rows whose owner cannot be resolved default to the import-runner, silently breaking owner-based Workflow Automation. Provision every owning user (active or deactivated) before the import window opens, then deactivate non-current users after the data lands.

Account-level change auditing is available via the Ultimate-tier Security dashboard and Device history views under Settings → Security ³⁶ — lower tiers can see import history and a 365-day Restore data window for deletions, but not granular per-field change tracking.

CRM-specific: lead scoring, automation, email and calendar sync

Lead-scoring models from HubSpot or Salesforce do not import — Pipedrive's lead-scoring lives in higher tiers and is configured under Leads → Lead Scoring with its own rule engine. Recreate the rule logic from source documentation rather than migrating accumulated score values; if you must preserve historical scores, put them in a *Legacy Lead Score* custom Numerical field and let new scoring accrue forward.

Workflow Automation rules (the Pipedrive automation builder) do not import either — recreate them under Settings → Automations. Triggers, conditions and actions use a Pipedrive-native vocabulary; even a one-to-one rule from HubSpot Workflows or Salesforce Flow needs to be re-authored.

Email and calendar sync are set up per user under Personal preferences → Email sync and → Calendar sync *after* users are provisioned and historical activities are loaded — Calendar sync supports Google, Office 365 and Microsoft Exchange only ³⁷. Do not enable two-way sync during the import window, or the connector will backfill against the same Activities you are loading.

Validation is the bridge between the import finishing and users being allowed in. The reliable approach is three-stage: a test load of 10 percent of records with stakeholder spot-checks, the full load with real-time monitoring of record counts and link integrity, and a 30-day post-migration data-quality audit. The most reliable signal is having department reps verify their own records on their own deals — they know what right looks like better than any reconciliation script.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5 percent variance gets investigated before users get login access.

• Total People imported vs source — minus deliberately excluded rows (role-based emails, bounced lists, opt-outs).
• Total Organizations imported vs source — checking that name-similarity merge did not over-collapse rows.
• Total Deals per pipeline per stage vs source, plus **sum of *Value* per pipeline** by currency — a non-trivial variance usually signals a stage-mapping error or a currency-precision drop.
• Total Activities per type (call, meeting, task, email, deadline) imported vs source — and a date-bucketed comparison to confirm Due date round-tripped.
• Linkage integrity — count Person→Organization, Deal→Person and Deal→Organization links and compare against the source-derived expected counts. Pipedrive does not flag orphaned deals automatically.
• Owner distribution — group by Owner and confirm no record landed on the import-runner's account that should not have.
• System ID uniqueness on re-imports — after the first full load, export everything and confirm every record carries a non-null System ID before any delta runs.

On top of reconciliation, run a manual spot-check protocol: pick 30 random records across items and verify each field against the source UI. Pick five high-value deals and trace the full link graph — Person, Organization, Activities, Notes, Products. If a non-trivial discrepancy shows up in three or more of the 30, halt the load, fix the root cause, and re-import the affected rows by System ID.

Pipedrive ships Restore data under Settings → Tools and apps → Restore data, which lets every user (Lite/Growth) or admin (Premium+) recover deleted Persons, Organizations, Deals, Products and Leads for up to a year after deletion ³⁹. There is also a Revert button on each spreadsheet import in the import history, valid for 48 hours after upload ². Both are real, but neither is a full bulk rollback — Restore is record-by-record and Revert only undoes the most recent run.

The real rollback strategy remains: export everything to S3 or a warehouse before the import starts, stamp every imported row with an *Import Batch ID* custom Text field, and if catastrophe strikes, bulk-delete by that batch ID via the list view filter and re-import from the cleaned source.

Cutover sequencing: (1) source goes read-only; (2) final delta export captures everything that changed during the test-import window; (3) delta is imported via spreadsheet by System ID; (4) reconciliation runs; (5) Workflow Automation rules and email sync switch on; (6) users get login access with a 48-hour hyper-care window; (7) source decommission is scheduled 30 to 90 days out, never the same day.

The Pipedrive Marketplace lists Service Partners tiered Platinum, Gold and Silver by certifications, customer count and revenue ⁴⁰. For sales-led migrations specifically, partners with explicit HubSpot-to-Pipedrive, Salesforce-to-Pipedrive or PipelineDeals-to-Pipedrive practices tend to ship cleaner than generalist implementation shops.

PD Experts (Platinum, DACH), Kulea (UK), Metawork Studio (DACH), MinorCo and EasyNerdy are commonly named in the migration corner of the market and each offers fixed-scope packages alongside managed services. Pipedrive's own implementation team handles enterprise onboarding; smaller teams are routed via the Find an expert matchmaking flow inside the Marketplace ⁴⁰.

On the migration-software side, Import2 is the recommended one-click migrator inside the Pipedrive Marketplace, supporting HubSpot, Salesforce, Zoho CRM and roughly 20 other source platforms with relational context preserved ²⁵. SyncMatters (formerly Trujay) ships a deeper field-mapping interface at $299–$2,999 self-serve plus a $750 guided tier. Both inherit Pipedrive's single-record throughput characteristics; the value is in the mapping UI and the handling of attachments and notes that CSV imports drop.

On the ETL and iPaaS side, Fivetran, Airbyte, Stitch and Workato all carry Pipedrive connectors. Their role in a migration is rarely the migration itself — it is the staging layer that lands source data into a warehouse, the transformation layer that converts option-field labels and resolves owner emails, and the ongoing-sync layer that takes over once the one-time migration is complete.

Managed-migration cost ranges vary widely. A clean HubSpot-to-Pipedrive move of under 10,000 contacts with no historical activities often lands in the £2,500–£7,500 / $3,000–$10,000 range with a setup fee plus per-object pricing. A Salesforce-to-Pipedrive project with deal history, custom field translation, activity migration and Apex-to-Workflow-Automation rebuilds typically runs $15,000–$60,000, driven by record count, custom-field complexity, historical-data depth and integrations to rebuild.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Pipedrive migrations and handles the field mapping, historical-data preservation, option-field ID translation, and validation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on record count and source platform, with separate line items for Activity history and attachment migration so the scope is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want a Pipedrive Service Partner, the in-product Import2 path, an iPaaS-first approach, or a specialist migration vendor. Explore FlitStack →