Migrate from Captorra to Twenty CRM

Captorra leads (inbound inquiries) map directly to Twenty People records. Email, name, phone, and source fields transfer as-is. Staff assignment fields are resolved by email match to Twenty Workspace Members — Captorra user records must exist in Twenty before the migration runs.

Captorra client contacts map to Twenty People. A Captorra contact's associated Company link becomes a relation to the Twenty Companies record using the domain or company name as the unique key. Multiple contacts per company are handled by creating one People record per contact with the same CompanyId lookup.

Captorra company records map 1:1 to Twenty Companies. Name, domain (Website), industry, employee count, and address fields migrate directly. Company phone and annual revenue map to the corresponding Twenty Company fields. Parent-company hierarchies in Captorra map to the Twenty Company relation field.

Captorra's Intake Matter and Case Management objects have no native equivalent in Twenty. We create a custom object named CaseMatter in Settings → Data Model, add all Captorra case fields as custom fields (case type, statute of limitations, practice area, case number), and map status values to a custom select field. The CaseMatter object links to the associated People record (client) and Company record (firm/defendant) via relation fields.

Captorra staff records (attorneys, intake specialists) do not become separate CRM objects in Twenty — they are Twenty Workspace Members. We resolve each Captorra staff reference by matching the staff email to an invited Workspace Member in Twenty. Unmatched staff references are flagged before migration; the firm must invite those users first.

Captorra referral source pick-list values (e.g., Google Ads, Client Referral, Partner) map to a custom select field (Referral_Source__c) on the Twenty People object. Every distinct Captorra value gets a corresponding option in the Twenty field settings under Settings → Data Model before the import.

Captorra case status values (New, In Progress, Pending, Closed Won, Closed Lost) map to a custom select field (Status__c) on the CaseMatter custom object. The value list is created in Twenty before migration. Probability and forecast category do not apply to legal case status — those are Opportunity fields in Twenty, not case fields.

Captorra's per-form custom fields (e.g., practice area dropdown, accident type, insurance carrier) become Twenty custom fields created under Settings → Data Model on the appropriate object (People for client-contact fields, CaseMatter for case-specific fields). Field type is preserved — text stays text, select stays select, date stays date. Select fields require option lists pre-created in Twenty.

Captorra notes and document references attached to leads, contacts, or matters migrate as Twenty Notes. The note body, author (resolved by email to Workspace Member), and associated People or CaseMatter record link are preserved. Inline file attachments are re-uploaded to Twenty's file storage.

Captorra activity logs (calls logged, emails tracked, follow-up tasks) map to Twenty Tasks. Task subject, due date, completion status, and the related People or CaseMatter record link transfer. Original activity timestamps are preserved on the Task record for audit continuity.

Captorra file attachments on leads, contacts, or matters are downloaded and re-uploaded to Twenty's file storage linked to the corresponding People or CaseMatter record. File size limits from Twenty's storage configuration apply — files over the default limit are flagged for manual handling.

Captorra intake workflow templates (automated lead routing, stage-gating, email triggers) do not have a counterpart in Twenty's schema. We export Captorra workflow definitions as a JSON reference document so the firm's admin can rebuild them in Settings → Workflows. The data (leads, matters, assignments) migrates — the automation logic does not.