Into Clarify

Sources that can move into Clarify: Spreadsheet / CSV, HubSpot, Pipedrive, Affinity, Twenty, Attio. A CSV import is free. A CRM migration is priced once per migration by record count (up to 50,000 records, up to 100,000 records, up to 200,000 records, up to 500,000 records, up to 1,000,000 records, up to 5,000,000 records, over 5,000,000 records); the sample is free. See pricing.

Object by object: What objects are supported for Clarify migrations.

What Shuttio writes

• Companies, people and deals: Into Clarify's company, person and deal objects, upserted on the unique field Clarify gives each, so a re-run updates instead of duplicating. Deal pipelines arrive as one stage field or as separate fields, whichever you choose.
• Custom objects and fields: An object you tick that Clarify does not have is created as a custom object with its fields, and missing fields are added to the objects it does have. Each one is entered in the ledger, so a rollback removes it.
• Notes: As comments on the record they belonged to: the deal if it has one, else the person, else the company.
• Tasks, with owners matched by email: As Clarify tasks linked to the deal, person or company. The owner is matched to a Clarify user by email; a task whose owner has no match is left unassigned, never given to someone else.
• Meetings and calls, as comments: Clarify builds meetings from the calendar you connect to it and does not accept written ones. A source meeting or call lands as a comment on its record saying what it was, when, and who was there.
• Emails, as comments: From HubSpot and Pipedrive. Clarify's own email list is filled by the mailbox you connect to it and does not accept written ones, so a logged email lands as a comment on its record: subject, date, direction, sender and recipients, then the body as plain text. Affinity emails do not move: its API returns no email bodies.
• Lists, as fields on the records: Clarify's API cannot add a record to a list. Membership becomes a multi-select field on each record, named after the source (for example "HubSpot lists"), and a list's own fields become one field per list and field.
• Files, as attachments: With the Attachments switch on, each file up to 50 MB is downloaded from the source and attached to the person, company or deal it belonged to. A file whose record did not migrate is not moved. Files Clarify itself pulled from emails are not touched, and a rollback removes only the files Shuttio added.

Where each thing lands

What the connection needs

Clarify has no scopes to choose. The run writes records, custom objects and fields, comments, tasks and attachments, so connect with a key that can do the same in your workspace. If Clarify answers 403 before it checks the key, the cause is on the network edge, not your key. Try again in a few minutes, and email help@shuttio.com if it keeps happening.

Known limits

• Files over 50 MB, linked files and file types Clarify refuses: Clarify checks the type of a file when it attaches it and refuses some (a zip archive, for one). Such a file, a file over 50 MB and an entry that is only a link are listed as failed rows and not copied.
• Fields created for lists, left after a rollback: Clarify's API has no way to delete a field. A rollback removes the records, notes, tasks, files and custom objects Shuttio created, and names the list fields it leaves for you to clear.
• Values on a record Clarify already had: A matched record is updated in place. A rollback removes what Shuttio created and does not restore the values it overwrote.
• Owners: Shuttio matches a task's owner to a Clarify user by email, for HubSpot and Pipedrive. A task from any other source arrives unassigned.
• Fields Shuttio adds to your existing objects stay after a rollback, because Clarify's API cannot delete a field. The rollback names them.
• Retry runs the failed items again and is free. Records already in Clarify are matched and updated.