Migrate from Dibcase Legal Case Management to Twenty CRM

Dibcase clients map directly to Twenty People records. Each client is an individual — attorney, claimant, or paralegal — and lands as a Twenty Person with name, email, phone, and address fields. Dibcase client IDs are preserved as Source_System_ID__c for delta-run de-duplication and audit traceability.

Dibcase marks clients as billable or non-billable for its tier-based billing. Twenty has no native billable flag on People. We migrate the flag as a custom select field (Source_Billable__c) with values Active, Deferred, Inactive, Other — preserving the Dibcase billing classification for financial reconciliation after migration.

Dibcase firms (law firms or disability practices) map to Twenty Companies. Firm name, domain/website, industry, phone, and address fields migrate directly. Dibcase firm IDs are stored as Source_System_ID__c on the Company record. Multi-office firms collapse to one Company record with address as a custom field for secondary locations.

Each Dibcase case becomes either a Twenty Opportunity (for firms treating cases as revenue-bearing matters) or a custom-case object (for firms needing SSA-specific fields not available on Opportunity). We recommend the custom-case object path for SSA/personal-injury practices — it preserves SSA form types, disability identifiers, and hearing dates as native custom fields without polluting the Opportunity sales pipeline.

Dibcase case types — Social Security Disability, VA Claims, Personal Injury, Workers Compensation — map to a custom pick-list field (Practice_Area__c) on the Twenty case object. Each value is mapped one-to-one. Firms with fewer practice areas may collapse PI and WC into a single 'Civil Litigation' value if Twenty's pick-list limit is a constraint.

SSA-specific Dibcase fields — SSA Claim Number, Disability Onset Date, CDI/CE Date, RFC Date, SGA Amount — have no Twenty native equivalent. We create text and date custom fields on the case object for each SSA field, preserving the original values verbatim so SSA administrative staff can verify claim continuity after go-live.

Dibcase case statuses (Active, Deferred, Inactive, Closed, Archived, Rejected Lead) map to a custom pick-list (Case_Status__c) on the case object. The SSA disability workflow stage values (Initial Claim, Reconsideration, Hearing, Appeals Council, Federal Court) are mapped separately as a SSA_Workflow_Stage__c pick-list — critical for firms that track case progress across the multi-step SSA adjudication process.

Dibcase stores attorney names on case records. We resolve each attorney by email against Twenty Workspace Members. Matched attorneys are recorded as the Opportunity owner or a case-team member. Unmatched attorneys are flagged as custom text fields (Assigned_Attorney_Name__c, Assigned_Attorney_Email__c) for manual Twenty user assignment before go-live.

Paralegal assignments on Dibcase cases migrate as text and email custom fields on the Twenty case object (Paralegal_Name__c, Paralegal_Email__c). Where Dibcase records reference a paralegal not yet in Twenty as a Workspace Member, the assignment migrates as a plain-text field value flagged for admin onboarding. A pre-migration report surfaces each unresolved paralegal so your admin can invite or create the corresponding Twenty user before records land and finalize case-team assignments.

Dibcase files stored in Dropbox, Google Drive, or AWS are retrieved via the integration APIs and re-uploaded as Twenty Files on the related Case Opportunity or Person record. Dropbox and Drive file URLs are also preserved as custom URL fields (Original_File_Link__c) for reference and audit continuity.

Dibcase notes map directly to Twenty Notes. Notes are attached to the related Case Opportunity or Person record. Original timestamps and author names are preserved. Rich-text formatting is simplified to plain text to avoid compatibility issues in Twenty's note renderer.

Dibcase case tasks and deadlines map to Twenty Tasks linked to the related Case Opportunity. Task due dates, descriptions, and assignee email resolution follow the same owner-matching logic as attorney assignments. Open/closed status maps to Twenty's completed checkbox.

Dibcase communication logs — calls, emails, meetings — are stored as Notes on the Case Opportunity with a type prefix in the note body (e.g., '[Call]'). Original timestamps and direction (inbound/outbound) are preserved in the note content. Calendared meetings with SSA staff or clients become Tasks with a meeting-type description.

Dibcase's ERE session logs (SSA download history, exhibit pulls, folder retrievals) have no Twenty native equivalent. We preserve ERE download history as Notes on the Case record with timestamps and SSN reference, allowing SSA administrative staff to consult the full SSA portal activity trail during the transition period. However, the Dibcase ERE connectivity mechanism cannot be migrated — ERE session state, automated download schedules, and SSA portal login tokens are lost at cutover. Teams must rebuild SSA portal connectivity using SSA's own API or establish manual SSA portal access workflows post-migration.