How to map Pipedrive labels and deal stages

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
• 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.
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.

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.

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.

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.

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.