Pipedrive to Attio, free.
Persons, organizations, deals, and the activities you have been tracking as both meetings and tasks.
- Connect with
- OAuth. Company-scoped, so the migration reads only the company you picked.
- Price
- Free, at any record count
- Moves
- 8 things, listed below
- Doesn’t move
- 5 things, each with the reason
What moves from Pipedrive
Each of these is written against the real API rather than a generic model, which is where the depth comes from.
Persons, organizations and deals
Persons land as people, organizations as companies, including every custom field on them.
Notes, and activities split two ways
Pipedrive files meetings and to-dos through one activities endpoint. Meetings become Attio meetings and everything else becomes tasks, and the completion view names which rows went where.
Saved filters as lists
A filter is a saved query, so it crosses as a snapshot of the records matching it at the time of the run, with its conditions written out in plain text alongside.
Phone numbers Attio will accept
Attio requires country codes. Numbers are normalized toward E.164 against the country you pick; anything genuinely ambiguous passes through and fails visibly rather than being guessed at.
And on every migration
Relationships, resolved in a second pass
Records are created first and linked second, so a deal finds its company no matter which order they arrived in. A link whose other end never made it is reported as a skipped row naming what it was waiting for.
Dedup against what is already in Attio
People match on email, companies on domain, custom objects on the unique key you designate. A matched record is updated in place, so running the same migration twice never leaves you two of anything.
A sample run before the real one
Cap the import at the first 50 records, read the result, then promote it to a full run with one click.
Cancel that leaves zero trace
Every record, note, task, meeting, list entry, attribute and select option this migration created is deleted or archived in reverse order. Whatever was in your workspace before is never touched.
5 things that don’t move
Each is a ceiling in an API, not a feature we haven't written yet. You'd find them on day two, so read them now.
Custom objects
Doesn't movePipedrive does not have them. It has custom fields on its fixed entities, and those all migrate. This is a ceiling in Pipedrive, not a gap here.
Field history
Doesn't movePipedrive's changelog is per-record rather than per-field, so there is no bulk read that could reconstruct a field's timeline honestly.
A record count before the run starts
Doesn't movePipedrive charges a full page read for a total, so progress counts up from zero and settles on the true figure once the first pass finishes.
Emails
Doesn't moveAttio asks migration tools not to import them — its own inbox sync covers email far better than a one-time copy would, and it keeps working after the migration.
File attachments
Doesn't moveAttio publishes no endpoint for writing files onto a record, so there is nowhere to put them.
Moving from somewhere else
HubSpot
Contacts, companies, deals and your portal's own objects — with the associations intact.
Affinity
Persons, organizations, opportunities — and the lists and fields that are where Affinity actually keeps your work.
Salesforce
Accounts, contacts, leads and opportunities, your __c objects, and both kinds of note.
CSV
A spreadsheet from anywhere, including the CRM that has no API worth using.
Move 50 Pipedrive records first. Then decide.
Free at any record count. Nothing is written to Attio until you have approved the structure and the field mapping.