1: Missing Required Data & Skipped Rows
Scenario: "My file imported, but half of my contacts or deals are missing!"
User Intent / Keywords: Missing records, rows skipped, red exclamation mark, import failed for some rows.
The Root Cause: Pipedrive requires strict architectural anchor fields. A Person must have a Name column populated. A Deal must have a Deal Title populated. If these cells are blank in the spreadsheet, Pipedrive will silently skip or flag those rows with an error icon.
Resolution Steps:
Have the user look at the import history screen and check if rows were flagged with a red warning icon.
Explain that Person Name and Deal Title are non-negotiable required fields.
Fix: Advise the user to update the source spreadsheet. If a contact name is missing, they can temporarily copy the email address or use a placeholder like "Unknown Contact" into the Name column, then re-run the import.
2: Disassociated Data Relationships
Scenario: "I imported my spreadsheet, but the deals aren't linked to my contacts or organizations."
User Intent / Keywords: Floating deals, unlinked contacts, data not connected, separate records created.
The Root Cause: The user imported multiple data objects (People, Organizations, Deals) from one sheet but forgot to map the cross-object structural relationships during the mapping wizard phase.
Resolution Steps:
Explain that Pipedrive treats People, Orgs, and Deals as independent objects.
To link them during a single import, the spreadsheet must have columns for both items in the same row, and both must be explicitly mapped in the wizard step.
Fix: If the import already happened, they will need to use the "Revert Import" tool to wipe it out. Then, re-upload and ensure that
Person -> NameandDeal -> Titleare both actively mapped in the same configuration screen.
3: Dropdown & Custom Field Errors
Scenario: "I’m getting 'Invalid Picklist Value' warnings or accidental new dropdown options."
User Intent / Keywords: Mapping warning, dropdown broken, custom field error, text mismatch, picklist.
The Root Cause: Spreadsheet data does not match pre-existing Pipedrive single-option or multi-option dropdown fields exactly (e.g., "Cold outbound" in Excel vs "Cold Outbound" in Pipedrive).
Resolution Steps:
Remind the user that picklist fields are case-sensitive and spacing-sensitive.
Fix: They have two options:
Option A: Fix it directly inside the Pipedrive import preview screen using the edit pencil icon on the warning rows.
Option B: Cancel the import, add the missing values to the field settings in Pipedrive (
Settings > Data Fields), and restart the import.
4: Silent Automations
Scenario: "I just imported a list of contacts/deals, but none of my workflow automations or welcome emails triggered."
User Intent / Keywords: Automation didn't run, emails didn't send, trigger failed after import, workflow broken.
The Root Cause: This is an intentional safety feature. Native spreadsheet imports in Pipedrive do not trigger Workflow Automations. This prevents users from accidentally sending mass emails or creating thousands of accidental tasks on a bulk upload.
Resolution Steps:
Validate that their automation isn't broken but it's behaving as Pipedrive intended.
Fix: If they need automations to trigger on these leads, they must either:
Use a bulk-update trick post-import (e.g., adding a specific label to the imported list in bulk, which can trigger workflows).
Import the data using an external API tool or integration platform (like Make or Zapier) instead of a spreadsheet.
Note: Importing data into your Pipedrive account won’t trigger any event-triggered automations, except when the import updates leads. However, automations based on date triggers can be activated through imports.
5: Historical Date Overwrites
Scenario: "All the historical deals I just imported say they were created today!"
User Intent / Keywords: Creation date wrong, historical data ruined, won date says today, timeline messed up.
The Root Cause: If no specific timestamp column is mapped to the default system time fields during import, Pipedrive automatically stamps the current date and time onto every single created record.
Resolution Steps:
Alert the user that they must fix this quickly before sales data reporting gets warped.
Fix: Revert the import immediately. Ensure the source spreadsheet has columns for
Deal Creation Date. When mapping for updating, explicitly connect those columns to the Pipedrive system field ID for deal.Deal Creation Date; Deal Closed On; Won Time; Expected Close Date, Lost Time are the default fields available to be imported with specific needed dates.
6: File Size & Scale Blockers
Scenario: "Pipedrive is refusing to upload my file completely."
User Intent / Keywords: Upload failed, file too big, limit reached, error loading CSV.
The Root Cause: Pipedrive’s native spreadsheet importer enforces a hard cap of 50,000 rows and 50MB per file.
Resolution Steps:
Ask the user to check the size and row count of their CSV/XLSX file.
Fix: Tell the user to split the file into smaller chunks (e.g., 25,000 rows each) and upload them sequentially. Pipedrive will still catch duplicates across the separate uploads using its global deduplication rules.
7: External System IDs & CRM Migrations
Scenario: "I can't map my Salesforce ID to Pipedrive's System ID field during import."
User Intent / Keywords: Salesforce ID, Hubspot ID, external ID, system ID mapping, central field assignment, migration ID, ID overwrite.
The Root Cause: In Pipedrive, the default "System ID" field is a read-only, internally generated unique identifier reserved exclusively for Pipedrive's backend database. The import wizard will not allow external, third-party IDs (like those from Salesforce, HubSpot, or an external SQL database) to be mapped directly into that specific default field, which causes import errors or skipped rows.
Resolution Steps:
Clarify the technical limitation directly: Explain that Pipedrive's native System ID field cannot be overwritten with data from another platform.
Provide the industry-standard workaround for CRM data migrations.
Fix: Guide the user through these steps:
Step 1: Cancel the current import and go to Settings > Data Fields.
Step 2: Create a new text-based Custom Field and name it something clear, like "Salesforce ID" (create this for both People and Organizations if applicable).
Step 3: Restart the import wizard and map the spreadsheet's legacy ID column directly to your newly created custom field instead of the system field.
8: Template Limitations & Header Mapping
Scenario: "I downloaded the Pipedrive template, but it's missing fields (like Source Channel or Product Category) that I see when I add a deal manually. How do I get my Excel data to show up on the deals dashboard?"
User Intent / Keywords: template missing fields, add excel to deals dashboard, custom fields in excel, download template layout, align headers, import new deals.
The Root Cause: Pipedrive's downloadable sample import templates are generic and only contain standard, default system fields. They do not dynamically update to include an account’s unique custom fields. Users often mistakenly believe they are locked into using only the columns provided in the downloaded template, or they don't realize they must build the custom fields in Pipedrive before uploading their data.
Resolution Steps:
De-escalate Template Anxiety: Reassure the user that the downloaded template is just a basic guide. They do not have to stick to its exact columns—they can use their own Excel sheet.
Check Pre-requisites (The "Pipedrive First" Rule): Remind the user that if they have unique data points in Excel (like "Product Category"), those custom fields must already exist in Pipedrive (
Settings > Data Fields) before they upload the spreadsheet.Fix (Best Practice Alignment): Guide the user to prepare their file and map it:
Step 1: Edit the spreadsheet's top row (headers) so that the column names exactly match the field names in Pipedrive (e.g., Change "What they want" to "Deal Title", and "Channel" to "Source Channel").
Step 2: Upload the file. Because the Excel headers now match Pipedrive's fields perfectly, Pipedrive's import wizard will auto-map them instantly.
Step 3: Complete the import, and the new data will automatically populate the corresponding columns on the Deals pipeline dashboard.
9: Mapping Fallbacks & Auto-Population
Scenario: "During Step 3, Pipedrive forces me to match 'person name2', and if I don't, it uses the email or phone number as the person's name."
User Intent / Keywords: person name2, step 3 match, email as name, phone as name, auto-populating name, match section, mapping step.
The Root Cause: A Name is a non-negotiable required field to generate any Person record in Pipedrive. If your spreadsheet contains secondary contact details (like a second email or a colleague's phone number) that prompt Pipedrive to map a second person (
Person 2), but the actual name column for that second person is blank, Pipedrive triggers a fallback mechanism. Rather than failing the import entirely, it copies the available email or phone string into the Name field to force the record creation.Resolution Steps:
Explain Pipedrive's fallback behavior: Clarify that the system only uses email/phone numbers as names when it is forced to create a contact record that lacks a designated name.
Help the user identify if they are accidentally mapping secondary contact columns to a completely new person (
Person 2) instead of attaching them to the primary person (Person 1).Fix: Guide the user through these options:
Option A (Fix the sheet): Update the source spreadsheet so that every row containing contact data has a legitimate entry in the name column (even a placeholder like the company name or "Contact 2").
Option B (Fix the mapping): In Step 3 of the import, check your mapping. Ensure that secondary emails or phone numbers are mapped as
Person - Email (Work)orPerson - Phone (Mobile)under the same Person object, rather than accidentally creating a newPerson 2object.
10: Cross-Module Label Loss (Leads vs. Deals)
Scenario: "I imported a list into the Lead Inbox with labels, but when I convert those leads into deals, the labels completely disappear from the deal summary tab."
User Intent / Keywords: label disappears, lead conversion label, missing label after conversion, lead to deal label loss, label mask, backend ID error.
The Root Cause: Pipedrive treats the Leads Inbox and Deals Pipelines as two entirely separate database environments. Even if you have a label named "Warm" in both Leads and Deals, Pipedrive reads them as completely different assets on the backend. A Lead label uses a long, unique alpha-numeric string, whereas a Deal label uses a simple number ID. When a Lead is converted to a Deal, the system looks for the exact database ID to transfer. Because the Lead label's ID doesn't exist in the Deal ecosystem, the label is dropped.
Resolution Steps:
Translate the technical bottleneck simply: Explain to the user that while human eyes see the word "Warm" in both places, the system sees two entirely different hidden ID codes that cannot bridge the gap during native lead-to-deal conversion.
Provide alternative strategic workflows to preserve this data.
Fix: Guide the user to use one of these two standard workarounds:
Option A (The Custom Field Route - Recommended): Do not use native labels for this data point. Instead, create a single custom dropdown field (e.g., "Lead Priority") and make sure it is enabled for both Leads and Deals. Custom fields configured for both objects will safely carry their text data over during a conversion.
Option B (Pipeline Bypassing): If these contacts are meant to become deals anyway, bypass the Leads Inbox entirely during the import. Upload the spreadsheet directly as Deals and place them into a designated stage in your primary pipeline.
11: Activity Mapping Order & ID Matching
Scenario: "I imported my historical task and activity list, but none of the activities are linking to my deal cards."
User Intent / Keywords: tasks not linked, activities unlinked, history missing from deals, link activities to deals, activity mapping error, deal ID for activities, tasks disconnected.
The Root Cause: This is an "order of operations" and data relationship failure. For Pipedrive to link an Activity to a Deal during an import, either the Deal and the Activity must be imported on the exact same spreadsheet row, or the Deals must already exist in Pipedrive before the activities are uploaded. If you upload a separate activity file without referencing Pipedrive's specific unique identifiers (IDs), the system cannot guess which activity belongs to which deal, resulting in floating, unlinked tasks.
Resolution Steps:
Explain the Order of Operations Rule: Gently clarify that Pipedrive needs a bridge to connect independent datasets. Deals must exist in the system before a separate activity history file can be attached to them.
Assess the Volume: If the user only has a handful of tasks, advise them to link them manually directly inside the app. If they have a large volume, recommend a structural re-import using IDs.
Fix (Relinking via Pipedrive ID): Guide the user through the following corrective steps:
Step 1 (Export Existing IDs): Go to the Deals list view in Pipedrive. Ensure the system "ID" column is visible. Export this list to an Excel sheet to grab the unique IDs Pipedrive assigned to those newly created deals.
Step 2 (Match the Sheet): Open the Activities spreadsheet and add a column for "Pipedrive Deal ID". Use a VLOOKUP or copy/paste to match the correct Pipedrive Deal ID to each corresponding activity row.
Step 3 (Re-import Activities): Re-upload the activity file. In the mapping step, map that new ID column explicitly to
Activity -> Deal -> Pipedrive ID. The system will automatically snap the historical tasks onto the correct deal cards.
12: Multi-Field Phone Mapping & Label Ordering
Scenario: "I have both Work and Mobile numbers for my contacts in my spreadsheet. Will Pipedrive capture both, and how do I control which phone number shows up first or gets labeled correctly?"
User Intent / Keywords: phone mapping order, phone work mobile, multiple phone numbers, pencil icon label, phone display order, primary phone number, contact numbers.
The Root Cause: Pipedrive natively supports storing multiple phone numbers under a single Person contact record. However, the system determines which number is the "primary" (first displayed) option based entirely on column hierarchy: the phone column that appears furthest to the left in the spreadsheet is prioritized. Additionally, Pipedrive requires manual interaction in the mapping interface to assign specific types (like Mobile vs. Work) to prevent them from just defaulting to a generic label.
Resolution Steps:
Explain the Left-to-Right Priority Rule: Inform the user that Pipedrive reads columns sequentially. The first phone column it encounters in the Excel/CSV file becomes the primary number on the contact card.
Introduce the Pencil Icon Customization: Explain that they can map multiple spreadsheet columns to the exact same Pipedrive
Person -> Phonefield, using the inline settings to distinguish them.Fix: Guide the user through these file preparation and mapping steps:
Step 1 (File Layout): Open the spreadsheet. Position the column they want as the primary number (e.g., Mobile) to the left of the secondary number column (e.g., Work).
Step 2 (Map Primary): In Step 3 of the Pipedrive import, find the first phone column. Map it to
Person -> Phone. Click the pencil icon next to the mapped field and select the matching label (e.g., Mobile).Step 3 (Map Secondary): Find the second phone column. Map it also to
Person -> Phone. Click its pencil icon and select the second label (e.g., Work). Both numbers will be cleanly saved to the same contact card in the correct order.
13: Multi-Product Deal Imports
Scenario: "How do I import a single deal that has 3 to 5 linked products without creating duplicate deals on my dashboard?"
User Intent / Keywords: import products, multiple products, multiple rows per product, duplicate deal, link product, sales sheets with line items.
The Root Cause: Pipedrive's native spreadsheet importer processes each row of a file as an individual, separate record. If a user tries to list the same deal on 5 different rows in order to include 5 distinct products during the initial import, Pipedrive will create 5 separate, identical duplicate deals. To cleanly link multiple products to a single deal, the system requires an anchor key—the unique, system-generated Deal ID.
Resolution Steps:
Explain the System Behavior: Clarify that Pipedrive will create duplicates if the exact same deal name appears across multiple rows during a first-time import.
Introduce the Two-Step Strategy: Guide the user to split the process between creating the deal cards first, and then associating the line-item products using system IDs.
Fix (4-Step Workflow): Guide the user with the following instructions:
Step 1 (Initial Import): Import your list to create the Deals linked to the Contacts first (without including the products yet, or including just the first product for each sale).
Step 2 (Export IDs): Go to your Deals list view in Pipedrive, ensure the "ID" column is visible, and export this list to an Excel/CSV file to capture the unique deal IDs Pipedrive just generated.
Step 3 (Prepare the Product Sheet): On your product spreadsheet, organize the data so that each product occupies its own row. Add a column for the Pipedrive Deal ID and use the exported data from Step 2 to fill in the correct ID for each corresponding product row.
Step 4 (Update Re-import): Upload the adjusted product spreadsheet back into Pipedrive. In the mapping step, make sure to map the ID column to
Deal -> System ID. Pipedrive will recognize the unique ID, prevent deal duplication, and cleanly append the multiple line-item products directly onto the correct deal cards.