Migration
HubSpot to Pipedrive migration service
Start with what stays behind. Marketing emails, landing pages, sales sequences, tickets and any custom object have no home in Pipedrive, and no amount of mapping changes that. What does move — companies, contacts, deals, notes and the calls, meetings and tasks logged against them — moves cleanly once each is fitted onto a smaller model: Companies become Organizations, Contacts become People, and every logged engagement becomes an Activity. The work is deciding that map before the export, then rebuilding the automations that survive it in Pipedrive's own event-driven engine.
The mechanics
What does not transfer from HubSpot to Pipedrive?
Marketing emails, landing pages, sales sequences, tickets, custom objects and per-property history. Pipedrive is a sales pipeline with add-ons, not a suite, so those either move to a tool built for them or stay in HubSpot read-only. Companies, contacts, deals, notes, files and logged activities transfer once each is mapped onto Pipedrive's smaller set of record types.
The order of operations is the same in every CRM move — freeze, export, map, load, reconcile, cut over — and it is set out generically on the CRM migration services page. What is specific here is the direction. Going from a large object model into a small one, nothing has to be invented on the destination side; the question is what to do with everything that has no slot, and that question has to be answered artefact by artefact before the export runs, because the import will not raise it for you.
A suite is being left, not just a CRM. A HubSpot portal that has been in use for a few years is rarely only a CRM. It is also the marketing email tool, the form builder, the landing page host, the meeting scheduler, the live chat and, on some subscriptions, the helpdesk. Pipedrive covers the pipeline and, through paid add-ons, a version of email campaigns, web forms and chat. Each of the other functions needs a named destination — a page builder, a helpdesk, an outreach tool, or a deliberate decision to stop doing it — and that list is the first deliverable, before any record is touched.
Associations collapse, and the collapse is a decision. HubSpot lets a contact belong to several companies and a deal carry any number of contacts, each with a label such as decision maker or billing contact. Pipedrive links a person to one organisation, and a deal to one person plus a list of participants. So every contact with two companies needs a primary chosen, and every deal with several contacts needs one nominated as the deal's person and the rest loaded as participants. The labels themselves have nowhere to go except a custom field, and that field has to exist before the load.
Lifecycle stage has no counterpart. HubSpot separates who somebody is from where they are in the funnel: a contact record carries a lifecycle stage and a lead status alongside it. Pipedrive expresses the early funnel differently — a lead in the Leads Inbox is a separate record until it converts, and after that a person is just a person, distinguished by labels and fields. Which HubSpot lifecycle stages become leads in the inbox, which become people with a label, and which are archived rather than imported at all, is written down before export and applied consistently.
Matching, and the ID that turns reconciliation into arithmetic. HubSpot deduplicates contacts on email address and companies on domain, so a HubSpot export is already fairly clean. Pipedrive does not enforce uniqueness on either, which means a load run twice, or a delta load that overlaps the first, creates a second copy of everyone without complaint. The defence is a custom field on every Pipedrive record holding the HubSpot record ID, populated from the export HubSpot produces through its own record export (opens in new window). Counts then reconcile by joining on a key rather than by eye, and any integration you keep has something stable to point at afterwards.
| HubSpot artefact | How HubSpot models it | Where it lands in Pipedrive | The decision it forces |
|---|---|---|---|
| Companies | A company object deduplicated on domain, associated to any number of contacts and deals | Organizations | How near-duplicate names are kept from doubling, since Pipedrive will not deduplicate on domain for you |
| Contacts | Unique on email, able to belong to several companies with a labelled association to each | People, each linked to one organisation | Which company is primary for each contact, and where the other associations are recorded |
| Contacts with no deal yet | A contact carrying a lifecycle stage and a lead status | A lead in the Leads Inbox, or a person with a label | Which lifecycle stages become inbox leads, which become labelled people, and which are archived instead of imported |
| Deals | Pipelines and stages with a probability each, stage requirements, and several associated contacts | Deals, in pipelines and stages with a probability each and required fields per stage | Which associated contact becomes the deal's person, and which become participants |
| Calls, meetings and tasks | Separate engagement types, each with its own properties such as call outcome and meeting outcome | Activities, typed as call, meeting, task, deadline, email or lunch, plus any custom type | Whether outcomes and dispositions become a custom activity field or are let go |
| Notes and attachments | Engagements attached to the record timeline | Notes and Files on the matching person, organisation or deal | How far back to load, since every year of history rarely earns its place in the new account |
| Logged and tracked emails | Email engagements captured by the tracking extension or BCC address | Pipedrive's own mail sync, connected fresh at cutover | Whether historical threads are attached as notes, losing threading, or left in the mailbox that already holds them |
| Tickets | A service object with its own pipelines and SLAs | No equivalent | A separate Pipedrive pipeline for light support, or a helpdesk built for it |
| Custom objects | Purpose-built records — properties, vehicles, matters, installations — associated to the standard objects | No equivalent | A pipeline, a set of custom fields on the deal or organisation, or a system outside the CRM linked by ID |
| Custom properties | Text, number, date, dropdown, multi-checkbox, calculation, score and rich-text properties | Custom fields: text, numeric, monetary, single and multiple option, date, address, user and more | Which calculation and score properties are loaded as static values, since their formulas do not travel |
| Workflows | Enrolment-based, with branches, delays, goals and re-enrolment settings | Automations: an event trigger, conditions, and a short list of actions | Which workflows rebuild directly, which are simplified, and which are retired on purpose |
| Sequences | Timed one-to-one email and task steps from a rep's mailbox, stopped automatically on reply | Automations with email steps, or a dedicated outreach tool | How a reply stops the sequence, which HubSpot handled without being asked |
| Marketing emails, forms and landing pages | Built and hosted inside the portal, with send statistics attached | Campaigns and Web Forms add-ons for the first two; nothing for landing pages | Which templates are worth recreating by hand, and where the landing pages live next |
| Lists, reports and dashboards | Active and static lists feeding custom reports | Filters and Insights, rebuilt against the new field names | Which reports anyone actually opens, and which measure change over time rather than current state |
| Subscription types | Consent held per subscription type plus a marketable-contact designation | One marketing status per person: subscribed, unsubscribed, archived or no consent | How several HubSpot consent states collapse into one Pipedrive state without anyone unsubscribed becoming subscribed |
Consent is not one more column in the person import. HubSpot's subscription types and Pipedrive's marketing status describe the same obligation with different vocabulary, and the collapse from many states to one is where an opt-out gets lost. Export every subscription state, write down the mapping, load the result as Pipedrive marketing status, and reconcile the counts against the obligations set out in the FTC's CAN-SPAM compliance guide (opens in new window) before any sending is enabled. Nothing goes out until those numbers agree.
Sequence
What changes in the plan when the destination is Pipedrive?
The order is unchanged: freeze, export, map, load, reconcile, cut over. What changes is where the judgement goes. Coming into Pipedrive, it is spent on collapsing many-to-many associations into one organisation per person and one primary person per deal, and on deciding which HubSpot workflows deserve a rebuild as Pipedrive Automations rather than a quiet retirement.
Inventory associations, not just records
Export the association tables alongside the objects. Every contact with two companies and every deal with three contacts is a decision that has to be made before the load, and none of them are visible in a list of records.
Name what leaves the CRM entirely
Tickets, custom objects, landing pages and marketing sends each get a named destination, and for most of them that destination is not Pipedrive. Deciding this first stops the migration silently becoming a search for a second tool mid-project.
Sample load, then reconcile on the HubSpot ID
A few hundred records first, joined back on the stored HubSpot ID. Pipedrive will not stop a duplicate person or organisation from being created, so this is where doubles appear — while they are still cheap to undo.
Automations rebuild on events, not enrolment
There is no converter between the two engines, and each workflow is read and rebuilt by hand. The structural difference is the trigger. A HubSpot workflow evaluates enrolment criteria against a record, walks it through branches and delays, and remembers that it has been through. A Pipedrive Automation fires when something happens — a deal changes stage, a person is created, a field is updated — checks a condition, and runs a handful of actions. Rules that should fire every time an event occurs are actually easier in Pipedrive than they were in HubSpot, where re-enrolment had to be switched on deliberately. Long nurture workflows with goal criteria and many branches are the opposite: they either simplify into two or three Automations, or they were marketing rather than sales logic and belong in whatever now handles marketing. Sequences are a separate question, because Pipedrive does not stop an email step when the prospect replies, and a rebuild that ignores that will email people who have already answered.
Stage design is the part worth redoing rather than copying
HubSpot deal stages carry a probability and can require properties before a deal advances, and both map neatly onto Pipedrive's stage probability and required-fields-per-stage setting. That makes it tempting to copy the pipeline as it stands. It is usually better to treat the move as the moment to re-derive stages from buyer commitment, write an exit criterion for each, and map the old stage onto the new one in the import file so history still lands somewhere sensible. The one thing to know before doing so is that time-in-stage history does not come across either way — Pipedrive computes stage durations from changes it witnessed — so the HubSpot stage reports worth keeping are exported and archived before cutover.
Email history, and what belongs to the mailbox rather than the CRM
HubSpot's tracked and logged emails feel like CRM data because they sit on the timeline, but the mailbox holds the messages and the CRM holds a reference. Pipedrive's mail sync connects to the same mailbox and starts logging from that point, with historical threads staying where they have always been. Threads that genuinely need to be on the record — an agreed scope, a pricing exception — can be attached as notes, at the cost of threading. Teams expect this to be a loss and it usually is not, but it needs saying before cutover rather than discovering it in the first week.
Cutover, reconciliation and disposing of the export
Cutover runs one pipeline at a time. Record counts are compared in both directions on the stored HubSpot ID, consent counts are compared separately, and a delta load picks up whatever was created during the freeze window. The HubSpot portal stays live and read-only for a lookback period, because per-property history and marketing statistics do not migrate and are still worth being able to open — and because every form, meeting link, chat widget and tracking script still pointing at it has to be found and replaced before it can be switched off. One step is easy to skip: the export is a complete copy of your customer database sitting in a folder, on a laptop, and probably in a shared drive as well. Destroying those working files at the end of the project — deliberately, everywhere they were copied, along the lines of NIST's media sanitization guidelines (opens in new window) — is part of the work, not an afterthought.
Where this sits next to the rest of the work
Going the other way — a team that has outgrown Pipedrive and is moving into HubSpot — is the mirror image of this page: instead of deciding what has no slot, the work is untangling what the deal fields and spare pipelines were standing in for, and our Pipedrive to HubSpot migration page covers that crossing on its own terms. Arriving at the same destination from an enterprise org is a heavier version of this page, because record types, validation rules and Apex have to be re-homed rather than merely collapsed, and our Salesforce to Pipedrive migration page maps that crossing separately. If you are leaving HubSpot but want the marketing suite, the funnels and the texting to come with you rather than be re-homed, the destination is probably not Pipedrive, and our HubSpot to GoHighLevel migration page is the better read. If the team already runs delivery on monday boards and wants the pipeline on the same surface, the mapping problem reverses — every object gets a board, and the work is designing them — which our HubSpot to monday CRM migration page covers. Once you have landed, making the pipeline work — stage design, Automations, field hygiene, API work — is the subject of our Pipedrive automation consulting page. If you are still choosing between them, our Pipedrive vs HubSpot for small business comparison sets out when each fits. And if the honest answer on the call is that HubSpot still fits and the real problem is how it has been configured, our HubSpot automation consulting page describes that work instead, while how engagements work explains how a scope gets agreed before any of it starts.
The honest part
Why move from HubSpot to Pipedrive at all?
Usually because the team is a sales team and has been paying for a marketing and service suite it does not use. Pipedrive does one thing, the pipeline, with less configuration and fewer places for data to hide. The trade is real: you give up the suite. Whether that trade suits you is what the first call is for.
| What | Treatment | Why |
|---|---|---|
| Company, contact and deal field values | Moves | They load cleanly once every destination field and every option value exists on the Pipedrive side first |
| Open deals and stage position | Moves | Stage, value, expected close date and owner land on a deal once the pipelines and users have been created |
| Notes, files and logged activities | Moves deliberately | They attach to the matching record, which is worth doing for open business and rarely worth doing for all history |
| Products and deal line items | Moves | The product catalogue rebuilds first, then products attach to deals — in that order, or the lines have nothing to reference |
| Lifecycle stage and lead status | Rebuilt as leads, labels and fields | Pipedrive has no lifecycle concept, so the funnel position is expressed through the Leads Inbox and labels instead |
| Associations and their labels | Collapsed and recorded | One organisation per person and one primary person per deal; the rest become participants or a field |
| Workflows | Rebuilt | A different execution model: an event firing every time instead of enrolment with memory, so each rule is re-expressed and re-tested |
| Sequences | Rebuilt or relocated | Simple cadences become Automations with email steps; anything that depends on stopping on reply moves to an outreach tool |
| Tickets and custom objects | Re-homed | Pipedrive has no slot for either, so each becomes a pipeline, a field set, or a record in a system built for it |
| Per-property history and time in stage | Stays behind | HubSpot keeps a change trail per property; Pipedrive keeps the current value and its own history from cutover onward |
| Marketing email content and send statistics | Stays behind | Send-level analytics belong to the system that did the sending, and templates are recreated rather than imported |
| Logged email threads | Re-established, not migrated | The mailbox owns the messages; both CRMs only hold a reference, so Pipedrive connects and starts logging from cutover |
| Forms, landing pages, meeting links, tracking code | Replaced | Anything still calling HubSpot keeps creating records there after cutover, and nobody notices for weeks |
You own the result outright: records in your own Pipedrive account, Automations documented against the event that starts them, a field map showing where every HubSpot property went, a written note of where each function that left the CRM now lives, and an equally written note of what was left behind on purpose. If your own team would rather run the load, we will build the field map and the scaffold and stay on as backup — and if the honest answer on the call is that HubSpot still suits you better than Pipedrive would, that is what you will hear.
Questions
What HubSpot teams ask before committing
What happens to HubSpot custom objects in Pipedrive?
Pipedrive has no custom objects, so each one needs a decision before export. A custom object that was really a process — onboarding, renewals, installations — becomes a Pipedrive pipeline with its own stages. One that was reference data becomes a set of custom fields on the deal or organisation. One that fits neither shape stays in a system built to hold it, linked from Pipedrive by ID.
Do HubSpot workflows convert into Pipedrive Automations?
No, and the execution model differs. A HubSpot workflow enrols a record once and remembers it. A Pipedrive Automation fires on an event, every time the event occurs, with a condition check and a short list of actions. Multi-branch nurture workflows do not fit that shape and are simplified or retired; stage-change, task-creation and field-update rules rebuild directly.
What happens to a contact associated with several companies?
Pipedrive links a person to one organisation, so one is chosen as primary before the import and the others are recorded in a field or a note. On deals the fit is better: HubSpot's additional deal contacts become deal participants in Pipedrive, and the primary contact becomes the deal's linked person. Association labels have no counterpart and are written into a field.
Can HubSpot sequences and marketing emails move to Pipedrive?
Not as they are. Sequences are rebuilt as Pipedrive Automations with email steps where the logic is simple, or move to a dedicated outreach tool where it is not. Marketing emails need the Campaigns add-on, and templates are recreated by hand. Landing pages have no equivalent in Pipedrive and stay on your website or a page builder.
How does marketing consent carry from HubSpot to Pipedrive?
As its own reconciliation, finished before any sending is switched on. HubSpot holds consent per subscription type plus a marketable-contact designation. Pipedrive holds one marketing status per person: subscribed, unsubscribed, archived or no consent. Several HubSpot states collapse into one Pipedrive state, so the collapse is written down, the counts are compared, and anyone unsubscribed anywhere lands as unsubscribed.
Free consultation
Tell us what is costing you the most time
Describe the process. You get a straight read on whether it is worth automating, roughly what it would take, and what we would tackle first — on a call that costs nothing.
- Under an hour, free, and no obligation
- Fixed price per stage, agreed before any work starts
- You own everything we build, documented and in your accounts
- If you do not need us, we will say so on that call
The form is the fastest way to reach us — we reply from a real person, usually within one business day.
Not sure which migration is right? See the CRM migration services overview.