Not an integration. A one-time migration, and it will not update what it finds.
Attio Plus, Pro or Enterprise, a workspace admin, and a decision to leave HubSpot
Contacts, Companies, Deals, one way, out.
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.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| 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. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
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. |
Worth knowing before you write a report against it, because the wording below is what you will be filtering and searching on rather than anything you choose.
| 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 |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, six action rows and three documented exclusions, each one's note, and the two vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
Read the second table as a pre-flight list rather than as troubleshooting. Every row on it is cheap to fix in HubSpot and expensive to fix after a full migration, and the documented recovery for a bad run is deleting every person and company in the workspace and starting again.
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. Pick one on each side and the grid marks the answer.
Pick one on each side.
| Attio plan | CSV import | The Migrate CRM tool |
|---|---|---|
| Free | Available | Not available |
| Plus | Available | Available |
| Pro or Enterprise | Available | Available |
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.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
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.
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.
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.
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.
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.
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.
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.
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 is for.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/hubspot-attio/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-attio.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyAttio 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.
WhyAttio 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.
WhyEmail 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.
WhyAttio 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.
WhyThe 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.
WhyThere 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.
WhyImport2 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.
WhyBy 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.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for this pair by name, in the words a person would use. 14 threads from 2024 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
Marketing is a really important part of the CRM ecosystem, but not something that Attio has an offering for (yet...). As an alternative for now, we recom
r/CRM·December 2025·3 points
Cut where the cached comment is. A vendor saying this in public is worth more than a competitor saying it, and it is the single most important thing to settle before migrating: a HubSpot portal usually carries marketing as well as CRM, and only one of those has somewhere to land.
Integrations are a big point of focus for us and it's why we made such a huge investment into our App SDK so that we can go toe to toe with Hubspot and Salesforce on integrations.
r/CRM·December 2025·3 points
Answering a question that opened by calling HubSpot's integration coverage its strength. Read it as a roadmap statement rather than a current capability: the investment is the news, and what exists today is what you would be migrating onto.
We wanted to start using Lemlist and Clay for our outbound and were frustrated that neither integrated well with Attio's API.
r/CRMSoftware·January 2026·2 points
From somebody who moved through four CRMs in a few months, including a month on Attio. It is one team's experience rather than a measurement, and the reason it belongs here is that both tools named have their own pages on this site against HubSpot, where the integrations are documented and native.
Hubspot has bigger chances that the sales and marketing teams know how to use it. Attio may need longer onboarding process. Personally, I will use Attio as it is not so bloated.
r/gtmengineering·December 2025·3 points
The most balanced comment in the set, and it holds both halves at once. A migration moves the data in a day; the familiarity that made HubSpot usable for a sales team does not come across with it, and nothing on this page helps with that.
We have taken the view since the beginning that these additional requirements are a core part of the product we build, which is why we have always invested in providing high uptime, strong support and exceptional security to all of our customers - regardless of what plan they're on!
r/CRM·December 2025·3 points
A vendor claim in a vendor AMA, printed as one. It is relevant because the grid above shows the migration tool itself is plan-gated, which is a different thing from the product being tiered on security, and both can be true at once.
This pair gets discussed as a choice rather than a procedure, and the most useful thread is an AMA where Attio's own co-founder answers questions about where HubSpot is still ahead. The honest summary of the set: Attio is widely described as the cleaner product, the integration surface and the marketing side are the acknowledged gaps, and the practitioners who hit those gaps hit them trying to connect the tools this directory covers.
Four of these five are a vendor answering questions about their own product, which is a weaker kind of evidence than usual and is also exactly what somebody considering this move wants to read. The third quote is the one from a customer, and it is the one that names a specific cost.
Attio is the newest CRM in this directory and the only one whose relationship with another CRM here is a migration rather than a connection. That is a deliberate product position rather than an oversight: a tool competing for the system of record has no reason to help you run two. It also means the search that brings people to this page, looking for a HubSpot Attio integration, is usually asking a question with no good answer, and the useful thing is to say so quickly.
If both systems genuinely have to run, the work moves to the orchestration layer and becomes a mapping project. Something has to read one and write the other on a schedule, somebody has to decide which system owns each field, and conflicts have to resolve by a rule written down in advance. That is days of work and a permanent maintenance commitment, and it is worth being honest that most teams who start it are postponing a decision rather than implementing one.
The migration itself is well designed and the sample run is the part to use properly. It creates the attributes in your workspace and lets you check how HubSpot properties landed before any volume moves, which is the cheapest moment to discover that a property you care about mapped somewhere unexpected. Run it, look at twenty records by hand, fix the mapping, and only then do the full pass. The undo exists, and it is much better not to need it.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under HubSpot, Attio and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
No. What Attio offers is Import2, a one-time migration service that reads HubSpot CRM and writes into Attio, free for Attio users on Plus, Pro and Enterprise. There is no ongoing sync, no two-way connector and nothing that keeps the two in step afterwards. If you are evaluating Attio while keeping HubSpot, this pair does not solve that and nothing native will.
They are matched, not updated. Import2 matches people by email address and companies by domain, and Attio documents that attribute values on existing records are not updated, though notes and tasks from the old CRM are added to them. To update attributes on a record that already exists you have to delete it first or import it separately by CSV, which is a very different operation from a merge.
Yes, and you should plan to use it. Attio supports undoing a migration, which removes the records it imported, and you can redo it afterwards. Undo does not remove the lists, attributes and other structures created during the process, so a second run starts from a workspace that is already shaped by the first.
Enable the Deals standard object before migrating opportunities, or they have nowhere to land. Custom objects do not need creating in advance because Import2 can create them during the migration. Only workspace admins can run it, and the documented workflow is a sample migration first, which creates the attributes and lets you check the mapping, then the full run.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.