Migrate from CaseManager to Twenty CRM

CaseManager contacts map directly to Twenty People. Each contact's name, email, phone, and job title become Twenty People fields. CaseManager contacts without a company link create standalone People records — users should consider linking to a default company or creating the primary company record first to maintain the relationship.

CaseManager company records map to Twenty Companies with industry, size, and domain preserved. Parent-child company hierarchies in CaseManager map to Twenty's parentCompany relation. When multiple CaseManager contacts share one company, they all link to the same Twenty Company record via companyId.

CaseManager cases map to Twenty Opportunities. The case name becomes Opportunity name; case value or amount maps to Opportunity amount; case status maps to Opportunity stage via value-mapping (Open→New, In Progress→Working, Closed Won/Lost→Won/Lost). Original create and close dates map to custom date fields to preserve history.

CaseManager status pick-list values map to Twenty Opportunity stage values. Each CaseManager status (Open, Pending, Closed Won, Closed Lost) receives a corresponding Twenty stage. Stage-transition timestamps in CaseManager can be preserved as custom datetime fields on the Opportunity record for audit continuity.

CaseManager priority (High, Medium, Low) has no direct Twenty equivalent. We create a custom select field called Case_Priority__c on the Opportunity object before migration. Values map value-by-value to preserve the original priority classification in the new system. The field is created in Settings → Data Model with the same picklist values that existed in CaseManager so that reporting continuity is maintained after cutover.

CaseManager per-case custom fields require Twenty custom field creation in Settings → Data Model before the import runs. Field types are mapped: text → TEXT, number → NUMBER, date → DATE, select → SELECT. Multiselect maps to MULTI_SELECT. Custom fields are created first; then migration populates them from CaseManager's field values.

CaseManager contact-level custom fields (beyond name, email, phone) migrate to custom fields on Twenty People. Boolean and select types map to Twenty's SELECT field type. Date fields map to DATE. All custom fields must be pre-created in Settings → Data Model before the CSV import runs, per Twenty's field-before-import requirement.

CaseManager logged calls, emails, and meetings map to Twenty Tasks. The activity type (Call, Email, Meeting) becomes a custom select field or the Task's body content. Original timestamps, owners, and linked contacts and cases map to Task dueDate, Task assignee (via People lookup), and the task's linked Opportunity.

CaseManager file attachments associated with cases link to Twenty Notes attached to the corresponding Opportunity. Files are re-uploaded to Twenty's storage. File size limits apply — files over the platform's attachment limit are flagged for manual download reference. The Note body carries the original attachment description or a download link.

CaseManager users are resolved by email against Twenty WorkspaceMembers. Unmatched owners are flagged before migration — the team either invites the user to Twenty first or reassigns their records to a fallback assignee. No record lands in Twenty without a valid owner lookup; orphan records are held for manual assignment.

CaseManager workflows and automations do not migrate. They must be rebuilt in Twenty's workflow builder using the exported CaseManager workflow definitions as a reference guide. We provide a workflow-export JSON and a rebuild checklist that maps each CaseManager trigger and action to its Twenty workflow equivalent so your admin can reconstruct automations without trial and error.