Pipedrive implementation plan: step by step, as a project

    The five steps we run in every Pipedrive implementation, what each one delivers, what it costs and which mistakes we see most.
    Implementation guideSander Vergouwen16 min readUpdated: 16 November 2026

    In short

    You implement Pipedrive in five steps: intake, blueprint, build, handover and aftercare. A core setup with data model, pipeline and stages takes 2 to 4 weeks and starts at 2,950 euros at Sales Surge. Automation, integrations and dashboards are separate phases with their own price. You pay per phase, before it starts, and every phase ends with something your team can use.

    Source: Sales Surge, Pipedrive Platinum Partner, more than 150 CRM implementationsAs of: 16 November 2026

    In this article
    1. The 5 steps
    2. How to implement Pipedrive
    3. How long does a Pipedrive implementation take?
    4. What does a Pipedrive implementation cost?
    5. Which pipelines and stages do you set up first?
    6. Which fields do you make required?
    7. How do you migrate data from Excel or HubSpot?
    8. Which automations do you build in week 2?
    9. How do you test Pipedrive before go-live?
    10. How do you get the team to use Pipedrive?
    11. The three mistakes we see most
    12. Doing it yourself
    13. Frequently asked questions

    Implementing Pipedrive in 5 steps

    This is the order we follow. It works for a first CRM and just as well for an account that grew messy over the years. The table shows who you need from your own team at each step.

    StepWhat happensTimingWho from your teamWhat you get
    1. IntakeGoals, systems, current process, who struggles with whatWeek 1Sales lead and whoever decides on budgetA written scope with a price per phase
    2. BlueprintStages, fields, routing, integrations and dashboards on paperWeek 1Sales lead, one rep, marketing if leads come from thereA design you sign off before anything is built
    3. BuildConfiguration, automations, integrations, migrationWeeks 2 to 3One admin who answers questions within a dayA working account in a test setup
    4. HandoverTesting, pilot group, training on your own dataWeeks 3 to 4The whole sales team, a few hours eachA team that works in it without us
    5. AftercareHypercare, adjustments on feedback, optional retainerAfter go-liveSales lead for a short weekly checkOne fixed point of contact

    The timing above is for a core setup, which takes 2 to 4 weeks. Every extra phase, such as sales automation or a website integration, has its own lead time. We plan some of them side by side, so the total is shorter than the sum.

    How to implement Pipedrive

    Start from how your buyer buys, not from the settings screen. Most failed setups began with someone clicking through Pipedrive and adding stages and fields as they went. Six months later nobody trusts the reports, because every rep fills it in differently.

    So the work splits into three layers, in this order. First the agreements: what a lead is, when a deal moves to the next stage, who owns what. Then the build that holds those agreements in place, with routing, tasks and integrations. Then the dashboards and a fixed rhythm to look at them. We call these Align, Automate and Accelerate, and the steps in the table above follow that order.

    If you would rather start from a ready-made data model than a blank account, Surge Setup gives you a starting point for the data model, so you skip the blank page. You then refine it with the steps below.

    How long does a Pipedrive implementation take?

    A core setup takes 2 to 4 weeks. That covers the data model, the pipeline, the stages and the groundwork for automation. Each extra phase adds its own lead time.

    What stretches a project is rarely the configuration. It is waiting: for a decision on stage definitions, for an export from the old system, for the one person who knows how the website forms work. We ask for one admin on your side who can answer questions within a working day. That alone keeps most projects inside the planning.

    For a full overview of where time goes in a CRM project, read our CRM implementation timeline.

    What does a Pipedrive implementation cost?

    These are our prices. Your quote fixes the price per phase after the intake.

    PhasePriceLead timeWhat is in it
    CRM implementationfrom 2,950 euros2 to 4 weeksData model, pipeline, stages, ready for automation
    Sales automationfrom 2,200 euros2 to 3 weeksRouting, follow-up, pipeline priority
    Marketing automationfrom 2,200 euros2 to 3 weeksLead scoring, nurture sequences
    Website and CRM integrationfrom 3,750 euros2 to 4 weeksForms straight into Pipedrive, no loose tools
    Dashboards and insightsfrom 1,500 euros1 to 2 weeksCore KPIs, conversion tracking
    Audit of an existing account2,200 euros7 to 10 daysFindings, roadmap, quick wins

    We invoice per phase, always before that phase starts. So you never pay for a phase before you have seen the result of the one before it. Pipedrive licences come on top. Which plan you need, and what it costs per seat, is in our Pipedrive pricing guide.

    Not sure what you need? The free Quick Scan looks at your CRM, data and workflows and tells you within 48 hours where the bottlenecks are.

    Which pipelines and stages do you set up first?

    One pipeline per way you win revenue, with four to seven stages that describe what the buyer did. Not what your rep did.

    The difference matters. A stage called Proposal sent records an action on your side. A stage called Proposal reviewed records that the buyer looked at it and reacted. Only the second one tells you anything about the chance of closing.

    Per stage, agree on five things

    • Entry: what must be true before a deal enters this stage.
    • Exit: what must have happened before it moves on.
    • Activity: what the rep does here, and which task Pipedrive creates for it.
    • Probability: the share of deals that usually moves on, so the forecast has something to work with.
    • Rotting time: how many days a deal may sit here before it turns red.

    Which fields do you make required?

    As few as possible. Start with around twelve fields, not forty. Every field has to earn its place by being used in a filter, a routing rule or a report.

    A set that works for most B2B teams: lead source, deal type, segment or industry, company size, owner, expected close date, lost reason, and three to five fields that belong to your own sales process, such as the product line or the contract term.

    Make a field required at the stage where it becomes known, not at deal creation. Asking for contract value in the first stage just teaches reps to type a random number. Pipedrive lets you set required fields per stage, so use that.

    • Naming: one fixed pattern for every custom field, so integrations and reports stay readable.
    • Dropdowns over free text: a dropdown for lead source gives you a report. Free text gives you forty spellings of LinkedIn.
    • An owner per field: someone who decides when a value changes or a field goes away.

    How do you migrate data from Excel or HubSpot?

    Clean first, then map, then a test import, then the real one. In that order and never in one go.

    From Excel the work is mostly cleaning. One row often holds a company, two contacts and a deal at once, and those have to be split into organisations, persons and deals. From HubSpot the work is mapping: HubSpot properties, lifecycle stages and associations do not line up one to one with Pipedrive fields and pipelines. The HubSpot to Pipedrive checklist lists what to check.

    1. Decide what moves: open deals, active contacts, their organisations and the history you actually use.
    2. Deduplicate on email, phone and company name before the import. Surge Dedupe shows every proposed merge for review, it never merges unseen.
    3. Map every source field to a Pipedrive field, and write down what you drop on purpose.
    4. Run a test import of a few hundred records and compare the counts with the source.
    5. Freeze the old system on the day of the final migration, so nobody keeps working in two places.

    For larger moves, Surge Shift handles the mapping, staging and a dry run before anything is written. The full method is in our guide to CRM data migration.

    Which automations do you build in week 2?

    The ones that make sure no lead waits. Routing, a first task and an alert when nothing happens. Fancier flows come after the team works in the basics.

    Routing: who gets which lead

    PatternWhen it fitsHow you build it
    Round-robinAn even split across the teamIn Pipedrive itself or through Make.com
    TerritoryReps split by region or industryA custom field that an automation matches
    CapacityWorkload based on open dealsMake.com with a count of open deals per owner
    HybridTerritory first, round-robin inside itA flow with several steps in Make.com

    Tasks and SLAs

    Let Pipedrive create the tasks, so nobody has to remember them. A set we often start with: first contact with an inbound lead within five minutes during office hours, a reply to an outbound response within 24 hours, a proposal within 48 hours of the request, and an alert to the manager after 14 days without activity.

    At Ontslagrecht Juristen every new lead gets a call task within 2 hours, with round-robin assignment. That gave 18% higher conversion.

    Integrations that come back in almost every project

    • Make.com: a web form arrives by webhook, Make looks up the organisation and person, creates or updates them, enriches through Apollo and creates the lead. Always with error handling, because a step that fails silently is a step you never see.
    • Apollo: fills company size, industry and role when a lead is created. Check that every source fits GDPR and record where data comes from.
    • CloudTalk: a finished call becomes an activity on the right contact, with the recording. A long call creates a follow-up task.
    • Instantly: a reply on a cold sequence creates or updates the person in Pipedrive, logs the reply and pauses the sequence for that contact.
    • Proposals: we run our own proposals and invoices through Pipedrive Smart Docs. Surge Quote turns a sales call transcript into a proposal. PandaDoc is a good choice when you need its approval flows, and we are a certified PandaDoc partner.

    Which tools belong around Pipedrive, and in what order you add them, is in the Pipedrive RevOps stack.

    How do you test Pipedrive before go-live?

    In a sandbox or a separate test pipeline, with dummy data, against a written list of scenarios. Delete the test pipeline before go-live.

    • Lead flow: a lead from every source arrives in the right fields, routing picks the right owner, duplicates get caught.
    • Automations: tasks fire on each stage change, SLA alerts trigger at the right moment.
    • Integrations: forms create leads, Make.com logs its errors, enrichment fills the expected fields.
    • Reporting and access: dashboards show the right numbers, and every role only sees what it should.

    Then a pilot group of two or three reps works in it for a few days. Before every bigger change, export the configuration and the automation rules, and agree up front what counts as a reason to roll back.

    How do you get the team to use Pipedrive?

    Train on their own data, keep a fixed weekly rhythm, and fix friction the same day. Adoption is the step that decides whether the rest was worth it.

    We never train on a demo account. Reps learn faster when they see their own deals. In the first month a short check per week shows who works in it and where people drop out. Managers learn to run their Monday pipeline review from the dashboard, and that does more for adoption than any training.

    Surge Adopt, a Chrome extension, puts guidance on top of Pipedrive itself and shows which habits stick. More on the people side is in our guide to CRM user adoption.

    • A one-pager per daily task: log a call, move a deal, create a proposal.
    • Short screen recordings of the five workflows people use most.
    • One name for questions, and one way to suggest an improvement.

    The three mistakes we see most

    • Building before agreeing. Stages and fields created before sales and marketing agree what a lead is. The fix later costs more than the build did.
    • Too many fields on day one. Forty fields, ten filled in, and reports nobody believes. Start with twelve and add when a real question comes up.
    • Automating a process that does not exist. Routing and sequences on top of a process that every rep runs differently. Automation then only makes the mess faster.

    Can you implement Pipedrive yourself? What works and what does not

    Setting up Pipedrive yourself is fine for a team of two or three users, with one pipeline, no migration and only the built-in email and calendar sync. Pipedrive is built for that, and the free trial is long enough to try.

    It gets hard at a few clear thresholds: a migration with history, more than one pipeline, routing between reps, integrations that write back into Pipedrive, or reporting for a board. Past those, a setup built on the side tends to drift within a quarter.

    Thinking about outsourcing it? The Pipedrive partner scorecard gives you twelve criteria, 25 questions to ask and the warning signs. Want us to do it? Our Pipedrive implementation service describes what we deliver.

    Frequently asked questions

    How long does a Pipedrive implementation take?

    A core setup with data model, pipeline and stages takes 2 to 4 weeks. Sales automation adds 2 to 3 weeks, a website and CRM integration 2 to 4 weeks, and dashboards 1 to 2 weeks. Some of that runs in parallel, so a full project is shorter than the sum. Your quote lists the planning per phase, and every phase ends with something you can use.

    How much does it cost to have Pipedrive set up?

    At Sales Surge a CRM implementation starts at 2,950 euros. Sales automation starts at 2,200 euros, a website and CRM integration at 3,750 euros, and dashboards at 1,500 euros. An audit of an existing account costs 2,200 euros. You pay per phase, always before that phase starts. Pipedrive licences come on top.

    Can I implement Pipedrive myself?

    Yes, if you are a team of two or three users with one sales process and no data to bring over. Pipedrive is built for that and the trial gives you room to try. Once you add a migration, several pipelines, routing between reps or integrations that write back into Pipedrive, a self-built setup tends to drift. That is usually the point where outside help pays for itself.

    How many pipelines do I need in Pipedrive?

    Start with one pipeline per way you win revenue, not per team. New business is almost always the first. Renewals, upsell or partner deals get their own pipeline only when their stages really differ. Most teams we start with run one or two pipelines in the first month and add a third later, once the first one is used every day.

    Which fields should I create first?

    Only the fields you will filter, route or report on. In practice that is around twelve: lead source, deal type, segment, owner, expected close date, a lost reason and a handful that belong to your sales process. Teams that start with forty fields fill in ten of them. Add a field when someone asks a question the CRM cannot answer yet.

    Should I migrate all my old data into Pipedrive?

    No. Bring over open deals, active contacts and the organisations behind them, plus the history you actually look at. Clean and deduplicate before the import, not after. Old closed deals can stay in an export unless you report on them. We always run a test import first and check the counts against the source before the final migration.

    Should a new inquiry become a lead or a deal?

    Usually a lead first. A lead sits in the Leads Inbox until someone has qualified it, and only then becomes a deal in the pipeline. That keeps your pipeline value honest. Teams that turn every form fill into a deal end up with a forecast full of things nobody is working on. Decide this once, in writing, before you build any routing.

    Which integrations should I connect first?

    Email and calendar sync come first, because without them activity never reaches Pipedrive. Then your web forms, so every inquiry lands in the same fields. After that the tools your team uses daily: calling through CloudTalk, enrichment through Apollo, proposals through Smart Docs or PandaDoc. Make.com sits in between for anything that needs logic across tools.

    How do you test Pipedrive before go-live?

    In a sandbox or a separate test pipeline with dummy data. Send a lead through every entry point and check that routing picks the right owner, that tasks fire on each stage change and that duplicates get caught. Then a small pilot group works in it for a few days. Only after that do we migrate the real data and open it up to the whole team.

    What happens after the Pipedrive implementation goes live?

    First a period of hypercare, where we fix what the team runs into and adjust workflows on their feedback. After that you can continue with a retainer for ongoing changes, new hires and integration maintenance. Many teams also book a review after the first quarter to check whether the stages still match how they sell.

    Partners in this guide

    Click a badge to sign up with our partners:

    Sander Vergouwen

    About the author

    Sander Vergouwen

    Co-founder of Sales Surge

    LinkedIn

    Trial through our partner link

    Try Pipedrive free for 30 days

    Our partner link gives you 30 days instead of the usual 14.

    That is because we are a Pipedrive Platinum Partner. You get full access and you do not need a credit card. When the trial ends, you decide whether to take a subscription.

    • 30 days instead of 14
    • Every feature included
    • No credit card needed

    Trial

    30 days free

    The link opens the Pipedrive sign-up page.

    Start your trial

    The trial starts straight away through the partner link.

    Ready to implement Pipedrive?

    We set up your CRM per phase, with a fixed price and a result at the end of each phase.