# How to map Pipedrive labels and deal stages Translate SourceLoop's internal lifecycle stages into Pipedrive Person labels (label_ids) and align inbound deal pipelines, both directions. Source: https://sourceloop.ai/help/map-pipedrive-labels/ Updated: 2026-05-28 --- Pipedrive doesn't have a built-in lifecycle stage field like HubSpot. Its closest equivalent is **Person labels** (the `label_ids` field), coloured tags you assign to a Person to indicate state. SourceLoop maps its internal lifecycle stages to one or more of those labels, both ways. This article walks through the mapping for Person labels and notes how SourceLoop handles Deal stages (preserved as-is on inbound, no mapping needed). ## Before you start You'll need: - [Pipedrive connected to SourceLoop](/help/connect-pipedrive-to-sourceloop/) - **Admin** or **Owner** role in SourceLoop - A list of your Pipedrive Person labels (visible in Pipedrive at **Settings -> Company settings -> Person Labels**) ## How the label mapping works The mapping is **per-connection** and **bidirectional**: - **Inbound** (Pipedrive → SourceLoop): when a Person syncs in, SourceLoop reads its assigned labels and translates each one to the matching SourceLoop stage. If a Person has multiple labels, the highest-funnel-position label wins (e.g., 'Customer' beats 'Hot Lead'). - **Outbound** (SourceLoop → Pipedrive): when a SourceLoop contact's stage changes, the mapping translates to the Pipedrive label and adds it to the Person's `label_ids`. Labels in Pipedrive are stored as numeric IDs but displayed by name and colour. SourceLoop's Stage Mapping panel handles the ID lookup automatically; you map by name. ## Step 1: Open the Pipedrive drawer 1. Sign in to [SourceLoop](https://app.sourceloop.ai/). 2. Open **Setup -> CRM -> Pipedrive**. The drawer opens with the sync toggles at the top and two stacked sections relevant here: **Lead status mapping** (for Person labels) and **Lifecycle stage mapping**. **Deal stages** sits below, but Pipedrive deal pipelines flow in automatically with no mapping required. ![SourceLoop Pipedrive drawer showing Lead status mapping (empty, prompting Edit), Lifecycle stage mapping (with explanation), and Deal stages with the Default pipeline values listed](/help/screenshots/sourceloop-pipedrive-field-mapping.webp) 3. Each mapping section has its own **Edit** button. Click **Edit** next to **Lead status mapping** to map Pipedrive Person labels to SourceLoop stages. ## Step 2: Map each Pipedrive label to a SourceLoop stage A typical mapping for an org using common label categories: - `Hot Lead` → In Progress - `Warm Lead` → Contacted - `Cold` → New - `Customer` → Converted - `Disqualified` → Lost For each row, pick the matching SourceLoop stage. The mapping saves on selection. > **Add-only labels** > In the Stage Mapping settings, you can choose between "Replace labels" (SourceLoop sets the exact mapped label and removes others on stage change) or "Add only" (SourceLoop adds the mapped label, never removes existing labels). Most teams use "Add only" so labels added manually by reps stay intact. ## Step 3: Verify the mapping is taking effect 1. Wait 15 minutes for the next delta sync (or click **Resync now** on the Pipedrive card). 2. Open a Person in SourceLoop's Contacts Hub. Its **Lifecycle stage** should reflect the mapped Pipedrive label. 3. Update the Person's labels in Pipedrive. Within 15 minutes the SourceLoop contact's stage updates to match. If the stage stays blank, see [Troubleshoot Pipedrive sync issues](/help/troubleshoot-pipedrive-sync/). ## Custom SourceLoop stages If the five default SourceLoop stages (New, Contacted, In Progress, Converted, Lost) don't match your funnel, add custom ones: 1. In SourceLoop, open **Settings -> Lifecycle stages**. 2. Click **Add stage** (e.g., 'Demo Scheduled', 'Proposal Sent', 'Negotiation'). 3. Save. Then map a Pipedrive label to each new stage in the Stage Mapping tab. ## Deal stages (no mapping needed) Pipedrive Deals run on multi-pipeline flows where each pipeline has its own ordered stages (e.g., Sales pipeline: Lead → Qualified → Proposal → Negotiation → Won). SourceLoop pulls your full pipeline structure on inbound sync and preserves it as-is for reporting. What this means in practice: - **No deal stage mapping is required.** Your existing pipeline structure shows up in SourceLoop's funnel and dashboard reports exactly as it is in Pipedrive. - **Multiple pipelines** are supported. SourceLoop preserves each pipeline separately, so a Deal in your Sales pipeline doesn't get conflated with one in your Onboarding pipeline. - **Stage rename / reorder in Pipedrive** flows through to SourceLoop on the next sync. If you want SourceLoop to write back to Deal stage (e.g., move a Deal forward based on a payment received), use a custom field mapping on the Deal entity instead, see [Push UTMs to Pipedrive](/help/push-utms-to-pipedrive/). ## Lead Inbox vs Persons (a quick note) Pipedrive's **Lead Inbox** is a pre-Deal staging area where new inbound leads land before promotion to a Deal. SourceLoop syncs Persons (which represent the contact regardless of stage), not the Lead Inbox specifically. If your team uses the Lead Inbox heavily, the mapping above still applies, the Person record is the source of truth. ## What's next If the mapping isn't behaving as expected, see [Troubleshoot Pipedrive sync issues](/help/troubleshoot-pipedrive-sync/). ## Frequently Asked Questions ### Pipedrive doesn't have a 'Lead Status' field. What does SourceLoop map to? Pipedrive uses **Person labels** (`label_ids`) as the closest equivalent to a lead status. Labels are coloured tags assigned to a Person (e.g., 'Hot Lead', 'Cold', 'Customer'). SourceLoop maps its internal lifecycle stages to one or more Pipedrive labels per stage. ### Can I use Pipedrive labels for multi-state tracking? Yes, a Person can have multiple labels at once. SourceLoop adds the mapped label when a stage changes; it doesn't remove other labels you've added manually. So labels like 'VIP' or 'Slack-customer' that your team uses outside the SourceLoop mapping stay intact. ### What about Deal stages? Do those need to be mapped? No. Pipedrive Deals use a multi-pipeline stage flow that SourceLoop pulls in as-is on inbound sync. Your existing pipeline structure is preserved exactly. The Stage Mapping tab is for **Person labels**, not Deal stages. ### My Pipedrive admin added a new label. Will SourceLoop pick it up? Yes, on the next properties cache refresh (every 24 hours, or on a manual reconnect). The new label appears in the Stage Mapping dropdown. Map it to a SourceLoop stage and save. ### What if a Person already has labels I don't want SourceLoop to touch? Configure SourceLoop's outbound to "add only, never remove" in the Stage Mapping settings. This way SourceLoop adds the mapped label on stage change but never removes labels you've added manually. ### Can I map multiple SourceLoop stages to the same Pipedrive label? Yes, that's the standard pattern. Pipedrive's labels are usually high-level ('Hot', 'Warm', 'Cold', 'Customer') while SourceLoop's stages can be more granular. Mapping 'In Progress' AND 'Converted' both to a 'Customer' label, for example, is fine.