Migrate from Aderant Milana to Salesforce Sales Cloud

Milana Matters have no direct Salesforce equivalent. The migration plan offers two paths: map Matters to Opportunities using the Matter name as Opportunity Name with Amount = billing value, or create a custom Matter__c object in Salesforce keyed by Matter ID. The custom object path is preferred for firms with complex multi-party matters that do not map cleanly to an Opportunity sales-cycle model.

Milana due dates are structured calendar entries tied to Court Rules. These map to Salesforce Tasks with a custom Milana_Deadline__c checkbox field set to TRUE so that a custom list view can isolate docketing entries from general CRM tasks. Original court rule reference preserved in Task.Description for audit continuity.

Milana Party records with Party Type = Attorney map to Salesforce Contacts for non-user records and to Salesforce Users for billable attorneys. The attorney Bar Number field maps to Bar_Number__c on Contact. Email address is the match key for User resolution. Unmatched attorneys become Contacts only; the firm decides whether to provision Salesforce licenses.

Milana Party records with Party Type = Client map to a Salesforce Account representing the client organization, with a primary Contact record for the relationship owner. Corporate clients map to Account with Industry set via value-mapping; individual clients map to Account (as Person Account if Salesforce Person Accounts are enabled) with Contact as the named attorney relationship.

Opposing counsel and witness records in Milana map to Salesforce Contacts with a custom Party_Role__c pick-list field storing the Milana Party Type value. This preserves the role distinction that Salesforce's standard Contact model does not natively capture. The migration plan flags these contacts for manual review of address and contact information accuracy before the full run.

Milana Court Rules (look-forward periods, skip rules, absolute deadlines) have no Salesforce standard equivalent. A custom Court_Rule__c object is created with fields for Rule_Code__c, Look_Forward_Days__c, Skip_Rule_Text__c, and a lookup to the Matter__c object. The rule enforcement logic (automated escalation, email alerts) must be rebuilt in Salesforce Flow post-migration.

Milana Docketing Constraints define filing restrictions (e.g., 'No filings within 30 days of trial date'). These migrate as custom text or pick-list fields on the Matter__c object. Complex multi-constraint rules with conditional logic are preserved as a concatenated text block in Constraint_Logic__c for manual Salesforce admin review and Flow conversion.

Milana Time Entries (hours, rates, LEDES codes, billable/non-billable flag) map to a custom Time_Entry__c object with a lookup to the Matter__c and Contact records. The Event object is used for attorney calendar reconstruction only. LEDES billing codes are stored as a custom pick-list field (LEDES_Code__c) mapped value-by-value from Milana's billing code table.

Milana expense records migrate as a custom Expense__c object linked to the Matter__c record via a lookup relationship, with fields for Expense_Type__c (pick-list), Amount__c (currency), Date__c, and Reimbursed__c (checkbox). Native Salesforce expense management would require a third-party AppExchange product; FlitStack migrates the historical expense data only and does not configure expense approval workflows or reimbursement automation post-load.

Milana document attachments and court-filing artifacts are downloaded from Aderant's cloud storage and re-uploaded to Salesforce Files attached to the relevant Matter__c record via ContentDocumentLink. File size limits apply (Salesforce default 25MB per file; larger documents require Salesforce CRM Content Advanced). Inline images in Milana notes are extracted and re-hosted.

Milana user accounts (attorneys, paralegals, admins) resolve by email match to Salesforce User records. Unmatched users are flagged before migration. The firm must provision Salesforce licenses for Milana users who need CRM write access; read-only migration does not consume Salesforce licenses.

Any Milana custom field defined outside Aderant's standard schema maps to a Salesforce custom field on the corresponding Salesforce object. Field type is mapped per Salesforce's supported types: text, number, pick-list, date, datetime, checkbox, currency. Milana multi-select fields become Salesforce multi-select pick-lists. Unsupported types default to text.