Migrate from Claritysoft to Twenty CRM

Claritysoft Contacts map 1:1 to Twenty's People object. Standard fields (name, email, phone, address, company association) transfer directly. Custom contact fields migrate as custom fields in Twenty, which must be pre-created in Settings → Data Model before CSV import. We flag any Claritysoft multi-email or multi-phone fields (type-labeled) for mapping to Twenty's single-value email and phone fields, or as additional custom fields.

Claritysoft Accounts map to Twenty Companies. Account name becomes the Company name; linked Contact associations migrate as relationship records. Account ownership maps to Twenty's workspace Member field. Note that Twenty's Company object has minimal standard fields per GitHub issue #13953, so industry, employee count, and annual revenue must be pre-created as custom fields before import.

Claritysoft Leads with lifecycle stage New or Contacted map to Twenty People as unqualified prospects. Leads with stage Qualified map to Twenty People with a custom lead_status field. We preserve the original Claritysoft lifecycle stage in a custom field for audit. The customer chooses during scoping whether qualified Leads also generate Twenty Opportunities.

Opportunities transfer directly with amount, stage, probability, and expected close date preserved. Pipeline stages from Claritysoft map to Twenty Opportunity stage values. For multi-pipeline Claritysoft accounts, we create multiple Twenty Opportunity pipelines or use a custom pipeline_type field to distinguish, depending on the customer's preference.

Tasks migrate to Twenty Tasks with due date, completion status, and owner preserved. Linked-to record associations migrate as Twenty relationship lookups. Task assignments resolve by matching Claritysoft owner email to Twenty workspace Member email.

Claritysoft Activity records (Calls, Meetings) map to Twenty Tasks with activity type preserved in a custom activity_type field. Start time, duration, and location transfer. Linked attendees map to Twenty workspace Members by email match. Meeting notes migrate as Twenty Note records linked to the parent Task.

Claritysoft Pipeline Stages map to Twenty Opportunity stage values. Stage names, order, and probabilities transfer. We configure stage values in Twenty before Opportunity import begins. Stage probability percentages round to the nearest integer allowed by Twenty.

Claritysoft Custom Modules (Accelerator and Enterprise only) migrate to Twenty Custom Objects. We pre-create the destination schema in Twenty's Settings → Data Model before any CSV import. Module relationships to standard objects (Contacts, Accounts) migrate as Twenty relationship fields. Custom Module data migrates last because lookup dependencies must resolve against migrated standard records. Calculated field logic does not transfer.

Claritysoft Custom Fields migrate to Twenty custom fields on the corresponding object. We create all custom fields in Twenty Settings → Data Model before importing data. Calculated Custom Fields from Claritysoft Accelerator/Enterprise must be manually rebuilt in Twenty because calculated logic does not transfer. Select field options migrate as Twenty select options.

Claritysoft Helpdesk Tickets (Accelerator tier and above) migrate to a Twenty Custom Object named Ticket. Ticket status, priority, assignee, subject, and description transfer. Conversation threads migrate as Note records or a custom comment field. We note that Twenty has no native helpdesk UI; the customer uses the custom Ticket object with Twenty's standard table and detail views.

Claritysoft Projects (Accelerator tier and above) migrate to a Twenty Custom Object with linked Tasks. Milestones map to a custom milestone field or subtasks. Assignee mapping resolves via email match to Twenty workspace Members. Project-level metadata (dates, status, budget) transfers as custom fields on the Project object.

Claritysoft Users and Owners map to Twenty workspace Members. We extract distinct owner and assignee emails from all migrating records and match against the Twenty workspace Member list. Members without a matching Twenty User go to a reconciliation queue; the customer's admin provisions missing members before record import resumes. Twenty requires all members to accept invitations before owner lookups resolve during CSV import.