Migrate from LegalEdge to Twenty CRM

Workflows and automation rules do not transfer — LegalEdge rules need manual rebuild in Twenty's Workflow Builder

LegalEdge automations (matter-stage notifications, deadline reminders, attorney assignment rules, billing triggers) are stored in LegalEdge's rule engine and have no exportable format. They cannot be imported into Twenty CRM. FlitStack AI extracts the LegalEdge workflow definitions as a configuration document — rule names, trigger conditions, and actions — which your Twenty admin uses to rebuild equivalent automations in Twenty's Workflow Builder. Plan 2–4 hours per significant automation for the rebuild. Workflow rebuild is the most time-intensive post-migration task for legal operations teams switching from LegalEdge to Twenty CRM.

Twenty's CSV import enforces a 20,000-record per-export limit — large LegalEdge matter databases require batched exports

Twenty's built-in CSV import caps each export at 20,000 records per file. LegalEdge instances with large matter databases (thousands of matters, tens of thousands of parties and time entries) need to be exported in batches — typically split by matter creation year, practice area, or matter status. FlitStack AI generates a batch plan specifying export filters, file naming, and the recommended upload order so no records are missed and relation resolution (via email, domain, external ID) remains consistent across batches. If LegalEdge's export interface allows programmatic filtering, FlitStack uses it to produce pre-sliced CSV files matching Twenty's import limits.

Custom fields must exist in Twenty before CSV import — the LegalEdge field pre-creation step is mandatory and cannot be skipped

Twenty's Data Model requires custom fields to be created in Settings → Data Model before any CSV import can reference them. This is a schema-first design: the import tool creates records and populates existing fields — it cannot create fields on the fly. For LegalEdge migrations with 10+ custom matter fields (practice area, jurisdiction, billing arrangement, statute of limitations, venue, opposing party, insurance carrier), FlitStack delivers a field creation checklist specifying field names, types (select, text, number, date, checkbox), and pick-list options for each. Admins must complete this checklist before the migration import runs — failing to do so results in those columns being silently skipped during import.

LegalEdge party-role pick-list values require a custom select field in Twenty — no native role-based contact model exists

LegalEdge distinguishes between party types using a role pick-list (Lead Attorney, Opposing Counsel, Client, Expert Witness, Court, Insurance Adjuster, Mediator) that is intrinsic to the matter-party relationship. Twenty CRM has no equivalent native role concept on People records — a Person record has no built-in role field for attorney-client relationships. FlitStack maps each LegalEdge party role to a custom select field (Party_Role__c) on the Twenty People object. The pick-list values must be defined in Twenty's Data Model before the People import. Without this field pre-created, role information from LegalEdge cannot be recovered — it is not stored in any other field.

Matter-to-Opportunity foreign key resolution requires email matching against Twenty workspace Members before the migration runs

LegalEdge matter assignments (which attorneys are on each matter) resolve in Twenty to Opportunity.accountOwner and People assignee fields. This resolution depends on Twenty workspace Members being invited and accepting their invitations before the migration runs. Twenty's documentation explicitly states that user references must exist in the workspace before import — if an attorney's email in LegalEdge does not match an invited Twenty user, the assignment cannot map and the record lands without an owner. FlitStack AI runs a pre-flight owner audit against LegalEdge's attorney list, comparing email addresses against invited Twenty Members, and flags any unmatched attorneys so your admin can invite them before the migration window opens.