Migrate from Clientify to Twenty CRM

Clientify Contacts map to Twenty's Person object, which stores name, email, phone, and linked company. Standard fields (firstName, lastName, email, phone) migrate directly. Custom contact properties from Clientify require pre-creation in Twenty's Settings → Data Model before import; picklist values must be whitelisted in Twenty or the import will reject those records. We use Twenty's REST API with batch chunking to load contacts in sequences of 200 records per request, with exponential backoff on rate limit responses.

Clientify Company records map 1:1 to Twenty Company records. Company domain, industry, size, and address fields transfer directly. The Company is imported before Person records so that the Person→Company lookup relationship is satisfied at import time. If Clientify stores multiple contacts per company, each Person record receives the correct Twenty Company UUID resolved during the transform phase.

Clientify distinguishes Leads from Contacts as separate record types with source, status, and score fields. We preserve this distinction by mapping Leads to Twenty's Person object with a leadStatus custom field, or to a Lead object if the destination Twenty instance has a configured Lead module. The customer's admin decides the lead strategy during scoping. We carry the original Clientify lead score into a custom field for reporting continuity.

Clientify Deals map to Twenty Opportunities. Deal name, value, stage, owner, and expected close date migrate directly. We read Clientify's pipeline stage labels and ordering and replicate them as Opportunity Stage values in Twenty. Closed-Lost and Closed-Won statuses transfer as Stage values with probability percentages preserved in custom fields if Twenty's standard stage model requires adjustment.

Clientify pipeline configurations (stage names, ordering, probabilities) are read from the export and replicated in Twenty's pipeline settings. Each Clientify pipeline becomes a Twenty Opportunity pipeline with corresponding stage values. Stage probabilities are set as numeric values matching Clientify's percentages. If Clientify uses multiple pipelines for different lines of business, we configure multiple Twenty pipelines and map deals to the correct one using a pipelineId field resolved during the transform.

Clientify Activities (logged calls, emails, meeting notes) attached to Contact or Deal records migrate to Twenty Task and Event records. Call engagements map to Task with a callType custom field and duration preserved; email engagements map to Task with email body and timestamp; meeting engagements map to Event with start and end time, location, and attendee list. All activities link to the resolved parent Person or Opportunity via Twenty's API relationship fields. Timestamp formats are normalized to ISO 8601 during the transform phase.

Clientify custom fields on Contacts, Companies, and Deals are mapped to Twenty custom fields. We pre-create the custom field schema in Twenty's Data Model via the metadata API before import begins. Field types are matched: Clientify text fields become Twenty text fields, date fields become date fields, picklists require pre-created option values in Twenty. Custom field API names in Twenty follow the snake_case convention. If a Clientify custom field has conditional display logic, we note it in the migration report for the customer's admin to re-implement manually in Twenty.

Clientify marketing campaign records (open rates, click rates, sent volumes, campaign names) migrate to a custom Campaign object in Twenty that we define during schema design. Campaign automation logic (sending times, A/B test configurations, trigger conditions) lives in Clientify's campaign builder and cannot be extracted; we export the performance data only. The campaign metrics migrate as data rows linked to the campaign name for historical reporting in Twenty.

Clientify user records (name, email, role, active/inactive status) map to Twenty WorkspaceMember records. We match by email address as the dedupe key. Active/inactive status is preserved, but role-based permissions and team structures in Twenty require manual configuration post-import. Any Clientify owner without a matching Twenty WorkspaceMember goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Clientify contact and company tags migrate to Twenty's Tag system. Tags are stored as a flat list and linked to Person and Company records via the relationship API. Dynamic segment definitions tied to Clientify filter rules cannot be extracted; we document the active segments and their filter criteria in the migration report for manual rebuild in Twenty's filter and view system.