Migrate from My Legal Software to Twenty CRM

Twenty CRM has no native legal matter object — matters become Opportunities with custom fields

My Legal Software's entire data model orbits the Matter (case) record: case number, practice area, billing rate, trust balance, responsible attorney, and originating attorney all live on the matter. Twenty CRM has no legal matter object — matters map to Opportunities and the legal metadata becomes custom fields. Custom fields must be created in Settings → Data Model before any CSV import runs, because Twenty's import creates records, not fields. FlitStack delivers a pre-flight custom field checklist and creates Case_Number__c, Practice_Area__c, Billing_Rate__c, Trust_Balance__c, and Originating_Attorney__c on the Opportunity object before the migration sequence starts. If a custom field is missing, the import skips the column silently and the data is lost.

Twenty CSV import requires parent records to exist first — Companies before People, People before Opportunities

Twenty CRM's import engine enforces referential integrity: you cannot import a Person with a companyId reference if the Company record does not already exist, and you cannot import an Opportunity linked to a Person that has not yet been created. My Legal Software stores contacts and matters in a flat or semi-relational structure where circular matter references are possible (e.g., related matters). FlitStack sequences the migration to respect Twenty's dependency order: Companies first, then People with companyId links, then Opportunities referencing people and companies, then Tasks. Any circular matter-to-matter references in My Legal Software are flagged during the audit phase and resolved by assigning one matter as the primary — duplicate matter records get a Related_Matter__c custom field pointing to the source system ID.

Workflows, billing automations, and trust-accounting rules do not migrate — must be rebuilt in Twenty's workflow builder

My Legal Software workflows, billing automation rules (trust-accounting triggers, matter-stage billing actions), and automated legal process sequences are platform-specific and have no transferable format. Twenty CRM's workflow builder uses a different automation model — triggers on record creation, field updates, and time-based actions. FlitStack AI migrates data and schema only; workflows and automations must be rebuilt manually. We provide a Workflow Reconstruction Reference document that enumerates every My Legal Software workflow with its logic, conditions, and actions so your team can recreate them in Twenty's workflow builder. Trust-accounting logic (retainer tracking, client trust ledger entries) has no functional equivalent in Twenty CRM and must be handled in a separate accounting system post-migration.

Twenty's 20,000-record per-import limit means large My Legal Software datasets must be chunked

My Legal Software practices with 40,000+ matters, 80,000+ contacts, and 200,000+ time entries exceed Twenty CRM's documented 20,000-record per-CSV-import ceiling. FlitStack splits large exports into sequential batches by object type and import order, maintaining referential integrity across batches using the source_system_id cross-reference. The delta-pickup window runs after all batches complete, capturing any records modified during the chunked migration window. Practices with more than 100,000 total records should budget additional time for multi-batch sequencing and pre-migration data audit to identify inactive records that can be archived rather than migrated.

Multi-contact matter assignments collapse to a single primary contact link in Twenty CRM

My Legal Software allows multiple contact roles on a matter (primary contact, billing contact, referring contact, opposing counsel) with each role independently linked to the matter. Twenty CRM's Opportunity Contact Roles model supports only one primary contact role per opportunity. FlitStack migrates the most-recently-modified contact association as the primary (maps to Opportunity.peopleId), and preserves the other contact roles as a custom multi-select field (Other_Contact_Roles__c) containing the contact names and role types from My Legal Software. During reconciliation, your team decides whether to surface additional contacts on the Opportunity as Notes with role context, or use a custom junction object if Twenty's custom object model is preferred.