Migrate from Aderant Milana to Twenty CRM

Milana Client records map directly to Twenty Companies. Client name maps to Company.name, primary address maps to the company's address fields, and industry can be set as a custom select. Multi-office clients create one Company record with address as the primary; branch offices can be tracked via a custom field.

Milana Contact records (attorneys, paralegals, opposing counsel, client representatives) map to Twenty People. Each person is linked to their associated Company via companyId. Role or relationship to a matter is preserved as a custom select field on the Person record.

Milana Matter is the core record but Milana's matter model includes billable hours, court info, and legal status fields that don't exist in Twenty's Opportunity. We map Matter.name to Opportunity.name, Matter.client to the related Company, Matter.status to a custom Opportunity status field, and billable amounts to Opportunity.amount. Legal-specific fields (court, judge, opposing counsel) become custom fields on the Opportunity.

Milana deadline events and calendar entries map to Twenty Tasks. The task title captures the deadline description, dueDate maps to Task.dueDate, and the assigned user is resolved by email match against Twenty Workspace Members. Calendar type (court hearing, filing deadline, client meeting) becomes a Task.customField.

Milana document records and file attachments associated with matters become Twenty Notes. The Note body captures document metadata (title, date, type) and a link to the re-uploaded file. We re-upload files to the attachment storage linked from the Note record.

Milana attorney and user records map to Twenty Workspace Members by email resolution. The Milana user email must match an invited Twenty workspace member to resolve correctly. Attorney role classifications such as partner, associate, paralegal, or contract attorney are preserved as a custom text field on the Workspace Member record for permissions and assignment context across matters and opportunities.

Milana's bill and invoice records have no direct Twenty CRM equivalent. We create a custom Invoice object in Twenty with fields: invoice number, amount, date, status, and a lookup to the related Opportunity (matter). Invoice line items become a second custom object linked to Invoice.

Milana time entries track billable hours per matter and attorney. We create a custom TimeEntry object with fields: hours, date, attorney (lookup to WorkspaceMember), matter (lookup to Opportunity), description, and billing status. TimeEntry links to both the attorney and the matter Opportunity.

Milana user-defined fields on any object map to Twenty custom fields on the corresponding object. Before import, FlitStack creates all custom fields in Twenty's data model so the CSV import can populate them. Field types are mapped: Milana text → Twenty text, Milana date → Twenty date, Milana picklist → Twenty select.

Milana's court rules library is a legal-domain knowledge base with no CRM equivalent. We do not migrate it. Firms must use Milana or a dedicated legal rules provider for court rule lookups post-migration. The rules data can be exported as a reference document.

Milana's automated docketing rules (trigger-based calendar event creation from court rules) have no direct Twenty CRM equivalent. Twenty's workflow builder handles CRM-level automation but not court-rule-driven event generation. We export Milana workflow definitions as a rebuild reference for the firm's legal operations team.

Milana tracks client trust account balances and insurance requirements as part of matter records. These are financial/accounting constructs outside Twenty CRM's scope. We preserve them as custom fields on the Company or Opportunity for reference only; the accounting logic must live in a dedicated legal accounting system.