# Move your Pipedrive CRM data into HubSpot CRM Your custom fields, your history, your relationships. Not only the fields both apps happen to have in common. Migratez runs Pipedrive CRM to HubSpot CRM migrations. The assessment is free and comes before any commitment. Canonical page: https://migratez.com/migrations/pipedrive-to-hubspot-crm-migration ## What lands in HubSpot CRM - Organizations → Companies - People → Contacts - Deals → Deals - Products → Products - Notes → Notes (on the record they belong to) - Call activities → Calls - Meeting activities → Meetings - Your other activities → Tasks (every activity type that is not a call or a meeting, including the ones you added yourself) - Files → HubSpot files, on the record they were attached to - Pipelines and stages → Created in HubSpot as pipelines and their stages - Whether a deal was won or lost → The won or lost stage of its HubSpot pipeline (Pipedrive keeps that on the deal rather than at the end of the funnel, so it travels as its own fact) - Custom fields → Created as custom properties on the object they belong to - Users → Matched to your HubSpot owners by email (and you name who inherits the records of anyone with no match) - Links between records → HubSpot associations ## What comes across Comprehensive by default, customizable on request. - **Relationships, not just records.** The graph survives. Deals stay attached to the right contacts and companies, activities stay on the record they belong to, and the links between them are rebuilt in HubSpot CRM rather than left behind. - **Your custom fields come with you.** They are found in Pipedrive CRM and created in HubSpot CRM before a single record is written. Not flattened into a notes field. - **History, not just the current state.** Notes, calls and meetings arrive on the record they belong to, with their owners and timestamps intact. - **Owners, pipelines and stages are reconciled.** Matched to your HubSpot CRM users and stages rather than reset to a default. - **Nothing is silently rewritten.** Where a conversion is genuinely lossy, the original value comes across alongside the converted one, so you can always see what the data was before we touched it. - **A field with no home is brought along.** If HubSpot CRM has no native place for something you use, we can create one for it rather than drop it. ## What happens to the rest - **How many custom properties HubSpot will hold depends on your plan** (requires_action). The 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. Instead: We count them with you before you commit to anything. Verified against https://knowledge.hubspot.com/properties/create-and-edit-properties ## If it goes wrong - **Undo the records we wrote.** Every write into HubSpot CRM is recorded, so one action takes the records we wrote back out again, in reverse. If it is not what you expected, restore and retry. - **Paused, not lost.** A stop, an error or an API limit pauses the run at its last checkpoint rather than killing it. Nothing is lost and nothing is written twice. - **Read-only in Pipedrive CRM.** Nothing is ever written back into Pipedrive CRM. It is the system you are leaving, and we only read it. - **A last catch-up before you switch over.** After the main load, one action brings across everything that changed in Pipedrive CRM since, so you can verify with both systems live and then switch over. ## What it costs One price, one time, set by how many records you move. - **From $399.** That covers up to 20,000 records. The price steps up with volume and it is for the migration, not a subscription. Nothing recurs. - **The free assessment settles the number.** It reads Pipedrive CRM and reports what is actually in it, so your price comes from your real record count rather than a sales call. You see it before you commit to anything. - **A 30-day money-back guarantee.** 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. ## Questions about moving Pipedrive CRM to HubSpot CRM ### Will my Pipedrive custom fields come across? Yes. The free assessment finds them on your Pipedrive items, and they are created as custom properties on the matching HubSpot object before a single record is written. You see that mapping before anything runs, and you can drop the fields nobody fills in any more rather than carry them over. ### What happens to my activities? 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. ### Do my pipelines and stages survive? 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. ### Do my emails come across? 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 to anything. ### What about the products priced on my deals? 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. ### What about my Leads inbox? 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 to anything. ### Do I have to build a field map? No. The mapping is written for this one direction and shown to you before anything runs, so your part is reviewing it rather than assembling it. A Pipedrive field with no native home in HubSpot can be brought along as a new property instead of being left behind. ### Who actually runs the migration? You create an account and connect Pipedrive, and the free assessment tells you what is in it and what it costs. HubSpot is connected next, so we can check it against what your account can hold. I run the migration itself and stay reachable while it does. Nothing moves until you ask for it. ### Can I keep working in Pipedrive while this happens? Yes. Nothing is ever written back into Pipedrive, we only read it. After the main load, one action brings across everything that changed in Pipedrive since, so you can verify with both systems live and switch over when you are ready. ### What if the result is not what I expected? Every write into HubSpot is recorded, so one action takes the records we wrote back out again. You can sort out what was wrong and run it again. ### What does it cost? One price, one time, based on how many records the migration moves. The free assessment counts them in your Pipedrive and gives you the exact price before you commit to anything. There is no subscription and no card form.