HubSpot to Pipedrive Migration Checklist 2026

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.

Frequently Asked Questions