Pipedrive CSV: Import Deals, People, and Organizations

Pipedrive Imports Are Pipeline Contracts

Sales teams in the US, UK, Australia, Canada, and Europe use Pipedrive CSV to migrate from spreadsheets, merge conference lead lists, and export deals for forecasting. Pipeline names, stage labels, and owner emails must match the company account — or deals land in the wrong stage with the wrong owner.

People, Organizations, Deals — Import Order

Import masters before transactions.

Step-by-Step: Import Deals from CSV

Conference-list to pipeline path.

• Export Pipedrive’s sample or an existing deals export to copy headers.
• Ensure Pipeline and Stage values match the account exactly.
• Map Owner to a Pipedrive user email that exists.
• Currency + value: plain decimals; strip symbols.
• Expected close dates: ISO or consistent locale.
• Clean in Online CSV Editor; dedupe on person email + org name.
• Import organizations → people → deals.
• Spot-check 10 deals in the pipeline UI.

Deal title,Pipeline,Stage,Value,Currency,Person email,Organization,Expected close date
Acme - Annual,Sales Pipeline,Qualified,12000,USD,alex@acme.example,Acme Ltd,2026-06-30

Exporting for Forecasts and RevOps

CROs still want Excel.

• Export deals filtered to open pipeline or the period you need.
• Keep Deal ID as text.
• Archive raw exports before analyst pivots.
• Join to Stripe/QuickBooks carefully — won deal ≠ cash collected.
• Convert to Excel for board decks after cleaning.

Custom Fields and Labels

Where duplicates multiply.

• Custom field names must match; slight spelling differences create parallel fields.
• Single-option fields need preexisting options when required.
• Phone/ZIP as text.
• UTF-8 for EU company names and umlauts.

Multi-Pipeline and Multi-Currency Orgs

Common in UK/EU agencies and US multi-product companies.

• Include Pipeline name on every deal row.
• Do not sum GBP and USD values without FX policy.
• Stage names differ per pipeline — validate pairs together.
• When sharing sheets across US and DE teams, normalize decimals and dates first.

Pipedrive vs HubSpot vs Salesforce CSV

Templates are not interchangeable.

• Maintain a master lead sheet; generate CRM-specific CSVs.
• See HubSpot CSV and Salesforce CSV guides for those importers.
• Lifecycle field names differ even when concepts match.

Common Mistakes

Pipeline chaos classics.

• Importing deals before people/orgs.
• Wrong stage label → deals stuck in default stage.
• Owner emails that are not users.
• Excel destroying deal values with currency formats.
• Re-importing the same event list weekly without dedupe.

Best Practices

Treat imports as revenue-system changes.

• Pilot in a test pipeline when possible.
• Version CSVs with source + date.
• Document pipeline/stage vocabulary.
• Dedupe on email before every lead dump.
• Cleanse in-browser for PII-heavy lists.

Why Use Convert CSV Online?

Convert CSV Online is free, browser-based, and requires no account for everyday conversions. Prep Pipedrive imports in the Online CSV Editor, fix EU delimiters, and convert exports to Excel for RevOps across US, UK, AU, CA, and EU teams.

Conclusion

Pipedrive CSV imports succeed when entities arrive in order and pipeline/stage/owner values match the live account. Export for foresight, import with pilots, and never confuse won-deal value with bank cash.