Move your CRM without losing a single note.

What comes across

From	Records	Kept
HubSpot	Contacts, companies, deals, pipelines and stages, notes, tasks, logged emails and calls, owners, custom properties	Original create dates, owners, stage history
Pipedrive	People, organizations, deals, pipelines, activities, notes, files, products, custom fields	Original dates, owners, activity history
Salesforce	Accounts, contacts, leads, opportunities, activities, custom fields	Opportunity history as stage events
CSV / spreadsheets	Any object, up to 500,000 rows and 50 MB per file	Field mapping saved for re-runs

The plan most teams follow

1. Week before: start a trial, connect one mailbox, and run a trial import into the workspace. Check 50 to 100 records by hand against the old CRM.
2. Map: confirm stage mapping per pipeline and which custom fields matter. Leave dead fields behind.
3. Freeze: pick a cut-over time (Friday evening is common) and ask the team to stop editing the old CRM.
4. Final import: re-run the importer. It only brings records changed since the trial import.
5. Monday: everyone connects their mailbox, automations are switched on, and the old CRM stays read-only until your contract ends.

Guided migration

On annual plans with 10 or more seats, an onboarding specialist plans the mapping with your admin, runs the trial and final imports, reconciles record counts and trains the team in two live sessions. There is no fee. Smaller teams get the same importers and chat support.

Timing it with your current contract

Most CRM contracts renew automatically and ask for notice 30 days or more before renewal. Check your order form for the notice date, then work back: a team of 25 typically needs one to two weeks from trial import to cut-over.

Read our longer write-up: Moving off HubSpot or Pipedrive without losing your history.

Start a trial import Plan a guided migration