Migrate from OneAdvanced Legal to Twenty CRM

OneAdvanced Legal clients map directly to Twenty People records. The client name splits into FirstName and LastName where available, otherwise the full name writes to a combined name field. Email, phone, and address fields map 1:1. A clientId foreign key is preserved in a custom Source_System_ID__c field for delta-run traceability.

Where OneAdvanced Legal stores a client organisation name alongside individual client contacts, FlitStack AI creates a Twenty Company record and associates the People record via companyId. This follows Twenty's relational import order: Companies first, then People linked to the parent company.

OneAdvanced Legal matters map to Twenty Opportunities but require transformation: a matter has a client, an open/closed status, a matter type (litigation, conveyancing, etc.), and a reference number. These map as Opportunity.name (matter reference), Opportunity.stage (mapped from matter status), and Opportunity probability set by your defined stage-to-probability table. Matter type becomes a custom Opportunity field (Matter_Type__c pick-list).

Twenty has no native matter object. For legal firms that need matter records as first-class entities, FlitStack AI creates a Matter custom object in Twenty before import, populating fields like Matter_Reference__c, Matter_Type__c, Practice_Area__c, and opened/closed dates. The Opportunity then links to the Matter via a relation field.

OneAdvanced Legal time entries (date, duration, description, billable flag, rate) have no direct Twenty equivalent. We create a Time_Entry__c custom object with fields: Entry_Date__c, Duration_Minutes__c, Description__c, Billable__c, Rate__c, and link it to the People record via a relation. Total billable hours per client are summarised in a read-only Total_Billable_Hours__c field on the People record.

OneAdvanced Legal bills contain invoice number, date, amount, and status. We create an Invoice__c custom object in Twenty with those fields plus Invoice_Number__c, Invoice_Date__c, Amount__c, Status__c, and link it to the associated People record. Note that Twenty does not process payments — the invoice record is a reference document only.

OneAdvanced Legal documents (letters, forms, briefs) attach to matters and clients. We import them as Twenty Notes attached to the relevant People or Opportunity record. File attachments are re-uploaded to Twenty's file storage. The note body records the document type and reference from the source system.

Both platforms expose an object called Task. OneAdvanced Legal tasks attached to matters (deadline, description, assignee, priority) map 1:1 to Twenty Tasks. The due date, task body, and assignee email are preserved. Task completion status is mapped to Twenty's boolean completed field. Any custom task flags (urgent, billable) become custom checkboxes on the Twenty Task record.

OneAdvanced Legal custom properties — practice-area flags, client-risk ratings, matter-source codes, and any firm-defined property — map to Twenty custom fields on the appropriate object (People, Company, Opportunity, or a custom Matter object). Each custom property requires a matching field to be pre-created in Twenty's Settings → Data Model section before the migration runs. FlitStack AI delivers a field-creation checklist during the planning phase listing every custom property, its target object, field type, and pick-list values so nothing is missed before import begins.

OneAdvanced Legal practice workflows (matter intake gates, billing approval chains, document production triggers) are platform-native and do not export. FlitStack AI provides a structured reference export of your workflow definitions so your Twenty admin can rebuild them in the Twenty workflow builder.