Migrate from Sentia to Twenty CRM

Sentia Contact records map directly to Twenty People. Standard fields (name, email, phone, address) transfer with format normalization. Any custom Contact-level properties migrate as custom fields on People. The Contact's linked Company association transfers as a Company relation in Twenty.

Sentia Company records map directly to Twenty Company. Company name is the dedupe key during import. Domain and website fields transfer to the Twenty Company URL fields. The Company-to-Contact relationship is preserved by resolving the Company reference on each imported People record.

Sentia's separate Lead object merges into Twenty People since Twenty has no distinct Lead concept. We preserve lead source and lead status as custom fields on the resulting People record. The Sentia lead_score property transfers to a custom number field. This merge happens at migration time using a transform that creates a single People record per unique email address across both Sentia Contact and Lead objects.

Sentia Deal records map to Twenty Opportunity. Deal name, amount, expected close date, and stage transfer directly. Pipeline assignment in Sentia maps to the Opportunity's pipeline in Twenty. We create the destination pipeline structure before Deal import so that stage assignment is valid at insert time.

Sentia's customizable pipeline stages map to Twenty Opportunity stage values by name proximity with explicit customer confirmation required. Stage probability percentages transfer as custom probability fields. If Sentia stages have no direct name match in Twenty's default pipeline, we create matching stages in Twenty's pipeline configuration before migration begins.

Sentia call activities map to Twenty Note records linked to the parent People or Company record. Call duration, disposition, and recording URL (if available) transfer as Note body text or custom fields. The original timestamp migrates as the Note creation date to preserve the activity timeline ordering.

Sentia email activities map to Twenty Note records. Email subject and body transfer to the Note title and body fields. The sender and recipient email addresses become part of the Note body or custom fields. The original email timestamp becomes the Note creation date.

Sentia meeting activities map to Twenty Note records. Meeting title, attendees, location, and notes transfer as Note body content. The original meeting date and duration become the Note creation date and a custom duration field.

Sentia standalone Note activities map directly to Twenty Note records with the same parent resolution logic (People, Company, or Opportunity). Rich text formatting in Sentia notes is preserved as plain text in Twenty Notes since Twenty Notes support plain text.

Sentia User records map to Twenty workspace Members. We resolve owners by email match during migration. The customer's admin must invite all team members to the Twenty workspace before data import because owner lookups require an existing Twenty User record. Users without a matching invite are held in a reconciliation queue.

Sentia custom fields on Contact migrate to custom fields on Twenty People. We discover the full field schema during discovery via Sentia's metadata API. On the Basic tier, fewer field types are API-accessible; we flag any fields unavailable for export before migration begins. All Twenty custom fields must be created in Settings → Data Model before CSV import.

Sentia record tags migrate as Tags on the equivalent Twenty record. Tags are preserved as string arrays on People, Company, or Opportunity. Where Sentia uses a hierarchical tagging taxonomy, we flatten to a single tag list with the full hierarchy path as the tag value.