Your custom fields, your history, your relationships. Not only the fields both apps happen to have in common.
Start free assessmentWe run Pipedrive CRM to HubSpot CRM migrations. The assessment is free and comes before any commitment.
Running this for a client? Explore partnership options.
Pipedrive CRM
HubSpot CRM
Keep deals linked to contacts and companies, and activities linked to their records in HubSpot CRM.
We find your custom fields in Pipedrive CRM and plan how their values will travel to HubSpot CRM before migrating their records.
Your activity history arrives on the record it belongs to. This page names which types transfer and any limit on them.
We match them to your HubSpot CRM users and stages.
The plan flags values that change during migration. The original value comes across beside the converted one.
Where possible, we create a field in HubSpot CRM for data with no matching field.
Each row explains a limit and what you can do about it. Open the details for the reason and supporting source.
How many custom properties HubSpot will hold depends on your plan
View detailsHide detailsThe number of custom properties you can create per object depends on your HubSpot subscription. If an item in Pipedrive CRM carries more custom fields than your plan allows, they cannot all land.
Verified against knowledge.hubspot.comWe count them with you before you commit.
Missing required fields can block records
View detailsHide detailsHubSpot rejects records that are missing fields your admin requires. Some fields are required only when another field has a particular value. We report which field is missing so you can correct it.
Verified against developers.hubspot.comWe report missing required fields during the migration. The assessment does not check these rules. Fill in the missing values in your source CRM or ask your HubSpot admin to change the rule, then we retry without duplicating records.
Linking records requires Edit Associations permission
View detailsHide detailsHubSpot calls links between records associations, such as a deal linked to a company. Without Edit Associations permission, HubSpot blocks us from creating those links.
Verified against developers.hubspot.comConnect using a HubSpot user with Edit Associations permission. If you have already connected, ask your admin to grant that user the permission. We can then retry the missing links.
One action removes the records we wrote to HubSpot CRM. Review what will remain before you undo and retry.
A paused run resumes where it stopped, without losing progress or duplicating records.
We only read Pipedrive CRM. Nothing is written back to it.
Keep working in Pipedrive CRM while you check the results. Then bring across the latest changes before switching over.
In HubSpot CRM after the migration
After you undo
Covers up to 20,000 records. Larger migrations use higher tiers. You pay once per migration, with no recurring charge.
Connect Pipedrive CRM to see your record count and price before you commit.
Ask for a refund within 30 days of your migration being marked complete. We reverse the migrated data out of HubSpot CRM and refund you.
Yes. The free assessment finds them on your Pipedrive items, and they are created as custom properties on the matching HubSpot object before records are migrated. Review the plan and choose whether to leave unused fields behind.
A call lands as a HubSpot call, a meeting as a meeting, and everything else on your activity list lands as a task, each one on the record it belongs to and with its owner and its date. Your notes come across as HubSpot notes, and the files on your Pipedrive records come across onto the record they were attached to.
Yes. Your pipelines and their stages are created in HubSpot and your deals land where they sat. Pipedrive keeps won and lost on the deal itself rather than at the end of the funnel, so a deal you marked won lands in the won stage of its HubSpot pipeline rather than wherever it stopped.
No, and the reason is on Pipedrive's side. Pipedrive keeps email in each user's own synced mailbox, private to that user, so there is no company-wide email history to read. Your calls, meetings, tasks and notes come across, and this is on your plan before you commit.
Your product catalogue comes across as HubSpot products. The products attached to each deal do not yet, and that one is our limit rather than HubSpot's, so it is on your plan before you pay rather than a surprise after the run.
It stays in Pipedrive for now. Your deals, people, organizations and their history come across, and a Pipedrive lead has no pipeline and no stage, so landing one as a deal would mean choosing a place in your funnel that nobody chose. It is on your plan before you commit.
No. We work out what each value becomes, so nobody builds a field map. You review the plan before the migration runs. A Pipedrive field with no native home in HubSpot can be brought along as a new property instead of being left behind.
We run the migration and stay reachable. Connect Pipedrive for the free assessment and price, then HubSpot to complete the plan. Nothing moves until you ask.
Yes. We only read Pipedrive and never write back to it. Keep working while you check the results, then bring across the latest changes before switching over.
You can undo the migration, correct the issue and run again. Created fields, shared catalogue data and any other items listed as retained stay in place.
One payment, based on the records that move. The free assessment of Pipedrive gives you the exact count and price before you commit. Payment is by invoice, with no subscription.
Next step
Create an account and connect Pipedrive CRM for your free assessment. See your record count and price before you commit. Nothing moves until you ask.
Start free assessment