---
title: "Close to Pipedrive Migration: Field Mapping & Rollback"
description: "Migrate Close to Pipedrive with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/close/to/pipedrive"
---

# Close to Pipedrive migration

We migrate Leads, Contacts, Opportunities, and activity history from Close into Pipedrive with the Lead/People split resolved up front, activity records preserved through the REST API with proper parent-record lookup, and every Close Custom Field mapped to a typed Pipedrive field before any data moves across.

Short answer

FlitStack AI migrates leads, persons, organizations, deals and pipelines from Close to Pipedrive, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

![](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) [See what moves →](https://flitstack.ai/migrations/crm/close/to/pipedrive#what-moves)

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

Source Close ![](https://flitstack.ai/platforms-trim/close.webp)

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

Lead Person Organization Deal Pipeline

Mapped field by field · sample run · one-click rollback

## What moves from Close to Pipedrive?

Moving from Close to Pipedrive is a structural migration across two platforms with different core data models.

Read the full summary

Close collapses prospects into Leads and Contacts on a shared record surface; Pipedrive separates unqualified prospects into Leads and qualified contacts into People (which can also live on an Organization). We resolve that split during scoping and design the mapping rules that prevent duplicate records from appearing in Pipedrive's activity timeline. Activity history (calls, emails, SMS, tasks) in Close lives as a JSON array on each record; we parse that array and reattach each activity to the correct Pipedrive entity using the People or Organization lookup. Custom Activities and Custom Objects require a three-phase import pipeline in Close (type, fields, records) that we replicate carefully in Pipedrive using the itemSchemas endpoints for custom objects. Workflows, Smart Views, and Sequences do not migrate; we deliver a written inventory of these for the customer's admin to rebuild post-migration.

1:1

### Lead → Lead

Close Leads with status Unqualified or Not Contacted map directly to Pipedrive Lead.

How it maps

We preserve the Close lead status label as a custom field on the Pipedrive Lead. Leads that are already converted in Close (status set to Customer) require a split decision: they either become Pipedrive People attached to an Organization, or they remain as closed Leads depending on the customer's go-forward pipeline definition. We resolve this during scoping by reviewing the customer's Close lead-status configuration.

1:1

### Contact → Person

Close Contacts map to Pipedrive Person.

How it maps

The Close contact organisation field maps to Pipedrive's Organization lookup. If a matching Pipedrive Organization does not exist at migration time, we create it first to satisfy the lookup dependency. Name, email, phone, and address fields migrate 1:1. Any Contact in Close that has no organisation set maps to a Person with no Organisation linkage, which we flag for manual enrichment post-migration.

1:1

### Organisation (Contact-level) → Organization

Close Contacts carry an organisation field that we extract and dedupe before creating Pipedrive Organizations.

How it maps

Organization name becomes the Pipedrive Organization name. Website, industry, address, and phone migrate to matching Pipedrive Organization fields. The Organization is created before any Person import so that the Organisation lookup is satisfied at the moment of Person insert.

1:1

### Opportunity → Deal

Close Opportunities map to Pipedrive Deals.

How it maps

The pipeline and stage reference from Close becomes the Pipedrive pipeline name and stage label. Deal value, expected close date, and owner migrate directly. Closed-won and closed-lost reasons from Close custom fields map to Pipedrive Lost Reason if configured in the destination pipeline settings.

configuration

### Pipeline → Pipeline

Each Close pipeline becomes a Pipedrive Pipeline.

How it maps

We create the pipeline in Pipedrive first, then map each Close stage to a Pipedrive stage with matching label and display order. Stage probability percentages from Close migrate to Pipedrive's stage probability where supported. If Close has more stages than the destination pipeline supports, we merge adjacent stages and document the consolidation.

1:1

### Activity: Call → Activity (type: Call)

Close call activities migrate to Pipedrive Activities with type = Call.

How it maps

The call outcome, duration, and recording URL from Close's JSON export map to Pipedrive Activity fields. Activity date and time are preserved. We resolve the parent Contact or Lead reference to the correct Pipedrive Person or Lead using the email address as the dedupe key.

******What moves 15 objects

Close Pipedrive

- Lead Lead 1:1
- Contact Person 1:1
- Organisation Organization 1:1
- Opportunity Deal 1:1
- Pipeline Pipeline transformed
- Activity: Call Activity 1:1

\+ 9 more in the mapping below

## How Close and Pipedrive differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension          | Close                                                                              | Pipedrive                                                                                                     |
| ------------------ | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Record model       | Leads and Contacts on shared surfaces with a status toggle                         | Separate Lead and Person objects with Organizations above contacts                                            |
| Activity scope     | Unified inbox combining email, SMS, and call history per Lead/Contact              | Activity log per Person or Organization with separate activity types                                          |
| Pipeline structure | Multiple pipelines gated behind Essentials; Power Dialer on Growth and Scale       | Flexible pipelines with drag-and-drop stages on all paid tiers                                                |
| Custom Activities  | Custom Activity Types with type-specific fields on Growth and Scale plans          | Activities are standard objects; custom activity types require custom fields and type-label conventions       |
| Custom objects     | Custom Objects available on Growth and Scale with dependency ordering              | Custom Objects via itemSchemas on Advanced and higher plans with separate API endpoints                       |
| Pricing model      | Per-seat with no marketing-contact billing; calling features tiered separately     | Per-seat across Essential, Advanced, Professional, Power, Enterprise with AI features bundled on higher tiers |
| Mobile experience  | Mobile app receives consistent complaints about notifications and refresh friction | Mobile app is widely regarded as reliable and well-maintained                                                 |

## What to watch for in a Close to Pipedrive migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Close Lead/Contact split creates record duplication risk

Close merges Leads and Contacts on a shared surface with a status toggle, while Pipedrive separates unqualified prospects into Leads and qualified contacts into People with an Organisation lookup above.

How we handle it

If a Contact in Close is migrated as a Person without checking whether a corresponding Lead already exists in Pipedrive, the result is two records for the same contact. We resolve this by using email address as the dedupe key and running a pre-migration reconciliation pass that identifies which Close Contacts are qualified (already customers) and which are still in a prospect state, routing each group to the correct Pipedrive object.

high

### CSV export silently drops all activity history

Close's CSV export intentionally omits activity data.

How we handle it

Calls, emails, SMS, and tasks appear only in the JSON export. If a customer has only been using CSV exports for their data extraction, their engagement history is not in the file and must be re-exported via the JSON endpoint before migration scoping begins. We always request JSON for activity-bearing records and verify the export contains the expected activity array before confirming the migration scope. This is one of the most common causes of incomplete Close migrations.

medium

### Activity reassembly requires parent-record lookup

Close activities are stored as a JSON array on each Lead or Contact record.

How we handle it

When migrating to Pipedrive, each activity must be reattached to the correct Person, Lead, or Organisation using a lookup by email, phone, or name. Pipedrive's API does not accept activity inserts without a valid parent reference (person\_id, org\_id, or lead\_id). We resolve the parent reference before every activity insert, and we batch activity imports in waves per parent record to stay within Pipedrive's rate limits and avoid orphaned activities.

medium

### Pipedrive custom objects use separate API endpoints

If the destination Pipedrive account uses custom objects (available on Advanced and higher plans), standard field endpoints like /dealFields do not surface those fields.

How we handle it

Custom object schemas and items require the /v1/itemSchemas and /v1/items endpoints instead. We use the correct endpoints for each record type during migration. Custom objects in Pipedrive also require the schema to be created before any items are imported, adding a pre-import setup phase that must complete before the migration window begins.

low

### Smart Views can only be exported from the Leads tab

Close exports are only available from Smart Views created in the Leads tab.

How we handle it

Smart Views built from the Contacts tab produce no export button in the UI. We handle this by querying Leads and Contacts via the API directly rather than relying on saved Smart View exports, ensuring all records are retrieved regardless of how the customer's saved views are structured. The Smart View filter logic is extracted from the API response and translated to Pipedrive saved filters where the criteria are supported.

## How the migration runs

1. ### Discovery and scoping

   We audit the source Close account across plan tier (Solo/Essentials/Growth/Scale), custom field definitions, custom activity types, pipeline count, activity volume per record, Smart View count, and active Workflow documentation.

   What this step covers

   We pair this with a review of the destination Pipedrive plan to confirm which features are available (custom fields on all plans, custom objects on Advanced and higher). The discovery output is a written migration scope that includes the Lead/Contact split rule, the pipeline and stage mapping, and the activity-reassembly strategy.

2. ### Schema design and pipeline configuration

   We configure the destination Pipedrive account before any data moves.

   What this step covers

   This includes creating Organizations from Close organisation fields, setting up Pipedrive Pipelines and stages mapped from Close's pipeline structure, creating custom fields with matching types and choice labels, and configuring any custom activity labels required for Close Custom Activities. Pipedrive's pipeline stages are created with probability weights matching the source Close pipeline where supported. Schema configuration happens in a staging environment or a fresh Pipedrive account so that the production account remains clean until cutover.

3. ### Sandbox migration and reconciliation

   We run a full migration into a test environment using production-like data volume.

   What this step covers

   The customer's RevOps lead reconciles record counts (Leads in, People in, Organisations in, Deals in, Activities in), spot-checks 25-50 random records against the Close source, and signs off the schema and mapping before production migration begins. Any mapping corrections, field-type mismatches, or pipeline structure changes happen here. We do not proceed to production until the sandbox migration is reconciled and signed off.

4. ### Owner reconciliation and User provisioning

   We extract every distinct Close user referenced on Leads, Contacts, Opportunities, and Activities and match by email against the Pipedrive destination's user table.

   What this step covers

   Owners without a matching Pipedrive user go to a reconciliation queue. The customer's Pipedrive admin provisions any missing users. Migration cannot proceed past this step because user references are required on most record inserts and Pipedrive rejects inserts with invalid owner IDs.

5. ### Production migration in dependency order

   We run production migration in record-dependency order: Organisations (from Close organisation fields on Contacts), People (with OrganisationId resolved), Leads (with the Lead/Contact split applied), Deals (with PersonId, OrganisationId, OwnerId, and PipelineId resolved), Custom Fields on Deals, Activities (Calls, Emails, SMS, Tasks via API with parent-record lookup), Custom Activities (three-phase: type, type-scoped fields, records), Attachments and Call Recordings.

   What this step covers

   Each phase emits a row-count reconciliation report before the next phase begins. Rate-limit handling and exponential backoff protect the migration from 429 responses during bulk activity inserts.

6. ### Cutover, validation, and Workflow rebuild handoff

   We freeze Close writes during cutover, run a final delta migration of any records modified during the migration window, then enable Pipedrive as the system of record.

   What this step covers

   We deliver the Workflow, Smart View, and Sequence inventory document to the customer's admin team with the recommended Pipedrive equivalent for each. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's sales team. We do not rebuild Close Workflows as Pipedrive Automations inside the migration scope; that work is handled by the customer's admin or a Pipedrive partner.

![](https://flitstack.ai/platforms/close.svg) Close ![](https://flitstack.ai/platforms/pipedrive.svg) Pipedrive

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Pipedrive Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**4-6 weeks** Typical, smaller accounts

**8-12 weeks** Large or heavily customised accounts

A quote scales with record volume, custom object count, and the complexity of the activity-history migration. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Close to Pipedrive →](https://flitstack.ai/contact)

## Why teams move from Close to Pipedrive

- Teams needing stronger pipeline visualisation and deal-centric reporting move from Close to Pipedrive. Close's reporting suits outbound call teams but reviewers on Reddit and G2 describe it as limited for multi-stage pipeline analysis across product lines or territories. Pipedrive's drag-and-drop pipeline view and goal-tracking features give sales managers more real-time visibility without exporting to a spreadsheet.
- Close's mobile app receives consistent complaints about missed call notifications and the need to reopen the app to refresh status. Pipedrive's mobile app is regarded as reliable and well-maintained for both iOS and Android, which matters for field sales and SDR teams that depend on real-time pipeline updates on the go.
- Pipedrive offers more customisation options at the field and pipeline level without requiring a higher pricing tier. Close's Custom Activities and Custom Objects are gated behind Growth ($99/seat) and Scale ($139/seat), while Pipedrive's custom fields and Advanced-tier custom objects are available at lower price points for teams that need custom data structures without the full calling-stack cost.
- Some teams require native Slack integration without a Zapier or API workaround. Close lacks native Slack at all tiers, which frustrates sales teams that rely on Slack for deal alerts, pipeline notifications, and rep-level activity digests. Pipedrive includes native Slack integration on all paid tiers, eliminating the middleware dependency for real-time pipeline updates.
- Pipedrive's custom objects use itemSchemas and item endpoints that align better with teams building data models for products, properties, subscriptions, or project records. Close's Custom Activities and Custom Objects require strict dependency ordering that adds migration complexity and a higher chance of import failure without a scripted three-phase pipeline.

Questions, answered

## Close to Pipedrive migration questions

How long does a Close to Pipedrive migration take?

Most migrations land between four and six weeks for accounts under 20,000 combined Leads and Contacts with no custom objects and a single pipeline. Migrations with custom objects, multiple pipelines, large engagement histories (over 200,000 activity records), or multiple Close users requiring Pipedrive account provisioning move to eight to twelve weeks because of the three-phase custom activity pipeline, the activity-reassembly lookup work, and the sandbox reconciliation cycle.

Do Close Workflows, Sequences, and Smart Views migrate to Pipedrive?

No. Close Workflows are automation sequences that are tightly coupled to Close's event model and are only available on Growth and Scale plans. Pipedrive Automations are a different trigger-and-action model. We do not migrate Workflows as code. We deliver a written inventory of every active Close Workflow with its trigger, conditions, and actions, plus a recommended Pipedrive Automation equivalent for the customer's admin to rebuild. Sequences and Smart Views similarly do not migrate; we document the Smart View filter criteria as a named checklist for manual recreation in Pipedrive's saved filters.

Do we lose historical engagement data (calls, emails, SMS, tasks) when migrating from Close to Pipedrive?

No, if the correct export method is used. Close's CSV export omits all activity data by design. We request JSON exports for activity-bearing records, which includes the full activity array per Lead and Contact. We then reassemble each activity in Pipedrive by resolving the parent Lead or Contact to the correct Pipedrive Person or Lead using email as the dedupe key, and insert the activity with the original timestamp preserved. Call recordings migrate as attachments on the matched Activity record. The only scenario where activity history is lost is when a customer has only provided CSV exports; we flag this during scoping and request JSON re-exports before migration begins.

Can we run Close and Pipedrive in parallel during the migration?

Yes, in a dual-write or hybrid model. We can configure a read-only migration where Close remains the system of record during the migration window and we capture a delta of any new or modified records after the initial cutover. The customer's team continues using Close for new activity until the final cutover date, at which point we run a delta migration and switch Pipedrive to the system of record. This approach minimises downtime and gives the sales team a defined cutover date rather than a gradual transition. We recommend a two-week parallel window maximum to avoid data divergence.

How do we handle Close Custom Activities and Custom Objects in Pipedrive?

Close Custom Activities require a three-phase import pipeline: create the Custom Activity Type, create type-scoped Custom Fields, then import the activity records. We replicate this sequence in Pipedrive by creating a named Activity with a custom activity\_label and type-specific custom fields. Close Custom Objects map to Pipedrive custom objects using the itemSchemas and items endpoints on Advanced and higher plans. If the destination Pipedrive account is on a lower plan, we migrate the custom object data as custom fields on the standard Contact or Opportunity object and flag the limitation for the customer's admin.

What happens to Close's calling features (Power Dialer, Predictive Dialer) after migration?

Close's built-in dialer stack is not available in Pipedrive. Pipedrive does not offer a native Power Dialer or Predictive Dialer; teams that rely on these features typically integrate a third-party VoIP provider (Aircall, RingCentral, Dialpad) via Pipedrive's API or a supported integration. We document the customer's existing dialer configuration during discovery and flag the gap in the handoff document so the customer's admin can evaluate and configure a replacement VoIP integration before the sales team goes live in Pipedrive.

Can FlitStack AI also migrate our data from Pipedrive back to Close if we need to reverse the migration?

Yes. Reverse migration follows the same dependency-ordered approach: Pipedrive Organisations become Close organisation fields, Pipedrive People become Close Contacts (or Leads if unqualified), Deals become Opportunities, Activities are reassembled against the parent Contact or Lead using email as the dedupe key, and Custom Fields are recreated in Close before record import. The migration scope and pricing are similar to the forward migration. We recommend completing a full data reconciliation in Close after the reverse migration before decommissioning the Pipedrive account.

## Related migrations

[![](https://flitstack.ai/platforms-trim/pipedrive.webp) Migrate to **Pipedrive** Every source we move into Pipedrive, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/pipedrive)

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

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

[See the service →](https://flitstack.ai/services/pipedrive-implementation) [**Civicrm to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/civicrm/to/pipedrive) [**Jobber to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/jobber/to/pipedrive) [**Entera to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/entera/to/pipedrive) [**Housecall Pro to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/housecall-pro/to/pipedrive) [**ActiveCampaign to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/activecampaign/to/pipedrive) [**Daylite to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/daylite/to/pipedrive) [**Close to monday CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/close/to/monday-crm) [**Close to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/close/to/hubspot) [**Close to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/close/to/salesforce-sales-cloud)

## Sources: official documentation

1. [Importing data into Pipedrive with spreadsheets — Knowledge Base](https://support.pipedrive.com/en/article/importing-data-into-pipedrive-with-spreadsheets)
2. [Updating Pipedrive data with a spreadsheet — Knowledge Base](https://support.pipedrive.com/en/article/updating-pipedrive-data-with-a-spreadsheet)
3. [5 Simple CRM Data Migration Methods — Pipedrive Blog](https://www.pipedrive.com/en/blog/crm-data-migration)
4. [Option fields and label-vs-ID matching — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/option-fields)
5. [Import fields — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/import-fields)
6. [Importing: errors and skip files — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/importing-errors-and-skip-files)
7. [Custom field types — Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/custom-field-types)

Get a quote

## Moving from Close to Pipedrive?

Tell us roughly how many records and objects you have. We scope the mapping and the Pipedrive setup with you, then send a quote.

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