How to Migrate from Close to Pipedrive
A Close Lead is a company-level record, not a Pipedrive Lead. Map Leads to Organizations, flatten the nested Contacts, and plan for activity history that the CSV export does not carry.
- Difficulty
- Moderate
- Typical duration
- 1–2 weeks
- Downtime
- None — import into Pipedrive while Close stays live
- Native importer
- Yes — Pipedrive's spreadsheet importer, and Import2 for CRM-to-CRM transfer
| Close | maps to | Pipedrive | What to watch |
|---|---|---|---|
| Lead | Organization | A Close Lead is the company-level record. Do not map it to a Pipedrive Lead. Pipedrive Leads are unqualified deal-like items held in the Leads Inbox. | |
| Contact (inside a Lead) | Person | Close exports contacts one row per contact. Carry the parent Lead name on each row so Pipedrive links the Person to the Organization. | |
| Opportunity | Deal | A Pipedrive deal needs a linked person or organization. Create the pipeline stages for each Close opportunity status first. | |
| Opportunity status | Deal stage | Close opportunities carry a status. Recreate each status you use as a stage in a Pipedrive pipeline. | |
| Custom field | Custom field | Pipedrive cannot import into a field that does not exist. Create each field on the right object first. | |
| Activity (email, call, SMS, note) | Activity or Note | Pipedrive imports activities and notes from a spreadsheet. Close exports activities only as JSON, so you convert them to rows first. | |
| Smart View | Filter | Close Smart Views are saved queries and do not export as records. Rebuild the ones the team uses as Pipedrive filters. |
What transfers cleanly
- Leads as Organizations, with name and custom fields.
- Contacts as People, with email, phone and the parent Lead name.
- Opportunities as Deals, with value and status.
- Activities and notes, once converted from JSON to spreadsheet rows.
- Pipelines, stages and custom fields, if you use Import2, which can create and map them.
What doesn't come across
- CSV has no activity data. Close states the CSV export leaves out activity. Emails, calls, SMS, notes and custom activities come out as JSON.
- Contacts export from the Leads view. A Smart View created on the Contacts tab cannot be exported. Use a Leads-tab Smart View and set the type to Contacts.
- Opportunities export button. Close documents it on the legacy List view only. The Opportunities export API accepts filters such as status and user.
- Download links expire after 7 days. Download the files the day Close finishes them.
- Smart Views. They do not export as data and need a rebuild as Pipedrive filters.
- Duplicates. Pipedrive lets you merge detected duplicates on import. Remove duplicates in the Close export first.
Migration order that works
- Write down the mapping: Lead is an Organization, Contact is a Person, Opportunity is a Deal. Check it with whoever owns the data.
- In Close, export Leads and Contacts from a Leads Smart View with All Fields, and Opportunities from the legacy List view or the export API. Export activities as JSON.
- In Pipedrive, create custom fields, pipelines and stages first. Provision users so owners resolve.
- Join contacts to their Lead in one sheet, so each row holds a person name, the organization name and, for deals, the deal title and value. Pipedrive links everything in a row.
- Run a small import first. Pipedrive's importer takes up to 200,000 rows and 50 MB per file, one tab per import. Rows that fail land in a skip file with the reason.
- Import Organizations and People, then Deals, then Activities and Notes. Choose the duplicate handling at the final step.
- Reconcile counts against Close. A Pipedrive global admin can revert an import within 48 hours.
Both products sell to small sales teams, so the object counts are usually modest. The trap is vocabulary. Close calls a company a Lead. Pipedrive has Leads too, and they mean something else.
Lead is not Lead
In Close, a Lead holds the company, its contacts, its opportunities and most of the activity. In Pipedrive, a Lead is an item in the Leads Inbox that has not become a deal. Map the Close Lead to a Pipedrive Organization. Map Close Contacts to People, and Opportunities to Deals. Import Close Leads as Pipedrive Leads and you lose the company structure.
Flatten the nesting in the spreadsheet
Close exports Leads one row per Lead and Contacts one row per Contact. Pipedrive's importer treats each row as one set of linked records: a row with a person name, an organization name and a deal value creates and links all three. Build one sheet with those columns, or import Organizations first and People after.
Move activity separately
Close's CSV export carries no activity data. Close exports emails, calls, SMS, notes and custom activities as JSON. Pipedrive's importer takes activities and notes from a spreadsheet, so a script converts the JSON to rows. Decide how far back the team needs history before you write it.
Use Import2 if you want the transfer done for you
Pipedrive documents Import2 for moving from another CRM. It can create pipelines and stages and map custom fields. Pipedrive says migrations can take up to 24 hours, and that you should set up users first, or the person running the import owns every record.
Need help moving from Close to Pipedrive?
Craftt, the CRM team behind weekcrm, plans and runs the migration: field mapping, deduplication, history and a cutover your team won't notice. You get a fixed quote within one business day.

