Migrate from Comet Suite to Twenty CRM

Direct object-to-object map. Twenty People stores first name, last name, email, phone, job title, and company link. If Comet Suite stores multiple phone types (mobile, work, home), we map each to Twenty's single Phone field or surface extras as a custom field.

Direct map. Twenty Companies stores name, domain, industry, employee count, annual revenue, and address fields. If Comet Suite uses a parent-child company hierarchy, the parent link maps to Twenty's Parent Company relation field. We preserve all standard company fields and ensure domain values are normalized for matching.

Direct object map. Twenty Opportunities store deal name, amount, close date, stage, and assignee. Stage pick-list values from Comet Suite are mapped value-by-value into Twenty's stage field before the import runs. Probability and forecast data migrate as custom fields for reporting continuity.

Direct map. Comet Suite notes migrate as Twenty Notes — free-form text attached to the parent People, Company, or Opportunity record. Original create dates and author references are preserved in custom datetime fields for audit trail purposes and historical reference.

Direct map. Comet Suite tasks (action items, reminders, to-dos) migrate as Twenty Tasks linked to the parent record. Status, due date, and assignee fields map directly. Completed flag translates to Twenty's completed boolean to reflect task state accurately.

Comet Suite call logs migrate as Twenty Tasks with type set to 'Call'. Original timestamp, duration, and owner are preserved as custom fields. Call outcome or disposition maps to a custom select field in Twenty for follow-up tracking.

Email activities from Comet Suite become Twenty Tasks with type set to 'Email'. Subject line maps to the Task name. Body content migrates as task description. Thread or message ID preserved in a custom field for reference linking.

Meeting records migrate as Twenty Events with original start and end times preserved. Attendee lists from Comet Suite map to Twenty's event participants or are stored in a custom text field. Location and meeting notes migrate as event description.

Comet Suite custom objects map 1:1 to Twenty custom objects. Each custom object must be created in Twenty Settings → Data Model before import. Custom object relationships (N:N junctions) map to Twenty relation fields on the custom object for referential integrity.

Comet Suite custom fields on People, Company, Deal, or custom objects require pre-creation in Twenty's data model before the migration. We generate a custom field manifest from Comet Suite and create them in Twenty before importing data, ensuring field existence at import time.

Comet Suite owner IDs are resolved by email match against Twenty workspace members. If a Comet Suite owner has no matching Twenty member at migration time, their records are assigned to a fallback member and flagged for post-migration re-assignment to maintain data integrity.

If Comet Suite supports N:N contact-to-company associations, we migrate one primary company as the People.companyId link and surface secondary companies in a custom text field for reference. Twenty does not support multi-company per contact natively, so this preserves full visibility.