Why teams leave Close
Close is excellent at one motion: high volume outbound calling. Teams leave when the motion changes. The company moves upmarket, deals get longer, and suddenly the team needs pipeline management, forecasting and account history more than a power dialer.
Price plays a role too. Close seats are expensive for people who do not dial all day. When account managers and founders need CRM access, the per-seat math starts favouring Pipedrive.
If your team still lives on the dialer, pause. Pipedrive plus a telephony integration can match Close, but it is two tools instead of one. Make the calling decision before the CRM decision, not after.
What carries over and what does not
The records move well. Close exports leads, contacts, opportunities and custom fields through CSV and a solid API. Notes and completed activities can be pulled per lead and imported as Pipedrive notes and activities.
The calling layer does not move. Recordings, voicemail drops, SMS threads and the dialer itself stay in Close. Sequences and their stats stay too. Email threads are the exception, because they live in your mail provider and resync once Pipedrive connects to the same mailboxes.
Field mapping: Close to Pipedrive
| Close | Pipedrive | Notes |
|---|---|---|
| Lead (the container) | Organization | Not the Pipedrive Leads inbox. Match on domain. |
| Contact | Person | Linked to its organization on import. |
| Opportunity | Deal | A Close lead can hold several. Import each as its own deal. |
| Lead status | Organization field or pipeline | Statuses like Qualified or Customer become a single option field. |
| Confidence | Deal probability | Map percentages to stage probabilities. |
| Smart views | Filters | Rebuild the handful in daily use. |
| Calls and SMS | Activities plus archive | Import as logged activities, recordings to your own storage. |
| Sequences | Campaigns or automations | Copy the templates out before cancelling. |
Pitfalls specific to Close
The naming trap catches everyone. Close calls its central object a Lead, and Pipedrive has a Leads inbox. They are unrelated. A Close Lead is an account with contacts and deals inside. Map it to an organization, or you flatten your entire book of business into an inbox.
Multiple opportunities per lead is the second trap. Close happily holds three open opportunities under one lead. Each must become its own Pipedrive deal, linked to the same organization. A naive one to one export loses the extras.
Recordings are the third and the most painful when missed. Once the Close subscription ends, the recordings are gone. Decide early which calls you are legally or commercially required to keep, export them through the API, and store them somewhere you control.
The step plan
1. Decide the telephony stack
Pick the calling tool that pairs with Pipedrive before touching data. Number porting takes weeks and sets your real timeline.
2. Archive the calling history
Pull recordings and SMS threads you must keep through the API. Store them in your own archive with the lead name and date in the filename.
3. Export and reshape the records
Export leads, contacts and opportunities. Split the lead file into organizations and map statuses to a field. Deduplicate on domain and email.
4. Build Pipedrive and test
Pipelines, stages, fields, users, then a fifty record test import. Check that multi-opportunity leads produced multiple deals.
5. Import, connect email, cut over
Import in order, have every user connect their mailbox, and set one cutover date. Keep Close read access until the first month closes clean.
Timeline and cost band
Three to five weeks covers most Close exits, at €4,000 to €10,000 with a partner. The telephony choice adds its own licence cost and porting lead time, so start it first. The cost page explains the wider bands, and the common mistakes guide covers the adoption traps that hit calling teams hardest. Teams weighing a lighter alternative should also read the Copper guide for contrast, and the six step method for where migration sits in the full rollout.