---
title: "Attio to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate Attio to HubSpot with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/attio/to/hubspot"
---

# Attio to HubSpot migration

Moving from Attio to HubSpot CRM consolidates your data onto a structured platform with mature reporting, cross-hub automation, and a native marketing stack. FlitStack AI maps every Attio People record to HubSpot Contacts, Companies to Companies, Deals to Deals with pipeline stage preservation, and custom Attio attributes to HubSpot custom properties — keeping original create dates, owner assignments, and association links intact during the transition.

Short answer

FlitStack AI migrates contacts, companies, deals, deal pipeline stages and hubspot custom object or custom properties from Attio to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 24–72 hours for under 50,000 records with 1–2 pipelines.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/attio/to/hubspot#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Attio ![](https://flitstack.ai/platforms-trim/attio.webp)

Destination HubSpot ![](https://flitstack.ai/platforms-trim/hubspot.webp)

Contact Company Deal Deal Pipeline Stage HubSpot Custom Object or Custom Property

Mapped field by field · sample run · one-click rollback

## What moves from Attio to HubSpot?

Attio's flexible object-relational model lets teams define any entity type with relationship attributes and N:N associations — a powerful approach for complex GTM motions that can become difficult to govern at scale.

Read the full summary

HubSpot uses a structured CRM object graph with Contacts, Companies, Deals, and optional Service Hub Tickets, where relationships are managed through association labels and primary lookups rather than flexible relationship attributes. We map Attio's People to HubSpot Contacts (preserving first name, last name, email, phone, job title, and address fields directly), Companies to HubSpot Companies (with domain, industry, and employee count mapping), and Deals to HubSpot Deals with stage values carried into the appropriate pipeline. Attio's custom objects map to HubSpot Custom Objects on Enterprise plans or become custom properties on standard objects for lower tiers. Activity history (calls, emails, meetings, notes) migrates as HubSpot engagements with original timestamps and owner links. Owner resolution uses email matching against HubSpot users. We sequence the migration so parent records (Companies) exist before child records (People/Contacts), and Deals reference valid Contacts and Companies before the full run. Attio workflows, sequences, and list automation logic do not migrate — we export the definitions for your HubSpot admin to rebuild as HubSpot workflows and sequences. Pricing covers record count, custom attribute count, and the number of Attio custom objects requiring mapping.

direct

### People → Contact

Attio People records map directly to HubSpot Contacts.

How it maps

Standard fields (first name, last name, email, phone, job title, address components) map 1:1. A People record with no associated Company lands as a HubSpot Contact without a primary company association — this requires a decision on whether to create placeholder company records.

transformed

### People (with Company association) → Contact + Account association

When an Attio People record has a Company association, we map the person to a HubSpot Contact and link it to the corresponding HubSpot Company via the primary Company ID lookup.

How it maps

Attio's N:N model means a person can link to multiple companies — we assign one as primary (most recently modified or by your specified rule) and surface the rest as secondary Company associations in HubSpot.

direct

### Company → Company

Attio Companies map to HubSpot Companies.

How it maps

Standard fields (name, domain/website, industry, employee count, annual revenue) map directly. Attio parent-child company hierarchies map to HubSpot's parent company lookup. Multi-company ownership (Attio's N:N model) collapses to one primary parent for HubSpot's single-parent model.

direct

### Deal → Deal

Attio Deals map to HubSpot Deals.

How it maps

The deal name, amount, expected close date, and owner all migrate directly. Deal stage/status maps to HubSpot pipeline stages — Attio's flexible status values are mapped to specific HubSpot stage names in your target pipeline. Each Attio deal pipeline requires a corresponding HubSpot pipeline.

value\_mapping

### Deal Status / Stage → Deal Pipeline Stage

Attio deal statuses are custom-defined per workspace — we map each Attio status value to a corresponding HubSpot stage name within your chosen pipeline.

How it maps

If Attio uses stages that don't match HubSpot conventions, we create matching stage names in HubSpot before migration so deal history reports show the correct stage progression.

custom\_field\_required

### Attio Custom Object (Enterprise workspace) → HubSpot Custom Object or Custom Property

If your Attio workspace uses custom objects (beyond People, Companies, Deals), we map each to HubSpot Custom Objects on Enterprise plans or create custom properties on the appropriate standard object for Starter/Professional tiers.

How it maps

Custom object relationships that use Attio's N:N model require HubSpot junction objects or association labels when the relationship needs to be preserved between standard objects.

******What moves 12 objects

Attio HubSpot

- People Contact 1:1
- People Contact transformed
- Company Company 1:1
- Deal Deal 1:1
- Deal Status Deal Pipeline Stage transformed
- Attio Custom Object HubSpot Custom Object or Custom Property transformed

\+ 6 more in the mapping below

## How Attio and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension               | Attio                                                                                                                                                                                              | HubSpot                                                                                                                                                               |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Object model philosophy | Attio uses a flexible object-relational model with user-defined objects, relationship attributes, and N:N associations. People and Companies are the only defaults; Deals and others are optional. | HubSpot uses a fixed object graph with Contacts, Companies, Deals (Opportunities), Tickets, and Products as standard objects. Custom Objects require Enterprise tier. |
| Record relationships    | Attio supports N:N relationships between any objects via relationship attributes. A single person can link to unlimited companies.                                                                 | HubSpot Contacts have one primary Company via Company ID lookup plus secondary associations. Deal-contact roles manage the many side.                                 |
| Deal stage model        | Attio Deals use status attributes with custom values per workspace. Stages are flexible text or pick-list values defined per deal.                                                                 | HubSpot Deals live inside Pipelines with Stage pick-list values scoped per pipeline. Multiple pipelines require multiple deal objects.                                |
| Custom field limits     | Attio caps custom objects by plan: 3 on Free, 5 on Plus, 12 on Pro, unlimited on Enterprise. Custom attributes per object are unlimited.                                                           | HubSpot allows 500 custom properties per object. Custom Objects on Enterprise allow 200 objects with unlimited properties per object.                                 |
| Automation migration    | Attio workflows and sequences use block-based logic with triggers, conditions, and actions. Cannot migrate — must rebuild.                                                                         | HubSpot workflows (Automation) and Sequences exist natively. Attio workflow definitions export as rebuild reference only.                                             |
| Activity history        | Attio logs calls, emails, meetings, and notes as timeline entries linked to records via API. Original timestamps and owners preserved.                                                             | HubSpot logs engagements (calls, emails, meetings, notes) as timeline activities with create dates and owner attribution.                                             |
| List segmentation       | Attio Lists are named saved views with filters. List membership reflects current record state, not a static set.                                                                                   | HubSpot uses Static Lists and Active Lists for segmentation. Active Lists use dynamic rules; Static Lists hold fixed membership.                                      |
| API rate limits         | Attio API limits: 100 requests/second for reads, 25 requests/second for writes. Batch endpoints available for bulk operations.                                                                     | HubSpot API uses tiered rate limits per portal tier. Private app tokens have different limits than OAuth. Bulk API handles large record sets.                         |

## Attio to HubSpot field mapping

The 30 most-used fields of 47 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/attio/to/hubspot.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Attio HubSpot

1. `first_name` People `firstname` Contact
2. `last_name` People `lastname` Contact
3. `email_address` People `email` Contact
4. `phone_number` People `phone` Contact
5. `mobile_phone` People `mobilephone` Contact

| Attio field                                       | HubSpot field                   | Mapping                 | Note                                                                                                                                                       |
| ------------------------------------------------- | ------------------------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `People.first_name`                               | `Contact.firstname`             | direct                  |                                                                                                                                                            |
| `People.last_name`                                | `Contact.lastname`              | direct                  |                                                                                                                                                            |
| `People.email_address`                            | `Contact.email`                 | direct                  |                                                                                                                                                            |
| `People.phone_number`                             | `Contact.phone`                 | direct                  |                                                                                                                                                            |
| `People.mobile_phone`                             | `Contact.mobilephone`           | direct                  |                                                                                                                                                            |
| `People.job_title`                                | `Contact.jobtitle`              | direct                  |                                                                                                                                                            |
| `People.linkedin_url`                             | `Contact.linkedin_company_page` | direct                  |                                                                                                                                                            |
| `People.city`                                     | `Contact.city`                  | direct                  |                                                                                                                                                            |
| `People.state`                                    | `Contact.state`                 | direct                  |                                                                                                                                                            |
| `People.country`                                  | `Contact.country`               | direct                  |                                                                                                                                                            |
| `People.postal_code`                              | `Contact.zip`                   | direct                  |                                                                                                                                                            |
| `People.created_at`                               | `Contact.original_create_date`  | custom\_field\_required | HubSpot's createdate is set at migration time. Original Attio created\_at preserved as a custom property for reporting continuity.                         |
| `People.updated_at`                               | `Contact.notes_last_updated`    | direct                  |                                                                                                                                                            |
| `People.attio_record_id`                          | `Contact.attio_id`              | custom\_field\_required | Attio internal ID stored on HubSpot contact for traceability, delta-run de-duplication, and source reference.                                              |
| `People.company (association)`                    | `Contact.associated_company_id` | transformed             | Attio's company association becomes Contact's primary Company ID lookup in HubSpot. Additional company associations become secondary associations.         |
| `People.owner (user reference)`                   | `Contact.hubspot_owner_id`      | transformed             | Owner resolved by email match to HubSpot users. Unmatched owners flagged before migration — fallback owner assigned or user account created.               |
| `Company.name`                                    | `Company.name`                  | direct                  |                                                                                                                                                            |
| `Company.domain`                                  | `Company.domain`                | direct                  |                                                                                                                                                            |
| `Company.website`                                 | `Company.website`               | direct                  |                                                                                                                                                            |
| `Company.industry`                                | `Company.industry`              | value\_mapping          | Attio industry pick-list values map to HubSpot industry pick-list. Custom Attio values not in HubSpot list are preserved as-is or mapped to nearest match. |
| `Company.employee_count`                          | `Company.number_of_employees`   | direct                  |                                                                                                                                                            |
| `Company.annual_revenue`                          | `Company.annualrevenue`         | direct                  |                                                                                                                                                            |
| `Company.phone`                                   | `Company.phone`                 | direct                  |                                                                                                                                                            |
| `Company.city`                                    | `Company.city`                  | direct                  |                                                                                                                                                            |
| `Company.state`                                   | `Company.state`                 | direct                  |                                                                                                                                                            |
| `Company.country`                                 | `Company.country`               | direct                  |                                                                                                                                                            |
| `Company.created_at`                              | `Company.original_create_date`  | custom\_field\_required | HubSpot's createdate set at migration time. Original Attio created\_at preserved as custom property for reporting continuity.                              |
| `Company.attio_record_id`                         | `Company.attio_id`              | custom\_field\_required | Attio internal ID stored on HubSpot company for traceability and delta-run de-duplication.                                                                 |
| `Company.parent_company (relationship attribute)` | `Company.parent_id`             | transformed             | Attio parent-child company hierarchy maps to HubSpot Parent Company lookup. Parent company must be migrated first; circular references flagged.            |
| `Deal.name`                                       | `Deal.dealname`                 | direct                  |                                                                                                                                                            |

## What to watch for in a Attio to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Attio N:N company associations collapse to HubSpot primary company lookup

Attio's object model allows a single Person record to link to multiple Company records simultaneously using relationship attributes.

How we handle it

HubSpot Contacts have one primary Company via the Company ID lookup field, with additional company associations available but not first-class lookups. When migrating Attio records with multiple company links, we assign one as the primary (by most-recent modification date or your specified rule) and surface the rest as secondary associations. You must decide which company counts as primary for HubSpot's reporting model before migration runs — this affects deal attribution, revenue reporting, and company rollup fields.

high

### Attio custom objects require HubSpot Enterprise or fallback property mapping

Attio workspaces on Pro and Enterprise plans often include custom objects beyond People, Companies, and Deals — these might model Subscriptions, Projects, Investors, or other domain-specific entities.

How we handle it

HubSpot Custom Objects are available only on Enterprise plans. If your Attio workspace uses custom objects and your HubSpot account is Starter or Professional, those custom objects map to custom properties on standard objects, which limits the richness of the relationship model. We surface this gap in the pre-migration plan and recommend upgrading to HubSpot Enterprise if custom object fidelity is required for your reporting.

medium

### Attio deal pipeline structures may not map 1:1 to HubSpot pipelines

Attio allows flexible status definitions per deal — teams commonly define custom stage names, add status-specific fields, or use status values differently per deal type.

How we handle it

HubSpot deal pipelines require a fixed set of stage names scoped to each pipeline. If your Attio workspace uses multiple deal pipelines with overlapping or conflicting stage names, we create corresponding HubSpot pipelines and map each Attio stage to the correct HubSpot stage within its pipeline. Pipeline-specific fields in Attio may need custom properties in HubSpot to preserve that data — we document this in the pre-migration schema plan.

medium

### Attio workflow definitions and sequences do not migrate

Attio workflows (block-based automations with triggers, conditions, and actions) and sequences (outbound cadences) are platform-specific configurations that cannot export in a portable format.

How we handle it

HubSpot has its own workflow engine and sequence tool, but they require rebuilding from scratch. We export Attio workflow definitions as JSON and sequence configurations as a reference document so your HubSpot admin has a rebuild guide. This is always disclosed upfront — no migration service should claim to preserve workflow logic between fundamentally different automation platforms.

low

### Attio list membership reflects current state, not historical snapshots

Attio Lists are saved views that filter records dynamically based on current attribute values — a contact that matched a list filter yesterday but no longer matches today is not a member of that list today.

How we handle it

HubSpot Active Lists work similarly (dynamic rules), but Static Lists hold explicit membership. We convert Attio Lists to HubSpot Active Lists where the filter logic translates, and Static Lists where explicit membership was maintained. For lists that rely on complex filter logic with no HubSpot equivalent, we document the list criteria for manual rebuild as HubSpot Active Lists.

## How the migration runs

1. ### Extract Attio workspace schema and data via API

   We connect to Attio's API using a read-only integration scoped to your workspace.

   What this step covers

   The extraction pulls all People, Companies, Deals, custom objects, activities, and relationship attributes. We capture object schemas (all attribute definitions and types), list definitions, and workflow/sequence metadata for the rebuild reference package. Attio's API rate limits (100 req/s read, 25 req/s write) govern extraction pacing — large workspaces extract over several hours to avoid 429 errors. The extraction output is a structured JSON dataset organized by object type, ready for transformation.

2. ### Design HubSpot schema and field mapping plan

   Based on the extracted Attio schema, we design the HubSpot target schema: creating custom properties for unmapped Attio attributes, setting up deal pipelines matching Attio's deal structure, and planning association labels for relationship attributes.

   What this step covers

   We deliver a schema plan document showing every Attio attribute, its HubSpot destination, the mapping type (direct, value mapping, custom field required), and any transformation notes. Your HubSpot admin approves the plan before any data is written — this is where you make decisions about primary company assignment, pipeline mapping, and custom object handling.

3. ### Resolve owners and validate foreign key dependencies

   Attio owner references on People, Companies, and Deals resolve by email address against HubSpot users.

   What this step covers

   We run an owner resolution scan that reports matched owners, unmatched owners, and HubSpot users with no Attio owner match. Unmatched owners require either HubSpot user account creation (so their Attio records can reference them) or reassignment to a fallback owner before migration. We also validate that all foreign key dependencies are satisfied — Companies must exist before Contacts reference them, and Contacts must exist before Deals reference them — flagging any records with broken references for your team to clean up.

4. ### Run sample migration with field-level diff

   A representative slice (typically 100–500 records across People, Companies, Deals, and a few activities) migrates to your live HubSpot account first.

   What this step covers

   We generate a field-level diff report showing every source Attio field value and its corresponding HubSpot field value — so you can verify that custom attribute mapping, stage name mapping, and owner resolution are correct before the full run. This is your QA checkpoint. You review the diff, we make corrections to the mapping plan, and then proceed to the full migration.

5. ### Execute full migration with delta-pickup window

   The full migration runs in dependency order: Companies first (HubSpot requires them before Contacts), then People mapped to Contacts, then Deals with their Contact and Company associations.

   What this step covers

   Activities and Tasks migrate with their linked record references intact. After the initial full run completes, a delta-pickup window (24–48 hours) captures any records created or modified in Attio during the migration window. An audit log records every operation. If reconciliation fails, one-click rollback reverts the HubSpot account to its pre-migration state so you can address the issue and retry.

6. ### Deliver rebuild reference package for workflows and sequences

   After the data migration completes, we deliver the rebuild reference package: Attio workflow definitions exported as JSON with screenshots, sequence configurations with step-by-step cadence logic, and list definitions with filter criteria.

   What this step covers

   This package is your roadmap for recreating Attio automation logic in HubSpot workflows and sequences. We do not rebuild workflows — that is a configuration task for your HubSpot admin or a HubSpot-focused consultant — but the reference package eliminates the need to reverse-engineer your old automation logic from memory.

![](https://flitstack.ai/platforms/attio.svg) Attio ![](https://flitstack.ai/platforms/hubspot.svg) HubSpot

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · HubSpot Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**24–72 hours for under 50,000 records with 1–2 pipelines** Typical, smaller accounts

**5–10 days for 500,000+ records or complex custom-object / multi-pipeline setups** Large or heavily customised accounts

Attio-to-HubSpot migration pricing scales with three primary drivers. First, total record volume across People, Companies, Deals, and custom objects determines the base migration tier. Second, the number of custom attributes in Attio that need HubSpot custom property creation adds scope — Attio's flexible schema often means dozens of custom attributes per object that don't map directly to HubSpot properties. Third, the number of distinct Attio custom objects that need mapping to HubSpot Custom Objects (Enterprise) or custom properties on standard objects increases planning and validation work. A 10-person team with under 5,000 records and one pipeline typically lands in the lower range. A 50-person team with multiple Attio custom objects, 50+ custom attributes, and three deal pipelines enters the upper range because each pipeline requires separate HubSpot pipeline configuration and each custom object needs its own mapping plan. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Attio to HubSpot →](https://flitstack.ai/contact)

## Why teams move from Attio to HubSpot

- Attio's blank-slate data model requires significant upfront configuration time — teams report spending weeks defining objects, relationships, and views before the CRM becomes operational. HubSpot's pre-built object structure lets revenue teams start logging activity on day one without a technical setup phase. Multiple Reddit threads describe Attio as 'powerful but overwhelming' for teams without a dedicated admin.
- HubSpot's native marketing hub (email, forms, landing pages, SEO, and advertising tools) is fully integrated with the CRM data model. Attio provides no native marketing automation — teams must build integrations to tools like Klaviyo, Mailchimp, or ActiveCampaign. For companies whose primary revenue motion is inbound marketing, HubSpot's unified platform reduces integration overhead and data sync complexity.
- Attio's reporting capabilities are frequently cited as immature in G2 reviews — users describe weak pipeline reporting, missing date-based automation triggers, and inability to build multi-object reports without custom configurations. HubSpot's reporting dashboard, attribution modeling, and revenue analytics provide deeper visibility without requiring a data analyst to configure them.
- The credit-based pricing model in Attio creates unpredictable monthly bills — workflow automations, AI enrichment steps, and enrichment actions each consume workspace credits, and teams consistently report burning through their monthly allocation faster than expected. Adding credit packs at $120/month for 10,000 credits on top of seat pricing undermines the apparent cost advantage over HubSpot's bundled tiers.
- HubSpot's partner ecosystem and third-party integration library is significantly larger than Attio's. G2 reviews note integration issues with Aircall, HubSpot (ironically), and other common GTM tools. Teams moving to HubSpot gain access to 1,000+ certified integrations without custom API work.

Questions, answered

## Attio to HubSpot migration questions

How long does an Attio to HubSpot migration take?

Most Attio-to-HubSpot migrations complete in 24–72 hours of clock time for under 50,000 total records with one deal pipeline and no custom objects beyond the standard People/Companies/Deals set. Larger setups with 500,000+ records, multiple Attio custom objects, or complex pipeline structures extend to 5–10 days. The longest planning step is designing the HubSpot schema and field mapping plan for custom Attio attributes — this typically takes 1–3 business days for your team to review and approve before extraction begins.

Will my Attio workflows and sequences migrate to HubSpot?

No. FlitStack AI migrates data and schema only — Attio workflows (block-based automations with triggers, conditions, and actions) and sequences (outbound cadences) do not transfer. They have fundamentally different architectures: Attio uses a flexible block-based model while HubSpot uses its own workflow engine and sequence tool. We export your Attio workflow definitions as JSON and sequence configurations as a step-by-step reference document so your HubSpot admin can rebuild them in HubSpot's native tools.

What happens to Attio's N:N company associations in HubSpot?

Attio allows a single person record to link to multiple companies simultaneously. HubSpot Contacts have one primary Company via the Company ID lookup field. We assign the most-recently-modified company association as the HubSpot primary and surface additional associations as secondary. You specify the assignment rule during planning — by most-recent activity, by relationship type, or by explicit priority flag in Attio. Deal attribution and revenue reporting use the primary company assignment.

Can I migrate Attio custom objects to HubSpot?

Yes, but the destination depends on your HubSpot plan tier. HubSpot Custom Objects require Enterprise tier — on Starter or Professional plans, Attio custom objects map to custom properties on standard objects (Contact, Company, Deal). We document which Attio custom objects exist in your workspace, assess whether they map cleanly to HubSpot Custom Objects or require property-based fallback, and deliver a custom-object mapping plan before migration runs. If custom-object fidelity is business-critical, we recommend confirming your HubSpot Enterprise eligibility before migration.

What happens to Attio deal status values in HubSpot?

Attio deal status values (which are workspace-defined and flexible) map to HubSpot pipeline stage names. If your Attio workspace uses multiple deal pipelines, we create corresponding HubSpot pipelines and map each Attio pipeline's statuses to the correct HubSpot pipeline's stage names. Any status-specific fields in Attio migrate as custom properties on the HubSpot Deal object. We deliver a stage-mapping matrix during the planning phase so you can verify that deal history reports will show the correct stage progression after migration.

Does the migration affect my Attio account during cutover?

No. FlitStack AI uses scoped read-only API access on Attio — your team continues working in Attio throughout the migration. We pull a complete snapshot of your workspace at extraction time, then run a delta-pickup window (typically 24–48 hours after the full migration run) to capture any records created or modified in Attio during the cutover. This ensures HubSpot reflects your final Attio state at go-live. No data is written to Attio during the process.

What happens to Attio Lists in HubSpot?

Attio Lists are named saved views with dynamic filters based on current attribute values. We attempt to convert these to HubSpot Active Lists where the filter logic translates to HubSpot's criteria format. Lists with complex filter logic that doesn't map to HubSpot Active List criteria are documented as manual rebuild recommendations. Static lists (explicit membership based on a point-in-time export) migrate as HubSpot Static Lists. We deliver a list-mapping matrix showing each Attio list, its HubSpot destination type, and any rebuild actions required.

## Related migrations

[![](https://flitstack.ai/platforms-trim/hubspot.webp) Migrate to **HubSpot** Every source we move into HubSpot, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/hubspot)

### [HubSpot implementation](https://flitstack.ai/services/hubspot-implementation)

[Set up HubSpot and migrate into it as one engagement.](https://flitstack.ai/services/hubspot-implementation)

[See the service →](https://flitstack.ai/services/hubspot-implementation) [**Dentrix to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dentrix/to/hubspot) [**Twenty CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/twenty-crm/to/hubspot) [**Jobber to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/jobber/to/hubspot) [**Freshsales to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/freshsales/to/hubspot) [**Insightly CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/insightly-crm/to/hubspot) [**Nimble CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/nimble-crm/to/hubspot) [**Attio to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/attio/to/salesforce-sales-cloud) [**Attio to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/attio/to/odoo-crm) [**Attio to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/attio/to/zoho-crm)

## Sources: official documentation

1. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
2. [Create and edit custom objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/object-settings/create-custom-objects)
3. [Import objects programmatically — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/import-objects)
4. [Understand property field types in HubSpot](https://knowledge.hubspot.com/properties/property-field-types-in-hubspot)
5. [Associate records on CRM objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/records/associate-records)
6. [Integration throughput and limits — HubSpot Knowledge Base](https://knowledge.hubspot.com/integrations/integration-throughput-and-limits)
7. [HubSpot Cloud Infrastructure and Data Hosting FAQ](https://knowledge.hubspot.com/account-security/hubspot-cloud-infrastructure-and-data-hosting-frequently-asked-questions)

Get a quote

## Moving from Attio to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
