---
title: "Migrate to Pipedrive: CRM Migration Guide & Service"
description: "Migrating to Pipedrive? Import limits, the full migration checklist and every source FlitStack AI moves into Pipedrive, with history and rollback."
url: "https://flitstack.ai/migrations/crm/pipedrive"
---

# Migrate to Pipedrive

Pipedrive is a pipeline-first sales CRM whose import model rewards teams that pre-create custom fields per plan tier, normalise option-field values, and respect the spreadsheet importer's shape before the first file is uploaded.

Short answer

FlitStack AI migrates pipelines, contacts, and deals into Pipedrive from 850+ CRMs, including HubSpot, Zendesk Sell, Mailchimp, Salesforce. Every field is mapped to Pipedrive's objects, history and associations come across, the Pipedrive setup is configured alongside, and the whole migration stays reversible in one click.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [Pipedrive implementation service →](https://flitstack.ai/services/pipedrive-implementation)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

From Any source ![](https://flitstack.ai/platforms-trim/hubspot.webp) ![](https://flitstack.ai/platforms-trim/zendesk-sell.webp) ![](https://flitstack.ai/platforms-trim/mailchimp.webp)

Destination Pipedrive ![](https://flitstack.ai/platforms-trim/pipedrive.webp)

HubSpot Zendesk Sell Mailchimp Salesforce HoneyBook

850+ sources mapped into Pipedrive

## Systems we move into Pipedrive

The CRMs teams most often move from. Each page shows what moves, the field mapping and what to watch for.

[HubSpot to Pipedrive](https://flitstack.ai/migrations/crm/hubspot/to/pipedrive) [Zendesk Sell to Pipedrive](https://flitstack.ai/migrations/crm/zendesk-sell/to/pipedrive) [Mailchimp to Pipedrive](https://flitstack.ai/migrations/crm/mailchimp/to/pipedrive) [Salesforce to Pipedrive](https://flitstack.ai/migrations/crm/salesforce-sales-cloud/to/pipedrive) [HoneyBook to Pipedrive](https://flitstack.ai/migrations/crm/honeybook/to/pipedrive) [Zoho CRM to Pipedrive](https://flitstack.ai/migrations/crm/zoho-crm/to/pipedrive) [Daylite to Pipedrive](https://flitstack.ai/migrations/crm/daylite/to/pipedrive) [![](https://flitstack.ai/platforms-trim/activecampaign.webp) ActiveCampaign to Pipedrive](https://flitstack.ai/migrations/crm/activecampaign/to/pipedrive) [Housecall Pro to Pipedrive](https://flitstack.ai/migrations/crm/housecall-pro/to/pipedrive) [Close to Pipedrive](https://flitstack.ai/migrations/crm/close/to/pipedrive) [Civicrm to Pipedrive](https://flitstack.ai/migrations/crm/civicrm/to/pipedrive) [Jobber to Pipedrive](https://flitstack.ai/migrations/crm/jobber/to/pipedrive) [Entera to Pipedrive](https://flitstack.ai/migrations/crm/entera/to/pipedrive) [Odoo CRM to Pipedrive](https://flitstack.ai/migrations/crm/odoo-crm/to/pipedrive) [Rocket Matter to Pipedrive](https://flitstack.ai/migrations/crm/rocket-matter/to/pipedrive) [Attio to Pipedrive](https://flitstack.ai/migrations/crm/attio/to/pipedrive) [SmartDesk to Pipedrive](https://flitstack.ai/migrations/crm/smartdesk/to/pipedrive) [![](https://flitstack.ai/platforms-trim/chartmogul.webp) ChartMogul to Pipedrive](https://flitstack.ai/migrations/crm/chartmogul/to/pipedrive)

## What Pipedrive supports, and where its import tools stop

- Clean drag-and-drop pipeline interface with minimal learning curve, making it approachable for small sales teams without dedicated CRM admins.
- Visual deal tracking keeps reps focused on next actions — activities, calls, and follow-up tasks surface directly in the pipeline view.
- Strong integrations via Zapier and native marketplace apps let teams wire Pipedrive into Calendly, ActiveCampaign, and similar sales-stack tools.
- Mobile apps for iOS and Android keep field reps connected to deals, contacts, and tasks without a desktop session.

**REST only** API token (token-based, obtained from Pipedrive app settings)

**Rate limits** Token-based rate limits introduced December 2024; limits vary by plan tier and token

| Object          | Support | Note                                                                                                                                                                                                                                                                                                                                                   |
| --------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Persons         | full    | Persons are the primary contact record in Pipedrive, holding name, email, phone, and address fields. They link to Organizations and can be attached to Deals. We migrate Persons 1:1 and re-link them to their Organizations and Deals in the destination.                                                                                             |
| Organizations   | full    | Organizations are company-level records that can hold custom fields and link to multiple Persons. We map them to Accounts or Companies in the destination and preserve all person-organization relationships.                                                                                                                                          |
| Deals           | full    | Deals are the core pipeline object, each tied to one Person, one Organization, and a Pipeline Stage. We preserve stage order, loss/reason flags, monetary value, and expected close dates. Stage names are remapped if the destination uses different terminology.                                                                                     |
| Leads           | mapped  | Leads are a separate pool from Deals introduced in Pipedrive's newer UX. Leads inherit all Deal custom fields. Where the destination has no separate Lead object, we merge Leads into Contacts and preserve Lead\_Status as a custom property.                                                                                                         |
| Activities      | mapped  | Activities encompass tasks, calls, meetings, and notes, each with a type, due date, assigned user, and optional deal/person link. We migrate activities as structured records with their metadata; note bodies migrate as text. Formatting differences between activity types require field-level mapping at migration time.                           |
| Products        | full    | Products are standalone items with pricing, SKU, and unit information that can be attached to Deals via Deal-Product associations. We migrate Products and their associations, preserving quantity and pricing per deal.                                                                                                                               |
| Custom Fields   | mapped  | Custom fields exist on Deals, Organizations, Persons, and Products. Pipedrive assigns each custom field a 40-character hash key that is unique per account — the same field name in two different accounts has different hash keys. We translate source hashes to destination-native field IDs during migration, preserving labels, types, and values. |
| Pipelines       | mapped  | Pipelines are containers for Deal stages and control visual layout. The pipeline definition itself is migrated; Deals are assigned to the matching pipeline in the destination by stage name. If the destination has no equivalent pipeline structure, we create one or map stages into an existing pipeline.                                          |
| Pipeline Stages | full    | Stages define deal progression within a Pipeline, each with a name, position, and probability. We map stage names and probabilities and preserve deal stage history where available from the API.                                                                                                                                                      |
| Users/Owners    | mapped  | Users are the team members who own records, activities, and deals. We map by email address and re-assign owner relationships in the destination. Role and permission structures are not migrated as they are destination-specific.                                                                                                                     |
| Tags            | full    | Tags are label strings applied to Persons, Organizations, Deals, and Products. We migrate tags as string arrays and apply them to the corresponding records in the destination by name match.                                                                                                                                                          |
| Notes           | full    | Notes are standalone content entries with optional person, organization, or deal attachments. We migrate note text and content, preserve the linked entity reference, and re-attach to the corresponding record in the destination.                                                                                                                    |
| Sequences       | none    | Sequences are structured email cadence workflows with step timing, templates, and tracking. The Pipedrive API does not expose Sequences for read or write. We do not migrate Sequences and flag them during scoping so customers can export templates manually.                                                                                        |
| Automations     | none    | Automations are condition-based workflow triggers scoped to Pipedrive's event model. The automation definition — conditions, actions, and branching logic — is not fully exposed via the REST API. We do not migrate Automations and recommend rebuilding them in the destination using equivalent features.                                           |

## The Pipedrive migration guide

## Why teams migrate to Pipedrive

*The four shapes a Pipedrive migration takes, and what makes the platform easier — or harder — than the category average.*

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[1](https://flitstack.ai/migrations/crm/pipedrive#source-1). 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[3](https://flitstack.ai/migrations/crm/pipedrive#source-3). 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[11](https://flitstack.ai/migrations/crm/pipedrive#source-11).

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[2](https://flitstack.ai/migrations/crm/pipedrive#source-2) [7](https://flitstack.ai/migrations/crm/pipedrive#source-7).

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[12](https://flitstack.ai/migrations/crm/pipedrive#source-12). 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.

## The Pipedrive data model you need to map into

*Items, fields, relationships, and the System ID you'll wire on every re-importable row — the destination schema decoded.*

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[13](https://flitstack.ai/migrations/crm/pipedrive#source-13).

| Object        | What it stores                                                   | Required                                                                         | Tier                                                       |
| ------------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| People        | Individual contacts — leads, prospects, customers                | Person name                                                                      | All tiers                                                  |
| Organizations | Companies or accounts associated with people and deals           | Organization name                                                                | All tiers                                                  |
| Leads         | Pre-qualified opportunities, separated from the main pipeline    | At least one lead field + linked person or organization                          | All tiers                                                  |
| Deals         | Revenue opportunities in a pipeline                              | Deal title (auto-generated if person/org mapped) + linked person or organization | All tiers                                                  |
| Projects      | Post-sale delivery work tied to a closed-won deal                | Project title + linked person or organization                                    | Power and Enterprise tiers (Projects add-on)               |
| Activities    | Calls, meetings, tasks, emails — timeline events                 | Type, due date, subject                                                          | All tiers                                                  |
| Notes         | Free-text annotations attached to people, deals or organizations | Content + linked item                                                            | All tiers                                                  |
| Products      | Catalogue of sellable items linked to deals                      | Name, code, unit price                                                           | All tiers (Products feature is Advanced+ for full tooling) |

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[13](https://flitstack.ai/migrations/crm/pipedrive#source-13). 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` [14](https://flitstack.ai/migrations/crm/pipedrive#source-14).

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[7](https://flitstack.ai/migrations/crm/pipedrive#source-7). If the ID does not exist, the row is skipped with `Person not found` or `Deal not found` [14](https://flitstack.ai/migrations/crm/pipedrive#source-14).

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[15](https://flitstack.ai/migrations/crm/pipedrive#source-15).

| Field type                            | Limit                                            | Notes                                                                                                                                                                                              |
| ------------------------------------- | ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Text                                  | 255 chars                                        | For short alphanumeric strings — emails, job titles, addresses[15](https://flitstack.ai/migrations/crm/pipedrive#source-15)                                                                        |
| Autocomplete                          | 255 chars                                        | Like Text but suggests previously entered values[15](https://flitstack.ai/migrations/crm/pipedrive#source-15)                                                                                      |
| Large text                            | Long form, no explicit cap published             | Use for descriptions, comments, multi-paragraph content[15](https://flitstack.ai/migrations/crm/pipedrive#source-15)                                                                               |
| Numerical                             | 16-digit precision                               | Numbers beyond precision are silently truncated[15](https://flitstack.ai/migrations/crm/pipedrive#source-15)                                                                                       |
| Monetary                              | Number + ISO currency code                       | Stores as `{key}` plus `{key}_currency`; user locale drives format[12](https://flitstack.ai/migrations/crm/pipedrive#source-12)                                                                    |
| Single option / Multiple options      | 10,000 options per field                         | Raised from 500 in 2021; stores internal option ID, not label[16](https://flitstack.ai/migrations/crm/pipedrive#source-16)                                                                         |
| Date / Time / Time range / Date range | ISO-8601 on load; UI accepts user-locale formats | Range fields create paired `{key}_until` data fields[15](https://flitstack.ai/migrations/crm/pipedrive#source-15)                                                                                  |
| Address                               | Single string + parsed sub-fields                | Google-geocoded; sub-fields (street, city, etc.) populate on save[15](https://flitstack.ai/migrations/crm/pipedrive#source-15)                                                                     |
| User / Person / Organization          | Foreign-key reference                            | Stores the linked item's ID; useful for one-to-one lookups[15](https://flitstack.ai/migrations/crm/pipedrive#source-15)                                                                            |
| Custom fields per item type           | Plan-scoped: 30 (Lite) → 300 (Ultimate)          | Counted per item type; required-field enforcement is Professional+ only[17](https://flitstack.ai/migrations/crm/pipedrive#source-17) [18](https://flitstack.ai/migrations/crm/pipedrive#source-18) |

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[13](https://flitstack.ai/migrations/crm/pipedrive#source-13) [30](https://flitstack.ai/migrations/crm/pipedrive#source-30).

**10,000** Options per single/multi-option field Raised from 500 in May 2021 after Pipedrive reviewed practitioner feedback. Still bites teams migrating from Salesforce, where a single picklist often exceeds the previous 500-option ceiling — and is enforced on every write, not at field-creation time.

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.

## Pre-migration prep — the work before you touch Pipedrive

*What must be true on the source, the destination, and across the team before the first spreadsheet hits the importer.*

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[2](https://flitstack.ai/migrations/crm/pipedrive#source-2) [20](https://flitstack.ai/migrations/crm/pipedrive#source-20).

> 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[14](https://flitstack.ai/migrations/crm/pipedrive#source-14).
- 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[12](https://flitstack.ai/migrations/crm/pipedrive#source-12).
- 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[23](https://flitstack.ai/migrations/crm/pipedrive#source-23). 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[33](https://flitstack.ai/migrations/crm/pipedrive#source-33).
- 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[33](https://flitstack.ai/migrations/crm/pipedrive#source-33).
- 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[7](https://flitstack.ai/migrations/crm/pipedrive#source-7).

### 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.

## Import mechanisms: spreadsheet and native migrator

*Two paths in, each with different ceilings and shapes. Picking the wrong one is how mid-migrations stall at scale.*

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[2](https://flitstack.ai/migrations/crm/pipedrive#source-2) [20](https://flitstack.ai/migrations/crm/pipedrive#source-20). 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[14](https://flitstack.ai/migrations/crm/pipedrive#source-14). A Revert button in import history undoes the most recent run within 48 hours[2](https://flitstack.ai/migrations/crm/pipedrive#source-2).

### 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[25](https://flitstack.ai/migrations/crm/pipedrive#source-25). 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.

Under 10,000 records on standard items → spreadsheet importer. HubSpot / Salesforce / Zoho source with relationships and history to preserve → native migration tool (Import2 / SyncMatters). Over 50,000 records or any need for idempotent re-runs → a staged loader (Import2/SyncMatters) plus careful pacing.

## Mapping your data into Pipedrive

*The longest section — because field mapping is where almost every migration that fails actually breaks.*

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)

| Source                                | Destination                          | Note                                                                                                                                   |
| ------------------------------------- | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
| first\_name + last\_name OR full name | Name                                 | Pipedrive stores a single Name field; combine on export                                                                                |
| email                                 | Email                                | Lowercase before import; not mandatory but critical for dedup matching                                                                 |
| phone                                 | Phone                                | Normalise to E.164; supports multiple labelled values per person                                                                       |
| owner / account\_owner                | Owner                                | Map by Pipedrive user email; provision users in destination before import                                                              |
| organization\_id / account\_name      | Organization                         | Link by Organization name (created first) or by ID after first export                                                                  |
| created\_at                           | Capture in a custom Date field       | Add Date is system-stamped to the import moment and cannot be overwritten[33](https://flitstack.ai/migrations/crm/pipedrive#source-33) |
| lead status / lifecycle               | Custom Single option field on Person | Pipedrive has no native lifecycle field; create a Single option list and migrate values                                                |

### Organizations

| Source           | Destination                                | Note                                                                                                                                                |
| ---------------- | ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| company\_name    | Name                                       | Required — rows missing this hit the skip file with `Organization name must be given` [14](https://flitstack.ai/migrations/crm/pipedrive#source-14) |
| website / domain | Custom Text field (no native domain field) | Pipedrive does not key on domain like HubSpot does — store and dedup manually                                                                       |
| address          | Address                                    | Single string; Pipedrive auto-geocodes and populates street, city, country sub-fields                                                               |
| industry         | Custom Single option field                 | Pre-create the option list with all source values to avoid skip-file rejects                                                                        |
| annual\_revenue  | Custom Numerical or Monetary field         | Monetary needs an accompanying ISO currency column                                                                                                  |
| parent account   | Not natively supported                     | Capture parent name in a custom Text field; rebuild hierarchy via Workflow Automation if needed                                                     |

### 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[35](https://flitstack.ai/migrations/crm/pipedrive#source-35).

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[35](https://flitstack.ai/migrations/crm/pipedrive#source-35).

| Source                         | Destination                                  | Note                                                                                                                            |
| ------------------------------ | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| deal\_name / opportunity\_name | Title                                        | Auto-generated as `[Org] deal` if Title is blank but Org is mapped[14](https://flitstack.ai/migrations/crm/pipedrive#source-14) |
| stage / pipeline\_stage        | Stage                                        | Stage name on the named pipeline; pre-create exact names before import                                                          |
| amount                         | Value                                        | Number; pair with a Currency column carrying ISO code (USD, EUR, GBP)                                                           |
| close\_date                    | Expected close date                          | Native field; ISO-8601 or user-locale format via UI                                                                             |
| owner                          | Owner                                        | Map by Pipedrive user email; controls visibility under default permission sets                                                  |
| primary\_contact               | Person                                       | Link by Person name or email; created first to enable the link                                                                  |
| account / organisation         | Organization                                 | Link by Organization name; deal inherits Org's address and custom Org fields                                                    |
| won/lost reason                | Lost reason (native) or custom Single option | Native Lost reason is a free-text field; convert to dropdown via custom field for reporting                                     |

### 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[17](https://flitstack.ai/migrations/crm/pipedrive#source-17) [18](https://flitstack.ai/migrations/crm/pipedrive#source-18). 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[15](https://flitstack.ai/migrations/crm/pipedrive#source-15).

### 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[13](https://flitstack.ai/migrations/crm/pipedrive#source-13). 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[25](https://flitstack.ai/migrations/crm/pipedrive#source-25); (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[32](https://flitstack.ai/migrations/crm/pipedrive#source-32).

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[32](https://flitstack.ai/migrations/crm/pipedrive#source-32).

### 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[33](https://flitstack.ai/migrations/crm/pipedrive#source-33). 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[36](https://flitstack.ai/migrations/crm/pipedrive#source-36) — 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[37](https://flitstack.ai/migrations/crm/pipedrive#source-37). Do not enable two-way sync during the import window, or the connector will backfill against the same Activities you are loading.

## The pitfalls that derail Pipedrive migrations

*Specific failure modes — ranked by impact, each tied to the exact Pipedrive mechanism that breaks.*

**high Option fields store internal IDs, not labels**

Single option and Multiple option custom fields in Pipedrive store an internal numeric option ID — for example, option `10` rather than the label `Enterprise`. Any update path that sends the label string instead of the ID is rejected without a useful field-level hint[12](https://flitstack.ai/migrations/crm/pipedrive#source-12). Pull the field's option list before the migration starts, build a label→ID lookup table, and translate during transform; never send labels.

**high Add date and Update time cannot be overridden**

Pipedrive system fields — Add date, Update time, Pipedrive System ID, Last activity date — are platform-managed and ignored if you send them during import[33](https://flitstack.ai/migrations/crm/pipedrive#source-33). Teams discover this on day two when Insights reports filtered by Add date return everything stamped to import day. The mitigation is to create Legacy Created Date and Legacy Modified Date custom Date fields on every item type, populate them from the source export, and rewrite all historical-period reports to use the legacy fields.

**high Currency column requires ISO code, not symbol**

Pipedrive's Monetary field is stored as a numeric value plus an ISO currency code in a paired `{key}_currency` data field[15](https://flitstack.ai/migrations/crm/pipedrive#source-15). Spreadsheet rows that put `$1,200` in the value column hit the skip file with `Please provide valid currency` [14](https://flitstack.ai/migrations/crm/pipedrive#source-14) — Pipedrive expects `1200` in the value column and `USD` in a separate Currency column. Strip the symbol, separate the code, and validate against ISO 4217 before upload; a single stray `€` row will reject every other deal that shares that import batch.

**high Required-field enforcement is Professional+ only**

Pipedrive's Required fields feature — which blocks users from saving a deal or person without the named field populated — is only available on Professional and higher plans, and only an admin can configure it[18](https://flitstack.ai/migrations/crm/pipedrive#source-18). Teams on Lite or Growth that rely on required-field validation in their source CRM lose that guard during migration. The mitigation: enforce required-field checks in the source export pre-flight, or upgrade to Professional before go-live and accept the per-user price step.

**medium Deal title auto-generation hides linkage errors**

If a Deal row has no Title column but does have a linked Person or Organization, Pipedrive auto-generates the title as `[Person name] deal` or `[Organization name] deal` [14](https://flitstack.ai/migrations/crm/pipedrive#source-14). This is convenient — but it also masks rows where the Person/Org link failed: those rows hit the skip file with `Deal title must be given` and the underlying cause (a typo in the Org name) is buried. Always populate Title explicitly during import; let auto-gen run only on rows you've consciously chosen to leave blank.

**medium Non-UTF-8 CSV encoding silently corrupts characters**

Teams exporting from Excel without explicitly saving as UTF-8 CSV hit encoding bugs on the first non-ASCII row — typically an accented name or a German umlaut[38](https://flitstack.ai/migrations/crm/pipedrive#source-38). The result is mojibake on the Pipedrive record or a row in the skip file. Always save CSVs as UTF-8 explicitly before upload; verify a sample row through a hex viewer or a quick Notepad++ encoding check before committing the full import.

## Validation and cutover

*What to verify after the import job, in what order — and how to fail safely when something is wrong.*

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[39](https://flitstack.ai/migrations/crm/pipedrive#source-39). There is also a Revert button on each spreadsheet import in the import history, valid for 48 hours after upload[2](https://flitstack.ai/migrations/crm/pipedrive#source-2). 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.

## Migration partners and tools

*Pipedrive Marketplace partners, migration software, ETL vendors — what each is good for and how to choose.*

The Pipedrive Marketplace lists Service Partners tiered Platinum, Gold and Silver by certifications, customer count and revenue[40](https://flitstack.ai/migrations/crm/pipedrive#source-40). 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[40](https://flitstack.ai/migrations/crm/pipedrive#source-40).

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[25](https://flitstack.ai/migrations/crm/pipedrive#source-25). 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 →]\(/contact)

In this guide

## Pipedrive migration checklist

An atomic, phased task list for migrating sales data into Pipedrive — covering scope, prep, export, transform, sandbox test, cutover, validation, and post-cutover cleanup. Typical timeline: 4–12 weeks.

0\. Decide & Plan 10 tasks

- **Document the full list of Pipedrive item types in scope.** Pipedrive supports eight importable item types: People, Organizations, Leads, Deals, Projects, Activities, Notes, and Products. Confirm which are in scope and which are deliberately out of scope.*If skipped: Discovering at cutover that Projects or Products were assumed but never planned forces re-scoping mid-migration.*
- **Define historical-data scope by item type.** Decide how many years of closed deals, completed activities, and archived notes you will move. Decide whether email threads and call logs are in scope.*If skipped: Pulling all history by default can multiply the dataset 5–10x and blow through the cutover window.*
- **Confirm the target Pipedrive plan and its custom-field ceilings.** Lite, Growth, Premium, and Ultimate cap custom fields per item type at different levels (roughly 30 on Lite through 300 on Ultimate). Required fields are Professional/Premium+ only.*If skipped: Buying Lite then discovering you need 80 custom fields per object blocks the migration until billing is escalated.*
- **Decide whether Smart Docs, Lead Scoring, and Campaigns are in scope.** Smart Docs and Lead Scoring are tier-gated. Confirm whether they need to be configured during this migration or deferred.
- **Identify GDPR data-residency and retention requirements.** Pipedrive hosts in AWS data centers in Europe and the US. Confirm which region your tenant uses and that it satisfies any contractual residency commitments.*If skipped: Discovering after cutover that your tenant is in the wrong region forces a second migration or a contractual exception.*
- **Confirm SOC 2, ISO 27001, and EU-US Data Privacy Framework evidence needs.** If your auditors require evidence packs at cutover, request the latest Pipedrive certification reports before the freeze date.
- **Assign a single accountable migration owner (DRI).** One named person owns scope decisions, cutover go/no-go, and post-migration signoff. Document their backup.
- **Document explicit out-of-scope items.** List the source-system features that will NOT be rebuilt in Pipedrive — chat transcripts, marketing automation flows, custom reporting macros, etc. Get sponsor sign-off in writing.*If skipped: Unwritten out-of-scope items resurface as urgent during cutover and derail the schedule.*
- **Set the target cutover date and source-system freeze window.** Pick a low-activity window (often a Friday evening through Sunday). Communicate the freeze date and time to all source-system users at least two weeks in advance.
- **Define written success criteria for the migration.** Examples: 100% of open deals migrated with correct stage; aggregate pipeline value within 0.5% of source; all owners assigned correctly; activities linked to correct deals.*If skipped: Without falsifiable criteria, the migration is never formally complete and tail issues drag on for months.*

1\. Pre-Migration Prep 23 tasks

- **Run dedup analysis on source People using email as the primary match key.** Resolve duplicate contacts at the source before export. Pipedrive's Spreadsheet Importer offers a merge option during import, but cleaner source data produces cleaner results.*If skipped: Importing duplicates means rebuilding deal-to-person associations against the wrong record after dedup.*
- **Run dedup analysis on source Organizations using domain as the match key.** Normalize company-name variations (Acme Inc., Acme Incorporated, ACME) to a single canonical form.
- **Standardize email casing to lowercase across all People records.** Mixed-case email values create silent duplicates against the lowercase keys Pipedrive uses for matching.
- **Normalize phone-number formats to E.164 with country code.** Pipedrive stores phone as text; agree on one format (+15551234567) and apply it before export.
- **Identify and resolve source records missing values that will be mandatory in Pipedrive.** Person name, Organization name, Lead title, Deal title, and Activity type+due date are mandatory. Records missing these will land in the skip file.*If skipped: Mandatory-field misses produce a skip file at import; without a triage plan you lose visibility into what failed.*
- **Export baseline record counts per object as of the export timestamp.** Capture counts for People, Organizations, Leads, Deals, Activities, Notes, Products, and Projects. These become the reconciliation target.*If skipped: Without a baseline you cannot tell at validation whether 'missing' records were never exported or lost in transit.*
- **Snapshot source pipeline-stage definitions and current deal distribution.** Document the stage name, order, and probability for every pipeline. Capture how many deals sit in each stage today.
- **Decide which closed-lost or archived deals are worth migrating.** Closed-lost deals from beyond your retention horizon may not justify the effort to move. Document the cutoff.
- **Provision the Pipedrive production tenant on the chosen plan.** Confirm seat count, currency, fiscal year, and default timezone at company creation.
- **Sign up for a Pipedrive Sandbox account for dry-run testing.** The Sandbox is a separate tenant for building and testing without impacting the production data set.*If skipped: Skipping sandbox forces all test errors to occur in production where rollback is harder.*
- **Create all human users in Pipedrive before any record import.** Record owners on imported deals, activities, and notes match by user email. Missing users default to the import-running user, scrambling ownership.*If skipped: If users do not exist before import, every record is owned by one person and you must reassign tens of thousands of records manually.*
- **Configure global account currency and add any secondary currencies.** Monetary custom fields pair with a {key}\_currency field holding the ISO code (USD, EUR). Set up every currency you will load.*If skipped: Loading EUR deals without the EUR currency added produces 'Please provide valid currency' skip-file errors.*
- **Set the company timezone to match the source system's timezone.** Activity due dates and deal close dates render against the company timezone; a mismatch silently shifts dates by hours.
- **Create every pipeline and stage that source deals will land in.** Match the stage names exactly to what your transform spreadsheet will emit. Stage probability is configurable per stage.
- **Create all custom fields on Person, Organization, Lead, Deal, Project, and Product before any import.** Pipedrive offers 16 custom field types including Text, Large text, Single option, Multiple options, Numerical, Monetary, Date, Date range, Time, Time range, User, Address, Phone, Autocomplete, Formula, and File.*If skipped: Importing into a custom field that does not exist drops the data silently. There is no retry after the import completes.*
- **Define every Single option and Multiple option custom field's full option list before import.** Each Single/Multiple option field caps at 10,000 options (raised from 500 in May 2021). Options have internal IDs that the importer matches against; missing options become skip-file rows.*If skipped: If an option does not exist when a row arrives carrying it, the row is rejected with an option-not-found error.*
- **Mark Professional/Premium+ Required fields only after the migration completes.** Required fields are Professional+ and they block record creation when empty. Leaving them off during import prevents legitimate historical records from being rejected.*If skipped: Turning Required on before import causes thousands of rows to fail validation because legacy data never carried that value.*
- **Disable Workflow Automation triggers that fire on record create or update.** Auto-emails, deal-stage notifications, and Sales Assistant nudges fire on every imported row otherwise. Pause all automations before import.*If skipped: An import of 50,000 deals can fire 50,000 stage-change emails to customers if automations are not paused.*
- **Disconnect outbound integrations (Zapier, Make, email sync, calendar sync) during import.** Reconnect after Phase 5 completes. Calendar sync is supported only for Google, Office 365, and Exchange.
- **Announce the source-system freeze date to all end users.** Send the announcement at least two weeks ahead with the exact freeze timestamp and the destination go-live time.
- **Schedule a Pipedrive basics training session for each end-user role.** Cover pipeline navigation, deal creation, activity logging, and email linking. Run the session in the week before cutover, not after.
- **Designate first-responders for the first 48 hours after cutover.** Name two admins and one Pipedrive-fluent power user who will triage user issues immediately. Publish their Slack handles or extensions.
- **Document the rollback decision criteria and owner.** Pipedrive's Spreadsheet Importer offers a Revert action within 48 hours. Decide who can pull that trigger and under what data-loss threshold.*If skipped: Without a documented rollback owner, the 48-hour Revert window expires during indecision and rollback becomes manual record-deletion.*

2\. Source Export 14 tasks

- **Export source contacts/persons to CSV with all standard and custom fields.** Include record ID, full name, email, phone, organization link, owner email, created date, and every custom field. Encode as UTF-8.*If skipped: Non-UTF-8 encoding causes Pipedrive's strict parser to reject payloads with 'Invalid or malformed' errors.*
- **Export source organizations/accounts to CSV with all fields and the parent-organization link if used.** Capture the parent\_org\_id relationship so multi-level company hierarchies can be rebuilt.
- **Export source leads (top-of-funnel records) as a separate CSV.** In Pipedrive, Leads live in the Lead Inbox and are distinct from Deals. Keep them separate during export so the load order can respect that.
- **Export source deals/opportunities to CSV with stage, value, currency, close date, owner, and linked person and organization IDs.** Capture both the source record ID (for traceability) and the linked person/org source IDs so relationships can be rebuilt.*If skipped: Without source IDs, you cannot reconnect deals to their people and organizations after the lookup IDs change in Pipedrive.*
- **Export source activities (tasks, meetings, calls, emails) to CSV with type, subject, due date, due time, duration, owner, and linked deal/person/organization IDs.** Pipedrive activity types include call, meeting, task, deadline, email, and lunch. Map your source types to these.
- **Export source notes with body, created date, author, and linked record IDs.** Pipedrive notes cap at roughly 100 kB each and a deal holds up to 100 notes. Long source notes may need to be split.*If skipped: Notes that exceed 100 kB are silently truncated or rejected, losing tail content that may contain important context.*
- **Export source products/catalog items with code, name, unit price, currency, and tax.** Pipedrive Products attach to Deals as line items with quantity and discount; capture the structure that powers that.
- **Export source projects (if in scope) with phase, owner, and linked deal.** Projects are an item type in Pipedrive and follow their own template/phase structure.
- **Export the user list with full name, email, role, and reporting hierarchy.** Used to provision Pipedrive users in Phase 1b and to map source owner\_id to destination owner email.
- **Export source pipeline definitions: pipeline name, stages, stage order, stage probability.** These power the pipeline-rebuild task in Phase 3d.
- **Export every source attachment along with its parent record ID and original filename.** Pipedrive's per-file cap is roughly 50 MB. Files larger than 50 MB must be hosted externally and linked.*If skipped: Files over 50 MB silently fail to upload; without a parallel hosting plan, content is lost.*
- **Export source automations, sequences, and workflow definitions as documentation, not data.** Workflows do not migrate as data; capture screenshots, trigger conditions, and actions for manual rebuild in Pipedrive's Workflow Automation.
- **Export reports and dashboards as documentation only.** Pipedrive Insights reports must be rebuilt manually after cutover.
- **Stamp every export file with its exact UTC export timestamp.** The timestamp defines the delta that the cutover final-pull (Phase 5) must capture.*If skipped: Without an export timestamp you cannot tell what activity occurred between Phase 2 and cutover.*

3\. Transform & Map 28 tasks

- **Build a master mapping spreadsheet covering every source field for every item type.** Columns: source object, source field, source type, destination object, destination field, destination type, transformation rule, nullability, mandatory-at-import flag.*If skipped: Without a single source-of-truth mapping document, field decisions get made twice and the second decision overwrites the first silently.*
- **Mark the Pipedrive mandatory fields per object: Person name; Organization name; Lead title + linked person/org; Deal title + linked person/org; Activity type+due date.** Confirm every source row will satisfy these. Build a pre-import validator if you have more than 10,000 rows.*If skipped: Mandatory-field violations are the #1 cause of skip-file rows during Pipedrive imports.*
- **Resolve every picklist value mismatch between source and destination.** Source 'Won-Closed' must become destination 'Won'. Build the mapping table inline in the master spreadsheet so transforms reference one location.
- **Designate Pipedrive System ID as the only valid upsert key for updates.** Pipedrive has no general 'External ID' concept. The Pipedrive System ID is assigned on first import and is the only upsert key the Spreadsheet Importer accepts for updates.*If skipped: Re-running an import without the Pipedrive System ID column duplicates every record instead of updating it.*
- **Decide handling for source fields with no Pipedrive equivalent.** Options per field: drop, concatenate into Notes, or create a Pipedrive custom field. Document the choice for every orphan field.
- **Decide handling for source records whose owner email does not exist in Pipedrive.** Either provision the missing user before import, reassign to a 'Migration' user, or drop the record. Document the rule.
- **Convert all date and datetime values to ISO-8601 with explicit timezone.** Format YYYY-MM-DD for Date fields and YYYY-MM-DDTHH:MM:SSZ for Date range and Time fields.*If skipped: Ambiguous DD/MM vs MM/DD strings get parsed by the importer's locale and silently shift dates by months.*
- **Populate the {key}\_currency companion column for every Monetary custom field.** Each Monetary field stores the numeric value in the field key and the ISO currency code (USD, EUR, GBP) in a parallel {key}\_currency column. Symbols like $ or € are rejected.*If skipped: Omitting the currency column produces 'Please provide valid currency' skip-file errors on every row.*
- **Normalize numeric values: strip thousand separators, force a decimal point, cap precision at 16 decimal places.** Pipedrive Numerical fields support precision up to 16; values beyond that lose precision silently.
- **Truncate Text custom field values to 255 characters.** Pipedrive Text (varchar) fields cap at 255. Use Large text for anything longer.*If skipped: Text values over 255 characters are silently truncated, losing the tail with no skip-file warning.*
- **Re-encode every text field as UTF-8.** Pipedrive's parser strictly enforces UTF-8 and rejects payloads with a 'control character error, possibly incorrectly encoded' message otherwise.*If skipped: Non-UTF-8 encoding causes entire batches to fail, not single rows.*
- **Escape commas, quotes, and newlines inside CSV cells per RFC 4180.** Wrap any cell containing a comma, quote, or newline in double quotes and double-up internal quotes.*If skipped: Unescaped commas split rows into wrong column counts and the Spreadsheet Importer rejects the row.*
- **Map Single option and Multiple option values to the destination's option labels exactly.** Internal option IDs differ between source and destination. The importer matches on label; case and whitespace must match the destination option exactly.*If skipped: A trailing space or wrong capitalization on an option label rejects the row with an option-not-found error.*
- **Split source records with more than 10,000 Multiple option selections into multiple records or fields.** Pipedrive's per-field option ceiling is 10,000. Values beyond that cannot be added.
- **Decide strategy for preserving the original record creation timestamp.** Pipedrive sets add\_time on import to the import moment. To preserve the source created date, store it in a custom Date field named 'Source Created Date'.*If skipped: Reporting that filters on add\_time will treat every migrated record as created at cutover, distorting historical trend analysis.*
- **Decide strategy for record ownership: best-match by source owner email, or assign all to a single 'Data Migration' user.** If using best-match, ensure every source owner email exists as a Pipedrive user before import (see Phase 1b).
- **Decide strategy for file attachments: re-upload binaries or preserve as external storage links.** Re-uploading preserves in-app access. External links keep files dependent on the source storage layer but avoid re-upload time.
- **Pre-sort the load order: Users, Products, Organizations, People, Leads, Deals, Projects, Activities, Notes, Files.** Children cannot reference parents that do not exist yet; this order respects every Pipedrive dependency.*If skipped: Loading Deals before Organizations strands deals without their org link and forces a re-link pass after.*
- **Rebuild every pipeline and stage exactly in Pipedrive before importing deals.** Pipelines and stages are created in Settings > Pipelines. Stage probability (0–100) drives forecast math and must match the source intent.*If skipped: Importing deals into a missing stage assigns them to the default stage and corrupts pipeline reporting.*
- **Map every source deal-stage value to a destination stage\_id.** Deals reference stage\_id, not stage\_name. Build a name-to-ID lookup table after stages are created.
- **Decide deal close-date handling for won and lost deals.** Pipedrive stores close\_time for won/lost deals. To preserve source close dates, write close\_time during import (rather than letting Pipedrive stamp the import moment).
- **Rebuild every Workflow Automation manually in Pipedrive after data load.** Source automations do not migrate. Capture trigger, conditions, and actions during Phase 2 and rebuild in Settings > Automations. Leave them inactive until validation completes.*If skipped: Activating automations before validation triggers email blasts and Sales Assistant nudges to customers on incorrect data.*
- **Recreate Smart Docs templates with destination field merge tokens.** Smart Docs is available on Premium/Ultimate and on lower tiers as a paid add-on. Merge fields use Pipedrive's variable syntax which differs from most source CRMs.
- **Recreate email templates referencing Pipedrive Person and Deal merge fields.** Source merge-field syntax does not translate. Rebuild every template and verify rendered output on a test record.
- **Recreate Activity templates and saved Activity types.** Custom activity types beyond the defaults must be added in Settings > Activity types before activities referencing them are imported.*If skipped: Activities referencing an undefined custom type are rejected at import.*
- **Plan the Lead Scoring rebuild if Lead Scoring is in scope.** Lead Scoring is tier-gated. Source scores rarely translate one-to-one; document the new rule set and apply it after leads are loaded.
- **Plan calendar sync setup as a per-user post-cutover task.** Pipedrive Calendar sync supports Google, Office 365, and Exchange only — not IMAP or POP. Two-factor Exchange users need an app password.
- **Map source contact-merge logic to Pipedrive's Spreadsheet Importer merge option.** When a row matches by email, the importer can merge into the existing person or create a duplicate. Document which is correct per row class.

4\. Sandbox Test Migration 12 tasks

- **Load a 1–5% representative sample of each item type into the Sandbox.** Use the Spreadsheet Importer at Settings > Tools and apps > Import data for each object type.*If skipped: Skipping a sample run means production becomes the first place errors surface.*
- **Trigger every option-field value at least once in the sample.** If a Multiple option field has 50 options, the sample should exercise all 50 so option-mapping errors surface here, not in production.
- **Verify 5–10 random Sandbox records field-by-field against the source.** Walk every custom field, every option value, and every linked record. Document and triage every mismatch.
- **Test edge cases: 255-character text, multi-line notes, emoji, RTL languages, leading/trailing whitespace, NULL values.** Each of these has historically broken at least one CRM importer; verify Pipedrive's behavior on yours.
- **Test Monetary field import with at least three currencies including a non-USD one.** Confirms the {key}\_currency column is wired correctly and that the company currency list covers your dataset.
- **Test parent-child relationships: organization with people, organization with parent\_org\_id, deal with linked person and org.** Open the imported deal in the Pipedrive UI and confirm person\_id and org\_id are populated correctly.*If skipped: Broken links are invisible from the deal list view but show as 'Person not found' in reports.*
- **Test activity-to-deal and activity-to-person linkage on the sample.** Activities without correct deal\_id or person\_id render orphan in the Activities calendar.
- **Test file attachment upload with a 1 MB, a 25 MB, and a 50 MB file.** Confirms both the success path and the 50 MB ceiling behavior.
- **Time the sample run end-to-end and extrapolate to full volume.** Use the sandbox load timing to extrapolate to your full record count.*If skipped: Extrapolation from a 100-row sample without accounting for parallelism produces a cutover estimate off by 10x.*
- **Confirm the Spreadsheet Importer Revert action works on a small Sandbox import.** Verifies the 48-hour rollback path that Phase 1c relies on.
- **Have a sales-ops or RevOps power user spot-check 20 Sandbox records.** They will catch business-logic issues (wrong stage, wrong owner, missing tag) that field-level checks miss.
- **Get written sandbox sign-off before proceeding to Phase 5.** Sign-off names the test artifacts (record counts, sampled records, edge-case results) and is the gate to production.*If skipped: Skipping sign-off lets unresolved Sandbox issues carry into production where the cost of fixing them rises.*

5\. Production Cutover 16 tasks

- **Confirm the source-system freeze is in effect; verify no writes in the last hour.** Audit the source change log if available, or sample 10 recent records and confirm modified\_at timestamps are all before freeze.*If skipped: Late writes after the freeze produce records that exist in source but not in destination, requiring a manual delta pass.*
- **Take a final full export to capture the delta since the Phase 2 baseline.** Diff the new export against the Phase 2 export and load only changed/new rows to minimize load time.
- **Confirm all destination automations are paused.** Re-verify Phase 1b: Workflow Automation, Sales Assistant nudges, and outbound integrations (Zapier, Make) are all off.*If skipped: A single live automation can send thousands of customer emails during the load.*
- **Load Products first, capturing returned IDs into a lookup file.** Deals will reference these product IDs when adding products as line items.
- **Load Organizations, capturing returned IDs.** Build org\_source\_id -> org\_pipedrive\_id lookup file for downstream loads.
- **Load People with org\_id populated from the lookup.** Process records in parallel batches to stay within Pipedrive's per-tenant throughput budget.
- **Load Leads with person\_id and organization\_id populated.** Leads land in the Lead Inbox and are distinct from Deals.
- **Load Deals with person\_id, org\_id, stage\_id, value, currency, owner\_id, and close\_time set.** Use stage\_id from the pipeline rebuild lookup, not stage\_name.*If skipped: Loading stage\_name instead of stage\_id silently puts the deal in the default stage.*
- **Load Projects (if in scope) with linked deal\_id and owner\_id.** Projects depend on Deals and Users existing first.
- **Load Activities with deal\_id, person\_id, org\_id, type, due\_date, due\_time, and done flag.** Closed activities should carry done=1 with marked\_as\_done\_time set to the source completion timestamp.
- **Load Notes with deal\_id, person\_id, or org\_id and add\_time set to the source created timestamp.** Use the add\_time override (where supported) so notes appear in the correct chronological position on the deal timeline.
- **Upload File attachments last, with the parent record ID required on each upload.** Files over 50 MB must be skipped here and linked externally per the Phase 3c decision.
- **Capture every import job's row count, success count, error count, and error log.** Build a job-status file the Phase 6 reconciliation reads from.*If skipped: Without per-job error logs you cannot tell which records failed and need a re-run.*
- **Cross-check destination counts against source counts after each item-type load completes.** If the delta exceeds your tolerance (often 0.1%), stop and diagnose before loading the next type.*If skipped: Pushing through with a known delta means later types reference records that should not exist.*
- **If any load step fails partway, stop, diagnose, fix the transform, and re-run with Pipedrive System ID as the upsert key.** Idempotent re-runs depend on the System ID being captured from the partial success.
- **Re-enable Workflow Automation and outbound integrations only after Phase 6 sign-off.** Reactivation order: integrations first (so they fire on subsequent changes), then workflow automations, then Sales Assistant.

6\. Validate 19 tasks

- **Compare total record count per item type: source vs Pipedrive.** Use the Pipedrive list views or exports for persons, deals, organizations, activities, notes, products, projects, leads and compare to baseline.*If skipped: An unexplained delta indicates either skip-file rows you missed or a parent-link failure that orphaned children.*
- **Compare aggregate open pipeline value: source vs Pipedrive, by currency.** Group deals by status=open and pipeline\_id, sum value, group by currency. Investigate any delta over 0.5%.
- **Compare won-deal count and aggregate value for the last 12 months.** Won-deal counts power most sales reporting; a delta here surfaces stage-mapping errors.
- **Spot-check 25–50 randomly selected deals field-by-field against source.** Walk every standard field and every custom field on each sampled deal.
- **Spot-check 25 randomly selected people including all custom fields.** Validates the People schema separately from the Deal schema.
- **Compare deal counts per pipeline-stage between source and Pipedrive.** A stage-by-stage diff surfaces stage-mapping errors that aggregate totals hide.*If skipped: Two stages that net to the same total but moved deals to the wrong bucket distort forecasts.*
- **Verify a random sample of 30 person-to-organization associations match source.** Confirms org\_id populated correctly on People rows.
- **Verify a random sample of 30 deal-to-person and deal-to-organization links.** Confirms person\_id and org\_id populated correctly on Deal rows.
- **Verify a random sample of 30 activity-to-deal links.** Confirms deal\_id populated correctly on Activity rows; orphan activities render in the calendar but not on the deal.
- **Confirm parent-organization (org-of-org) hierarchies rebuild correctly.** Walk a known multi-level hierarchy from source and verify it in the Pipedrive org detail view.
- **Confirm file attachments are accessible and bound to the correct record.** Open 20 random attached files from inside their parent deal/person/org to verify both linkage and binary integrity.*If skipped: Files that uploaded successfully but linked to the wrong record are invisible without per-record inspection.*
- **Verify the Source Created Date custom field is populated on every migrated record.** Confirms the audit-trail strategy from Phase 3c worked end-to-end.
- **Run a GDPR access-request rehearsal on a test contact.** Confirms the new tenant's data-subject-access flow works against migrated data.
- **Confirm Pipedrive's region (EU or US AWS) matches the contractual residency commitment.** Validates the Phase 0 residency check against the actual provisioned tenant.*If skipped: Discovering a region mismatch after go-live triggers either a tenant rebuild or a customer notification.*
- **Verify Pipedrive Security Dashboard captures login history per user.** Confirms audit logging works for the new tenant from day one.
- **Have 3–5 power users complete their daily workflow end-to-end in Pipedrive against migrated data.** Examples: log in, find a deal, add a note, log a call, move stage, send email via linked inbox.
- **Document every issue raised in UAT with severity (blocker / important / cosmetic).** Blockers must be resolved before Phase 7; cosmetic items go to the 30-day backlog.
- **Confirm Insights reports reflect expected totals on at least three pre-agreed reports.** Open pipeline by owner, deals won this quarter, activities completed this week.
- **Get written sign-off from the migration sponsor before opening Pipedrive to end users.** Sign-off references the reconciliation report, UAT log, and the compliance checks above.*If skipped: Opening to users before sign-off means data errors get found by sales reps mid-call, eroding trust in the new system.*

7\. Post-Migration Cleanup 12 tasks

- **Announce Pipedrive go-live to all end users with login URL, support contact, and the source read-only date.** Include a one-pager pointing to the most common 'where did this go' translations.
- **Run the planned end-user training sessions by role (sales rep, sales manager, ops).** Use migrated data live in the sessions so users see their own records, not toy examples.
- **Set the source system to read-only on the announced date.** Read-only mode preserves it as a reference but prevents drift between source and Pipedrive.*If skipped: Leaving the source writable creates two sources of truth and reps will use whichever is faster, scrambling the data again.*
- **Rebuild every Insights report and dashboard in Pipedrive.** Reports do not migrate. Rebuild against destination field keys and confirm totals against the Phase 6 validation report.
- **Reactivate Workflow Automation rules one category at a time, monitoring for unintended fires.** Start with low-risk notifications. Watch Sales Assistant suggestions for a day before activating customer-facing automations.*If skipped: Activating all automations at once on freshly loaded data can fire bulk customer emails referencing stale context.*
- **Recreate every email template, Smart Docs template, and sequence template manually.** Verify each renders against a live migrated record before publishing to end users.
- **Reconnect calendar sync per user (Google, Office 365, or Exchange).** Pipedrive does not bulk-enable calendar sync; each user runs Personal preferences > Calendar sync individually.
- **Reconnect outbound integrations: Zapier, Make, BI tools, email-sync providers.** Restore in the order they were paused; verify each integration sees migrated records correctly.
- **Archive Phase 2 source-system exports to long-term cold storage with documented retention.** Retain for the duration of your compliance window in case forensic comparison is needed.
- **Schedule a 30-day post-migration retrospective.** Invite the DRI, sponsors, first-responders, and 2–3 end users. Capture what worked, what hurt, and what to do differently next time.
- **Decide and document the source-system decommission date.** Typically 90 days after cutover, after the final compliance retention window. Confirm contract terms before fully shutting it down.
- **Close the migration project formally.** Final status report, lessons-learned doc, and project closure ticket. The migration is not done until this exists.

Questions, answered

## Migrating to Pipedrive: questions

How long does migration to Pipedrive take?

A small-business migration with under 5,000 records and standard items runs one to three business days end-to-end. A mid-market HubSpot-to-Pipedrive project with deal history, activities and Workflow Automation rebuilds runs two to four weeks elapsed time; a Salesforce-to-Pipedrive move with Apex rebuilds runs eight to twelve weeks.

Can I migrate from HubSpot to Pipedrive?

Yes — HubSpot-to-Pipedrive is one of the most common shapes, supported natively via the Import2 app in the Pipedrive Marketplace. Standard objects map cleanly: Contacts to Persons, Companies to Organizations, Deals to Deals. HubSpot Workflows, Sequences and lead-scoring models do not transfer and must be rebuilt in Pipedrive.

Can I migrate from Salesforce to Pipedrive?

Yes. Accounts map to Organizations, Contacts to Persons, Opportunities to Deals, Tasks and Events to Activities, Files to Files. Apex code, Flow, Process Builder and Validation Rules do not transfer and need to be rebuilt as Pipedrive Workflow Automation. Plan for option-field ID translation and Salesforce User ID to Pipedrive owner-email mapping.

Does Pipedrive preserve original timestamps on import?

Partially. Activity Due date and Note creation date can be backdated and show up correctly on the contact timeline. System fields like Add date and Update time cannot be overridden — they stamp to import day. Use custom Legacy Created Date and Legacy Modified Date Date fields to preserve audit trail.

Can I run a re-importable update flow on Pipedrive?

Yes — export every item type once after the first full load, capture the Pipedrive System ID column back into your source database, and on subsequent deltas include that column mapped to Pipedrive System ID in the spreadsheet importer. The importer will update by ID rather than create new records.

Can I migrate Custom Objects to Pipedrive?

No — Pipedrive does not currently offer Custom Objects 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.

What happens to deal history and pipeline stages during migration?

Recreate every pipeline and every stage name in Pipedrive before importing deals — rows targeting non-existent stages either reject or auto-create empty stages with no probability set. Stage history is not auto-preserved; if you need it for reporting, export stage transition timestamps from the source and store them in custom Date fields.

Is there an undo or rollback for Pipedrive imports?

Yes — the spreadsheet importer offers a Revert button for 48 hours after each import, and Restore data lets users recover deleted records for up to a year. Neither is a bulk-rollback button across multiple imports — stamp every imported row with an Import Batch ID custom field for surgical rollback.

### [Pipedrive implementation](https://flitstack.ai/services/pipedrive-implementation)

[Set up Pipedrive (pipelines, properties, automation, permissions) and migrate into it as one engagement.](https://flitstack.ai/services/pipedrive-implementation)

[See the service →](https://flitstack.ai/services/pipedrive-implementation)

### [All crm migrations](https://flitstack.ai/migrations/crm)

[Every destination we migrate pipelines, contacts, and deals into.](https://flitstack.ai/migrations/crm)

[Back to CRM →](https://flitstack.ai/migrations/crm)

## Sources

1. [Pipedrive — Wikipedia](https://en.wikipedia.org/wiki/Pipedrive)
2. [Importing data into Pipedrive with spreadsheets — Knowledge Base](https://support.pipedrive.com/en/article/importing-data-into-pipedrive-with-spreadsheets)
3. [We ditched HubSpot at $2M revenue and saved $12K/year — r/CRMSoftware](https://www.reddit.com/r/CRMSoftware/comments/1seflc1/we_ditched_hubspot_at_2m_revenue_and_saved_12kyear/)
4. [Updating Pipedrive data with a spreadsheet — Knowledge Base](https://support.pipedrive.com/en/article/updating-pipedrive-data-with-a-spreadsheet)
5. [5 Simple CRM Data Migration Methods — Pipedrive Blog](https://www.pipedrive.com/en/blog/crm-data-migration)
6. [Option fields and label-vs-ID matching — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/option-fields)
7. [Import fields — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/import-fields)
8. [Importing: errors and skip files — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/importing-errors-and-skip-files)
9. [Custom field types — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/custom-field-types)
10. [Custom Field's Options Increased to 10,000 — Pipedrive](https://support.pipedrive.com/en/article/custom-field-options-10000)
11. [Custom fields — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/custom-fields)
12. [Required fields — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/required-fields)
13. [Export and Import to CRM — Pipedrive Features](https://www.pipedrive.com/en/features/data-import-export)
14. [Testbox: On-Demand Sandbox Environment for Developers — Pipedrive R\&D](https://medium.com/pipedrive-engineering/testbox-on-demand-sandbox-environment-for-developers-33025fa045f7)
15. [Import2 App Integration — Pipedrive Marketplace](https://www.pipedrive.com/en/marketplace/app/import-2/bf7972b87b5a9861)
16. [Relationships overview — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/relationships-overview)
17. [File uploading limits — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/file-uploading-limits)
18. [5 Simple CRM Data Migration Methods — Pipedrive Resources](https://www.pipedrive.com/en/crm/resources/crm-data-migration)
19. [How can I move deals to another pipeline? — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/how-can-i-move-a-deal-to-another-pipeline)
20. [Security dashboard — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/security-dashboard)
21. [Calendar sync — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/calendar-sync)
22. [CSV encoding issues — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/csv-encoding-issues)
23. [How can I restore data? — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/restore-data)
24. [Find a Pipedrive Consultant — Pipedrive Expert Marketplace](https://www.pipedrive.com/en/marketplace/partners)

Get a quote

## Moving to Pipedrive?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Pipedrive setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
