Migrate from The Customer Factor to Twenty CRM

TCF contacts map directly to Twenty People. TCF stores name, email, phone, address, and job title fields — all map to corresponding Twenty People fields. TCF contacts without a primary company link to a default placeholder company in Twenty or are flagged for manual review.

TCF companies map to Twenty Companies preserving business name, domain, industry, employee count, and address fields. TCF parent-child company hierarchies map to Twenty Companies with the parent company stored on the child record via the parent CompanyId field. We verify that parent companies migrate before child records so the lookup relationship resolves correctly during import.

TCF deals map to Twenty Opportunities with amount, name, and close date transferring directly. TCF deal status (Open, Won, Lost) requires a custom mapping to Twenty Stage records that your admin creates in Settings → Data Model before migration runs. Probability percentages from TCF map to Stage probability values.

TCF estimates have no native equivalent in Twenty CRM. We create a custom Estimate object with fields for estimate number, line items (product, quantity, unit price), tax, discount, status, and linked People and Companies records. Multi-line items denormalize into a text or JSON field since Twenty custom objects don't support native line-item sub-objects.

TCF invoices require a custom Invoice object in Twenty with fields for invoice number, amount, status (Draft, Sent, Paid, Overdue), payment date, and linked People and Companies records. TCF payment history and line items store as custom fields or a denormalized text field.

TCF call logs and email records map to Twenty Tasks with subject, type (Call, Email), body content, completion status, and original timestamp preserved. Tasks link to the parent People or Companies record by record ID. Task type is set from TCF's activity type field.

TCF meeting records map to Twenty Events with subject, start time, end time, and body content preserved. Original timestamp and meeting organizer link to the parent People or Companies record. TCF meeting attendees stored as custom fields or linked via a custom Attendees object.

TCF notes map directly to Twenty Notes with body content, creator, and create timestamp preserved. Notes attach to the parent record (People, Companies, or Opportunity) via Twenty's attachment model. Rich-text formatting in TCF notes is preserved where supported. The migration maintains the chronological sequence of notes tied to each parent entity for audit continuity.

TCF users resolve to Twenty Workspace Members by email match. TCF user name and avatar data map to Twenty member profile fields. TCF role-based permissions do not migrate — these must be manually configured in Twenty Settings → Members with the same access structure recreated.

TCF file attachments re-upload to Twenty Files. Each file attaches to its parent record (People, Companies, or Opportunity) in Twenty. Original file metadata (create date, size) is not preserved by Twenty's import mechanism and stores as a custom field for reference.

TCF embeds custom fields within contact, company, and deal objects. In Twenty, custom fields that don't fit existing objects require a custom object to be created first in Settings → Data Model before fields can be added. TCF custom field types (text, number, date, pick-list) map to corresponding Twenty field types.