Salesforce to Clarify
Accounts, contacts, leads and opportunities, your __c objects, and both kinds of note.
What crosses
Everything Salesforce will give us
Each of these is written against the real API rather than a generic model, which is where the depth comes from.
Accounts, contacts, leads and opportunities
Leads land as people. A lead already converted in Salesforce is not imported twice — it resolves onto the contact it became, so tasks and notes pointing at the lead still find their record.
Custom objects
Any queryable __c object. The field Salesforce marks unique or idLookup becomes the dedup key, and lookup fields resolve to the Clarify object you pointed that lookup's target at.
Both note systems
Classic Notes and enhanced ContentNotes, the latter read with their document links so each note lands on the right record rather than on the user who wrote it.
Tasks, with priority and owner
Salesforce priorities map onto Clarify's, and a task is assigned to its Salesforce owner wherever that owner's email matches a Clarify user. An unrecognised priority is left blank rather than guessed.
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.
Events
Not migratedA Salesforce event is a meeting, and every field that makes a meeting a meeting is read-only in Clarify. Connect the same calendar to Clarify instead and it builds them itself, and keeps building them.
ContentNotes your user cannot see
Not migratedWithout the org permission "Query All Files", Salesforce returns only the notes shared with the connecting user and reports that as the whole set. The connection checks your permission sets and warns before the run; an org that will not report them cannot be checked at all.
Polymorphic lookups
Not migratedA field like WhatId can point at several kinds of record at once. No single Clarify field can hold that, so it is left for the mapping review rather than guessed.
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.
Pipedrive
Persons, organizations, deals, and the activities you have been tracking against them.
Affinity
Persons, organizations, opportunities — and the global fields a naive export loses.
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 Salesforce and read the receipt when it lands.
Nothing is written to Clarify until you have approved the structure and the field mapping.