HubSpot to Pipedrive Migration: Export, Field Mapping and What Breaks (2026)
By Mikhail Oskola, Founder & AI Automation Architect · · 9 min read
Checked: HubSpot's guide to exporting records, Pipedrive's HubSpot migration guide and its Import2 guide, and the prices on our CRM consulting page on 12 November 2026.
A HubSpot to Pipedrive migration takes seven steps. Build Pipedrive's users, custom fields, pipelines and stages first, export each HubSpot object to its own CSV file, and import organizations and people before deals, leads, activities and notes. Then rebuild your HubSpot workflows as Pipedrive automations and check a sample of records before you cancel HubSpot. A HubSpot record export carries property values and associations, not the activity timeline, so decide early what happens to calls, notes and emails. We checked both vendors' help pages on 12 November 2026. Retailbox Automation, which does CRM migrations, wrote this guide, so it ends with what we charge and when you don't need us.
Should you leave HubSpot for Pipedrive?
Pipedrive describes itself as "a sales-focused CRM designed to help you track leads, deals and contact relationships across your sales pipeline" (https://support.pipedrive.com/en/article/hubspot-to-pipedrive-migration, updated 23 September 2026). The move makes sense when your team uses HubSpot mostly for the pipeline: deals, contacts, tasks and a few sales emails.
It gets harder when HubSpot also runs your marketing or your support. Pipedrive's migration guide maps deals, contacts, companies, pipelines, stages, activities, leads and custom properties. It has no row for tickets, forms or marketing emails, and it notes that Pipedrive doesn't split marketing and non-marketing contacts: "in Pipedrive you need to add a marketing status to your contacts." If those parts of HubSpot are busy, work out where each one goes before you commit.
Still deciding? Our HubSpot vs Pipedrive comparison sets prices and limits side by side, and the 6-question CRM picker gives a first answer.
Decide these before you export anything
The import is the quick part. These decisions take longer, and they're cheaper to make before any data moves:
- Pipelines and stages. Which HubSpot pipelines survive, which merge, and what each Pipedrive stage means. Pipedrive's guide has you add stages that replicate your HubSpot deal stages before the import, so this has to be settled first.
- Custom properties. For each one, keep, merge or drop. The ones you keep become Pipedrive custom fields of the right type (text, dropdown, date). Pipedrive suggests using the same names as in HubSpot so its importer maps them automatically.
- Users and owners. Invite your team to Pipedrive before the import, so every owner on a deal or activity has a user to land on. Pipedrive warns that if an Import2 migration starts before users are invited and pipelines are created, "your data will be owned by the user who initiated the migration" (https://support.pipedrive.com/en/article/importing-data-from-a-previous-crm-using-import2, updated 3 September 2026).
- Leads. Pipedrive "treats leads as pre-deal contacts in the Leads Inbox." Decide whether HubSpot leads arrive as Pipedrive leads or as people, and use one rule for the whole team.
- History. Decide how far back calls, notes and emails need to come, and whether the rest can stay in the export files. HubSpot's record export doesn't carry the activity timeline, so history is a separate job (next section).
- Marketing contacts. Pipedrive has no marketing/non-marketing split, so decide who gets a marketing status and which tool sends your newsletters after the switch.
What HubSpot exports, and what it leaves behind
HubSpot's record export is available on all products and plans, and the user running it needs export permissions. It "downloads their current property values and associations." You can export appointments, calls, contacts, companies, courses, custom objects, deals, listings, marketing events, payments and tickets (https://knowledge.hubspot.com/import-and-export/export-records, updated 12 November 2026).
Two details catch people out. First, "by default, only the properties and associations in the view will be included in the file." Click Customize in the export dialog, or the file holds only the columns your list view shows. Second, associations come as "up to 1,000 associated record ID values per association column and the associated record name." Those IDs, or the email addresses, are what you use to link people to organizations in Pipedrive.
The activity timeline is a separate job. HubSpot's page says that to export contact activities such as calls and notes you can "Export individual contact data", "Export certain activity reports" or "Use the engagements API". The last one needs a developer.
Workflows, sequences and marketing emails aren't on the export list, so they stay in HubSpot. Each one gets rebuilt in Pipedrive or retired. The limits are generous: up to 300 exports in a rolling 24 hours and three at a time. Large exports can take a few hours and may arrive as several files in a zip.
How HubSpot maps to Pipedrive
The names change on the way. The first two columns come from the terminology table in Pipedrive's HubSpot migration guide, read on 12 November 2026. The last column is what we'd check on each one.
| HubSpot | Pipedrive | What to watch |
|---|---|---|
| Company | Organization | Import first, and merge duplicates before you export |
| Contact | Person | Link each person to their organization with a unique field such as email |
| Deal | Deal | Import after people and organizations so each deal has someone to attach to |
| Pipeline and deal stages | Pipeline and stages | Build the stages in Pipedrive before the import |
| Tasks, calls and emails | Activities | Add your missing activity types in Pipedrive first |
| Lead | Lead (Leads Inbox) or person | One rule for the whole team |
| Custom property | Custom field | Same name and the right field type, so the importer maps it |
| Tags | Labels | Pipedrive suggests labels to keep HubSpot tags for filtering |
| Marketing contact | Contact, no distinction | Add a marketing status in Pipedrive |
| Workflows | Automations | Rebuilt by hand; neither vendor's guide moves them |
| Tickets | No row in Pipedrive's guide | Decide where support work lives before the switch |
HubSpot to Pipedrive migration, step by step
This follows Pipedrive's own guide, with a few checks added around it.
The seven steps
- Clean HubSpot. Remove duplicate contacts and companies and drop the properties nobody fills in. Pipedrive recommends reviewing and deduplicating before you migrate.
- Set up Pipedrive: invite users, create custom fields (Company settings > Data fields), build pipelines and stages, and add missing activity types (Company settings > Activities).
- Export each HubSpot object to CSV, one at a time. Click Customize so every property you need is in the file, and keep the record IDs or emails that link records together.
- Test-import 5 to 10 records, as Pipedrive recommends. If the mapping is wrong, revert the import and fix it.
- Run the full import through Tools and apps > Import data in Pipedrive's order: organizations, people, deals, leads, activities, then notes.
- Rebuild your HubSpot workflows as Pipedrive automations, and test each one on a real record before you switch it on.
- Spot-check records with filters, as Pipedrive suggests, and compare a sample field by field against HubSpot, history included. Save the HubSpot export files before you cancel.
Time the switch-off against your HubSpot renewal date, so you don't pay for both CRMs longer than you planned.
What usually breaks
The full list, for any pair of CRMs, is in what breaks in a CRM migration. For HubSpot to Pipedrive, watch these:
- People without their organization. HubSpot exports contacts and companies as separate files. If the linking field is missing or inconsistent, people arrive in Pipedrive with no organization and deals arrive with no one attached.
- History left behind. A contact export doesn't include notes and activities, so a team that skipped the activity export finds the timelines empty on day one.
- Workflows nobody wrote down. A HubSpot workflow that assigned leads or sent a follow-up stops when HubSpot is cancelled. List every active workflow before you start.
- Records owned by the wrong person. Owners who don't have a Pipedrive user yet, or an Import2 run started before users were invited, leave records with the person who ran the import.
- Missing columns. An export taken straight from a list view holds only that view's properties, unless someone clicked Customize.
- Marketing contacts mixed with customers. Without a marketing status set on import, Pipedrive can't tell who opted in to your marketing emails.
Import2, CSV, or both CRMs side by side
Pipedrive offers two routes in. The first is Import2, a third-party partner that connects to HubSpot directly. Open Tools and Apps > Import data > Import from other software, and HubSpot is on the supported list. Only global admins can run it. "Import2 offers a free migration of up to 1,000,000 records and paid migrations for larger databases." It can create pipelines, stages and custom fields for you, lets you customize mappings and filter record types, and you "can undo and redo the migration as needed at no extra cost." Pipedrive suggests allowing 24 hours.
The second is CSV: export each object from HubSpot, then import it with Pipedrive's spreadsheet importer. It's slower, but you see every column before it lands, and each import can be reverted. CSV suits data that needs heavy cleaning on the way; Import2 suits a HubSpot account that's already tidy.
Some teams keep both CRMs running for a few weeks while a pilot group works in Pipedrive. It means two sources of truth, so set a cutoff date after which nobody enters new data in HubSpot.
How long it takes and what it costs
The import itself is the short part; Pipedrive suggests allowing 24 hours for an Import2 run. What takes longer is everything around it: rebuilding workflows, moving history and sorting out marketing contacts.
These are our prices, copied from our CRM consulting page on 12 November 2026. They're ranges, not quotes, and the fixed price is agreed before any work starts, after a free 30-minute call. Pipedrive licenses are a separate line; current prices for both CRMs are in our HubSpot vs Pipedrive comparison.
| Scope (our CRM consulting page) | Typical time | Price (2026) |
|---|---|---|
| CRM setup: one CRM configured from scratch or reconfigured, with the core team trained | 1–2 weeks | $2,000–$5,000 |
| Full implementation + training: complete CRM build or migration with role-based training across the team | 3–8 weeks | $5,000–$25,000 |
| Hourly consulting: selection advice, health checks, a single training session | Billed as used | $50–99/hr |
| Managed support: monitoring, fixes and refresher training | Month-to-month | $299–2,000/mo |
| Doing it yourself with Import2 or CSV | Depends on your data | Your staff's time |
Can you migrate HubSpot to Pipedrive yourself?
Often, yes. With one pipeline, a handful of custom properties, no active workflows and no history you need to keep, Import2 or a careful CSV import is a job someone on your team can do. Follow the steps above and don't skip the check at the end.
Get help when HubSpot also runs your marketing or support, when workflows run your sales process, or when the call and note history matters. Those are the parts that are hard to recover once HubSpot is cancelled.
Going the other way: Pipedrive to HubSpot
Moving into HubSpot uses different tools: HubSpot's Smart Transfer lists Pipedrive as a source. Our Pipedrive to HubSpot migration guide has the object map and steps for that direction.
Who does HubSpot to Pipedrive migrations
Retailbox Automation sets up and migrates CRMs for small and mid-size B2B teams on HubSpot, Pipedrive, Zoho and monday.com. We do the data mapping, cleanup, automation rebuild and team training, and we check a sample of records before the old CRM is switched off.
We're a small team of 2–9 people in Orlando, FL, working since 2019. Of the 258 clients in our project registry with a recorded tool stack, 17 used HubSpot.
What a migration includes, and how we price it, is on our CRM migration page.
Want this built for your team? CRM migration, including HubSpot to Pipedrive — in business since 2019, 470+ jobs on Upwork.
Related services
HubSpot vs Pipedrive
Still deciding whether to switch? Prices, automation limits and contract terms of both CRMs, side by side.
Pipedrive to HubSpot migration
Going the other way? The object map, Smart Transfer and the steps for moving into HubSpot.
what breaks in a CRM migration
The full list of what goes wrong when CRM data moves, whichever system is the source.
Pipedrive vs Zoho CRM
Weighing Pipedrive against Zoho CRM before you move? Prices and limits of both.
Frequently asked questions
Can you import HubSpot data into Pipedrive?+
Yes. Export each HubSpot object (companies, contacts, deals and so on) to CSV and import it through Tools and apps > Import data in Pipedrive, in this order: organizations, people, deals, leads, activities, then notes. Or use Import2, Pipedrive's third-party migration partner, which connects to HubSpot directly and is free up to 1,000,000 records. Only Pipedrive global admins can run Import2.
Does HubSpot email history move to Pipedrive?+
Not with a standard record export. HubSpot's export carries property values and associations, and for activities such as calls and notes HubSpot points you to individual contact data exports, activity reports or its engagements API. Neither vendor's migration guide covers email history, so decide how far back you need it and keep the HubSpot export files, as Pipedrive's guide suggests.
Do HubSpot workflows move to Pipedrive?+
No. Workflows aren't on HubSpot's export list, and Pipedrive's migration guide doesn't move them. List every active HubSpot workflow before you start, rebuild the ones you still need as Pipedrive automations, and test each on a real record before switching it on.
How long does a HubSpot to Pipedrive migration take?+
The import can be quick; Pipedrive suggests allowing 24 hours for an Import2 migration. The project around it takes longer. On our CRM consulting page, a single CRM setup runs 1–2 weeks and a complete CRM build or migration with team training runs 3–8 weeks. Workflows, history and marketing contacts are what push it toward the long end.
Can I run HubSpot and Pipedrive together during the switch?+
Yes, for a short pilot. Let one group work in Pipedrive while the rest stay in HubSpot, then set a cutoff date after which nobody enters new data in HubSpot. Two CRMs updated in parallel for long means two versions of the truth. Time the cutoff against your HubSpot renewal date.