This moves selected contact data into a DialBreeze list. It does not synchronize Pipedrive deals, stages, activities, notes, owners or opt-outs. No automatic follow-up or CRM writeback is included. Review calling eligibility separately before a list enters a session.
1. Export a filtered People view.
Pipedrive requires export permission, and an export only includes data visible to the exporting user. Open the contact People list view, filter to the authorized calling cohort and choose the columns with the gear icon. Use … → Export filter results for the displayed fields. Choose CSV rather than a chart or deal detail XLSX export.
The Pipedrive export documentation ↗, updated September 3, 2026, distinguishes this from the global-admin Tools and apps → Export data path. The latter can export all People, but that is not an eligibility filter. A deal-based export may repeat a person across multiple deals: review and deduplicate the person/phone pairs before preparing your list. Notes and activities are exported separately; they are not part of this contact import.
2. Build a contact-only upload copy.
Keep the original export with Person ID in a secure reconciliation sheet. In a separate working copy, rename the supported columns explicitly. Pipedrive export labels vary with the selected fields and language, so the table is a mapping recipe, not a guarantee about every header.
| Source data | CSV header | Preparation |
|---|---|---|
| Person first name / last name | first_name / last_name | Use separate columns. If only a full name was exported, split it with human review; do not assume a final word is always a surname. |
| Person phone | phone | Select one number; export labels and multiple values need cleanup. Preserve +country code as text. |
| Person email | Use one chosen address, not a labeled or delimited collection. | |
| Optional contact address | address | Map only if the address belongs to this person, not an unrelated organization or deal. |
| Person ID | No mapped generic CRM ID | Keep in your private reconciliation file. It is not a DialBreeze lead ID. |
| Deal stage, owner, notes, activities | Not mapped | Leave outside this contact upload; maintain workflow and restrictions in your source system. |
Do not leave a full name under Name and expect it to become first and last names. The current importer accepts first_name and last_name. For a labeled phone such as “mobile: …”, remove the label in your working copy and check the number. Choose the actual phone you intend to dial when the export contains multiple phone values. Keep international numbers as text with + and the country code; a bare ten-digit number is treated as US by the importer.
first_name,last_name,phone,email
Jordan,Example,+12025550102,jordan@example.comThis is format-only fictional data, not a calling target. Keep consent evidence and restrictions outside the import, and check them before authorizing a session. A Pipedrive Person ID does not become a persistent external-ID link in the current generic CSV importer.
3. Validate a five-row file before the full cohort.
- Create a separate named test list in DialBreeze and use CSV upload. Save as UTF-8 with one header row and one selected phone per person. Use a new list that is not selected in any active session. The current importer creates NEW leads immediately; it is not a preview-only or release approval gate. Do not start a dialing session.
- Inspect all five records. Check split names, email, phone country code and any address. Compare the file count with accepted rows; a row without a parsable phone is skipped.
- If a field is blank, check the header rather than assuming a provider mapping exists. Remove ambiguous records from the production file until a person reviews them.
- Before a retry, inspect existing list contents. Generic CSV import is not a Pipedrive-ID upsert; repeated uploads do not promise duplicate-free reconciliation.
- Record the source filter, export time and file version. Recheck current stop requests and other restrictions in Pipedrive before the admin releases the calling list.
4. Review any contact import back into Pipedrive.
DialBreeze's admin CSV export contains contact and address fields—not call dispositions, notes or tasks. Its Code and Phone Number are separate columns: combine them as text into +{Code}{Phone Number} for a Pipedrive Person phone. Map the separate first/last names to person fields, and map Email to the person email field. Do not treat the exported DialBreeze ID as a Pipedrive Person ID.
Use your retained source IDs and a reviewed match to decide which existing person should change. Do not rely on name alone. Pipedrive's spreadsheet import documentation ↗, updated October 7, 2026, requires a name (or first and last names) for People and recommends email or phone to reduce duplicates. Its path is Tools and apps → Import data → Import from spreadsheet. Select contact data types only, review field mappings and the preview, then choose duplicate handling intentionally.
Review the import summary and skip file rather than assuming success. The source documentation describes global-admin revert within 48 hours; verify that option in your account before a large change. This guide does not authorize a CRM write. For call outcomes, the separate Pro/Team outbound webhook requires a receiver, signature checks, matching rules and downstream failure handling maintained by your team.
Ask for assisted setup, not an API connection.
Describe whether you need a People calling list or an outcome handoff. Do not email API tokens, passwords, OAuth credentials or customer exports. Setup is assisted and calls use your own Telnyx account. The request takes no payment and does not create an account.