---
title: "Twenty CRM to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate Twenty CRM 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/twenty-crm/to/hubspot"
---

# Twenty CRM to HubSpot migration

Moving from Twenty CRM to HubSpot connects your open-source data to HubSpot's all-in-one CRM platform with lifecycle stages, deal pipelines, and marketing hub infrastructure. FlitStack AI maps every People record, Company, Opportunity, and custom object — preserving original create dates and owner assignments so your HubSpot instance reflects the full history of your Twenty workspace from day one.

Short answer

FlitStack AI migrates contacts, leads, companies, deals and deal.pipeline + deal.stages from Twenty CRM 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: 48–72 hours for under 50,000 records.

![](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/twenty-crm/to/hubspot#field-mapping)

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

Source Twenty CRM ![](https://flitstack.ai/platforms-trim/twenty-crm.webp)

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

Contact Lead Company Deal Deal.pipeline + Deal.stage

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

## What moves from Twenty CRM to HubSpot?

Twenty CRM stores data in four core objects — People (contacts), Companies, Opportunities, and Tasks/Notes — with a relational model built on PostgreSQL.

Read the full summary

HubSpot uses Contacts (with lifecycle\_stage as a single unifying property), Companies, Deals (HubSpot's term for Opportunities), and a native engagement logging system. The migration maps each Twenty People record to a HubSpot Contact, creates or links the corresponding HubSpot Company record, and converts Opportunities to HubSpot Deals with pipeline and stage preserved as HubSpot-native deal properties. Custom objects in Twenty map 1:1 to HubSpot custom objects where available, though Twenty's flexible data model may require HubSpot custom properties or custom objects to be pre-created. FlitStack's migration engine reads Twenty's REST and GraphQL APIs to pull full record payloads, resolves owner email addresses against HubSpot users, and loads data via HubSpot's Bulk API for large volumes or the CRM API v3 for smaller sets. Activity history — Tasks and Notes in Twenty — migrates as HubSpot engagements with original timestamps and associated contact links intact. Workflows, sequences, and any automation logic inside Twenty cannot migrate because HubSpot has no equivalent workflow engine that accepts imported rule definitions; FlitStack exports the workflow structure as a JSON specification your HubSpot admin rebuilds inside HubSpot's automation builder.

direct

### People → Contact

Twenty People records migrate directly to HubSpot Contacts.

How it maps

The email address is the unique identifier used for de-duplication and owner matching. Any Person without an email address is flagged as a partial record and either assigned to a default owner or held for manual review before the full migration runs.

direct

### People.jobTitle → Contact

Maps to the HubSpot jobtitle standard property.

How it maps

If the source field is empty, the property is left blank — no default value is inserted to avoid polluting reporting. Job title values are stored as free-text in both systems, so no value mapping is required.

split

### People (with no associated Opportunity) → Lead

HubSpot differentiates Leads from Contacts.

How it maps

FlitStack classifies Twenty People without an associated Opportunity as HubSpot Leads. If a Lead converts to a Contact in HubSpot post-migration, the conversion links the record to the existing Contact and preserves the original create date from Twenty as the Lead creation date.

direct

### Company → Company

Twenty Companies map 1:1 to HubSpot Companies.

How it maps

The domain field in Twenty populates the HubSpot website property. Parent-child company hierarchies in Twenty (where a company has a linked parent company) migrate using HubSpot's parent company association. Circular references are flagged and resolved by flattening to the top-level parent.

direct

### Opportunity → Deal

Twenty Opportunities migrate as HubSpot Deals.

How it maps

The deal name maps to dealname, amount maps to amount, and close date maps to closedate. Each Twenty Opportunity is associated with one Company (via companyId) and optionally linked to People records through the opportunity's contact associations.

value\_mapping

### Opportunity.stage → Deal.pipeline + Deal.stage

Twenty stage values are mapped value-by-value to the target HubSpot pipeline stage.

How it maps

If the target pipeline does not yet exist in HubSpot, FlitStack creates a default pipeline and stage set before migration. Probability and forecast category are set per stage as part of the value mapping. Teams with multiple Twenty pipelines map each one to a separate HubSpot pipeline.

******What moves 14 objects

Twenty CRM HubSpot

- People Contact 1:1
- People.jobTitle Contact 1:1
- People Lead split
- Company Company 1:1
- Opportunity Deal 1:1
- Opportunity.stage Deal.pipeline transformed

\+ 8 more in the mapping below

## How Twenty CRM 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        | Twenty CRM                                                                                                               | HubSpot                                                                                                                                     |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Contact model    | Twenty uses People as a single unified object — contacts and leads are not separated.                                    | HubSpot splits Contacts (Customers) from Leads, with lifecycle\_stage driving the distinction.                                              |
| Deal tracking    | Twenty Opportunities are standalone records with stage and amount fields, no native pipeline view beyond a kanban.       | HubSpot Deals live inside Pipelines with stage probability, forecast category, and deal-specific properties per pipeline.                   |
| Workflows        | Twenty has a workflow builder for internal automations, available on Pro and Organization tiers.                         | HubSpot's automation engine requires manual rebuild — no workflow import is supported.                                                      |
| Pricing model    | Twenty Pro is $9/user/month, self-hosting is free under AGPL-3.0, API limits are 100–200 calls/minute depending on tier. | HubSpot Free covers basic CRM; custom properties and advanced features require Starter at $20/user/month or Professional at $50/user/month. |
| Activity logging | Twenty Tasks and Notes are separate objects linked to any record via relations, with no native engagement timeline.      | HubSpot logs engagements (calls, emails, meetings, notes) on the Contact timeline with original timestamps and owners.                      |
| Custom objects   | Twenty supports unlimited custom objects on Organization tier, up to 10 on Pro, stored as PostgreSQL tables.             | HubSpot custom objects are Enterprise-only, stored in the CRM with their own properties and associations.                                   |
| API export limit | Twenty's CSV export caps at 20,000 records per export; API access is tier-gated.                                         | HubSpot's Bulk API handles up to 10 million records per import; standard API v3 handles smaller incremental loads.                          |

## Twenty CRM to HubSpot field mapping

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

******Field mapping 5 shown

Twenty CRM HubSpot

1. `name` People `firstname` Contact
2. `name` People `lastname` Contact
3. `email` People `email` Contact
4. `phone` People `phoneNumber` Contact
5. `phonenumber` People `mobilePhoneNumber` Contact

| Twenty CRM field          | HubSpot field                   | Mapping                 | Note                                                                                                                                                                                           |
| ------------------------- | ------------------------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `People.name`             | `Contact.firstname`             | transformed             | Twenty's name field splits into firstname and lastname. If the source uses a single full-name string with no delimiter, the last token becomes lastname and everything else becomes firstname. |
| `People.name`             | `Contact.lastname`              | transformed             | Extracted from the full-name field using the same split logic as firstname. Single-token names are assigned to lastname with firstname left blank.                                             |
| `People.email`            | `Contact.email`                 | direct                  |                                                                                                                                                                                                |
| `People.phone`            | `Contact.phoneNumber`           | direct                  |                                                                                                                                                                                                |
| `People.phonenumber`      | `Contact.mobilePhoneNumber`     | direct                  |                                                                                                                                                                                                |
| `People.jobTitle`         | `Contact.jobtitle`              | direct                  |                                                                                                                                                                                                |
| `People.city`             | `Contact.city`                  | direct                  |                                                                                                                                                                                                |
| `People.state`            | `Contact.state`                 | direct                  |                                                                                                                                                                                                |
| `People.country`          | `Contact.country`               | direct                  |                                                                                                                                                                                                |
| `People.company`          | `Contact.associatedCompanyId`   | transformed             | Twenty's companyId foreign key resolves to a HubSpot Company record ID. The Company must exist in HubSpot before the Contact is created — migration is sequenced Companies first.              |
| `People.createdAt`        | `Contact.createdate`            | direct                  |                                                                                                                                                                                                |
| `People.updatedAt`        | `Contact.lastupdateddate`       | direct                  |                                                                                                                                                                                                |
| `People.id`               | `Contact.hubspot_source_id`     | custom\_field\_required | Twenty's internal ID is stored as a custom text field for traceability, delta-run matching, and rollback identification.                                                                       |
| `Company.name`            | `Company.name`                  | direct                  |                                                                                                                                                                                                |
| `Company.domain`          | `Company.website`               | direct                  |                                                                                                                                                                                                |
| `Company.industry`        | `Company.industry`              | value\_mapping          | HubSpot's industry pick-list is mapped value-by-value. Unknown or blank values default to the HubSpot 'Other' option.                                                                          |
| `Company.employees`       | `Company.numberofemployees`     | direct                  |                                                                                                                                                                                                |
| `Company.annualRevenue`   | `Company.annualrevenue`         | direct                  |                                                                                                                                                                                                |
| `Company.city`            | `Company.city`                  | direct                  |                                                                                                                                                                                                |
| `Company.country`         | `Company.country`               | direct                  |                                                                                                                                                                                                |
| `Company.linkedinUrl`     | `Company.linkedin_company_page` | direct                  |                                                                                                                                                                                                |
| `Company.createdAt`       | `Company.createdate`            | direct                  |                                                                                                                                                                                                |
| `Company.id`              | `Company.hubspot_source_id`     | custom\_field\_required | Twenty's internal ID preserved as a custom text field for traceability and post-migration reconciliation.                                                                                      |
| `Opportunity.name`        | `Deal.dealname`                 | direct                  |                                                                                                                                                                                                |
| `Opportunity.amount`      | `Deal.amount`                   | direct                  |                                                                                                                                                                                                |
| `Opportunity.stage`       | `Deal.dealstage`                | value\_mapping          | Stage values are mapped to the target HubSpot pipeline stage. Probability and forecast category are applied per stage as part of the mapping.                                                  |
| `Opportunity.pipeline`    | `Deal.pipeline`                 | value\_mapping          | If Twenty has named pipelines, each one maps to a separate HubSpot pipeline. The pipeline must exist in HubSpot before migration — created during schema setup.                                |
| `Opportunity.closeDate`   | `Deal.closedate`                | direct                  |                                                                                                                                                                                                |
| `Opportunity.probability` | `Deal.closedatetype`            | custom\_field\_required | Twenty probability percentage maps to a custom number field if not natively supported in the target pipeline stage probability model.                                                          |
| `Opportunity.company`     | `Deal.associatedCompanyId`      | transformed             | Links the Deal to the migrated HubSpot Company record using the resolved Company ID.                                                                                                           |

## What to watch for in a Twenty CRM 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

### Twenty's unified People object requires a lifecycle split in HubSpot

Twenty stores contacts and leads as a single People object — there is no separate lead concept.

How we handle it

HubSpot separates Leads from Contacts and uses lifecycle\_stage to drive the distinction. FlitStack routes Twenty People without an associated Opportunity to HubSpot Leads and People with at least one linked Opportunity to Contacts. The lifecycle split is based on Opportunity association, not on any HubSpot-specific field, because Twenty does not natively store a lifecycle stage equivalent. Teams that want all contacts as HubSpot Contacts (not Leads) should specify this preference during the planning phase before migration runs.

high

### HubSpot pipelines require pre-creation before Deals can migrate

HubSpot requires a pipeline to exist before a Deal can be assigned to it — you cannot bulk-create pipelines and Deals in the same migration operation.

How we handle it

FlitStack's schema setup phase delivers a pipeline creation plan: one HubSpot pipeline per Twenty pipeline, with stage names, probabilities, and forecast categories mapped value-by-value. If your Twenty instance uses custom stage names, each one requires a corresponding stage in the target pipeline before the Deal migration step. This is a planning dependency that adds 1–3 days to the pre-migration timeline but prevents Deal import failures on migration day.

medium

### Multi-company associations collapse to a single primary Company on the Contact

Twenty allows a single Person to be associated with multiple Companies via its N:1 relation model.

How we handle it

HubSpot Contacts have one primary Company association plus optional secondary associations via Company Contact Relationships (a feature available in HubSpot Sales Hub Professional and above). FlitStack migrates the most-recently-modified Company as the primary and surfaces the rest as secondary associations. If your HubSpot instance is on Starter, secondary company associations are lost — the primary company is retained and the remainder are flagged for manual re-association post-migration.

medium

### HubSpot's marketing contact billing model has no Twenty equivalent

HubSpot charges based on the number of Marketing Contacts in your portal — contacts that have been in a marketing email, form, or list.

How we handle it

Twenty has no equivalent billing flag. When migrating from Twenty, all contacts land as standard HubSpot CRM contacts. If your team plans to use HubSpot's marketing automation (email sequences, forms, ads), those contacts may become Marketing Contacts after they engage with a marketing asset, which triggers HubSpot's billing model. FlitStack preserves a source-system flag (Migrated\_From\_Twenty\_\_c) on every record so your team can track the origin of contacts for billing reconciliation.

medium

### Twenty's custom object extensibility may exceed HubSpot Starter's capacity

Twenty allows unlimited custom objects on its Organization tier, built as PostgreSQL tables under the hood.

How we handle it

HubSpot custom objects require the Enterprise tier and have their own schema constraints (property limits, association rules, no custom junctions). Teams migrating from Twenty with complex custom object schemas — especially custom objects with many-to-many relationships to each other — may need to restructure the data model in HubSpot or upgrade to Enterprise. FlitStack audits the Twenty custom object schema during discovery and flags any custom object that cannot map directly to a HubSpot custom object.

## How the migration runs

1. ### Audit Twenty's data model and export full record payloads

   FlitStack connects to Twenty's REST API using credentials scoped to the workspace.

   What this step covers

   We export every standard object (People, Company, Opportunity, Task, Note) and every custom object as a full JSON payload — not just the fields visible in the default view. Because Twenty's CSV export caps at 20,000 records per file, we use the API for all record volumes. The audit phase also captures relationship metadata: which People are linked to which Companies, which Opportunities have which People associated, and which Tasks/Notes belong to which records. This gives us the complete relational graph before we write a single line of field mapping logic.

2. ### Design the HubSpot schema and pre-create pipelines, custom objects, and custom properties

   Before any data moves, FlitStack delivers a HubSpot schema setup plan: pipeline names and stage definitions, custom object schemas (if on Enterprise), and any custom properties needed to store Twenty-specific fields.

   What this step covers

   We also create the value-mapping tables for pick-list fields — stage names, industry values, and any custom select fields in Twenty. Your HubSpot admin executes the schema setup plan in your HubSpot portal. Once confirmed, FlitStack validates the schema is in place before triggering the migration engine.

3. ### Run a sample migration with field-level diff

   A representative slice — typically 100–500 records spanning People, Companies, Deals, and a mix of custom properties — migrates first.

   What this step covers

   FlitStack generates a field-level diff comparing each source field against the destination field value so you can verify the mapping is correct before committing. The diff surfaces issues like: wrong probability on a deal stage, blank job title where a value was expected, or a company association that failed to resolve. Your team reviews the diff and signs off before the full migration is scheduled.

4. ### Execute full migration with owner resolution and activity history

   The full migration loads all records in the correct sequence: Companies first (since Contacts and Deals have foreign keys to them), then People split into Contacts and Leads, then Opportunities as Deals with stage and pipeline mapping.

   What this step covers

   Owner IDs resolve against HubSpot users by email — unmatched owners are held in a flag report and assigned to a fallback owner you designate. Task and Note records migrate as HubSpot engagements with original timestamps and parent record links. For large volumes, FlitStack uses HubSpot's Bulk API to keep migration time within the 48–72 hour window.

5. ### Capture delta changes during cutover and run post-migration validation

   After the full migration completes, FlitStack opens a delta-pickup window of 24–48 hours.

   What this step covers

   Any record created or modified in Twenty during this window is captured and merged into HubSpot so the destination reflects Twenty's final state at go-live. Post-migration validation checks record counts, association integrity (every Deal linked to a Company, every Contact linked to at least one Company), and a spot-check of field values against the source export. An audit log records every operation. If validation fails, one-click rollback reverts the HubSpot instance to its pre-migration state.

![](https://flitstack.ai/platforms/twenty-crm.svg) Twenty CRM ![](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

**48–72 hours for under 50,000 records** Typical, smaller accounts

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

A quote scales with record count, the number of custom properties and objects in Twenty, and the degree of data-model divergence between Twenty's relational schema and HubSpot's Contact–Company–Deal model. Teams with fewer than 10,000 records and no custom objects fall at the lower end. Migrations requiring HubSpot custom object pre-creation, value-by-value stage mapping across multiple pipelines, or activity-history reconstruction (Tasks and Notes with association links) land in the mid-to-upper range. Enterprise-tier setups with 500+ custom fields push toward the ceiling of the typical range. Every quote is scoped with you; there is no self-serve pricing.

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

## Why teams move from Twenty CRM to HubSpot

- Twenty lacks native marketing automation, reporting depth, and the multi-hub ecosystem (Sales, Marketing, Service, CMS) that growing teams need to consolidate tools. HubSpot's integrated platform removes the need to stitch together separate point solutions for email campaigns, lead nurturing, and deal tracking.
- HubSpot's lifecycle stage property and contact-based reporting give sales and marketing a shared view of pipeline health from first touch to closed-won. Twenty's reporting is functional but lacks the funnel analytics and attribution models that HubSpot builds in natively at no extra cost beyond the CRM tier.
- Self-hosting Twenty means your team owns infrastructure but also owns uptime, backups, and upgrades. HubSpot's SaaS model removes that operational burden, which matters for teams under 50 reps who chose Twenty expecting to scale but found the DevOps overhead outweighing the cost savings.
- HubSpot's marketplace of pre-built integrations covers 1,000+ connected apps with no custom API work required, spanning CRM, marketing, communication, and analytics tools that teams already use. Twenty's extensibility is real but requires development effort to connect to common sales-stack tools that HubSpot connects to natively out of the box, meaning more engineering time spent on integration maintenance rather than revenue-generating activities.

Questions, answered

## Twenty CRM to HubSpot migration questions

How long does a Twenty CRM to HubSpot migration take?

Most Twenty-to-HubSpot migrations complete in 48–72 hours of clock time for datasets under 50,000 records. Larger migrations with 500,000+ records or custom object schemas that require HubSpot Enterprise custom object setup extend to 5–10 days. The longest single step is the HubSpot schema setup phase — creating pipelines, custom objects, and property definitions — which runs in parallel with the migration planning and adds 1–3 days before the first record moves.

Will my Twenty workflows migrate to HubSpot?

No. Workflows, sequences, and automation rules in Twenty do not migrate to HubSpot — HubSpot's automation engine has no import path for external workflow definitions. FlitStack exports your Twenty workflow configurations as a JSON specification that documents the trigger, conditions, and actions for each automation. Your HubSpot admin uses this as a rebuild reference inside HubSpot's workflow builder. This is true for every CRM-to-CRM migration regardless of source platform — automation logic is always a manual rebuild.

What happens to my Twenty Opportunities in HubSpot?

Twenty Opportunities become HubSpot Deals. The deal name, amount, and close date map directly. The Twenty stage maps to a HubSpot pipeline stage value-by-value — each Twenty pipeline requires a corresponding HubSpot pipeline to be pre-created. Probability and forecast category are applied per stage. Opportunities without an associated Twenty Company are linked to a primary Company record created from the Person's company data. If an Opportunity has no company link at all, a placeholder Company record is created and flagged for your team's review.

Can I migrate Twenty custom objects to HubSpot?

Yes, but the destination depends on your HubSpot plan. On HubSpot Enterprise, Twenty custom objects map 1:1 to HubSpot custom objects with their own properties and associations. On Starter or Professional, custom objects are not available — FlitStack converts them to custom properties on the standard Contact or Company object. The migration plan specifies which approach applies based on your current HubSpot tier. Any custom object relationship in Twenty that uses a many-to-many model requires a custom junction approach in HubSpot, which is documented in the field mapping plan.

What does Twenty's People object become in HubSpot — a Contact or a Lead?

It splits. HubSpot separates Leads (people not yet in an active sales process) from Contacts (people with an active relationship). FlitStack routes Twenty People with at least one linked Opportunity to HubSpot Contacts. Twenty People with no linked Opportunities route to HubSpot Leads. This is a planning-time decision — if you want all migrated people as Contacts regardless of Opportunity association, specify this before migration and FlitStack will map everything to Contact, creating Deals from any linked Opportunities.

Does the migration affect my Twenty CRM account during cutover?

No. FlitStack uses scoped read access on Twenty — your team continues working in Twenty throughout the migration. The scoped access allows us to export records but does not modify anything in your Twenty instance. A delta-pickup window of 24–48 hours after the initial migration captures any records created or modified during the cutover period. Your Twenty account is fully operational until the moment your team switches to HubSpot as the system of record.

How does FlitStack handle Twenty workspace members who don't have HubSpot user accounts?

Owner resolution matches Twenty workspace member email addresses against HubSpot user email addresses. Any Twenty owner without a corresponding HubSpot user account is flagged in a pre-migration report before the full run starts. Your team has two options: invite the user to HubSpot before migration so they can be matched automatically, or designate a fallback HubSpot user to own all records from unmatched Twenty owners. No record migrates without a resolved owner — unowned records would appear in HubSpot without an assignee, which breaks reporting.

What happens to notes and activity history from Twenty after migration?

Twenty Notes migrate as HubSpot engagement notes attached to the relevant Contact or Company record, with the original create timestamp preserved. Twenty Tasks migrate as HubSpot engagements with their body, due date, status, and assignee. If a Task in Twenty is linked to multiple records, the engagement is logged against the primary Contact and a note records the additional associations. Rich-text formatting in Twenty notes is preserved where HubSpot's note format supports it. Embedded images are downloaded and re-hosted as HubSpot file attachments.

## 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) [**Jobber to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/jobber/to/hubspot) [**Streak to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/streak/to/hubspot) [**Copper to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/copper/to/hubspot) [**Dentrix to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dentrix/to/hubspot) [**Attio to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/attio/to/hubspot) [**Freshsales to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/freshsales/to/hubspot) [**Twenty CRM to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/twenty-crm/to/salesforce-sales-cloud) [**Twenty CRM to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/twenty-crm/to/zoho-crm) [**Twenty CRM to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/twenty-crm/to/dynamics-365-sales)

## 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. [Migrating from Other CRMs — Twenty Documentation](https://docs.twenty.com/user-guide/data-migration/how-tos/migrating-from-other-crms)
6. [Data Migration — Twenty Documentation](https://docs.twenty.com/user-guide/data-migration/overview)

Get a quote

## Moving from Twenty CRM 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)
