Back to Resources

Migration Guide

18 min

HubSpot to Pipedrive Migration Checklist 2026

47 steps from data export to team training. The exact checklist a Pipedrive Gold Partner uses to migrate B2B teams from HubSpot, with zero data loss.

This is the operational checklist Sales Surge uses to migrate B2B sales teams from HubSpot to Pipedrive. It covers the full lifecycle: pre-migration audit, data preparation, pipeline design, custom field mapping, workflow translation, email and integration setup, dashboard rebuild, training, and a 47-item post-migration QA. Designed for sales leaders, RevOps managers, and admins who need a structured, low-risk path off HubSpot.

Most B2B teams of 5-50 reps overpay for HubSpot and underuse 70% of its features

A clean HubSpot to Pipedrive migration takes 4-6 weeks for standard setups, 8-10 for complex ones

Data preparation in HubSpot is where 80% of migration risk lives, do this before touching Pipedrive

Pipedrive workflows replace HubSpot workflows, but the logic must be redesigned, not copy-pasted

The 47-step QA checklist below catches the silent issues that surface 30 days post-launch

Migrating from HubSpot to Pipedrive looks simple on paper: export some CSVs, import them into Pipedrive, retrain the team. In practice, sales teams lose deals, automation, and trust when the migration is rushed. This checklist is the structured method we use at Sales Surge to migrate B2B teams from HubSpot to Pipedrive without dropping balls. It assumes a real production HubSpot instance with workflows, sequences, custom properties, and integrated tools, not a sandbox. Use it as your project plan or as a sanity check on a partner's proposal.

1. Why companies migrate from HubSpot to Pipedrive

Three patterns drive most HubSpot to Pipedrive migrations we run. First, cost: HubSpot Sales Hub Professional starts around 90 EUR per user per month with a five-seat minimum, and Operations Hub for serious automation pushes the bill to 800 to 3,600 EUR per month. Pipedrive Power sits at 59 EUR per user per month with no minimum and no separate automation tier. Second, complexity: HubSpot's growing object model (contacts, companies, deals, tickets, custom objects, plus marketing assets) becomes overhead for sales teams that just need a clean pipeline. Third, sales focus: HubSpot is a marketing platform that added sales tools, Pipedrive was built for sales from day one. Teams that live in the pipeline find Pipedrive faster to use and easier to adopt. None of these are absolutes. HubSpot is the right call for marketing-led organisations with a large content engine. Pipedrive wins for sales-led B2B teams of 5 to 200 reps where pipeline velocity and rep adoption matter more than marketing automation depth.

2. Pre-migration audit (1 week before)

Before you touch Pipedrive, audit what you actually have in HubSpot. Most teams discover that 30 to 50 percent of their HubSpot setup is unused or broken. Migrating that mess into Pipedrive just relocates the problem. Run this audit one week before the migration kicks off. Document every active workflow with its trigger and outcome. List every custom property on contacts, companies, and deals, and mark which ones have less than 20 percent fill rate (candidates for deletion). Export a list of all integrations: calling tools, proposal tools, marketing automation, enrichment, calendar. Identify the system of record for each data type, contacts often live half in HubSpot and half in a marketing tool. Pull a deal stage report for the last 12 months and confirm which stages actually move pipeline versus which are noise. Interview three reps and one manager about what they use daily, you will be surprised what the team does not touch.

3. Phase 1, Data preparation (week 1)

Data preparation is where 80 percent of migration risk lives. In HubSpot, run a deduplication pass on contacts and companies before exporting. Use HubSpot's native dedup tool or a partner-built script. Standardise country and phone formats, you cannot fix this cleanly post-import. Export contacts, companies, deals, notes, and activities as CSV. For deals, include the deal owner, deal stage, close date, amount, pipeline name, and every custom property you intend to keep. For activities (calls, emails, meetings, tasks) export the timestamp, owner, related deal or contact, and notes. Decide what historical data to bring across: most teams migrate the last 24 months of closed deals plus all open deals, and archive the rest. Trying to migrate ten years of legacy activity is the single biggest source of post-launch slowness and confusion.

4. Phase 2, Pipeline structure design in Pipedrive

Do not replicate HubSpot's pipeline one-to-one. Use the migration as a chance to fix what you wished was different. Decide how many pipelines you need: new business and renewals are almost always separate, partnerships and upsell often deserve their own. For each pipeline, define 5 to 7 stages with a clear, observable definition for each (something the rep does or the prospect confirms, not a vague feeling like 'qualified'). Add stage probabilities for forecasting, and decide which stages require which custom fields to be filled before a deal can move forward. This 'required fields per stage' rule is the single biggest data quality lever in Pipedrive, and it is something HubSpot does not enforce nearly as well.

5. Phase 3, Custom fields mapping

Build a field mapping document in a spreadsheet. Three columns: HubSpot property, Pipedrive field, transformation rule. For each HubSpot custom property you want to keep, decide whether it maps to a Pipedrive deal, person, or organisation field, what type it should be (text, number, single option, multiple options, monetary), and whether the values need cleaning during import (for example normalising 'NL', 'Netherlands', and 'The Netherlands' into one). Be ruthless: if a property has under 20 percent fill rate or has not been used in reporting in the last year, do not migrate it. Every field you create in Pipedrive is a field a rep can leave empty, breaking your data quality from day one.

6. Phase 4, Workflow translation (HubSpot workflows to Pipedrive automations)

Do not lift and shift workflows. Most HubSpot workflows we audit have stale branches, dead ends, or duplicate logic. List every active HubSpot workflow with its business purpose, then redesign it in Pipedrive's workflow automation. Pipedrive automations cover the core sales motions: deal stage changes triggering tasks, deal creation triggering owner assignment, inactive deal alerts, follow-up reminders, and email templates. For more complex flows (lead routing by territory, multi-step nurture sequences, cross-system data sync) use Make.com on top of Pipedrive's webhooks. Make.com plus Pipedrive replaces what HubSpot Operations Hub does, at roughly 10 percent of the cost.

7. Phase 5, Email integration setup

Connect each rep's email to Pipedrive using Smart Email Bcc or the native Gmail and Outlook integration. Decide on email tracking and template policies up front: who can see whose emails, which templates are shared, which are personal. If you used HubSpot sequences, plan the equivalent in Pipedrive (native cadences for simple sequences, or Smartlead, Instantly, or Apollo for outbound at scale). Set up email signature standards and confirm calendar sync (Google Calendar or Microsoft 365) so meeting booking flows work from day one. Test sending and receiving for at least three pilot reps before rolling out to the wider team, email setup is the single most common day-one frustration.

8. Phase 6, Reports and dashboards rebuild

Take inventory of every HubSpot report and dashboard the team actually uses. Most teams keep 5 to 10 reports and quietly abandon the rest. Rebuild only the ones that drive decisions: pipeline by stage, forecast by close date, win rate by source, activity per rep, average sales cycle. In Pipedrive, build manager dashboards (team performance, pipeline health) separately from rep dashboards (my deals, my activities, my targets). Set up insights filters for the slices you care about (by region, by product, by deal size). If you need executive-level reporting beyond Pipedrive's native insights, plan a Looker Studio or Power BI connector from day one rather than retrofitting it later.

9. Phase 7, Team training and rollout

Training is where most migrations either land or fail. Run role-based sessions: reps need 90 minutes on daily workflow (creating deals, logging activities, moving stages, using filters), managers need 60 minutes on dashboards and forecasting, admins need a separate session on automations and field governance. Record every session. Provide a one-page cheat sheet per role. Run a two-week pilot with 3 to 5 reps before opening Pipedrive to the full team, this is when you find the real adoption blockers. Plan a daily 15-minute check-in for the first week post-launch, then weekly for month one. Keep HubSpot read-only for 30 days after Pipedrive go-live so reps can reference history without being tempted to dual-enter data.

10. Common pitfalls and how to avoid them

Five mistakes show up in nearly every failed HubSpot to Pipedrive migration. One: migrating everything 'just in case' and burying reps in noise. Solution: be ruthless during the audit. Two: trying to launch in one big-bang weekend. Solution: phased rollout with a pilot group. Three: skipping the workflow redesign and directly translating HubSpot workflows into Pipedrive. Solution: rebuild from business outcomes, not from existing automation. Four: forgetting marketing handoff. If HubSpot was your marketing automation, decide how leads now flow into Pipedrive (often via Make.com plus a tool like Encharge, ActiveCampaign, or Customer.io for the marketing side). Five: cutting training to save budget. The CRM you adopt is the CRM that wins, not the CRM with the best features.

11. Timeline expectations

Standard migration (single pipeline, under 50 users, fewer than 20 custom fields, basic integrations): 4 to 6 weeks end to end. Complex migration (multiple pipelines, 50 to 200 users, 50+ custom fields, calling and proposal tool integrations, marketing automation handoff): 8 to 10 weeks. Enterprise migration (multi-region, multi-language, custom integrations, large historical data scope): 10 to 14 weeks. These ranges assume a dedicated internal owner on your side and one external implementation partner. They do not include time spent waiting for stakeholder decisions, which is usually the real bottleneck. Build a calendar with named decision deadlines for pipeline structure, field list, and integration scope.

Post-Migration QA Checklist (47 items)

Run through every item in the first 14 days post-launch. Anything unchecked becomes a Week 2 issue.

Data integrity (1-12)

Total open deal count in Pipedrive matches HubSpot export within 1 percent

Total contact count matches expected migration scope

Total organisation/company count matches expected migration scope

Spot-check 20 random open deals: owner, stage, amount, close date all correct

Spot-check 10 random contacts: linked to correct organisation

Spot-check 10 random closed-won deals: amount and close date correct

All custom fields in mapping doc exist in Pipedrive with correct type

No duplicate contacts created during import

No duplicate organisations created during import

Phone numbers normalised to international format

Country values normalised to a single standard

Activity history (calls, emails, meetings) attached to correct deals/contacts

Pipeline & process (13-22)

All pipelines visible to the correct user groups

Stage names and order match the design document

Stage probabilities set for forecasting

Required fields per stage enforced and tested

Lost reasons list configured

Currency settings correct per pipeline if multi-currency

Default deal owner rules in place for new deals

Lead inbox configured (if using Leads feature)

Filter views set up for each role (rep, manager, admin)

Saved views shared with the right teams

Automation & workflows (23-32)

Every business-critical HubSpot workflow has a Pipedrive equivalent

All Pipedrive automations tested with sample deals

Owner assignment rules trigger correctly on new deal creation

Stage-change automations create the right tasks

Inactive deal alerts firing at the correct interval

Follow-up reminders sending to the correct owner

Make.com scenarios live and monitored

Webhook endpoints configured and verified

Error notifications routed to the admin

Run-rate limits checked on Pipedrive API and Make.com plan

Integrations & email (33-40)

Email sync working for every active rep

Calendar sync working for every active rep

Calling tool (CloudTalk, Aircall, Toky) connected and logging activities

Proposal tool (PandaDoc, Better Proposals) connected and writing back deal status

Outbound tool (Apollo, Instantly, Smartlead) syncing replies into Pipedrive

Marketing automation handoff tested with a sample lead

Enrichment tool (Lusha, Cognism, Apollo enrichment) connected

Slack or Teams notifications configured for key deal events

Reporting & adoption (41-47)

Manager dashboard built and shared

Rep dashboard built and shared

Forecast report matches sales leadership's expected format

Activity report tracks the KPIs the team is held to

Training recordings stored in a known location

One-page cheat sheet distributed per role

HubSpot set to read-only and decommissioning date confirmed

Frequently Asked Questions

How long does a HubSpot to Pipedrive migration take?

A standard migration with one pipeline and under 50 users takes 4 to 6 weeks. Complex migrations with multiple pipelines, 50 to 200 users, and integrated calling and proposal tools take 8 to 10 weeks. Enterprise scope can run 10 to 14 weeks. The timeline depends more on internal decision speed than technical work.

Will we lose any data during the migration?

No, when the migration is structured correctly. The 47-step QA checklist exists specifically to catch any data discrepancies in the first two weeks. We keep HubSpot read-only for 30 days post-launch as a safety net. The data we deliberately leave behind (low-value historical activity, unused custom properties) is documented before migration so nothing is lost without an explicit decision.

Can we keep HubSpot for marketing and use Pipedrive for sales?

Yes, this is one of the most common hybrid setups. HubSpot Marketing Hub stays for landing pages, forms, and email campaigns. Pipedrive becomes the sales system of record. Lead handoff happens via the native HubSpot to Pipedrive integration or via Make.com for more control. This usually cuts the HubSpot bill by 50 to 70 percent since you can drop Sales Hub and Operations Hub.

What about HubSpot sequences and snippets?

Pipedrive has native email templates and basic cadences. For HubSpot-style sequences with branching logic, most teams use Smartlead, Instantly, or Apollo on top of Pipedrive. The setup is leaner and the cost is significantly lower than HubSpot Sales Hub Enterprise.

How do we handle reporting that we built in HubSpot?

Audit which reports the team actually uses in the last 90 days. Most teams keep 5 to 10 reports out of dozens. Rebuild those in Pipedrive's native insights. For executive-level dashboards, connect Pipedrive to Looker Studio or Power BI from day one.

Do we need a Pipedrive partner or can we do this ourselves?

If you have under 5 users, no integrations, and no historical data, self-migration is realistic with this checklist. For 10+ users, integrated tools, or migration of more than 12 months of data, a partner pays for itself by avoiding the post-launch issues that take weeks to unwind. A Pipedrive Gold Partner like Sales Surge has migrated dozens of teams off HubSpot using exactly this method.

What is the cost difference between HubSpot and Pipedrive?

For a typical 15-user B2B sales team, HubSpot Sales Hub Professional plus Operations Hub Starter runs around 2,150 EUR per month. The equivalent Pipedrive Power plus Make.com Pro runs around 920 EUR per month. Annual savings of roughly 14,800 EUR, before counting the time saved on simpler administration.

Want a Pipedrive Gold Partner to Run This for You?

Sales Surge migrates B2B teams from HubSpot to Pipedrive in 4 to 8 weeks, fixed price, zero data loss guaranteed. Book a call to scope your migration.

Book a Migration Call

HubSpot to Pipedrive Migration Checklist 2026 | Sales Surge