How to Migrate from HubSpot to Attio
Plan a HubSpot-to-Attio migration: choose an import route, map records, validate history and replace the HubSpot workflows your team still needs.
- Difficulty
- Depends on objects, history and integrations
- Typical duration
- Scope after a sample import
- Downtime
- Agree a cutover and change-capture plan
- Native importer
- Import2 via Attio on paid plans; CSV and API are alternative routes
| HubSpot CRM | maps to | Attio | What to watch |
|---|---|---|---|
| Company | Company | Preserve source IDs and reconcile domains and associations in a sample. | |
| Contact | Person | Check duplicates, multiple email addresses, owners and company links. | |
| Deal | Deal | Enable the destination object and validate pipeline, currency, owner and dates. | |
| Custom property or object | Attribute or object | Check destination plan limits, types and reference relationships before the full import. | |
| Note or task | Note or task where supported | Check content, parent record, owner and timestamps in the chosen migration route. | |
| Email, meeting or call recording | Route-dependent history or archive | Inventory separately; do not infer activity coverage from successful contact imports. | |
| Ticket or marketing asset | Separate tool or archive | Assign a destination and an owner; CRM records alone do not replace the surrounding operation. |
What transfers cleanly
- Companies, people and deals are the core mapping to validate in the sample.
- Treat custom fields, owners, relationships, notes and tasks as separate acceptance checks.
What doesn't come across
- Sequences exist in Attio Pro, but workflow definitions and enrolment state need a separate migration plan.
- Mailbox and calendar sync are not proof that every historical HubSpot activity was preserved.
- Rebuild or replace the HubSpot marketing and service workflows you still need.
Migration order that works
- Inventory objects, counts, attachments, activities, workflows and integrations; preserve source exports.
- Choose the migration route and plan; define the mapping and acceptance criteria.
- Run a representative sample before importing the full dataset.
- Reconcile counts and inspect relationships, history, permissions and rejected records.
- Confirm how records changed during migration will be captured before cutover.
- Run the agreed full import and repeat the acceptance checks with business owners.
- Reconnect integrations deliberately and retain the old system until sign-off and rollback requirements are met.
Choose a route before changing the workspace
Attio documents Import2 for HubSpot migrations on paid plans. CSV is an alternative, but Attio's CSV importer does not import notes. Import2 does not update attributes on matching existing records and excludes call recordings. Validate these limits against your scope before starting.
Avoid deleting existing destination records just to make an import easier. If the workspace is already in use, take exports and agree how existing data will be protected, updated and reconciled.
A useful sample must include the difficult records
Choose examples with several company associations, an open and a closed deal, custom properties, missing emails, duplicate contacts and notes. Include records with history that the business would need in a dispute or a customer handover. Record the expected destination for each example.
Acceptance checklist
| Check | Evidence to save |
|---|---|
| Counts | Source and destination totals by object, with every exclusion or rejected record explained. |
| Relationships | A sample of person-to-company and deal associations, checked against source IDs. |
| History | Representative notes, tasks, meetings and emails compared individually; unsupported history archived. |
| Ownership | A documented mapping from former users to destination users. |
| Reporting | Totals for a familiar report reconciled before and after the move. |
| Workflow | One end-to-end sales process tested by its owner. |
| Cutover | A plan for changes made during import, sign-off and rollback. |
Budget for the surrounding work
Use the cost calculator for seats, onboarding, add-ons and implementation. Enter the actual implementation quote rather than assuming a migration service replaces all configuration work.
Correction, 12 October 2026: this guide previously described only CSV/API and incorrectly said Attio lacked sequences. It now identifies the Import2 route and separates importing records from rebuilding workflows and validating history.
Need help moving from HubSpot CRM to Attio?
Craftt, the CRM team behind weekcrm, plans and runs the migration: field mapping, deduplication, history and a cutover your team won't notice. You get a fixed quote within one business day.