Migrate from MyCase to Twenty CRM

MyCase contacts map directly to Twenty People. The primary company association (if any) becomes the People.companyId link in Twenty, preserving the firm relationship. Original contact IDs are preserved in a custom field for traceability and delta-run de-duplication. FlitStack AI also verifies email uniqueness before loading to avoid duplicate People records.

MyCase company/firm records map to Twenty Companies. Firm name, address, phone, and website transfer directly, and any custom fields on the company record are recreated via Settings → Data Model before import. Parent-subsidiary firm hierarchies in MyCase map to the Twenty Companies parentId field if the relationship structure is two-level; deeper hierarchies are flagged for manual resolution.

MyCase matters are the core legal record and map to Twenty Opportunities representing the client engagement. Case number, practice area, status, open/close dates, and assigned attorney map to corresponding Opportunity fields. The case's client (Contact) becomes the Opportunity's linked Person.

MyCase practice areas (litigation, transactional, estate planning, etc.) map to Twenty Opportunity Stage values. Each practice area becomes a distinct stage so the pipeline kanban view reflects the firm's actual matter progression. Stage-entered dates from MyCase are preserved as custom datetime fields.

MyCase time entries (billable hours, activity logs tied to matters) require a custom object in Twenty. Fields include date, hours, description, billing rate, and matter reference. IOLTA trust account associations cannot translate — these must be reconstructed in Twenty's accounting integration.

MyCase invoices, trust account transactions, and IOLTA records have no direct equivalent in Twenty. These are preserved as a custom object for historical reference, but the financial reconciliation logic must be rebuilt outside Twenty or via a custom integration. FlitStack AI can export a detailed billing ledger CSV to assist with the rebuild.

MyCase tasks associated with cases map to Twenty Tasks with the parent Opportunity linked via the opportunityId field. Due dates, assignees, status, and description transfer; assignee resolution uses email matching to Twenty Workspace Members. Tasks created by MyCase workflows (automated deadline creation) do not migrate — those automation rules are not portable and must be rebuilt in Twenty's workflow builder.

Free-form notes on MyCase cases and contacts map to Twenty Notes. Rich-text formatting in MyCase notes is preserved where the export format allows, and the note body is transferred as-is. Notes linked to specific contacts or cases are attached to the corresponding Twenty People or Companies record, maintaining the contextual relationship for future reference.

MyCase Drive documents and case file attachments do not export via the API in a directly migratable format. FlitStack AI provides a file inventory list so your team can re-upload documents to Twenty manually or via API after migration. Documents are not lost — they require a separate upload step.

MyCase custom fields on cases (e.g., court jurisdiction, opposing counsel, filing deadline) are recreated as custom fields on the Twenty Opportunity object via Settings → Data Model. Field type mapping applies: text fields, date fields, and pick-lists translate to their Twenty equivalents.

MyCase custom fields on contacts (e.g., bar number, practice focus, referral source) are recreated as custom fields on the Twenty People object via Settings → Data Model before the migration runs. Email, phone, and address fields map directly; legal-specific attributes require custom field creation and type mapping (text, picklist, date) to ensure data integrity during the CSV import.

MyCase users and staff members are mapped to Twenty Workspace Members. Email-based matching links MyCase owner IDs to Twenty user accounts. Unmatched users are flagged before migration — invitations must be sent and accepted in Twenty before owner assignment can resolve.

MyCase's client-facing portal access flags and client portal activity history have no direct equivalent in Twenty. Client portal status is preserved as a custom field on the People record for reference, but the portal itself must be reconfigured in Twenty.

MyCase workflows that auto-create tasks on case creation, send deadline reminders, or fire based on matter status changes cannot be migrated. Twenty's workflow builder (Pro/Organization tiers) must be used to recreate these. FlitStack AI exports workflow definitions as a rebuild reference document for your Twenty administrator.