HubSpot to Attio migration
Shuttio moves contacts, companies, deals, products, line items, tickets, quotes and leads from HubSpot into Attio, with notes, tasks, meetings, calls, emails, files and lists. Migration into Attio with Shuttio is free at any record count. It starts with a free sample of every object you tick (5% of your companies, contacts or deals, 10 to 1,000 records, picked at random, with their linked records), so you read the result in Attio before the full run, and a rollback removes what it created.
- Can I move HubSpot to Attio?
- Yes.
- What moves:
- Contacts, companies, deals, products, line items, tickets, quotes and leads, with notes, tasks, meetings, calls, emails, files and lists.
- What doesn't:
- A dynamic list's filter itself; History on a property the portal will not report; Emails, unless you tick them; and 2 more, each with its reason.
- Price:
- Free at any record count, the sample and the full run.
- How long:
- A full migration takes 24–72 hours, depending on your record count and on HubSpot's API request limits. The free sample runs first, and the full run is one background job with live progress.
No Attio account yet? Sign up with our partner link and get 10% off any plan.
- Moves
- 8 kinds of record, plus notes, tasks, meetings, calls, emails, files and lists
- Doesn’t move
- 5 things, each with the reason
- Connect
- HubSpot: OAuth. Attio: OAuth
- Price
- Free at any record count
Where each HubSpot object lands
Read from the code that runs the migration. Source column names are shown as the source reports them.
| HubSpot object | Lands in | Standard fields |
|---|---|---|
| Contacts | People |
|
| Companies | Companies |
|
| Deals | Deals |
|
| Products | Its own object, or the one you already have with that name |
|
| Line items | Its own object, or the one you already have with that name |
|
| Tickets | Its own object, or the one you already have with that name |
|
| Quotes | Its own object, or the one you already have with that name |
|
| Leads | People, deals at the stage Lead, or their own object (you choose) | Fields are mapped on the Fields step |
Every other property is created as an Attio attribute and shown on the Fields step. A record matches on email (people) or domain (companies) and is updated in place, so running it twice never leaves two of anything.
Notes, tasks, meetings, calls, emails, files, owners and lists
| Kind | How it moves | What happens |
|---|---|---|
| Notes | Yes | On the record each note was attached to; an edited note updates on a later run. |
| Tasks | Yes | Linked to their records. |
| Meetings | Yes | Meeting participants are carried by name only, so no new people are created. |
| Calls | Yes | Into Attio's Phone calls, with the time, length, direction, outcome and call notes. A call with no migrated person, or a workspace that has not allowed activities, becomes a note instead. |
| Emails | Off by default | Logged emails land as a Logged emails activity on their records, with sender, recipients, date and body. Off by default: Attio's mailbox sync may already show the same mail. |
| Files | Yes | Files up to 50 MB, uploaded to the record they were attached to. A larger file and a link are listed as failed rows. |
| Owners | Yes | Deal owners and task assignees, matched to an Attio member by email. |
| Lists | Yes | Static lists keep their members; a dynamic list arrives as a snapshot of its members, with its conditions written out as text. |
Deal pipelines and stages
Shuttio reads each HubSpot deal pipeline with its stages from the portal, and each deal takes the stage it is in. One pipeline becomes Attio's Deal stage. With two or more you choose on the Fields step: a list per pipeline, or a stage field per pipeline. Switch Pipelines off on the Options step and the names land in text fields instead.
Your own fields
| HubSpot field type | Created in Attio as |
|---|---|
| Single-line or multi-line text | Text |
| Number | Number |
| Number shown with a currency symbol | Currency |
| Date picker | Date |
| Date and time | Date and time |
| Single checkbox | Checkbox |
| Phone number | Phone number |
| Dropdown or radio select (Lifecycle stage, Lead status) | Select, with the source's options |
| Multiple checkboxes | Text: the values are joined into one text value |
A field you added yourself arrives as a new Attio attribute of the type above. The Fields step lists every field before anything is written, and you can rename, skip or point a field at an attribute Attio already has.
5 things that don’t move
Each has a reason. You would find them on day two, so they are here on day zero.
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.
How the move runs
- 1
Source
Choose HubSpot as the source and Attio as the destination.
- 2
Connect
HubSpot: OAuth. Pick the portal, approve the scopes, disconnect whenever you like. Attio: sign in with Attio (OAuth).
- 3
Options
Up to five switches decide which kinds of data the next steps offer, such as custom fields, lists and custom objects. Nothing is written yet.
- 4
Objects
Tick what to move. Each row shows where the object lands in Attio.
- 5
Fields
Rename a field, skip it, or point it at a field that exists. When a field goes into an existing field, the step warns you that values on matched records are overwritten, and counts the fields concerned.
- 6
Filters
Limit which records move, per object. Filters do not change the price.
- 7
Import
A free sample runs first: 5% of your companies, contacts or deals, 10 to 1,000 records, picked at random, with their linked records. A deal in the sample still finds its company, because every object takes the records linked to the ones already picked. Lists and files move with the full migration. You open the result in Attio, then run the full migration. It is free. Pause, resume and cancel work while it runs. The Records tab lists every source record as moved, updated, skipped or failed, with the reason, and downloads as a CSV. Move new records brings over the records created in HubSpot after the migration started.
What Shuttio needs from HubSpot
Shuttio only reads from the source. These are the permissions it asks for, and why.
| Scope | Why Shuttio needs it |
|---|---|
| oauth | HubSpot requires it of every app. |
| crm.objects.contacts.read | Reads contacts, and the notes, tasks, meetings and calls attached to your records. |
| crm.schemas.contacts.read | Reads your contact properties, so each can be mapped to a field in the destination. |
| crm.objects.companies.read, crm.schemas.companies.read | Reads companies, their properties and their associations. |
| crm.objects.deals.read, crm.schemas.deals.read | Reads deals, their properties and their associations. |
| crm.objects.products.read, crm.objects.line_items.read | Reads products and line items. |
| crm.lists.read | Reads your lists and their members. |
| Optional: crm.objects.custom.read, crm.schemas.custom.read | Reads your custom objects (Enterprise). If your portal has none, HubSpot drops the scope. |
| Optional: crm.objects.tickets.read | Reads tickets (Service Hub). |
| Optional: crm.objects.quotes.read, crm.objects.leads.read | Reads quotes and leads (Sales Hub). Without quotes access, line items import without their quote link. |
| Optional: crm.objects.owners.read | Matches each record's owner to a user in the destination by email. Without it, owners fall back to the fallback owner. |
| Optional: files | Reads the files attached to notes, emails, calls, meetings and tasks. Without it, the files step writes one "Reconnect HubSpot to move attachments." row and moves nothing. |
| Optional: sales-email-read | Reads logged emails with their bodies, for a move into Clarify or Odoo. Without it, the emails step writes one "Reconnect HubSpot to include emails" row and moves nothing. |
Shuttio only reads from HubSpot. An optional scope that your portal lacks is dropped at install instead of failing it, and the Objects step offers "Reconnect HubSpot" for what is missing.
Prepare HubSpot before you move
Two HubSpot settings change what a move produces. Craftt lists them as settings to turn off before an Import2 move: the default assignment of a company owner to its contacts, and the automatic creation of companies from contacts. Turn them off here too, so the move does not add owners and companies that nobody chose.
Decide one thing before the sample: whether any HubSpot deal pipeline holds work that is not sales, such as onboarding or renewals. With two or more pipelines you choose on the Fields step between a list per pipeline and a stage field per pipeline, so decide first where onboarding or renewal work should live in Attio.
Keep the HubSpot record ID. Shuttio writes every record keyed on it, so a second run updates and never duplicates; if you also load a CSV by hand, keep the ID column to link and check records later.
Sources: Craftt: HubSpot to Attio
Who can do the migration
You can move HubSpot into Attio yourself for free, with Attio's own Import2 flow or with Shuttio. Pay someone when the data model needs a redesign on the way in, not only a copy. Attio's Experts directory listed 65 partners on 4 November 2026.
Import2 moves companies, people, deals, custom objects, notes, tasks and files. Craftt reports that it lands HubSpot calls as notes, turns leads into contacts and does not move emails, meetings or attachments; Attio's page lists files as moved, so test one file-heavy record in the sample. Import2 maps to objects, not lists (Attio points to the CSV importer for lists), and does not update the attributes of records that already exist in Attio.
| Who | Price | Fits when | Limit |
|---|---|---|---|
| Import2, from Attio's Migrate button | Free on Plus, Pro and Enterprise | You are a workspace admin and want companies, people and deals moved as they are | Admins only. It does not update records already in Attio. Its undo leaves the lists and attributes it created |
| Shuttio | Free into Attio at any record count | You want a free sample first, an outcome for every record and a rollback | Moves data only. You rebuild automations and reports by hand |
| Craftt | $700 flat for the migration; the Sprint from $2,500 | You want someone else to map, dedupe and verify the move | The $700 covers the migration of HubSpot only; a redesigned workspace is the Sprint |
| Hack'celeration | From $2,000; one week to six months by scope | You want an agency that also builds the wider go-to-market stack | The price depends on scope |
| Attio Experts directory | Most partners quote after a call | You want a partner in your region or industry | 51 of 65 partners are Core tier (4 November 2026): compare reviews, not tier alone |
Sources: Attio: migrate data from another CRM, Craftt: Attio migration, Craftt: HubSpot to Attio, Hack'celeration: Attio agency, Attio Experts directory
What to rebuild by hand
Forms, sequences, landing pages, calls to action, lead scoring and chat do not migrate, and Craftt's playbook lists automations as work to rebuild. Attio has no ticket object: most teams rebuild HubSpot tickets as a custom object or move support to a dedicated tool. Reports and dashboards become views, filtered lists and dashboards in Attio, and workflows become Attio workflows.
Write the list of active HubSpot workflows before cutover, ranked by how often each fires, and rebuild the top five first.
Sources: Craftt: HubSpot to Attio
Cutover
Your team keeps working in HubSpot while you check the copy. After the full run, Move new records copies the records created in HubSpot since the migration started; edits to records already moved are not copied, so freeze HubSpot edits on cutover day.
Check records, not totals: compare counts per object, open 20 deals and confirm each shows its company and contact, then read the reason for every failed row in the Records tab. Run both systems in parallel for a week with HubSpot read-only, and cancel HubSpot only after your team has closed a real week of work in Attio.
Sources: Craftt: HubSpot to Attio
HubSpot also moves into
Import2 does not support Clarify or Odoo as a destination.
Price
Free at any record count. The sample, the full run, Retry and rollback cost nothing.
HubSpot to Attio with Shuttio or by hand
Attio's own Migrate CRM flow runs Import2, which is free too. Import2 brings notes and tasks, turns calls into notes and does not import meetings or emails; its undo leaves the pipelines, stages and fields it created until their support resets them. Shuttio moves meetings, calls and logged emails (from HubSpot and Pipedrive) onto the right records, rolls back every record, attribute and option it created, and after the full run moves the records created in the source since it started. The full row-by-row comparison is at shuttio.com/vs/import2. Against a manual CSV export: a CSV is one object per file and a record export has no notes, tasks or meetings in it, so a deal's company is a column you match by hand and its notes, tasks and meetings are not in the file. Shuttio reads HubSpot through its API, creates records first and links them second, matches records already in Attio instead of duplicating them, and lists every record's outcome. If you only need one object's fields and no history, a CSV import is enough, and Shuttio runs those free into Attio too.
Questions
How much does a HubSpot to Attio migration cost?
Free at any record count. The sample, the full run, Retry and rollback cost nothing. Attio is the destination, so there is no per-record price. Attio's own Migrate CRM flow runs Import2, which is free too. Import2 brings notes and tasks, turns calls into notes and does not import meetings or emails; its undo leaves the pipelines, stages and fields it created until their support resets them. Shuttio moves meetings, calls and logged emails (from HubSpot and Pipedrive) onto the right records, rolls back every record, attribute and option it created, and after the full run moves the records created in the source since it started. The full row-by-row comparison is at shuttio.com/vs/import2.
What does the free sample move?
5% of your companies, contacts or deals, 10 to 1,000 records, picked at random, with their linked records. Lists and files move with the full migration. It is a real write into Attio, so it can be rolled back.
What does not move from HubSpot to Attio?
A dynamic list's filter itself; History on a property the portal will not report; Emails, unless you tick them; Files over 50 MB and linked files; and 1 more. Each has a reason on this page.
Can I undo the migration?
Yes. Rollback deletes the records, notes, tasks, meetings, files and list entries that the sample or the full run created, in reverse order, from a ledger. A record that already existed in Attio and was updated in place stays, and the values it overwrote are not restored; the Fields step warns you before the run.
Does it change anything in HubSpot, and what about records created while I migrate?
Shuttio only reads from HubSpot. It never writes to it. After the full run, Move new records moves the records created in HubSpot after the migration started. Edits to records already moved are not copied.
What happens to HubSpot calls and emails?
Each HubSpot call lands in Attio's Phone calls on its deal, person or company, with the time, length, direction, outcome, call notes, numbers and recording link. SMS, WhatsApp and LinkedIn messages logged in HubSpot get an Attio activity each. Logged emails can land as a Logged emails activity; they start unticked, because Attio's mailbox sync may already show them. Into Odoo, emails move too, and each call is a Done entry of Odoo's Call type in the chatter, with its time, length, direction, outcome and notes.
Who can migrate HubSpot to Attio for me?
You can do it yourself with Attio's Import2 flow (free on Plus, Pro and Enterprise, for workspace admins) or with Shuttio, and pay someone when the move is also a redesign: pipelines merged, custom objects added, ownership and stages cleaned up. Craftt does a standalone HubSpot migration into Attio for a flat $700 and credits the $700 against a Tune-Up or Sprint booked within 90 days. The table under "Who can do the migration" lists the options with their limits.
Move HubSpot to Attio in a free sample first.
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.