Pipedrive to Clarify
Persons, organizations, deals, and the activities you have been tracking against them.
What crosses
Everything Pipedrive will give us
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
Notes become Clarify comments. Activities become Clarify tasks, assigned to the Pipedrive user who owned them where that user's email matches a Clarify user.
Phone numbers Clarify will accept
Clarify 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.
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 Clarify
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, 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.
Limits
8 things that do not cross
Each of these is a ceiling in an API rather than a feature we have not written yet. You would find them on day two, so you may as well read them now.
Deduplicating organizations
Not migratedPipedrive's fixed schema has no domain field, and matching companies on name would merge two different customers who happen to share one. Organizations are created, not matched, and the run says so before it starts.
Custom objects
Not migratedPipedrive 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.
A record count before the run starts
Not migratedPipedrive 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
Not migratedClarify 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
Not migratedClarify publishes no endpoint for writing files onto a record, so there is nowhere to put them.
Meetings
Not migratedEvery field that makes a meeting a meeting - title, time, participants, location - is read-only in Clarify's schema. Clarify builds meetings from the calendar you connect, so a copied one would be a shell it would immediately contradict.
Lists and saved views
Not migratedClarify has no list object and no list-membership endpoint. A HubSpot list, an Affinity list or a Pipedrive saved filter has nowhere to land, so the members cross as records and the grouping does not.
Field history
Not migratedClarify stores a field's current value, not its timeline. A stage that changed in March imports as the value it holds today; there is no route that would let us date it.
Other sources
Moving from somewhere else
HubSpot
Contacts, companies, deals and your portal's own objects — with the associations intact.
Affinity
Persons, organizations, opportunities — and the global fields a naive export loses.
Salesforce
Accounts, contacts, leads and opportunities, your __c objects, and both kinds of note.
Attio
Every object in the workspace, read the way Attio actually stores it.
CSV
A spreadsheet from anywhere, including the CRM that has no API worth using.
Connect Pipedrive and read the receipt when it lands.
Nothing is written to Clarify until you have approved the structure and the field mapping.