A CRM migration is a data project. That line has shown up in so many kickoff decks it deserves its own property in HubSpot. So why does the first report after a Pipedrive to HubSpot move so often start an argument?
Most of the move is documented. HubSpot Smart Transfer maps Pipedrive people to contacts, organizations to companies and deals to deals, plus notes, products, users and activities. The drag sits in the gaps between the two vendors’ documents: data that comes across only once, close dates HubSpot has to rebuild, and the fields HubSpot uses to decide two records are the same company. Clean those match fields in Pipedrive, pick a cutover date, and confirm the mappings before a single record syncs.
What follows is a playbook in the order things go wrong, from the first sync to the first pipeline review.
What transfers from Pipedrive to HubSpot?
Per HubSpot’s Supported apps for HubSpot Smart Transfer page, last updated October 2, 2026, Smart Transfer maps Pipedrive people to contacts, organizations to companies and deals to deals, along with notes, products, currencies, users and activities. Syncing Pipedrive activities requires a Data Hub subscription, and HubSpot says Smart Transfer will sync email activities from Pipedrive, but not logged emails.
| Pipedrive | HubSpot | How it moves |
|---|---|---|
| People, organizations, deals | Contacts, companies, deals | Ongoing sync |
| Notes, products, currencies, users | Notes, products, currencies, users | Ongoing sync |
| Email, meeting, call, task and custom activities | Email activities, meetings, calls, tasks | Ongoing sync, needs Data Hub. Logged emails are not synced |
| Attachments, deal participants, products on deals, organization relationships | Attachments, contact associations, deal line items, labeled associations | One-time transfer after the first sync |
| Leads | Not listed in HubSpot’s Pipedrive mapping table | Plan separately. A HubSpot import is another way in |
Source: HubSpot Knowledge Base, Supported apps for HubSpot Smart Transfer, last updated October 2, 2026. Check it against your own HubSpot subscription before you plan around it.
Two rows in that table deserve a second look. If your team works a busy Leads Inbox, those records need their own plan. And since logged emails are not synced, check which kind of email history your team relies on before you count on it arriving.
Choose the route before you choose the date
You have two ways in: Smart Transfer, or a Pipedrive export followed by a HubSpot import. Per HubSpot’s Smart Transfer guide (October 2, 2026), only Super Admins can access Smart Transfer, the transfer runs one way into HubSpot, and custom field mappings need a Data Hub subscription. The sync can take several hours depending on the volume of data, then keeps running in the background to keep transferred records up to date.
The export route avoids the subscription question and hands you a trap that is easy to miss. Pipedrive’s export documentation (September 3, 2026) says you can only export the data visible to you based on your visibility group or item visibility. Activities, notes and files linked to deals and contacts come out separately, and files stored in Google Drive are not exported during global export.
Say a sales manager runs the export from their own login. The file opens, the columns look right, and it holds exactly what that manager can see. Nothing in the file tells you what is missing. Run the export as a global admin.
The export route also leaves no second try on activities. Per HubSpot’s import guide (October 7, 2026), existing emails, meetings, notes and tasks cannot be updated via import. Get that file right before it goes in.
If you go with Smart Transfer, turn off the Automatically sync toggle first. HubSpot recommends it when you need filters or want to confirm mappings before syncing, to prevent unwanted records from being transferred. Confirming mappings on an empty portal is a lot calmer than confirming them on a full one. For the general limits of the tool, see HubSpot Smart Transfer limitations.
Why do duplicates show up first after the move?
Duplicates show up on day one, because HubSpot needs something to match on. Per HubSpot’s import guide (October 7, 2026), HubSpot matches imported rows to existing records on Record ID for any object, Email for contacts and Company domain name for companies. Record ID supersedes the others, and a row without a Record ID value creates a new record.
Read that from the Pipedrive side. An organization with no website domain gives HubSpot nothing to match a company on. A person with no email gives it nothing to match a contact on. And a duplicate pair sitting in Pipedrive today arrives in HubSpot as a duplicate pair, now a cleanup job in a system your team is still learning.
Merge in Pipedrive while you still know the data. Pipedrive’s Merge Duplicates tool, under Tools and apps, lists possible duplicate people and organizations. Per Pipedrive’s documentation (September 3, 2026), merging is available to admin users or regular users with the right permission, and the primary item’s information wins where the two records conflict. Pick the primary on purpose. If duplicates get through anyway, why HubSpot duplicates keep coming back covers how to keep them out.
Why do close dates look wrong after the move?
Close dates break at the first closed-won report. Pipedrive keeps several dates where HubSpot keeps one Close date, so per HubSpot’s Smart Transfer guide and supported apps page (both October 2, 2026), Smart Transfer creates a close date backfill workflow that reads Pipedrive’s Won time, Lost time and Expected close date, plus a create date backfill from Creation time.
HubSpot names the three fields. It does not say which one wins when a deal has more than one filled in. Don’t guess. Pull a handful of won, lost and open deals after the sync and compare each HubSpot Close date with the Pipedrive record it came from, before anyone builds a forecast on top of it. If the numbers still disagree after that, why HubSpot reports don’t match covers the usual causes.
Then the one-time data starts to drift
Four kinds of Pipedrive data move once and stop. HubSpot’s supported apps page (October 2, 2026) lists attachments, deal participants as contact associations, products on deals as deal line items and organization relationships as labeled associations as a one-time transfer after the first sync, and says that data will not automatically stay up to date.
Say a rep adds a second buyer to a deal in Pipedrive the morning after the one-time transfer runs. The deal keeps syncing. The buyer stays out of HubSpot, and the gap surfaces the day someone builds a buying committee report.
That makes the cutover date the decision that matters most, more than the migration date. Tell reps the day Pipedrive stops being the place they work. Run the one-time transfer after that. Anything added in Pipedrive later is a manual job, and someone should own it.
Which Pipedrive reporting limits push teams to HubSpot?
Check this one before you start, because the move might not be the answer. Per Pipedrive’s Insights: reports, goals and dashboards and Insights: dashboards articles (September 3, 2026), only Premium and higher plans can use custom fields for filtering and building reports in the visual builder, and only Premium and higher plans can create additional dashboards. A dashboard holds a maximum of 25 reports, and the number of reports you can create depends on your plan’s usage limits.
All Pipedrive users can use custom fields in the table view, so the limit sits on the visual builder, not on the data. If the report your team wants needs a custom field in the visual builder and you sit below Premium, the plan is part of the answer. If you need reporting Pipedrive’s Insights does not offer on any plan, that is a better reason to move.
A CRM migration is a lot of work to discover it was the plan.
What Smart Transfer’s clean-up and revert leave behind
Smart Transfer ships two tools for after the sync, and both work on what the transfer created, not on your records. Per HubSpot’s clean-up guide (November 26, 2025), a scan marks QA properties, empty properties and text properties for enumeration workflows that Smart Transfer created, grouped under a Migration Clean up property group. Per the revert guide (November 26, 2025), Revert removes settings the transfer created and deletes newly created synced records, but only rolls back changes made by Smart Transfer.
The duplicate companies, the people with no email and the organizations with no domain are still there after both run. That work stays with you, which is the case for doing it in Pipedrive first.
The clean-before-you-move checklist
Clean the fields HubSpot matches on and decide what the sync leaves behind. This list is short on purpose. Work through it before the first sync:
- Run Merge Duplicates on people and organizations, and pick each primary record on purpose.
- Filter organizations with no website domain and fill in the ones you plan to keep.
- Filter people with no email and decide whether they move at all.
- List the custom fields your team leaves empty and retire them, since each one is another property to map. How to find unused fields walks through the audit.
- Decide where Leads Inbox records go, since HubSpot’s Pipedrive mapping table does not list them.
- Write down the cutover date and tell the reps.
One thing to do this week: pull the two filtered lists, organizations with no domain and people with no email. Those lists are the part of your Pipedrive data HubSpot will have nothing to match on, and their length tells you how much cleanup sits ahead of you before you sign anything.
Move it as it is, or clean it first
You can move the data as it sits in Pipedrive and clean it in HubSpot, alongside everything else a new CRM asks of your team that quarter. Or you can clean the match fields and merge the duplicates in Pipedrive first, and move less. The first gets you live sooner. The second means the first HubSpot pipeline review is about the pipeline.
If you want a read on duplicate records and missing contact data before you choose, the free CRM Diagnostic works with HubSpot, Salesforce and Pipedrive and runs 40+ automated checks across data quality, pipeline hygiene, freshness, reachability and ICP fit. For the cost side of a CRM move, see what a Salesforce to HubSpot migration costs.