Migrate from Twenty CRM to HubSpot

Twenty People records migrate directly to HubSpot Contacts. 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.

Maps to the HubSpot jobtitle standard property. 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.

HubSpot differentiates Leads from Contacts. 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.

Twenty Companies map 1:1 to HubSpot Companies. 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.

Twenty Opportunities migrate as HubSpot Deals. 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.

Twenty stage values are mapped value-by-value to the target HubSpot pipeline stage. 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.

Twenty Tasks map to HubSpot engagements of type TASK. The task body becomes the note on the engagement. The assignee resolves against HubSpot users by email. Completed tasks carry their completion timestamp as the engagement date. Tasks linked to multiple records in Twenty are logged against the primary contact in HubSpot with a reference note.

Twenty Notes migrate as HubSpot engagement notes attached to the relevant Contact or Company. The rich-text content is preserved where HubSpot's note format allows. If Twenty notes contain embedded images, those are downloaded and re-hosted as HubSpot file attachments linked to the note.

Twenty custom objects map 1:1 to HubSpot custom objects (HubSpot Enterprise only). If the destination HubSpot instance is not on Enterprise, FlitStack creates a custom object-like structure using custom properties on the standard Contact or Company object. The mapping plan specifies which approach applies before migration begins.

Twenty's phone and phonenumber fields map directly to HubSpot's phoneNumber and mobilePhoneNumber standard properties. Both fields store values as free-text strings with no format normalization applied during migration. Phone number formatting and validation—including international prefixes, dashes, parentheses, and extensions—should be run as a post-migration data-quality step using a dedicated validation tool or HubSpot workflow to standardize formats across your contact records.

Twenty allows a Person to be associated with multiple Companies. HubSpot Contacts have one primary Company association. FlitStack sets the most-recently-modified Company in Twenty as the primary in HubSpot and adds secondary associations using HubSpot's Company Contact Relationships feature (available in Sales Hub Professional and above).

Twenty owner IDs resolve to HubSpot user IDs by matching the email address stored on the Twenty workspace member. Unmatched owners are flagged before migration — your team either invites them to HubSpot first or assigns their records to a designated fallback owner. No deal lands in HubSpot without a resolved owner.

Workspace Members in Twenty are matched to HubSpot Users by email. The match is 1:1 where the email exists in both systems. HubSpot's user-level permissions and team structure are not migrated — those are destination-side configuration that your HubSpot admin sets up separately.

Original create dates from Twenty records are preserved as custom datetime fields in HubSpot (Created_From_Source__c) because HubSpot sets CreatedDate at the time of import. This preserves historical reporting continuity — your HubSpot analytics can reference the original creation date from Twenty alongside the HubSpot migration timestamp.