---
name: hubspot-attio-integration
description: Connect HubSpot and Attio: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, companies, deals. Use when the user wants to set up, audit or troubleshoot HubSpot and Attio together, or asks why data is not moving between them.
---

# HubSpot and Attio

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-attio-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** Attio Plus, Pro or Enterprise, a workspace admin, and a decision to leave HubSpot

**What moves:** contacts, companies, deals, one way, out of HubSpot.
**How it is built:** native, built on the api. **Effort:** days.

## The short version

The honest headline is that this is not an integration and treating it as one wastes a week: Attio's Import2 reads HubSpot and writes into Attio once, as a migration, with a sample run to check the mapping and an undo if it goes wrong. There is no sync in either direction and no supported way to run both CRMs in step. If that is what you need, the answer is the orchestration layer and a field-by-field decision about which system owns what, which is a project rather than a connector. Read this page as migration documentation, because that is the only sanctioned path between these two tools.

## What each Attio plan lets you bring across

Rows: Attio plan. Columns: How your HubSpot data gets in. HubSpot charges nothing to leave and gates nothing here. Attio gates the tool that makes leaving easy, which is a reasonable place to put a paywall and worth knowing before you plan the move.

| Attio plan | CSV import | The Migrate CRM tool |
|---|---|---|
| Free | Available | Not available |
| Plus | Available | Available |
| Pro or Enterprise | Available | Available |

- **Available.** Attio documents Migrate CRM as available on plus, pro and enterprise plans, and says Import2 can be used on any paid Attio plan. CSV import is documented without a plan restriction and is the route every workspace has.
- **Not available.** The migration tool is not offered on the free plan. A free workspace can still import by CSV, which means doing the object mapping and the validation by hand rather than having Import2 drive it.

Counted off that grid, of six pairings: five give you available, one gives you not available.

Two columns and one real decision, which is unusual for this directory and right for this pair. The CSV route works everywhere and costs you the mapping; the migration tool costs a plan and gives you a sample run to check before committing, which is the thing actually worth paying for.

## What actually syncs

Direction is written from HubSpot's point of view: out means out of HubSpot, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| People | One way, out | Read out of HubSpot and matched into Attio by email address. Existing Attio records keep their attribute values. |
| Companies | One way, out | Matched by domain, same rule: an existing record is not updated, it is matched. |
| Deals | One way, out | Only if the Deals standard object is enabled in Attio first. Otherwise opportunities have nowhere to go. |
| Notes and tasks | One way, out | Added even to records Attio already holds, which is the one thing that does reach an existing record. |
| Custom objects | One way, out | Created by Import2 during the migration, so they do not have to exist in Attio beforehand. |
| Anything back to HubSpot | One way, in | Nothing, ever. This is a one-time read of HubSpot and a write into Attio. |

## Which field lands where

There is no field mapping to maintain, because there is nothing ongoing to maintain. What there is instead is a set of validation rules that decide which of your HubSpot records survive the trip, and two identifiers that decide which ones merge.

| In HubSpot | In Attio | What to know about the match |
|---|---|---|
| Company | Keyed on Domain | Each domain can only be associated with a single company record. Two HubSpot companies on the same domain become one Attio company, whether or not you meant them to. |
| Person | Keyed on Email address | Each email can only be linked to one person record. The same merge happens, and it is the main reason the record count on the other side is lower. |
| Domains | Root only, validated | attio.com and www.attio.com are accepted. Attio stores only the root domain, not full URLs or page paths, and an invalid format causes an error rather than being cleaned up. |
| Phone numbers | Plus country code, then the number | Attio validates country and area codes, so a wrong one errors. Hyphens are optional, which is the only forgiving part of the rule. |
| Deals | May have required attributes | Attio notes some objects have attributes that must be included for the import to succeed. Worth checking per object rather than assuming a contact-shaped rule applies. |
| Objects you did not enable | Not migrated | Selected at the start under Objects. Adding one later is another migration rather than an adjustment. |
| New attributes Attio creates | Yours to review or archive | Attio tells you to check them after the sample and update or archive as needed, which is the step that keeps a migrated workspace from looking like somebody else's. |
| Anything after the migration | Nothing | This is a one-time move. Attio does not keep reading HubSpot afterwards, and a record changed in HubSpot the next day stays changed only there. |

### What to settle before the full run, because it does not undo

| The action | How it reads on the record |
|---|---|
| Phone numbers without a country code | Error. Fix them in HubSpot first |
| Domains stored as full URLs | Error. Attio keeps only the root |
| Two contacts sharing an email address | One Attio person. Documented, and not reversible per record |
| An object you forgot to enable | Another migration |
| A migration you want to redo cleanly | Bulk delete every person and company first |
| An error during the process | Attio sends you to help@import2.com with its support team copied, plus your migration ID and a screenshot |

**What does not cross:**

- Any ongoing sync. This is a migration tool, so nothing in HubSpot is read again once the run is finished and nothing is written back.
- HubSpot marketing. Attio's own co-founder says in public that marketing is not something Attio has an offering for yet, which is the gap to plan around rather than discover.
- Records that fail validation. A bad phone number or domain is an error rather than a cleaned value, so the data quality work happens in HubSpot before the export.

## Connect it, in this order

**Who has to do it:** An Attio workspace admin, and somebody who can export from HubSpot. Import2 runs the migration itself, so there is a third party in the loop.
**How long:** A day, spread over a sample migration, a review and the full run. Not an afternoon.

### 1. Confirm the plan carries the migration tool

*Where:* Attio: your plan

Attio documents Migrate CRM as available on plus, pro and enterprise plans, and Import2 as usable on any paid Attio plan. A free workspace is doing this by CSV, which is a different job with different rules.

### 2. Fix the formatting in HubSpot before you export anything

*Where:* HubSpot: your data

Attio validates two things strictly. Phone numbers need a country code in the form plus country code then the subscriber number including area code, and Attio checks that country and area codes are real. Domains must be valid and Attio stores only the root, so a full URL with a path will fail.

### 3. Understand the two identifiers you cannot change

*Where:* Attio: how records match

Companies are keyed on Domain and people on Email address, and each value can only belong to one record. That is a deduplication rule and a constraint at once: two HubSpot contacts sharing an email cannot both exist in Attio.

### 4. Enable the objects you intend to bring across

*Where:* Attio: object settings

Attio asks which types of data to migrate, and some objects such as Deals have required attributes that must be present for the import to succeed. Enabling an object after the migration means doing part of it again.

### 5. Start the migration from the workspace menu

*Where:* Attio: workspace name, Migrate CRM

Click your workspace name at the top of the left sidebar, then Migrate CRM, find HubSpot in the list and click Migrate. From here Import2 is driving, and Attio is the destination rather than the operator.

### 6. Run the sample first and actually read it

*Where:* Attio: the sample migration

Verify the sample succeeded and review any new attributes that appeared, updating or archiving them as needed. Attributes created by a migration are the thing teams find six months later and cannot explain.

### 7. Request and run the full migration

*Where:* Attio: Request full migration

If prompted, click Request full migration and refresh the page, after which a button to start the full run appears. The gap between sample and full is where the review is supposed to happen.

### 8. Know how to start over, because it is brutal

*Where:* Attio: Companies and People

A clean redo means deleting all person and company records: clear all filters, tick the header checkbox, then More and Delete records. That is the documented reset, and it is the reason the sample step exists.

This is the only pair in the directory where the right outcome is that the two systems stop talking. Everything above is a one-way move, and the honest comparison is not with another integration but with staying where you are, which is what the rest of the [CRM layer](layer:crm) is for.

## How to check it worked

- Check the sample for attributes you did not expect. Attio tells you to review and archive them, and that advice is easy to skim past when the record counts look right.
- Pick ten records you know well and compare them field by field against HubSpot. A migration that reports success and loses a field is the failure mode worth catching before the full run.
- Test a phone number without a country code and a domain with a path. Both should fail, and seeing the validation work tells you what the full run will reject.
- Count the records that did not arrive. Two HubSpot contacts sharing an email address become one Attio person, which is correct behaviour and still a number somebody should know.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| The migration fails on phone numbers | Attio validates country and area codes and expects the format plus country code followed by the subscriber number including the area code. | Normalise them in HubSpot before exporting. Hyphens are fine; a missing or wrong country code is not. |
| Domain values are rejected | Attio verifies that domains are valid and stores only the root. A full URL or a malformed prefix errors rather than being tidied up. | Strip to the root domain in HubSpot first. attio.com and www.attio.com are both accepted formats. |
| Fewer people arrived than HubSpot had | Email address is the unique identifier for a person and each email can only be linked to one record, so duplicates in HubSpot merge on the way in. | Expect it and count it. If those were genuinely different people sharing a mailbox, that has to be fixed in HubSpot before the migration rather than after. |
| A deal import failed with everything apparently present | Attio notes that some objects, Deals among them, have required attributes that must be included for a successful import. | Check the required attributes for each object you enabled, rather than assuming the rules that worked for contacts apply. |
| There are attributes in the workspace nobody created | The migration creates attributes to hold what it found. Attio tells you to review them after the sample migration and update or archive as needed. | Do that review at the sample stage. After a full run they are mixed in with everything else and much harder to attribute. |
| The migration needs redoing from scratch | There is no partial undo. Attio documents a bulk delete as the way back. | Navigate to Companies or People, clear all filters, tick the first checkbox next to the column header, then More and Delete records. This is why the sample run exists. |
| An error appears mid-migration with no obvious cause | Import2 is running the migration, not Attio, so the diagnostic path leaves Attio. | Email help@import2.com with Attio support copied at support@attio.com, including the migration ID and a screenshot of the error. That is the documented route. |
| Something in HubSpot changed after the migration and Attio does not know | By design. This is a one-time move with no ongoing sync in either direction. | Pick a cutover date and stop writing to HubSpot. Running both as systems of record is the failure this pair makes easy and nothing here prevents it. |

## What breaks, from the vendors' own docs

- **It is a migration, and migrations are one-time.** There is no ongoing sync, no scheduled run and no two-way option. Teams that import to evaluate Attio while still working in HubSpot end up with two CRMs drifting apart from the moment the import finishes, which is a worse position than not having imported. Decide whether you are migrating or evaluating before you run it.
- **Existing records are matched, not merged.** Attribute values on records already in Attio are not updated. Notes and tasks are added; everything else on the record stays as it was. Attio's documented workaround is to delete the existing records first or import them separately by CSV, so a partial prior import makes the real migration harder rather than easier.
- **Undo leaves the structure behind.** Undoing removes the imported records but not the lists, attributes and other structures the migration created. A second attempt therefore runs into a workspace that is already shaped by the first, which is usually fine and occasionally confusing when attribute names were auto-created from HubSpot properties you have since renamed.
- **Admins only, and a plan gate.** Only workspace admins can run Import2 and it is available on Plus, Pro and Enterprise. Attio's free tier cannot do it, so the evaluation path many teams want, import a copy and have a look, requires buying a plan first.

## The APIs, if you are building around it instead

### HubSpot

- **Base:** `https://api.hubapi.com`
- **Auth:** `Authorization: Bearer <private-app-token>` for a private app, or OAuth for a marketplace app. Full CRM API access is on every tier including Free.

| Call | Request | What it does |
|---|---|---|
| `PATCH /crm/v3/objects/contacts/{contactId}` | `{ "properties": { "rc_title": "VP Sales" } }` | Update a contact. Send only the properties you own. |
| `POST /crm/v3/objects/contacts/search` | `{ "filterGroups": [...], "properties": [...] }` | Find records by property. Use this to pull the slice that is missing a field. |
| `POST /crm/v3/objects/contacts/batch/update` | `{ "inputs": [ { "id": "...", "properties": {...} } ] }` | Batch of up to 100. Prefer this over per-record PATCH at volume: it is one request against the rate limit. |

**Rules that will cost you time if you skip them:**

- **Rate limits.** A private app gets 190 requests per 10 seconds on Professional and Enterprise, 100 on Free and Starter. Daily caps are 250,000 / 625,000 / 1,000,000 calls **per account, shared across every app**. A public OAuth marketplace app is capped at 110 per 10 seconds per installing account.
- **Calling an external API from a workflow needs Data Hub Professional or Enterprise.** Both the webhook action and the custom code action live in that hub, not in Sales Hub. Check this before designing an in-HubSpot build.
- **Custom code actions get 20 seconds and 128 MB.** Combined length of all workflow secrets is capped at 1,000 characters. Secrets are read with `process.env.NAME`.
- **Workflows:** up to 50 simple on Starter, up to 300 fully customisable on Professional.
- **Never write to a property a human maintains.** Use prefixed properties (`rc_*`) and promote with a separate workflow only where the human field is empty.

**HubSpot custom code action (Node 20):**

```javascript
// Input field: email   Output fields: rc_status, rc_title, rc_company, rc_headcount
// Secret: RC_API_KEY
const axios = require('axios');

exports.main = async (event, callback) => {
  const email = event.inputFields['email'];
  const res = await axios.post(
    'https://api.reversecontact.com/v2/enrich/persons',
    { email },
    { headers: { Authorization: `Bearer ${process.env.RC_API_KEY}` } }
  );

  const person = res.data?.data?.person;
  const company = res.data?.data?.company;

  // null means "not found", not "try harder". Write nothing and flag it.
  if (!person) return callback({ outputFields: { rc_status: 'no_match' } });

  callback({ outputFields: {
    rc_status:    'matched',
    rc_title:     person.currentPosition?.title || '',
    rc_company:   company?.name || '',
    rc_headcount: company?.employeeCount || 0
  }});
};
```

Docs: https://developers.hubspot.com/docs/api/overview

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- Attio help centre: migrate data from another CRM: https://attio.com/help/reference/imports-exports/migrate-data-from-another-crm
- Attio help centre: introduction to data importing: https://attio.com/help/reference/attio-101/introduction-to-data-importing
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-attio-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-attio-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
