HubSpot to Pipedrive Migration: 7-Phase Checklist (2026)

    Seven phases from audit to training, and 47 checks after go-live. The checklist we use as Pipedrive Platinum Partner, with a count per object before and after.
    Migration GuideSander Vergouwen16 minUpdated: 16 November 2026

    In short

    A HubSpot to Pipedrive migration runs in seven phases: data preparation, pipeline design, field mapping, workflow rebuild, email and integrations, reporting, and training. After go-live you run 47 checks in the first 14 days. For a standard migration with one pipeline and under 50 users, 4 to 6 weeks is a common range. You prove nothing went missing with a count per object before and after.

    Source: Sales Surge, migration method as Pipedrive Platinum PartnerAs of: 16 November 2026

    In this article
    1. Why teams move
    2. Pre-migration audit
    3. What does not come across
    4. Phase 1: data preparation
    5. Exporting HubSpot data
    6. Phase 2: pipeline design
    7. Phase 3: field mapping
    8. Import tooling
    9. Phase 4: workflows
    10. Phase 5: email and integrations
    11. HubSpot Marketing plus Pipedrive
    12. Phase 6: reporting
    13. Phase 7: training
    14. Pitfalls
    15. Timeline
    16. Post-migration checklist: 47 checks
    17. Frequently asked questions

    This is the method we use as Pipedrive Platinum Partner, named one of the top 8 Pipedrive partners worldwide in July 2026, across more than 150 CRM implementations. It assumes a real HubSpot account with workflows, sequences, custom properties and connected tools. Use it as your own project plan, or to check a partner's proposal. Rather have it done for you? See our HubSpot to Pipedrive migration service.

    Why do B2B teams move from HubSpot to Pipedrive?

    Most teams move for three reasons: the bill, the weight of the platform, and how much of it the sales team actually uses. None of these is a law. HubSpot is a good choice for marketing-led companies, and we set it up too. The point is to know which of the three applies to you before you plan a migration.

    1. The bill grows with every hub

    HubSpot prices per hub and per seat. Sales Hub Professional starts at $90 per seat per month billed annually, plus a one-off onboarding fee. Advanced automation and data sync sit in Operations Hub, which is a separate subscription. Pipedrive prices per user per month on one plan, with automation built into the higher plans. The table below puts the two side by side for a team of 15.

    Licence costs for 15 users, list prices per month billed annually, excluding VAT, checked November 2026.
    LinePrice per seat15 users per monthSource
    HubSpot Sales Hub Professionalfrom $90, billed annuallyfrom $1,350, plus $1,500 one-off onboardinghubspot.com, November 2026
    HubSpot Operations Hubseparate hub, price per tieron top of Sales Hubhubspot.com, November 2026
    Pipedrive Premium€59, billed annually€885pipedrive.com, November 2026
    Pipedrive Ultimate€79, billed annually€1,185pipedrive.com, November 2026
    Make.com for complex flowspriced by operations, not by seatdepends on volumemake.com, November 2026

    Prices change, and both vendors run discounts and annual billing. Check them at the vendor on the day you decide. For a wider comparison with Zoho in it, see our CRM comparison with prices and sources.

    2. The platform is heavier than the sales team needs

    HubSpot keeps adding objects: contacts, companies, deals, tickets, custom objects and every marketing asset. For a team that mainly works a pipeline, that is overhead. Pipedrive starts from the pipeline and stays there.

    3. Sales lives in the pipeline

    Pipedrive was built for sales from the first version. Reps who spend their day moving deals usually find it quicker to work in. If you want the full trade-off, read Pipedrive vs HubSpot.

    What should you audit in HubSpot before you start?

    Audit what is actually in use, one week before the migration starts. Almost every HubSpot account we open has workflows nobody remembers and properties nobody fills. Moving that into Pipedrive only relocates the mess.

    1. List every active workflow with its trigger, its outcome and its owner.
    2. List every custom property on contacts, companies and deals. Mark the ones filled on fewer than 20 percent of records as candidates to drop.
    3. List every integration: calling, quotes, enrichment, marketing, calendar, forms.
    4. Decide per data type which system is the source of truth. Contacts often live half in HubSpot and half in a marketing tool.
    5. Pull a stage report for the last 12 months and see which stages actually move deals and which are noise.
    6. Ask three reps and one manager what they open every day. What they never mention is a candidate to leave behind.
    7. Count every object: contacts, companies, deals per pipeline, activities, notes. This count is your baseline for the check after go-live.

    What does not come across from HubSpot?

    Contacts, companies, deals, notes, products and owners map cleanly. Tickets, custom objects, marketing assets, sequences, lists and workflows do not come over one to one. They need a new home or a rebuild, and you decide that before the export, not after.

    HubSpot objects and where they go in Pipedrive.
    HubSpotPipedriveStatus
    ContactsPersonsComes across
    CompaniesOrganizationsComes across
    DealsDeals, per pipelineComes across
    PropertiesCustom fieldsComes across after mapping
    Products and line itemsProducts on the dealComes across
    Notes, calls, meetings, tasksNotes and activitiesComes across through the API export
    Logged emailsNotes, or email sync from go-livePartly: history as notes, new mail through sync
    Owners and teamsUsers and visibility groupsRebuild: create users before the import
    Pipelines and stagesPipelines and stagesRebuild: redesign, do not copy
    TicketsNo native object. Surge Service (beta) inside Pipedrive, or an external helpdeskDoes not come across
    Custom objectsNo equivalent. Custom fields or a separate toolDoes not come across
    Marketing emails, forms, landing pages, eventsStay in HubSpot Marketing or move to a marketing toolDoes not come across
    SequencesPipedrive sequences or InstantlyRebuild
    Active and static listsFiltersRebuild
    WorkflowsPipedrive automations and Make.comRebuild
    Reports and dashboardsInsights, or Surge Reports for cross-object reportingRebuild

    Tickets are the one that surprises teams most. If support runs in HubSpot Service Hub, decide first where support goes. Surge Service is our helpdesk inside Pipedrive. A separate helpdesk with a Pipedrive integration also works.

    Phase 1: data preparation (week 1)

    Clean the data in HubSpot before you export it. Fixing formats and duplicates after the import is slower and less reliable.

    1. Run a deduplication pass on contacts and companies in HubSpot.
    2. Standardise country values and phone numbers to one format.
    3. Decide the history scope. Most teams take all open deals plus the closed deals of the last 24 months, and archive the rest.
    4. Write down what you leave behind and who agreed to it. That list is part of the migration, not a footnote.

    Trying to bring ten years of activity across is the most common cause of a slow, cluttered Pipedrive after go-live. Archive old history as a file you can still search.

    How do you export HubSpot data completely?

    The export screens in HubSpot give you records and their properties. For the full activity history and the links between objects, you need the HubSpot API. That is the difference between a migration where deals arrive empty and one where a rep sees the last call.

    What the standard export covers

    • Contacts, companies and deals with the properties you select.
    • The deal owner, stage, close date, amount and pipeline name.
    • One file per object, so the links between them have to be rebuilt by ID.

    What needs the API

    • Calls, meetings, tasks and notes with their timestamps and owners.
    • Logged emails, as far as they were logged on the record. Mail that only sat in someone's inbox is not in HubSpot.
    • Associations: which contact belongs to which deal and company.
    • Attachments, which come as separate files.

    The limits to plan for

    The API has rate limits, so a large account takes hours to read, not minutes. Marketing engagement such as email opens and form history stays in HubSpot. Keep the HubSpot export files and the ID mapping until the check after go-live is closed. Our general guide on CRM data migration covers the same steps for other systems.

    Phase 2: pipeline design in Pipedrive

    Do not copy the HubSpot pipeline one to one. Use the migration to fix what you always wanted different.

    1. Decide how many pipelines you need. New business and renewals are almost always separate. Partnerships and upsell often deserve their own.
    2. Give each pipeline 5 to 7 stages, each with a definition you can observe: something the rep did or the prospect confirmed.
    3. Set stage probabilities for the forecast.
    4. Decide per stage which fields must be filled before a deal can move. In Pipedrive this rule does more for data quality than any training.

    Phase 3: custom field mapping

    Build a mapping sheet with three columns: HubSpot property, Pipedrive field, and the rule that converts the value. For each property, decide whether it becomes a deal, person or organization field, and which type it gets: text, number, single option, multiple options or monetary.

    • Normalise values during the import. 'NL', 'Netherlands' and 'The Netherlands' become one option.
    • Drop properties filled on fewer than 20 percent of records, or not used in a report in the last year.
    • Every field you create is a field a rep can leave empty. Fewer fields is better data.

    Which tool do you use for the import?

    For a small account the Pipedrive importer is enough. For a large account with activity history, you want a tool with mapping, staging and a dry run. That is why we built Surge Shift.

    Import tools for a HubSpot to Pipedrive migration.
    Pipedrive importerSurge Shift
    What it isThe spreadsheet import built into PipedriveOur migration tool, built by Sales Surge
    Good forPersons, organizations and deals from CSV or ExcelLarge accounts with history and several objects
    MappingPer import, in the import screenMapping per object before the import
    Test runImport, check, undo if neededStaging and a dry run before anything is written
    LimitHistory and links between objects take manual workOur product, so you work with us or with the tool

    Whichever tool you use, the order is fixed: users first, then organizations, then persons, then deals, then activities and notes. Read more on Surge Shift.

    Phase 4: rebuild workflows as Pipedrive automations

    Rebuild from the business outcome, not from the old workflow. Most HubSpot workflows we audit have stale branches, dead ends or logic that runs twice.

    1. Write down per active workflow what it is for, in one sentence.
    2. Rebuild the core sales motions in Pipedrive automations: tasks on stage change, owner assignment on new deals, alerts on inactive deals, follow-up reminders.
    3. Move the complex flows to Make.com on top of Pipedrive: routing by region, multi-step nurture, sync with other systems.
    4. Test every automation with sample deals before go-live.

    Phase 5: email and integrations

    Connect every rep's mailbox before go-live and test it with a pilot group. Email is the most common day-one frustration.

    • Connect Gmail or Outlook through the Pipedrive email sync, or use Smart Email BCC.
    • Agree up front who sees whose mail and which templates are shared.
    • Plan the replacement for HubSpot sequences: Pipedrive sequences for simple follow-up, Instantly or Apollo for outbound at volume.
    • Confirm calendar sync so meeting booking works from the first day.
    • Test sending and receiving with at least three pilot reps.

    Can you keep HubSpot Marketing and use Pipedrive for sales?

    Yes, and we build it regularly. HubSpot Marketing Hub keeps landing pages, forms and campaigns. Pipedrive becomes the sales system of record. The connection between them decides whether it works.

    What you decide before you connect

    1. Which system owns the contact record. Usually HubSpot for marketing fields and Pipedrive for everything after the handoff.
    2. The trigger for the handoff, for example a lifecycle stage or a lead score.
    3. Which direction unsubscribes and consent travel. They must reach both systems.
    4. How you prevent duplicates when the same person arrives twice.

    Native integration or Make.com

    The native HubSpot integration with Pipedrive covers a simple contact sync. Make.com gives you control over field mapping, conditions and error handling. We use Make.com when the handoff has rules. The downside of this setup: you run two systems, and someone has to own the sync.

    Phase 6: rebuild reporting

    Rebuild only the reports the team opened in the last 90 days. Most teams keep 5 to 10 and quietly drop the rest.

    • Pipeline by stage, forecast by close date, win rate by source, activity per rep, average sales cycle.
    • Manager dashboards for team performance and pipeline health, separate from rep dashboards with my deals and my activities.
    • For reporting across objects that native Insights cannot do, plan Surge Reports, Looker Studio or Power BI from the start.

    Phase 7: training and rollout

    Training decides whether the migration lands. Train per role, on your own data.

    1. Reps: 90 minutes on daily work. Creating deals, logging activities, moving stages, using filters.
    2. Managers: 60 minutes on dashboards and the forecast.
    3. Admins: a separate session on automations and field rules.
    4. Run a two-week pilot with 3 to 5 reps before opening Pipedrive to everyone.
    5. Hold a 15-minute check-in every day in the first week, then weekly in the first month.
    6. Keep HubSpot read-only for 30 days, so reps can look things up without typing data twice.

    Record every session and give each role a one-page cheat sheet. How to make adoption measurable afterwards is in our guide on CRM user adoption.

    Common pitfalls in a HubSpot to Pipedrive migration

    1. Bringing everything along just in case. Reps drown in noise. Be strict in the audit.
    2. Switching over without a pilot and without a count beforehand. A planned cutover in one weekend is fine, once a pilot group has worked in Pipedrive and every object has been counted.
    3. Copying workflows one to one. Rebuild from what each workflow is for.
    4. Forgetting the marketing handoff. If HubSpot ran marketing, decide how leads reach Pipedrive now.
    5. Cutting training to save budget. The CRM the team uses wins, not the CRM with the most features.
    6. No baseline count. Without a count per object before the export, you cannot prove afterwards that nothing went missing.

    How long does a HubSpot to Pipedrive migration take?

    Common lead times per migration size, as a market range rather than a fixed Sales Surge timeline.
    ScopeWhat it includesLead time
    StandardOne pipeline, under 50 users, fewer than 20 custom fields, basic integrations4 to 6 weeks
    ComplexSeveral pipelines, 50 to 200 users, 50 or more custom fields, calling and quote tools, marketing handoff8 to 10 weeks
    LargeSeveral regions and languages, custom integrations, a lot of history10 to 14 weeks

    These are common ranges, not a fixed timeline of ours. What we expect for your account follows from the scoping. The ranges assume one person on your side who owns the project, and one implementation partner. They do not include waiting for decisions, which is usually the real bottleneck. Put named decision dates in the plan for the pipeline structure, the field list and the integration scope.

    Post-migration checklist: 47 checks

    Run every check in the first 14 days after go-live. Anything still open becomes a week-two issue.

    Data integrity (1 to 12)

    1. Every object count (persons, organizations, deals per pipeline, activities, notes) matches the baseline, or the difference is written down and explained
    2. Contact count matches the agreed migration scope
    3. Organization count matches the agreed migration scope
    4. Spot-check 20 random open deals: owner, stage, amount and close date are correct
    5. Spot-check 10 random persons: linked to the right organization
    6. Spot-check 10 random won deals: amount and close date are correct
    7. Every field in the mapping sheet exists in Pipedrive with the right type
    8. No duplicate persons created by the import
    9. No duplicate organizations created by the import
    10. Phone numbers in international format
    11. Country values in one standard
    12. Activity history attached to the right deals and persons

    Pipeline and process (13 to 22)

    1. Every pipeline visible to the right user groups
    2. Stage names and order match the design
    3. Stage probabilities set for the forecast
    4. Required fields per stage enforced and tested
    5. Lost reasons configured
    6. Currency settings correct per pipeline if you sell in more than one currency
    7. Default owner rules in place for new deals
    8. Leads inbox set up, if you use it
    9. Filters set up per role: rep, manager, admin
    10. Saved views shared with the right teams

    Automation and workflows (23 to 32)

    1. Every business-critical HubSpot workflow has a Pipedrive equivalent
    2. Every Pipedrive automation tested with sample deals
    3. Owner assignment fires correctly on new deals
    4. Stage-change automations create the right tasks
    5. Inactive deal alerts fire at the right interval
    6. Follow-up reminders reach the right owner
    7. Make.com scenarios live and monitored
    8. Webhooks configured and verified
    9. Error notifications reach the admin
    10. API and Make.com plan limits checked against your volume

    Integrations and email (33 to 40)

    1. Email sync works for every active rep
    2. Calendar sync works for every active rep
    3. Calling tool (CloudTalk or similar) connected and logging activities
    4. Quote tool connected and writing deal status back
    5. Outbound tool (Apollo, Instantly) syncing replies into Pipedrive
    6. Marketing handoff tested with a sample lead
    7. Enrichment tool connected
    8. Slack or Teams notifications set up for key deal events

    Reporting and adoption (41 to 47)

    1. Manager dashboard built and shared
    2. Rep dashboard built and shared
    3. Forecast report in the format sales leadership expects
    4. Activity report tracks the numbers the team is held to
    5. Training recordings stored in a known place
    6. One-page cheat sheet handed out per role
    7. HubSpot set to read-only and a shutdown date agreed

    Frequently asked questions

    How long does a HubSpot to Pipedrive migration take?

    Common ranges are 4 to 6 weeks for a standard migration with one pipeline and under 50 users, 8 to 10 weeks with several pipelines, 50 to 200 users and connected calling and quote tools, and 10 to 14 weeks for a large scope across regions and languages. These are market ranges, not a fixed timeline of ours. What usually stretches the timeline is not the build but how fast decisions get made on your side.

    Will we lose any data during the migration?

    Nobody can promise that, so we make it checkable instead. Before the export we count every object in HubSpot, and after the import we count again in Pipedrive. Every difference is written down with its reason. What we leave behind on purpose, such as old activity or empty properties, is agreed in writing beforehand. HubSpot stays read-only for 30 days as a fallback.

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

    Yes, and we build it regularly. HubSpot Marketing Hub keeps landing pages, forms and campaigns, and Pipedrive becomes the sales system of record. The handoff runs through the native integration or through Make.com when it needs rules. Decide up front which system owns the contact, when a lead is handed over, and how unsubscribes reach both systems.

    What happens to our HubSpot sequences and snippets?

    They do not come across, you rebuild them. Pipedrive has email templates and sequences for simple follow-up. For outbound at volume with branching, most teams add Instantly or Apollo on top of Pipedrive. That keeps the CRM lean, but it is one more tool someone has to manage, so name an owner for it.

    How do we handle the reporting we built in HubSpot?

    Check which reports the team actually opened in the last 90 days. Most teams keep 5 to 10 and drop the rest. Rebuild those in Pipedrive Insights. For reporting across objects that Insights cannot do, such as funnel health or deal risk, plan Surge Reports, Looker Studio or Power BI from day one.

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

    With under 5 users, no integrations and no history to bring along, you can do it yourself with this checklist. With 10 or more users, connected tools or more than 12 months of data, a partner saves you the problems that only surface after go-live. We are a Pipedrive Platinum Partner with more than 150 CRM implementations, and we use exactly this method.

    What is the cost difference between HubSpot and Pipedrive?

    For 15 users, HubSpot Sales Hub Professional starts at $1,350 per month ($90 per seat, billed annually) plus $1,500 one-off onboarding, with Operations Hub on top if you need advanced automation. Pipedrive Premium costs €885 per month (€59 per user, billed annually) and Ultimate €1,185 (€79, billed annually). Make.com adds a subscription priced by volume. List prices per month billed annually, checked in November 2026 on hubspot.com and pipedrive.com.

    Official partners

    Click a badge to sign up with our partners:

    Sander Vergouwen

    About the author

    Sander Vergouwen

    Co-founder of Sales Surge

    LinkedIn

    Rather have a Pipedrive Platinum Partner run this?

    We migrate B2B teams from HubSpot to Pipedrive in phases, with a count per object before and after and a written list of what stays behind. Book a call to scope it.