# Clarify Migrate

> The only migration tool built for Clarify. It moves a HubSpot, Salesforce, Pipedrive, Affinity or Attio database — or a CSV — into Clarify: designing the Clarify structure, mapping every field for the customer to approve, importing each record, and producing a per-record receipt of what landed and what did not.

It is not a general CRM importer pointed at Clarify. Every decision in it is a fact about Clarify's own API: that each object allows exactly one unique field (companies on domain, people on email, deals on name), that the schema routes answer before they have finished applying and must be confirmed against the live schema, that meetings are read-only because Clarify builds them from the connected calendar, and that there is no list object to write a list into. General-purpose migration services — Import2, MigrateMyCRM and the rest — do not list Clarify as a destination at all.

What every migration does: proposes the Clarify structure from the source schema for the customer to edit, shows the full field mapping before any write, runs the first fifty records as a sample, then imports everything with a durable resumable job. Cancelling deletes every record, comment, task, field and object the run created, in reverse order, from a ledger written as it went.

What no migration does, because Clarify cannot store it: meetings, lists and saved views, per-field history, email bodies, file attachments.

Pricing: the structure review, the field mapping and the fifty-record sample are free. The full run is priced in bands by record count, quoted before it starts.

## Sources

- [HubSpot to Clarify](https://clarify-migrate.vercel.app/migrate/hubspot-to-clarify): Contacts, companies, deals and your portal's own objects — with the associations intact.
- [Pipedrive to Clarify](https://clarify-migrate.vercel.app/migrate/pipedrive-to-clarify): Persons, organizations, deals, and the activities you have been tracking against them.
- [Affinity to Clarify](https://clarify-migrate.vercel.app/migrate/affinity-to-clarify): Persons, organizations, opportunities — and the global fields a naive export loses.
- [Salesforce to Clarify](https://clarify-migrate.vercel.app/migrate/salesforce-to-clarify): Accounts, contacts, leads and opportunities, your __c objects, and both kinds of note.
- [Attio to Clarify](https://clarify-migrate.vercel.app/migrate/attio-to-clarify): Every object in the workspace, read the way Attio actually stores it.
- [CSV to Clarify](https://clarify-migrate.vercel.app/migrate/csv-to-clarify): A spreadsheet from anywhere, including the CRM that has no API worth using.

## Product

- [How it works](https://clarify-migrate.vercel.app/#how): The four steps, two of which the customer approves before anything is written.
- [Why there is only one](https://clarify-migrate.vercel.app/#why): The four properties of Clarify's API that a general-purpose importer gets wrong.
- [What lands in Clarify](https://clarify-migrate.vercel.app/#features): Relationships, custom objects, notes as comments, tasks with their owner and priority.
- [FAQ](https://clarify-migrate.vercel.app/#faq): Cost, data handling, what happens on a failure mid-run.

## Security

- [Security](https://clarify-migrate.vercel.app/security): What is encrypted and under which key, what a model sees (the schema and up to three truncated sample values per field, never the records), what is deleted on completion, and every subprocessor.

## Start

- [Start a migration](https://clarify-migrate.vercel.app/): Sign in with Google. Nothing is written to Clarify until the structure and the mapping are approved.