How to Set Up Pipedrive: A Complete Setup Guide

Setting up Pipedrive properly means designing a pipeline that matches your actual sales motion, deciding which fields are required and when, building a small number of automations that save reps real time, connecting the tools reps already use, migrating existing data with cleanup instead of a straight import, and only then building reports. Skip the design decisions and jump straight to import, and you end up with a nicer-looking version of the same messy spreadsheet you started with. This guide walks through each step in the order that actually works, along with the mistakes that show up most often and a realistic timeline.

If you’re still weighing Pipedrive against the process you’re running today, Pipedrive vs a Spreadsheet covers that comparison directly. This guide assumes Pipedrive is the confirmed destination and focuses on doing the setup right the first time.

Design your pipeline stages around your real sales motion

Pipeline design is the first decision, and it’s the one that determines whether reps actually use the tool six months from now. The instinct is to reach for a generic template, or worse, to copy an enterprise-style pipeline with ten or more stages because it looks thorough. Resist that instinct. Most sales teams need 4-6 stages: enough that a rep can look at the board and immediately understand where a deal stands and what needs to happen next, but few enough that moving a deal forward doesn’t feel like administrative overhead.

Build the stage list from how deals actually move today, not from how the sales process is documented on paper. Pull a sample of 15-20 recently closed-won deals and trace which stages they genuinely passed through. Stages that no deal ever occupies are candidates to cut. Stages that deals visibly skip, jumping from an early conversation straight to a signed contract, suggest your real process has already diverged from what’s written down, and setup is the moment to reconcile the two rather than encode the version that no longer matches reality.

If your business runs more than one genuinely different sales motion, new business versus renewals, or a short-cycle product line alongside a longer-cycle service, Pipedrive supports multiple pipelines, and using that deliberately is usually better than cramming every motion into one pipeline with stages that mean different things depending on who’s looking at the board. Assign probability percentages to each stage too, since that’s what makes weighted forecasting in reports usable rather than decorative.

Set required fields and data-quality rules before data lands

Required fields and format rules only do their job if they’re configured before data is imported, not after. Importing everything first and adding validation rules afterward means retroactively fixing a database that’s already inconsistent, which is a much slower process than getting the rules right at the start.

Tie required fields to the point a deal is actually created or moves stage, rather than applying them blanket-wide. Requiring a lead source at deal creation makes sense because it feeds reporting later; requiring ten fields on every deal regardless of context just trains reps to enter a placeholder value to get past the form. Decide field-by-field which ones genuinely feed a report or an automation trigger downstream, since those are the fields where a malformed entry breaks something rather than just looking untidy.

Data-quality rules set at deal creation, tied to specific stage transitions rather than applied uniformly, consistently outperform blanket-required-field policies in adoption, because reps stop treating required fields as friction once each one has a visible, obvious reason to exist.

This is also the point to decide field formats, currency and deal-value conventions, and how custom fields will be used, since custom fields tend to accumulate unchecked once a team starts adding “just one more” field per request. A field audit six months in almost always turns up several fields nobody has looked at since they were created.

Build a small number of automations, not everything possible

Workflow Automation is where a lot of Pipedrive setups either save the team real time or generate noise that gets ignored within a month. The goal isn’t to automate everything the platform allows; it’s to automate the handful of triggers that actually remove manual work reps were doing anyway: task creation on stage change, a notification when a high-value deal moves, a follow-up reminder after a set number of days with no activity.

Rotting-deal rules deserve specific attention because they’re the single most commonly skipped setting, and their absence is one of the most damaging gaps in a Pipedrive setup. A rotting-deal rule flags any deal that’s sat in the same stage past a threshold you set, surfacing it visually on the board or via notification. Without that rule turned on, deals can sit untouched for months while the pipeline still looks full and healthy in a report. Turning rotting-deal rules on at setup, not as an afterthought once someone notices the forecast looks wrong, is one of the cheapest fixes available relative to the problem it prevents.

For a deeper breakdown of which specific automations are worth building first and which ones tend to create more noise than value, see Pipedrive Automation: What to Automate First.

Connect the tools your reps already use

Integration setup covers email, calendar, lead sources, and anything else in the stack reps touch daily. Native two-way email and calendar sync means activity gets logged automatically instead of relying on a rep to remember to note a call happened, which matters directly for the reporting step later. Native integrations cover most common lead-source and marketing tools; anything more specific can usually go through the Pipedrive API without custom development.

This is also the stage to make an explicit decision about LeadBooster and Campaigns rather than assuming either is already included. Both are separate paid add-ons on top of Pipedrive’s core plans: LeadBooster covers chatbot, live chat, web forms and a prospecting tool, and Campaigns covers email marketing. Teams that skip this scoping conversation upfront often discover the gap mid-setup, when someone goes looking for a feature that turns out to require an additional line item. Deciding in week one whether either add-on is genuinely part of the plan avoids a budget surprise later, and it’s a conversation worth having alongside a look at overall Pipedrive implementation cost so the full picture, add-ons included, is priced before work starts.

For teams selling more than one product, this is also where the Products feature gets configured, attaching a real product catalog and pricing to deals so pipeline value reflects an actual product mix instead of one manually-typed number per deal. Teams that sell both products and services often combine the Products catalog for standardized SKUs with custom fields, or a separate pipeline, for services work that doesn’t fit a fixed price list.

Migrate existing data with mapping and de-duplication, not a straight import

Migration is where the biggest quality risk in a Pipedrive setup actually lives, and it’s the step most likely to get rushed because it feels like the least interesting part of the project. Treating migration as a straight import, dumping an old spreadsheet or CRM export directly into Pipedrive, carries forward every stale deal and duplicate contact the old system had, just in a cleaner-looking interface. The trust problem doesn’t go away; it just gets a nicer coat of paint.

Do the cleanup before import. Map every field from the source system to its Pipedrive equivalent explicitly, including deciding what happens to fields that don’t have a direct match. De-duplicate contacts and companies before the data moves, particularly if you’re consolidating more than one source, a CRM export plus a sales spreadsheet plus a list someone kept in a separate tool. Match on email and normalized company name rather than relying on any post-import cleanup to catch it, since duplicate-detection tools in most CRMs are built to catch a new duplicate a rep accidentally creates going forward, not to untangle a messy multi-source consolidation after the fact.

Decide how much historical data to bring over as active records versus reference-only. Most teams migrate open deals in full and import closed-won and closed-lost history as read-only records for reporting continuity, rather than as fully active records competing for attention on a live board. That keeps the new pipeline clean without losing the historical data leadership still wants to reference.

Build reporting once activity logging is actually consistent

Reporting is deliberately the last step, not the first, because a report is only as trustworthy as the activity data feeding it. Build pipeline, conversion and activity reports once logging habits are established across the whole team, not immediately at launch when some reps are still getting used to the tool.

The most common reporting failure in a new Pipedrive setup isn’t a broken report configuration, it’s inconsistent input. When some reps log every call and email and others log nothing, activity-based reports end up comparing behavior rather than results, and the numbers stop meaning what leadership assumes they mean. This is usually a manager-level habit issue rather than a settings problem, and it’s worth confirming logging consistency with a few weeks of real usage before building the dashboards leadership will start making decisions from.

Once logging is consistent, weighted pipeline value (using the stage probabilities set during pipeline design), conversion rate by stage, and average time-in-stage are the reports most teams find genuinely useful day to day, more useful than a large dashboard with every metric the platform can generate.

A realistic week-by-week Pipedrive setup timeline

A typical Pipedrive implementation through a partner runs 2-6 weeks, and the timeline tracks migration complexity and pipeline count more than raw deal volume.

Week 1: Discovery and pipeline design. Stages, probabilities and rotting-deal rules get mapped against the real sales motion rather than a generic template, and the team makes an explicit decision on whether LeadBooster or Campaigns are actually in scope.

Weeks 2-3: Automation build, field configuration, and migration. Workflow Automation gets built, required fields and formats get configured, and data migration from a spreadsheet or legacy CRM happens with mapping and de-duplication done before import, not after.

Weeks 4-5: Integration and reporting. Email, calendar and lead-source tools get connected, and report and dashboard build happens once activity-logging habits are confirmed across the team.

Week 6: Training, parallel run, and go-live. The team gets trained on the new setup, runs a short parallel period alongside the old system, and then goes live. Simple single-pipeline projects for a small team often compress to 2-3 weeks total; a complex migration with heavy de-duplication needs can extend the full project toward 6 weeks.

Cost tracks the same complexity drivers as timeline. Industry ranges for a partner-led setup run roughly $2.75k for a basic single-pipeline configuration to $16k for a complex migration with multiple pipelines and heavy data cleanup (Sales Surge industry research, 2026). See the Pipedrive implementation cost guide for a fuller breakdown of what moves a project toward either end of that range, and aibrevo’s pricing page for how project scope translates into a quote.

The setups that struggle six months in almost never fail because of a missing feature. They fail because the pipeline was built to look thorough on day one instead of matching how the team actually sells, and nobody revisited the stage list once real usage showed which stages were fiction.

Common mistakes that undo a Pipedrive setup

A handful of mistakes account for most of the Pipedrive setups that stop working within a few months of launch.

Too many pipeline stages. Teams copy an enterprise-style 10-stage pipeline onto a simple sales motion, and reps stop updating deals because moving them forward feels like unnecessary admin. Fewer, clearer stages get used consistently; more, precise-sounding ones get quietly ignored.

No rotting-deal rules turned on. Deals sit untouched in a stage for months with nothing flagging it, so the pipeline looks healthy in a report while a meaningful share of the deals in it are actually dead. Rotting-deal rules exist specifically to surface this before it distorts forecasting.

Activities logged inconsistently across reps. Some reps log every call and email while others log nothing, so activity-based forecasting and performance reports end up comparing behavior rather than results. This usually needs a manager-level habit fix, not a settings change.

Skipping the LeadBooster or Campaigns scoping decision upfront. Teams assume lead capture or email marketing is bundled into the core plan, only to discover both are separate paid add-ons partway through setup. Deciding upfront whether you’ll actually use them avoids a mid-project budget surprise.

Treating migration as a straight import with no cleanup. Old, stale or duplicate deals get imported as-is because it’s faster than cleaning first, and the new pipeline inherits the same trust problem the old spreadsheet had, just in a nicer interface.

When a Pipedrive setup needs a rebuild instead of a fix

Pipedrive is simple enough by design that most problems that show up after launch are fixable without starting over. Knowing which category a given problem falls into saves time and avoids rebuilding something that only needed a small correction.

A single automation firing at the wrong stage or condition is a quick, isolated fix, not evidence the whole setup is broken. A handful of deals missing required data is a reminder or required-field fix, addressable without restructuring anything. A single wrong number in an otherwise-trusted report is usually a filter or field-mapping issue.

On the other side, a pipeline with ten or more stages that nobody on the team agrees on usually needs a genuine redesign, collapsing back to the 4-6 stages that actually reflect the sales motion, rather than tweaking individual stage names. Activity logging that’s wildly inconsistent across the entire team, not just one or two reps, points to a structural problem, required activity types and manager enforcement, rather than a one-off correction. And an old account set up years ago with no rotting-deal rules and no products structure for a multi-SKU business usually needs a fuller reconfiguration rather than piecemeal patches. If you’re evaluating an existing setup against these signals, Pipedrive implementation services covers what an audit-first engagement looks like before any rebuild work starts.