Your custom properties, your history, your relationships. Not only the fields both apps happen to have in common.
Start free assessmentWe run HubSpot CRM to Attio CRM migrations. The assessment is free and comes before any commitment.
Running this for a client? Explore partnership options.
HubSpot CRM
Attio CRM
Keep deals linked to contacts and companies, and activities linked to their records in Attio CRM.
We find your custom fields in HubSpot CRM and plan how their values will travel to Attio CRM before migrating their records.
Your activity history arrives on the record it belongs to. This page names which types transfer and any limit on them.
We match them to your Attio CRM users and stages.
The plan flags values that change during migration. The original value comes across beside the converted one.
Where possible, we create a field in Attio CRM for data with no matching field.
Each row explains a limit and what you can do about it. Open the details for the reason and supporting source.
Calls, emails, meetings, your catalogue and your custom objects need an Attio Pro workspace
View detailsHide detailsAttio lets a workspace add an object of its own only from Pro upwards. Below that a workspace is companies and people plus one or three of Attio's own, and there is nowhere for a call, an email, a meeting, a product or a HubSpot custom object to be created. Your companies, people, deals, notes, tasks and files need no object at all and land on any plan.
Verified against attio.comWe tell you which of these your migration needs before you commit.
An Attio deal has six fields
View detailsHide detailsName, stage, owner, value, and the company and people it links to. That is the object, and Attio designed it that way. So a HubSpot deal's close date, description, deal type, original source, next step and closed-lost reason have no attribute of their own to land in.
Verified against docs.attio.comEach one is preserved on the deal exactly as HubSpot had it, rather than pushed into a field that means something else, and the free assessment shows you which of your deal fields this affects before anything runs.
Attio keeps one list of deal stages, not pipelines
View detailsHide detailsA HubSpot portal with a sales pipeline and a renewals pipeline has two funnels with stages of their own. An Attio deal has one stage attribute, a single status with one list of options. Two stages that share a name merge onto one, and which funnel it belonged to is not something Attio can hold afterwards.
Verified against docs.attio.comEvery deal keeps the stage it was in, won or lost or still open, so nothing needs re-marking by hand.
Lifecycle stage and lead status have no home in Attio
View detailsHide detailsAttio has no lead vocabulary. A person is a person, and where somebody sits in the funnel is a list or a deal rather than a field on the contact. HubSpot's lifecycle stage, lead status and original source have no attribute of their own to land in.
Verified against docs.attio.comYour deals carry the pipeline position they had, and the free assessment names the fields this affects before anything runs.
A note does not keep who wrote it
View detailsHide detailsAttio's create-a-note endpoint takes no author, so a note arrives stamped with the workspace member whose connection wrote it. A note that says Priya wrote it in HubSpot will not say so in Attio. The note itself, its title, its text and the date it was written all come across, on the record it belonged to. It is a small loss, and one we would rather you read here than notice later.
Verified against docs.attio.comThe note itself, its title, its text and the date it was written all come across, on the record it belonged to.
Nobody owns a company in Attio
View detailsHide detailsAttio's writeable attributes for a company are its name, domains, description, team, categories, location and social links. There is no owner among them, because Attio models ownership on the deal and leaves the rest to lists and views. Your HubSpot owners travel on your deals, and the owner on a company is one of the few things this migration reads and cannot place.
Verified against docs.attio.comYour owners travel on your deals, and you say who takes the companies and the people.
One action removes the records we wrote to Attio CRM. Review what will remain before you undo and retry.
A paused run resumes where it stopped, without losing progress or duplicating records.
We only read HubSpot CRM. Nothing is written back to it.
Keep working in HubSpot CRM while you check the results. Then bring across the latest changes before switching over.
In Attio CRM after the migration
After you undo
Covers up to 20,000 records. Larger migrations use higher tiers. You pay once per migration, with no recurring charge.
Connect HubSpot CRM to see your record count and price before you commit.
Ask for a refund within 30 days of your migration being marked complete. We reverse the migrated data out of Attio CRM and refund you.
Yes. The free assessment finds them in HubSpot, and they are created as attributes on the matching Attio object before records are migrated. You see that on your plan before anything runs, and you can drop the properties nobody fills in any more rather than carry them over.
Your notes land as Attio notes and your tasks as Attio tasks, both of which Attio has natively. Calls, emails and meetings land in one activities object we create in your workspace, because Attio ships no record for an interaction at all. Keeping all three kinds in one object means your history costs your plan a single slot rather than three.
Because landing them means adding an object to your workspace, and Attio allows that only from Pro upwards. It is a choice on your plan rather than a surprise. Leave them out and this migration creates nothing in your workspace at all, and your companies, people, deals, notes, tasks and files still come across.
The stages do, the pipelines do not. Every stage your HubSpot deals sit in is created on Attio's deal stage list before the load runs, so each deal arrives in the stage it was in. Attio keeps one list rather than several funnels, so two pipelines that both have a Qualification stage arrive as one, and which funnel a deal came from is not recoverable afterwards.
It lands in the stage that meant won, because the stage itself is what carries the meaning in Attio. Attio publishes no separate won or lost flag on a deal, so we do not invent one from a stage name. The close date is the harder loss and it is on your plan before you pay, since an Attio deal has no close date field.
Each one becomes an Attio object of its own, with its records and the properties you use on them. That needs a Pro workspace, since Attio allows an object of your own only from Pro upwards, and the free assessment tells you how many objects your migration would add before you commit.
No. We work out what each value becomes, so nobody builds a field map. You review the plan before the migration runs. A HubSpot property with no native home in Attio can be brought along as a new attribute instead of being left behind.
We run the migration and stay reachable. Connect HubSpot for the free assessment and price, then Attio to complete the plan. Nothing moves until you ask.
Yes. We only read HubSpot and never write back to it. Keep working while you check the results, then bring across the latest changes before switching over.
You can undo the migration, correct the issue and run again. Created fields, shared catalogue data and any other items listed as retained stay in place.
One payment, based on the records that move. The free assessment of HubSpot gives you the exact count and price before you commit. Payment is by invoice, with no subscription.
Next step
Create an account and connect HubSpot CRM for your free assessment. See your record count and price before you commit. Nothing moves until you ask.
Start free assessment