Migrate from CompanyHub CRM to Twenty CRM

CompanyHub Contact records map directly to Twenty People. The CompanyHub email address serves as the dedupe key and becomes the primaryEmail field in Twenty. Custom fields on Contact (phone, address, industry, custom selects) map to typed custom fields on the Twenty People object. If the CompanyHub Contact references a linked Company, we resolve that Company to a Twenty Company and set the companyLink relation on People before inserting. Original Lifecycle Stage values from CompanyHub custom properties migrate to a custom select field on People for reporting continuity.

CompanyHub Company records map to Twenty Company records using the domain field as the dedupe key, which becomes the website field in Twenty. Company address, industry, size tier, and custom fields transfer to typed Twenty Company fields. Twenty Company is created before any People import so that the companyLink relation is satisfied at the moment of People insert.

CompanyHub Deal records map to Twenty Opportunity records. Standard fields (amount, expectedCloseDate, probability) migrate to the equivalent Twenty Opportunity fields. The CompanyHub pipeline stage becomes a custom select field on Opportunity and we also write the original stage name to a custom field for continuity. We resolve CompanyHub's linked Company and Contact to their Twenty equivalents before inserting Opportunities so that the relation fields are satisfied.

CompanyHub's customizable pipeline stage names and order are captured during discovery and mapped to a Twenty custom select field called dealStage on the Opportunity object. We create the select options in the same display order as CompanyHub with the same labels. Probability percentages from CompanyHub stage settings are noted for manual configuration in Twenty's pipeline settings post-migration.

CompanyHub Task records map to Twenty Task records with title, dueDate, assignee (resolved via owner email match), and completion status preserved. Tasks that were auto-generated by UTrons workflows are flagged in the migration report with a note that the trigger rule requires a new automation in Twenty. Manually created tasks migrate as standard Twenty Tasks.

CompanyHub email sync records are migrated as Twenty Tasks with an email subtype. Subject, body, timestamp, and recipient details transfer. We flag that CompanyHub's API may return only metadata without full message body content in some cases; we migrate what the payload contains and document any records where body text is absent. The link to the associated People record is resolved at migration time.

CompanyHub Custom Tables (Properties, Courses, Payments, etc.) map to Twenty custom objects. Because CompanyHub's API does not expose Custom Table field definitions programmatically, we request customer-provided screenshots or field documentation during discovery. We pre-provision each Twenty custom object with matching field names and types before any row data is imported. Many-to-many relation fields between Custom Tables and standard objects map to Twenty's relation field types. This is the highest-risk mapping step and the primary reason for pre-provisioning.

CompanyHub unlimited custom fields on Contacts, Companies, and Deals transfer to Twenty custom fields on People, Company, and Opportunity. We export field definitions (name, type, select options) alongside field values so that Twenty custom fields are created before row imports begin. Picklist-type custom fields become Twenty select or multi-select fields with the same option set.

CompanyHub Owners map to Twenty Members. We resolve by email match against the Twenty workspace members list. During discovery we confirm all owners referenced in CompanyHub data have a corresponding Twenty account, because Twenty requires users to exist before importing records that reference them as assignees. Any CompanyHub owner without a Twenty match goes to a reconciliation queue for the customer to provision before record import resumes.

CompanyHub Quotes (Professional+ tier) do not have a direct equivalent in Twenty CRM. We migrate Quote line items, totals, and template references into a set of custom fields on the related Opportunity record: quoteTotal, quoteLineItems (as a text summary), and quoteTemplate reference. Full Quote PDF documents cannot be migrated programmatically; we deliver a written list of Quote record IDs and recommended steps for manual re-creation in Twenty.

CompanyHub Notes attached to Contacts, Companies, or Deals migrate to Twenty Note records linked via the relation field to the target People, Company, or Opportunity. Note body transfers as text content. Note timestamps preserve the original creation date for timeline continuity. Attachments stored in CompanyHub Notes are listed separately for manual upload to Twenty because the CompanyHub API does not expose attachment binary content in all cases.