Migrate from CentraHub CRM to Twenty CRM

CentraHub Account records map directly to Twenty Company records. The Account ID becomes the primary dedupe key during import. We write Companies first in the migration sequence because Twenty's Person-to-Company relationship requires the Company to exist before a Person can be linked to it. Account address fields (street, city, state, country, postal code) map to Twenty's address compound field, and the Account name maps to Company name.

CentraHub Contact records map to Twenty Person records. We resolve the parent Company by matching the Contact's Account reference to the Account ID we imported in the Companies phase. If a Contact has no Account assignment, we create a stub Company record to satisfy the foreign key constraint. Contact name fields, email, phone, job title, and standard address fields map directly. We preserve the Contact's created date and last modified date as Twenty's createdAt and updatedAt.

CentraHub Leads map to Twenty Person records in the same object as Contacts. We apply a qualification filter based on Lead status and created date to determine whether to treat the record as a raw lead (no Company attachment) or a qualified lead (attached to a Company). The original Lead status is preserved in a custom field for segmentation. Any Lead without an email address is flagged as incomplete and held in a reconciliation queue for the customer's admin to complete or suppress.

CentraHub Deals map to Twenty Opportunities. The Deal's associated Account maps to the Opportunity's Company via the Company lookup. We map deal amount, close date, and stage name directly. Stage matching is performed against Twenty's default pipeline stages, and any CentraHub stages with no direct match are flagged for the customer to configure before migration runs.

Each unique CentraHub Deal stage name becomes a Twenty Opportunity stage label. Stage probabilities migrate from CentraHub to Twenty if they exist as custom fields. We configure the pipeline in Twenty's workspace settings before the Opportunity import phase begins, and we flag any stage names that differ from Twenty's defaults so the customer can decide on normalization before cutover.

CentraHub Tasks map to Twenty Task records. The task due date, priority, status, and description fields migrate directly. We resolve the task's associated Contact or Account reference to the corresponding Person or Company in Twenty and attach the task to the correct record via the targetObject and targetRelatedObject fields. Standalone tasks with no association are imported as orphaned tasks flagged for manual reassignment.

CentraHub call activity records map to Twenty Task records with type = call. Call duration, disposition, and outcome stored in CentraHub custom fields migrate to custom fields on the Twenty Task. The activity timestamp becomes the Task's due date and completion date. We attach the call task to the related Person or Company via the targetObject lookup.

CentraHub email activity logs migrate to Twenty Comment records on the Person record. The email subject, body (plain text or HTML-stripped), sender, and recipient map to Comment fields. We attach each Comment to the Person record via the targetObject field. Email activity timestamps are preserved as the Comment creation date.

CentraHub Notes attached to Contacts, Accounts, or Deals migrate to Twenty Comment records with type = note. The note body migrates as the Comment content, and the associated Person or Company lookup is resolved via the Person/Company mapping. Notes without a parent association are flagged and held for manual review.

CentraHub per-module custom fields map to Twenty workspace-level custom fields. We extract the full custom field schema per module during discovery, map each field's data type to the nearest Twenty field type (text, number, date, single-select, multi-select, URL, phone, email), and create the custom fields in Twenty before the corresponding record import phase. Picklist values map to Twenty select options; multi-select picklists map to Twenty multi-select fields.

CentraHub tags applied across objects migrate to Twenty Tag records. Tags are stored as tag-to-record associations in both systems, so we preserve the full tag list per object type and re-attach them post-import using Twenty's tag association API. Tags that do not match exactly are flagged for manual mapping during reconciliation.

CentraHub Owner records map to Twenty WorkspaceUser records. We resolve owners by email match. Any CentraHub Owner without a matching Twenty user is held in a reconciliation queue for the customer's admin to provision before the Person and Opportunity import phases begin, because OwnerId references are required on most Twenty standard objects.