The #1 way to move a CRM into Clarify.
HubSpot, Salesforce, Pipedrive, Affinity, Attio or a CSV. We design your Clarify structure, map every field for you to approve, import each record — then hand you a receipt for what landed, what did not, and why.
Sign in with Google · Free until you approve the run · Nothing is written until you do
HubSpot → Clarify
Running3,176 of 3,196Why there is only one
Built against Clarify's API, not adapted to it
Every general-purpose importer treats a destination as a place to put rows. Four things about Clarify make that fail, and each of them is why this exists.
It writes Clarify's schema, not a CSV into it
Custom objects, fields and select options are created through Clarify's own schema routes — which answer before they have finished, so every change is confirmed against the live schema before a single record is written into it.
It knows Clarify's one unique field per object
Companies dedup on domain, people on email, deals on name, because that is the single unique key Clarify allows each of them. An importer that did not know this would create you a second copy of everything on the second run.
It tells you what Clarify will not take
Meetings are read-only in Clarify's schema. Lists do not exist in it. Field history has nowhere to go. Every one of those is on the source pages, before you start, rather than discovered on day two.
It can undo itself
Every record, comment, task, field and object the run created is removed in reverse order from a ledger written as it went. The two things Clarify's API cannot delete are named for you rather than left behind quietly.
Sources
Where you are coming from
Six connectors, each written against that system's real API rather than a generic model. Each page lists what crosses and what does not.
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.
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.
Something else?
Close, Copper and folk are next. Until then, a CSV export covers it — and we will tell you when it does not.
How it works
Four steps, and you approve two of them
A migration is irreversible in most tools. Here every decision is a proposal you edit before anything is written.
Connect your source and Clarify
OAuth for HubSpot, Pipedrive and Salesforce, an API key for Affinity and Attio, or upload a CSV. Revoke us from your own admin whenever you like.
Approve the structure
We read your schema and propose the Clarify objects, fields and select options to create. You edit it. Nothing reaches Clarify until you say so.
Review the field mapping
Every source field, matched to a Clarify field, with value rewrites and defaults. Change anything; the changes stick across re-runs.
Run fifty, then run everything
A sample run of the first 50 records, so you can read the result before committing. One click promotes it to the full migration.
What lands in Clarify
The parts other migrations quietly drop
Associations, custom objects, note bodies, task owners — the things you only discover are missing on day two.
Relationships, resolved properly
Records are created first and linked second, so a deal finds its company no matter which arrived first. A link whose other end never made it is reported, not dropped.
Your custom objects, not a template
HubSpot custom objects, Salesforce __c objects and Attio's own objects are discovered from your schema, with the field your system enforces uniqueness on used as the dedup key.
Notes and tasks, with the right owner
Notes land as Clarify comments on the record they belong to. Tasks keep their priority and go to the person who owned them, matched by email — never to the nearest name.
Cancel that leaves zero trace
Every record, comment, task, field and object we created is removed in reverse order from a provenance ledger. What was there before is never touched.
Re-running never duplicates
People match on email, companies on domain, custom objects on the key you designate. A matched record is updated in place, so a retry resumes instead of piling up.
A reason for every failure
Failures are grouped by cause with the fix spelled out — and you can re-run only the rows you corrected, not the whole migration.
Security
Your records never pass through a model.
Claude proposes the Clarify structure from your schema and up to three truncated sample values per field. The import is a separate path: your records stream from your CRM into Clarify without a model in the loop, at fifty rows or five million.
Read the security pageOAuth, not pasted credentials
Scoped, revocable tokens for HubSpot, Pipedrive and Salesforce.
Encrypted, and not beside the key
Each credential is sealed under its own data key, wrapped by a master key held outside the database.
Jobs carry an id, nothing else
No credentials or records in a queue payload, a log line or a dashboard. Ever.
Your CSV is deleted on finish
We keep the structure, the mapping and the id map. Not your rows.
FAQ
Questions we get before the first run
Why is this the only tool that migrates into Clarify?
Because a migration is not a file transfer. It is a set of decisions about one specific destination: which field each system is allowed to dedup on, which routes answer before they have finished, what the destination silently refuses to store. Import2 and MigrateMyCRM move data between the big CRMs and neither of them lists Clarify at all. This is written against Clarify's API and nothing else.
What does it cost?
It is priced by how many records you are moving, in bands, and you see the figure before the run starts — after the free structure and mapping review, and after the free fifty-record sample. Nothing is charged for a migration you decide not to run.
What happens to my data?
Your records stream from your CRM into Clarify without passing through a model. Credentials are encrypted under a key held outside the database, uploaded CSVs are deleted when the job finishes, and we keep the mapping and the id map rather than your rows.
Can I see what will happen before it happens?
That is the design. You approve the Clarify structure and the field mapping before a single write, and you can run the first fifty records and read the result before promoting it to the full migration.
What if something goes wrong halfway through?
The job is durable and resumable — it picks up where it stopped rather than starting over. Cancelling deletes everything the migration created, in reverse order, and names the things Clarify's API cannot delete so you can clear them yourself.
My CRM isn't on your list.
Export it to CSV and import that — the structure is proposed from your columns, and you can build companies out of a column and link them as the rows import. Close, Copper and folk are next as native connectors.
Start with fifty records and read the receipt.
Nothing is written to Clarify until you have approved the structure and the field mapping.