HubSpot to Attio migration: the complete playbook
The data transfer is the easy half. This is the playbook we use in production: the full object mapping, what breaks, a 10-point pre-migration checklist, realistic phases, and the cases where you should not migrate at all.
Migrate if your motion is sales-led or relationship-driven, your HubSpot is essentially a Sales Hub wrapped around a contact database, and you are paying for hubs nobody opens. Attio gives you a faster, cleaner, API-first CRM whose data model bends to how you actually sell, and the move typically fits in 3 to 5 weeks.
Stay on HubSpot if your revenue depends on Marketing Hub (nurture sequences, landing pages, forms, attribution), on Service Hub tickets, or on native dashboards that finance already trusts. Attio does not replace those today, and pretending it does is how migrations fail.
Either way, the database move is days of work. Rebuilding workflows, scoring, reporting and team habits is the part that decides whether the migration pays off. Budget for the rebuild, not the export.
How HubSpot objects map to Attio
Most of the mapping is clean. The traps are in lifecycle stages, calculated properties and activity history, where the two systems think differently. Here is the full table we work from.
| HubSpot | Attio | Migration notes |
|---|---|---|
| Contacts | People | Native object. Emails are multi-value on one person, so the same human with two addresses stops being two records. Define identity-based dedup rules before import, not after. |
| Companies | Companies | Near 1:1. Attio auto-creates and enriches companies from email domains. Decide upfront which source wins on conflict: your HubSpot data or Attio's enrichment. |
| Deals | Deals (records in a list) | Attio models deals as records grouped in a list with statuses. Each pipeline becomes a list, each deal stage becomes a status. Multi-pipeline portals map to multiple lists or one list with a stage attribute. |
| Lifecycle stages | Status or select attribute | No native lifecycle field in Attio. Rebuild it as a status attribute on People or Companies with explicit transition rules. This is the moment to fix lifecycle logic instead of importing its debt. |
| Custom properties | Attributes | Typed mapping: enumeration to select, multiple checkboxes to multi-select, number, date and text to native types. Calculated and score properties do not transfer; they get rebuilt. |
| Notes | Notes | Importable via API with original timestamps. Authorship maps only if the same users exist in Attio; otherwise notes arrive under the importing user with the original author named in the body. |
| Calls, meetings, tasks | Tasks and notes | Open tasks transfer as tasks. Historical call and meeting engagements have no first-class equivalent; import the ones that matter as timestamped notes, archive the rest. |
| Logged emails | Native Gmail sync | Attio rebuilds email history by syncing the mailboxes you connect. BCC-logged email and mail from departed reps does not come back. Details in the section below. |
| Active and static lists | Lists and views | Static lists import as list memberships. Active lists become saved views with filters; a few need a small automation to replicate enrollment behavior. |
| Workflows | Attio workflows + n8n | Nothing migrates. Every automation is rebuilt natively or in n8n or Make. Treat this as a feature: most portals carry years of zombie workflows that deserve to die here. |
| Tickets | Custom object or your support tool | Attio has no Service Hub. Keep tickets in Zendesk or Intercom and sync the relationship, or model a lightweight ticket object if volume is small. |
| Marketing emails, forms | Not migrated | Attio is not a marketing automation platform. Pair it with a dedicated outbound or lifecycle email tool such as Lemlist. Budget for this before you decide, not after. |
Two structural differences are worth internalizing before you map a single field. First, Attio treats relationships as first-class records: a person can relate to several companies, a deal can reference any object, and lists are views on one shared truth rather than copies of it. Field-for-field transposition wastes that. The portals that get the most out of a move are the ones that redesign the model on their real motion, then map the old data into it, not the other way around.
Second, HubSpot's lifecycle stage is a platform-wide concept with hardcoded behavior. In Attio you own that logic entirely. That is more work upfront and much more honest afterward, because the lifecycle your team sees is the one you actually defined, with transition rules you can read. If you want the deeper product comparison before committing, we keep one updated at Attio vs HubSpot.
What breaks in a HubSpot to Attio migration
Every migration vendor will tell you what transfers. Here is what does not, and what we do about each item. Knowing this list before cutover is the difference between a controlled move and an unpleasant Q3.
Deal stage history
HubSpot stores property history: every stage change on every deal, with timestamps. That history does not transfer as history. Export it before you lose portal access, then backfill the dates that matter (entered SQL, entered negotiation, closed) as plain date attributes on each deal. Those timestamps are where the truth hides. On one B2B SaaS funnel we audited, deals sat in SQL for 102 days on average, and only the stage history could prove it. Lose the export and that number becomes unknowable.
Activity logs
Years of logged calls, meeting outcomes and task history have no one-click import path. The pragmatic move: archive the full engagement export somewhere queryable, then selectively import the activities that still carry decision weight (last meeting notes on open deals, call summaries from the current quarter) as timestamped notes. Importing everything buries the signal under five years of "left voicemail".
Logged emails
Attio rebuilds the email graph by syncing the mailboxes you connect, which is genuinely better than logging because nobody has to remember to BCC. What it cannot rebuild: email that only existed in HubSpot via BCC logging, threads from the mailboxes of people who left, and manually forwarded conversations. Inventory your mailboxes and their retention before committing to a date, and accept that some history lives only in the HubSpot archive you keep.
Workflows and sequences
Zero automatic migration. Every workflow gets classified: rebuild in Attio, replace with n8n or Make, or retire. In practice the retire pile is the biggest one, because most portals accumulate automations nobody can explain. The rebuild is also where Attio's automation model differs: fewer built-in marketing actions, a much cleaner API surface for anything custom. Sales sequences move to a dedicated tool like Lemlist.
Lead scoring
HubSpot score properties recalculate inside HubSpot, so the values you export are frozen snapshots, not living scores. Scoring gets rebuilt in Attio from attributes plus automation, or as an AI scoring agent if the logic deserves it. Treat the rebuild as a chance to audit whether the old score ever predicted anything; in our experience the answer is often uncomfortable.
Dashboards and reporting
Dashboards do not move, and honesty requires saying it plainly: Attio's native reporting is thinner than HubSpot's. It is workable. For a PE and M&A investment fund we built 9 reporting views and a 7-chart dashboard through the API. But "through the API" is the operative phrase. If your team expects drag-and-drop report building on day one, calibrate expectations now, or keep a BI layer in the loop.
The 10-point pre-migration checklist
Run this before the first record moves. Every item here exists because skipping it cost someone a week.
- Export everything, including property historyFull export of contacts, companies, deals and engagements, plus the property history for deal stages and lifecycle stages. Once the portal closes, there is no going back for the timestamps.
- Audit field usageList every property with its fill rate and last-written date. Most portals carry dozens of fields nobody has touched since the person who created them left. Dead schema does not get migrated.
- Clean lifecycle states before the moveMigrate truth, not debt. Fix the contacts marked customer who never bought, the deals marked won that were not, the leads who unsubscribed years ago. The volumes section below shows what this looks like at scale.
- Set identity rules for deduplicationDecide what makes two records the same person: name plus company plus LinkedIn profile, not just email. The same human routinely shows up under a booking address and a work address.
- Map every pipeline and stage on paper firstOne sheet: HubSpot pipeline and stage on the left, Attio list and status on the right, signed off by the people who own the pipeline. Ambiguity here multiplies into every record.
- Inventory every workflow, then kill the zombiesClassify each automation as rebuild, replace or retire, with an owner per decision. Expect the retire column to win.
- Inventory integrations and API consumersStripe, billing, support, enrichment, forms, Zapier zaps: anything reading from or writing into HubSpot needs a new target and a switch date.
- Choose what not to migrateHard-bounced emails, contacts with no activity in years, closed-lost deals from three pipelines ago. Define the cut lines explicitly so nobody relitigates them mid-migration.
- Plan the email syncList which mailboxes will connect to Attio, what history depth each holds, and whose mailboxes are already gone. This determines how much email history you can actually rebuild.
- Write the verification plan before the dry runRecord counts per object, owner coverage, spot checks on a random sample, and a named person who signs off the cutover. If you cannot say what "verified" means, you are not ready to move.
Phases and a realistic timeline
3 to 5 weeks for most sales-led teams, including the model redesign. Larger portals with heavy automation run longer, and the long pole is never the data. It is the rebuild around it.
Audit and scope · 2 to 4 days
Field usage audit, workflow inventory, integration map, mailbox inventory, cut lines. This phase is exactly what our free diagnostic covers, so you can get it without committing to anything.
Model design in Attio · 3 to 5 days
Objects, attributes, lists and statuses designed on your real motion, not transposed from HubSpot's defaults. This is where the migration earns its keep: the model you design here is the one your team lives in for years.
Dry run on a copy · about 1 week
Full import into a staging workspace. Run the verification plan, fix the mapping, run it again. Repeat until counts match and spot checks pass. Nothing touches production until the dry run is boring.
Cutover · 1 to 2 days
Freeze window on HubSpot writes, final delta import, integrations switched to Attio, dedup pass, sign-off against the verification plan. The team starts Monday in the new system.
Rebuild automations and reporting · 1 to 2 weeks, overlapping
Workflows rebuilt in Attio or n8n, scoring re-implemented, reporting views and dashboards constructed. Sequenced by revenue impact: the automation that books meetings comes back first.
Hypercare and handover · 1 week
The team works, we watch. Edge cases get fixed the day they appear, the documentation gets finished against reality, and you get the keys: model, workflows, runbook. Zero lock-in.
What migration-grade hygiene looks like in real volumes
Numbers from our CRM migration and hygiene practice, anonymized. They are here for one reason: to show the scale of what "clean before you move" actually means, because most migration content pretends a CSV upload is the job.
On a B2B SaaS scale-up's HubSpot, a funnel hygiene pass found 247 MQLs entered over the period, 13 of them marked won, and only 5 of those real. The same audit surfaced an average of 102 days spent in SQL, a number nobody had ever computed because nobody had pulled the stage history. The lifecycle cleanup that followed: 35,788 contacts excluded from communications, 143 lifecycle corrections, 158 stale deals closed as Lost, and 35,930 contacts de-tagged, with zero accidental wins across the entire run. Every write was verified before and after, because at that volume a single bad filter rewrites your revenue history.
On a PE and M&A investment fund's Attio, the system we operate runs 24 workflows in production. Among them: a post-meeting extraction pipeline that turns calls into structured records (participants, amounts, next steps) with an adversarial second pass that rejects anything not actually said in the meeting; cross-email deduplication that matches Calendly booking stubs to LinkedIn-enriched profiles; an enrichment refresh across 953 stale profiles; a rebuilt pipeline board with the owner populated on 71 of 71 deals; and native reporting, 9 views plus a 7-chart dashboard, built through the API.
The point is not the numbers. The point is that a migration executed at this level of care produces a CRM the team trusts on day one, and a migration executed as a bulk upload produces a second dirty system with a better interface.
Six cases where we would tell you to stay on HubSpot
We build on Attio by preference and say so openly. That only stays credible if we also name the cases where the move is wrong. Here they are.
Your demand gen lives in HubSpot
Nurture sequences, landing pages, forms, attribution reporting: Attio replaces none of it. You would be buying a CRM and then re-buying a marketing stack around it. If Marketing Hub earns its bill, stay.
You depend on native dashboards
If leadership runs on HubSpot's report builder and custom report library, Attio's native reporting will feel thin. It can be built, we have done it through the API, but "can be built" is not "comes in the box".
You need quotes inside the CRM
Attio has no native quoting. We pair it with PandaDoc and it works well, but if HubSpot's quote objects and payment links are load-bearing for your sales flow, that is a real dependency to price in.
Support tickets run your renewals
No Service Hub equivalent exists in Attio. If tickets, SLAs and the support inbox are inseparable from your revenue motion, you would need Zendesk or Intercom plus sync work. Sometimes that is an upgrade. Sometimes it is just more pieces.
You lean on the app marketplace
Attio's ecosystem is young. The API is excellent and n8n covers most gaps, but if your team installs apps rather than builds integrations, HubSpot's marketplace depth is a genuine advantage you would give up.
The problem is process, not the tool
If stages are vague, ownership is unclear and nobody updates anything, migrating moves the mess to nicer furniture. Fix the process first, on the CRM you have. We tell prospects this in diagnostics more often than you would think.
HubSpot to Attio migration FAQ
How long does a HubSpot to Attio migration take?
Does deal stage history transfer to Attio?
Do logged emails come over?
What happens to our HubSpot workflows?
What does a HubSpot to Attio migration cost?
Can we run HubSpot and Attio in parallel?
Not sure which side of the verdict you are on?
Tell us about your HubSpot in the form, text or voice memo, whichever is faster for you. We map where it hits the ceiling, whether a move to Attio actually pays off in your case, and what it would cost. Free, 30 minutes of our work, an answer within 24h.
Free 30-minute diagnostic