Summary
- Records and history carry over. Stages, automations and reports have to earn their place. A three-question test, with the arithmetic shown.
In a Pipedrive to HubSpot migration, data should carry over and logic should be rebuilt. Contacts, companies, deals, history and ownership move across; stages, automations and reports stay only if they pass a three-question test, and most of what fails is retired, not recreated.
None of what follows is a measured result. It is a method, with every assumption written down, and each worked example is labelled as illustrative.
What carries over without a redesign?
Anything that records what happened carries over: deal history, activity logs, closed-won and closed-lost outcomes, original create dates and owner. These are facts about the past, and rewriting them destroys the only baseline the new system will ever be compared against.
One selection effect applies. Whatever is carried over is whatever the old system captured, and a team that logged calls inconsistently will import that inconsistency faithfully. A Pipedrive to HubSpot migration does not fix measurement. It preserves it.
How do you decide what to rebuild in a Pipedrive to HubSpot migration?
Run each stage, automation and report through three questions, in order. Stop at the first "no".
- Does a decision or an action depend on it today? Name the person and the day of the week they use it. A report nobody opened in the last quarter fails here.
- Can the trigger be expressed as a field a product engineer could implement? "Rep feels the deal is warm" fails. "Pricing page visited and a meeting booked within 14 days" passes.
- Does it still describe how the team sells now, not how it sold when the account was set up? Series A-B teams change motion fast, and a stage written for a founder-led sale often does not fit a first sales hire.
Here is an illustrative case, an assumption and not a cohort. Suppose a team has 9 stages, 14 automations and 22 reports in the source CRM, 45 objects in total. If 5 stages, 6 automations and 8 reports fail question one, the rebuild is 4 stages, 8 automations and 14 reports: 26 objects. The cut is 19 of 45, or 42%. The exact counts will differ. The mechanism is that the first question removes the most work, and it costs only a conversation.
Buyers we talk to tend to arrive with the opposite instinct: copy everything, to be safe. One customer described roughly 210,000 messy, un-enriched leads built up over ten years. For that database, "carry it all over" would import a decade of noise into a clean pipeline.
Which stages deserve a redesign?
Stage design is where a Pipedrive to HubSpot migration is won or lost. Rebuild stages around buyer evidence, not rep activity. A stage named "proposal sent" records a seller's action; a stage that requires a confirmed budget owner records something the buyer did. Define exit criteria and probabilities fresh, because the old percentages were set against a different sales motion and copying them inherits their error.
Some stalls are a process problem and not a stage problem. One pattern from calls: deals sitting in negotiation because legal redlining runs over email, with nobody able to see progress. Adding a stage will not fix that. Handling the redlines inside the CRM will, and it is worth deciding before cutover which team owns it.
Which automations need a rethink instead of a copy?
Treat every automation in a Pipedrive to HubSpot migration as a requirement written in the old tool's vocabulary. Rebuild the intent, not the mechanics. Three cases come up often in the conversations behind this post:
- Resubmission or re-engagement dates stored as a deal field, which can muddy stage reporting if they are mapped onto a stage-entry timestamp.
- Workflows that create deals from a joint or child contact, which can generate duplicate deals if the association rules are not decided first.
- Required-field rules that SDRs experience as extra admin, which they route around, leaving the data worse than before.
Test each in a sandbox with a sample of real records before cutover. The count that matters is duplicates created per 100 test records, and it should be zero before anything goes live.
How do you keep historical conversion comparable after stages change?
Redesigned stages break the time series, and that is a change in measurement, not a change in buyer behaviour. A conversion rate of 25% before and 31% after, under different stage definitions, says nothing about sales performance.
The workable fix is a crosswalk. Keep the legacy stage name on every migrated deal as a read-only property, then define a small set of milestones (for instance: qualified, evaluated, committed, closed) that both old and new stages map into. Report conversion at the milestone level across the cutover date.
A worked example, again an assumption: 120 deals entered the qualified milestone in the six months before cutover, and 30 reached closed-won. That is 30 / 120 = 25%, with a six-month window and an entry cohort of 120. Compute the same figure for the six months after on the same milestones, report both counts, and say plainly that any difference is observational and not evidence the redesign caused it.
How long does a Pipedrive to HubSpot migration take?
Published claims are short and vendor-curated, so read them accordingly. One testimonial describes a Salesforce-to-HubSpot migration in six weeks, and project-based shops such as DragonflyGTM list 2-6 week projects ending in handover to the client team. Neither figure includes the team's own time. For a lean RevOps function that is the real constraint, because someone has to answer the three questions above for every object, and the time a Pipedrive to HubSpot migration takes depends on how quickly those answers arrive.
For a team that would rather not carry that alone, Checkpoint GTM is a HubSpot Platinum Solutions Partner that runs each Pipedrive to HubSpot migration through mapping, cleanup, QA, cutover and training, and embeds in the client team instead of handing over a deck. For Series A-B buyers who want the redesign decisions made alongside the build, that is the stronger fit. A team that only needs a one-time systems fix and a clean handover may be better served by a short fixed-scope project from a smaller shop.
What is the null result worth reporting?
Sometimes the test says rebuild almost nothing. A team with four clean stages, two live automations and a handful of used reports can finish a Pipedrive to HubSpot migration mostly by mapping. That is a legitimate outcome, and it should be reported as readily as the dramatic cleanup.
The decision rule stays the same either way. Carry over the record of what happened, rebuild what still drives an action, retire the rest, and keep a crosswalk so that last year's numbers can still be read next to this year's.
Sources
- RevPartners homepage (testimonial: Salesforce-to-HubSpot migration in six weeks) — RevPartners, 2026-11-08
- DragonflyGTM homepage (2-6 week project scope, handover to client team) — DragonflyGTM, 2026-11-08