How to import deals in Pipedrive and verify the import

To import deals into Pipedrive, start with a clean CSV or spreadsheet, then use the Deals import flow to map each column to the right deal field. Make sure the file includes the values Pipedrive needs for title, value, stage, owner, and any related person or organization fields you want to attach. After the import runs, review the summary for skipped or failed rows so you can fix bad mappings or bad data before you try again.

Prerequisites

• A CSV or spreadsheet file with one deal per row.
• Column headers that are clear enough to map to Pipedrive fields.
• The deal fields you plan to import, especially title, value, stage, and owner.
• Access to the Pipedrive account and pipeline you want to import into.
• If you plan to attach people or organizations, those names or IDs in the file as well.

Before you start, clean up the file so repeated rows, blank required values, and inconsistent stage or owner names are easier to spot. If your team uses custom deal fields, confirm the exact field names in Pipedrive first so you can match them during mapping.

Import deals into Pipedrive

1. Open the Deals import flow in Pipedrive.

Use the import option from the Deals area, then choose the file that contains your deal records. The exact labels in the menu can vary by account, but you should be starting an import from Deals, not from people or organizations.

2. Choose the file format and confirm the columns in your file.

A CSV or spreadsheet is the usual starting point. Check that each row is one deal and that the file includes the columns you need before you continue. If a column is blank for some rows, decide whether that value can stay empty or whether you need to fill it in first.

3. Map each column to the correct Pipedrive field.

Match your source columns to Pipedrive fields one by one. title should map to the deal title, value to the deal amount, stage to the pipeline stage, and owner to the user who should own the deal. If you have related person or organization columns, map those too so the deal lands with the right records attached.

If you use custom deal fields, map them explicitly instead of assuming Pipedrive will guess correctly. A wrong mapping here is the main reason deals end up with the wrong stage, owner, or notes.

4. Check how duplicates, required fields, and empty cells will be handled.

Review the import settings before you run it. If the file contains deals that might already exist, decide whether to allow duplicates, skip them, or handle them another way based on your team’s process.

Fill in any required fields before importing. If Pipedrive expects a deal title, stage, or another field and the cell is empty, that row can fail. Empty cells are fine only for fields your setup does not require.

5. Run the import and review the summary.

When the import finishes, read the summary carefully. Look for rows that were skipped, failed, or imported with warnings, and use the row details to see which field caused the problem. If the summary shows a pattern, such as the same field failing on many rows, fix the source file or mapping before reimporting.

6. Correct any deals that landed in the wrong stage or owner.

If some deals imported into the wrong stage, update the stage values in the source file so they match the pipeline stages exactly, then reimport the affected rows or edit the deals in Pipedrive if only a few records are wrong. If the owner is wrong, check whether the file used a name that does not match a Pipedrive user or whether the owner mapping pointed to the wrong field. Reassign the deals to the right owner after import if needed, then use the corrected file the next time you import.

Common problems when importing deals

Duplicate deals are one of the most common problems. Depending on your import settings and how Pipedrive matches records, duplicates may be created, skipped, or linked in a way you did not expect. If duplicates matter in your setup, decide before import whether you want to keep both records, overwrite anything, or stop and clean the file first.

Missing required fields usually show up as row errors. If your setup requires a deal title, stage, or another field, fill those values before you try again.

Mismatched stage names happen when your spreadsheet uses labels that do not exactly match the pipeline stages in Pipedrive. Fix the stage values in the file so they match what Pipedrive can map.

Owner problems usually mean one of two things: the owner name in the file does not match a user in Pipedrive, or the mapping pointed to the wrong user field. If the owner does not exist, create the user in Pipedrive first or assign the deals to an existing user during import.

If many rows fail for the same reason, stop and correct the file before reimporting. That is usually faster than patching the same mistake one deal at a time.

Completion

The import worked if your deals appear in Pipedrive with the right title, value, stage, owner, and related records, and the summary shows only the rows you expected to fail or skip.