HubSpot to Attio, Clarify, Odoo, Pipedrive, Breakcold and Twenty
Contacts, companies, deals, products, tickets and your portal's own objects — with the associations intact.
Migration into Attio is free in Shuttio, at any record count, with a free sample first and a rollback. Attio's built-in Import2 is free too; here is what differs.
- Connect with
- OAuth. Pick the portal, approve the scopes, disconnect whenever you like.
- Price
- Attio: free at any record count. Clarify and Odoo and Pipedrive and Breakcold and Twenty: free under 5,000 records in total: contacts, companies, deals, notes, activities and files together, otherwise priced by record count; the sample is free
- Moves to
- Attio, Clarify, Odoo, Pipedrive, Breakcold and Twenty
- Moves
- 13 things into Attio, listed below
- Doesn’t move
- 5 things into Attio, each with the reason
HubSpot, one destination at a time
Field-by-field mapping, what doesn't move, price and questions for each pair.
Where HubSpot data can go
The destinations a customer can start today, with the price of each.
- Attio
- Free at any record count.
- Clarify
- A CSV import is free. A CRM migration is free under 5,000 records in total: contacts, companies, deals, notes, activities and files together; otherwise it is priced once per migration by record count (up to 50,000 records $249, up to 100,000 records $499, up to 200,000 records $749, up to 500,000 records $999, up to 1,000,000 records $1,499, up to 5,000,000 records $4,749, over 5,000,000 records email help@shuttio.com). The sample is free and you see the price before the full run starts.
- Odoo
- A CSV import is free. A CRM migration is free under 5,000 records in total: contacts, companies, deals, notes, activities and files together; otherwise it is priced once per migration by record count (up to 50,000 records $249, up to 100,000 records $499, up to 200,000 records $749, up to 500,000 records $999, up to 1,000,000 records $1,499, up to 5,000,000 records $4,749, over 5,000,000 records email help@shuttio.com). The sample is free and you see the price before the full run starts.
- Pipedrive
- A CSV import is free. A CRM migration is free under 5,000 records in total: contacts, companies, deals, notes, activities and files together; otherwise it is priced once per migration by record count (up to 50,000 records $249, up to 100,000 records $499, up to 200,000 records $749, up to 500,000 records $999, up to 1,000,000 records $1,499, up to 5,000,000 records $4,749, over 5,000,000 records email help@shuttio.com). The sample is free and you see the price before the full run starts.
- Breakcold
- A CSV import is free. A CRM migration is free under 5,000 records in total: contacts, companies, deals, notes, activities and files together; otherwise it is priced once per migration by record count (up to 50,000 records $249, up to 100,000 records $499, up to 200,000 records $749, up to 500,000 records $999, up to 1,000,000 records $1,499, up to 5,000,000 records $4,749, over 5,000,000 records email help@shuttio.com). The sample is free and you see the price before the full run starts.
- Twenty
- A CSV import is free. A CRM migration is free under 5,000 records in total: contacts, companies, deals, notes, activities and files together; otherwise it is priced once per migration by record count (up to 50,000 records $249, up to 100,000 records $499, up to 200,000 records $749, up to 500,000 records $999, up to 1,000,000 records $1,499, up to 5,000,000 records $4,749, over 5,000,000 records email help@shuttio.com). The sample is free and you see the price before the full run starts.
What lands in each, and what a rollback leaves: Pipedrive, Breakcold, Twenty.
What moves from HubSpot into Attio
Each of these is written against the real API rather than a generic model, which is where the depth comes from.
Contacts, companies and deals
Every property the portal reports, mirrored into Attio with the fields you kept. Contacts land as people.
Products, line items, tickets, quotes and leads
Each lands in an Attio object with a fixed shape, or in the one you already have when its name matches. Products stand alone, line items link to their deal, quote and product, tickets to their companies, contacts and deals, and quotes to their deals and companies. Leads go where you choose: people, deals at the stage Lead, or their own object.
Your portal's own custom objects
Discovered from the portal schema, not from a list we maintain. The property HubSpot enforces uniqueness on becomes the dedup key, so re-running updates rather than duplicates.
Associations, in full
Read through the v4 batch association API with paging. The inline association parameter on a record read silently truncates a contact with hundreds of associations; this does not.
Notes, tasks and meetings
As Attio notes, tasks and meetings. Note bodies re-sync on a later run, and a note you moved in HubSpot moves in Attio.
Calls, as Attio phone calls
Each call lands in Attio's Phone calls on its deal, person or company, with the time, length, direction, outcome and call notes; the numbers and recording link open the notes. A call with no migrated person, or a workspace that has not allowed activities, becomes a note titled "Call: <title>" instead. Phone numbers and recording links are copied as they are, so anyone who can open the call can use the link.
SMS, WhatsApp and LinkedIn messages
Messages logged in HubSpot land in an Attio activity per channel (SMS, WhatsApp message, LinkedIn message) on their records, with the text and direction. Where the workspace has not allowed activities, each becomes a note.
Lists, static and dynamic
Members become Attio list membership. A dynamic list crosses as a snapshot of who was in it at the moment of the run, and its filter conditions ride along as text.
Property history
Optional. Each property's past values arrive as Attio value history, so a stage change from March still reads as March. Requested on the batch read the import already makes.
And 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 Attio
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
A connected CRM imports a sample first (5% of your companies, contacts or deals, 10 to 1,000 records, picked at random, with their linked records), you read the result, then one click runs the rest. A CSV imports in full, free, and rolls back if it is wrong.
Cancel removes what Shuttio created
Every record, note, task, meeting, file, list entry, attribute and select option this migration created is deleted or archived, in reverse order. A record it matched and updated in place stays, and the values it overwrote are not restored. Anything else in your workspace is never touched.
What moves from HubSpot into Clarify
Import2 does not support Clarify or Odoo as a destination. What each HubSpot object becomes depends on what HubSpot holds; every row below is something the Clarify writer does.
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, Pipedrive, SugarCRM and Vtiger. 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.
Files over 50 MB, linked files and file types Clarify refuses
Doesn't moveClarify 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
Doesn't moveClarify'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
Doesn't moveA matched record is updated in place. A rollback removes what Shuttio created and does not restore the values it overwrote.
What moves from HubSpot into Odoo
Import2 does not support Clarify or Odoo as a destination. What each HubSpot object becomes depends on what HubSpot holds; every row below is something the Odoo writer does.
Companies and contacts
Companies and contacts go to Odoo's partners (res.partner), a contact linked to its company in a second pass. A partner is matched by domain or email and updated, not duplicated.
Deals and leads
Deals go to CRM opportunities and leads to CRM leads (when Odoo has leads switched on). Each source pipeline is recreated as a sales team with its stages in the source's order, and won and lost stages are kept.
Products
Into Odoo products (product.template), with the SKU, price and cost where the source has them.
Projects and their tasks
From Pipedrive, into Odoo's Project app (it must be installed). A project keeps its name, customer, manager (matched by email), dates, description and tags, with its stage when your Odoo has project stages and a tag when it does not. A task goes to its project with its stage in that project, deadline and assignee. Time sheets, files and subtasks do not move, and the Odoo app does not carry them yet.
Custom fields
A source column goes to an existing writable x_ field you pick, or to a new x_ field Shuttio creates when your key has the rights. A field Odoo refuses is named in the run summary and never fails the run.
Owners, matched by email
A record's owner becomes the Odoo salesperson with the same email. An owner with no match goes to the fallback user you choose before the run.
Notes, tasks and meetings
Notes become internal notes in the record's chatter. An open task becomes a scheduled To-Do activity; a completed one becomes a Done entry in the chatter. A meeting becomes a Calendar event when the Calendar app is installed, and a chatter note when it is not.
Emails, in the chatter
From HubSpot and Pipedrive, written as email messages in the chatter of the contact, company or opportunity they belonged to, with the sender, subject, date and body. Recipients are named in the body and are never notified. Affinity emails do not move: its API returns no email bodies.
Files, as attachments
Each file becomes an attachment on the same record, when you connect with an API key. The import package and the Odoo app do not carry files.
Three ways to write
Shuttio writes through an Odoo API key, builds an import package you load yourself, or writes through the Shuttio app installed in your Odoo.
Source lists
Doesn't moveThe Odoo writer has no place for a CRM list or saved filter, so none is written. The members stay in the source.
Custom objects
Doesn't moveShuttio writes companies, contacts, deals, leads and products into Odoo, and projects with their tasks into its Project app. Any other object is not written, and its columns can go to x_ fields on those five.
Rollback of an import package
Doesn't moveA package is loaded by you, so Shuttio wrote nothing to your Odoo and cannot remove it. In Odoo, filter by the tag "Migrated <date>" the package puts on its records, select all and delete. Runs through an API key and through the Odoo app roll back with Shuttio.
5 things that don’t move into Attio
Each is a ceiling in an API, not a feature we haven't written yet. You'd find them on day two, so read them now.
A dynamic list's filter itself
Doesn't moveAttio has no filtered-membership API and no list description field, so the rule cannot be recreated. You get the members and the conditions in writing.
History on a property the portal will not report
Doesn't moveSome portals lower or refuse the history batch. The import falls back to current values and tells you in the summary rather than reporting a silent zero.
Emails, unless you tick them
Doesn't moveLogged emails from HubSpot and Pipedrive land in Attio as a Logged emails activity on their records, but they start unticked: Attio's mailbox sync may already show the same mail, and with both ticked it appears twice. Without the Attio connection's activity access, each email is listed as a skipped row rather than written as a note.
Files over 50 MB and linked files
Doesn't moveFiles up to 50 MB are uploaded to the record they were attached to, when the Attio connection has the file scope (an older connection is asked to reconnect). A larger file, and an entry that is a link rather than a file, is listed on the run as a failed row and not copied.
Goals, invoices, payments, carts and other commerce or admin records
Doesn't moveThey track billing and internal targets rather than customer relationships, and Attio has no object shaped for them. Pipelines and stages already arrive as each deal's status.
Moving from somewhere else
Pipedrive
Persons, organizations, deals, products and projects, and the activities you have been tracking as both meetings and tasks.
Affinity
Persons, organizations, opportunities — and the lists and fields that are where Affinity actually keeps your work.
SugarCRM
Accounts and contacts, leads, opportunities with their sales stages, products, cases, projects and custom fields — and the notes, tasks, meetings and calls attached to them.
Vtiger
Organizations, contacts, leads, opportunities with their sales stages, products, tickets, projects and your custom fields — and the comments, tasks, events and calls attached to them.
Twenty
People, companies and opportunities with their stages, the objects and fields you added, and the notes and tasks attached to them, from Twenty Cloud or your own server.
CSV
A spreadsheet from anywhere, including the CRM that has no API worth using.
Attio
An Attio workspace into Clarify: companies, people and deals with their fields, notes, tasks, calls and lists.
Attio
One Attio workspace into another: objects, fields, records, lists, notes, tasks, meetings and files, with every field type kept.
Move 50 HubSpot records first. Then decide.
Nothing is written to your new CRM until you have reviewed the objects and fields, and every CRM migration starts as a free sample: 5% of your companies, contacts or deals, 10 to 1,000 records, picked at random, with their linked records.