HubSpot → Attio

Catalog plan outline

General guidance from the Afterstack catalog for HubSpot → Attio. Not HubSpot or Attio vendor documentation.

Migration friendliness

HubSpot 7/10 · Attio 7/10

Speed to live

HubSpot 6/10 · Attio 7/10

Catalog migration difficulty

HubSpot high · Attio not set

Data to export from HubSpot

• pipeline and deal records
• custom objects
• sequences and cadences
• call and voice logs
• synced email and calendar links
• workflow rules
• saved reports
• campaign and automation records
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: inbound, pipeline, accounts

How the catalogs differ

• Attio is flagged for custom objects. Collapse unused fields before loading them.
• Attio is not flagged for: call and voice logs, campaign and automation records, installed marketplace apps.
• HubSpot is flagged with an open API, which is the export path to test.
• Attio is flagged with an open API for the load.
• HubSpot is cataloged as a fit for: Inbound-led teams that want marketing and sales in one suite.
• Attio is cataloged as a fit for: Product-led and sales-led startups that treat the data model as the product.

Phases

1. Export

   Take HubSpot as the source of truth for this pair. Export pipeline and deal records; custom objects; sequences and cadences; call and voice logs; synced email and calendar links; workflow rules; saved reports; campaign and automation records; installed marketplace apps; AI assistant configuration; records for the catalog use cases: inbound, pipeline, accounts. The inbound suite that became a CRM — free to start, pricey once you grow up.

2. Map

   Load into Attio only after the field map is written down. A CRM that treats your data model as the product. Attio is flagged for custom objects. Collapse unused fields before loading them.

3. Prove a sample

   Attio scores 7/10 on speed to live and 7/10 on migration friendliness. Run one sample load and one report the team already uses in HubSpot before a full cutover.

4. Cut over

   HubSpot scores 7/10 on migration friendliness and is marked high difficulty in the catalog. Keep HubSpot readable until the team is working in Attio. HubSpot’s free CRM pulled a generation of marketers off spreadsheets. The paid Hubs are where the lock-in lives: marketing, service, commerce, and a Breeze AI layer. It is friendly on day one and a platform negotiation by year three.

HubSpot to Attio: what the vendor docs actually cover

Linked sentences come from vendor documentation opened for this page. Everything else is general guidance, not HubSpot or Attio vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from HubSpot

HubSpot's export article, updated 2 April 2026 and opened on 2026-10-08, exports current property values and associations. The object list in that article includes contacts, companies, deals, tickets, calls, and custom objects, among other record types. You need export permission. The account can run 300 exports in 24 hours, and only 3 at the same time. Download links expire after 30 days. Activity history is called out as a different export path, so a contact CSV is not the email log. A second HubSpot article, import objects, was updated 7 October 2026. It describes loading data into HubSpot, which matters if you have to roll back. That import article says existing emails, meetings, notes, and tasks cannot be updated through import, association labels need Professional or Enterprise, and marketing contacts need Marketing Hub Starter or above plus the Marketing Contacts feature. Import and edit permissions are both required.

• HubSpot export records — checked 2026-10-08
• HubSpot import objects — checked 2026-10-08

How Attio imports

Attio's migration article lists HubSpot CRM as a supported Import2 source. Import2 is for admins on Plus, Pro, and Enterprise, and the article says Attio users are not charged for it. It will not update attributes on a person that already exists under the same email, or a company that already exists under the same domain. Call recordings are not part of Import2. If you skip Import2 and use CSV, the header is mandatory, and the caps are 100,000 rows, 100 columns, and 100 megabytes. Notes and tasks are excluded from CSV. Attio's API overview is available if you would rather script the load. It does not replace the HubSpot export permission model.

• Attio migrate from another CRM — checked 2026-10-08
• Attio CSV import — checked 2026-10-08
• Attio developer overview — checked 2026-10-08

Object and field mapping

• HubSpot contacts become Attio people. Email is the identity Import2 refuses to update when it already exists.
• HubSpot companies become Attio companies. Domain is the identity that blocks updates.
• HubSpot deals need a field map you write down. The migration article names HubSpot CRM as a source and does not publish a column-by-column deal dictionary in the section used here.
• HubSpot tickets are in the HubSpot export. They are not named in the Attio Salesforce object list, and this page does not pretend the HubSpot Import2 source includes a ticket object unless Attio's article says so. It does not, in the text that was read.
• HubSpot calls can be exported as records. Call recordings are outside Import2, so a call row and a recording file are different problems.
• Custom objects export from HubSpot if you have them. Attio still needs a destination attribute or object you created on purpose.

What will not carry over

• HubSpot association labels, unless you rebuild them. Even HubSpot's own import keeps labels on Professional and Enterprise only, which is a hint that labels are not a casual CSV column.
• Updates to existing Attio people and companies matched by email or domain.
• Notes and tasks through Attio CSV.
• Call recordings through Import2.
• Marketing-contact status as an Attio concept. That flag is a HubSpot Marketing Hub rule.
• The activity timeline. HubSpot says activity history is a different export from current properties.

Cutover checklist

1. Confirm the HubSpot user has export permission.
2. Stay under 300 exports a day and 3 at once.
3. Download before the 30-day link expiry.
4. Export activity history separately if the timeline matters.
5. Confirm Attio is on Plus, Pro, or Enterprise and that an admin will run Import2.
6. List HubSpot emails that already exist in Attio so skipped updates are expected.
7. Decide the ticket outcome in writing: archive in HubSpot, or a custom Attio object you build. Do not assume Import2 creates tickets.
8. Keep the HubSpot portal readable. Rollback imports cannot update existing emails, meetings, notes, or tasks.
9. Sample a deal with associations before you stop working in HubSpot.

Common pitfalls

• Exporting only contacts and calling it the CRM. Deals, tickets, calls, and custom objects are separate exports.
• Losing the file after 30 days because the link died.
• Expecting Import2 to fill blanks on people you already imported during a pilot.
• Using HubSpot's import article as if it described Attio. It describes HubSpot, and it is cited here for rollback limits.
• Quoting a HubSpot blog price during the cutover. This migration note uses the export and import articles, not a pricing guide.

Related catalog pages

• Best AI-native HubSpot alternatives (2026) — Which tool, compared
• What should replace HubSpot? — Switch narrative
• Attio product page — A CRM that treats your data model as the product.
• Attio vs HubSpot — Head-to-head already in the catalog
• CRM & sales category — Catalog hub for this category