Migrate from Aderant Milana to Pipedrive

Milana matters become Pipedrive Deals. We preserve the matter number as Deal_name and create custom fields (Matter_Number__c, Court_Venue__c, Jurisdiction__c, Case_Type__c) to carry Milana's structured data. Pipeline stage in Pipedrive maps to matter status — open matters map to active pipeline stages, closed matters map to Won/Lost.

Milana client records with firm name, address, and primary contact map directly to Pipedrive Organizations. We populate the Organization name from Milana client_name and address fields from the client address record. Multiple matters per client collapse to multiple Deals linked to one Organization.

Milana attorney and client contacts migrate to Pipedrive Persons. We map first name, last name, email, phone, and job title directly. The Person is linked to the corresponding Organization (the client firm or opposing counsel organization) using Pipedrive's org_id field.

Milana calendar events become Pipedrive Activities. We map event title to Activity subject, start/end datetime, and owner. Activity type (call, meeting, deadline) is derived from Milana's event category. Original timestamps and event attendees are preserved in custom fields if Pipedrive's standard Activity model cannot capture them.

Documents attached to Milana matters re-upload to Pipedrive as Files linked to the corresponding Deal. We preserve the original filename and attachment date. File size and format limits per Pipedrive plan apply — documents exceeding 250MB are flagged for chunked upload.

Milana opposing counsel data (firm name + attorney name + contact info) merges into two Pipedrive records: an Organization for the opposing law firm and a Person for the specific attorney, linked by org_id. This preserves the relationship without creating duplicate records.

Milana's jurisdiction-specific court rules library has no Pipedrive equivalent. We export the rules configuration as a structured JSON reference file for manual documentation. Users who need court rules in Pipedrive must rebuild using Pipedrive Automations triggered by Deal custom fields.

Milana time entries and billing rates cannot map to Pipedrive's deal model. We export time-entry data as a CSV reference file linked by matter number. Pipedrive has no native billing — firms requiring time tracking must pair Pipedrive with a billing tool and reconcile via the exported reference data.

Milana automates deadline cascades based on court rules (e.g., filing a complaint auto-creates the answer deadline, discovery deadlines, and trial-setting deadlines). Pipedrive Automations can replicate simple triggers but not jurisdiction-specific rule chains. We document the rules for manual rebuild in Pipedrive's automation builder.

Milana staff and attorney user accounts are linked to Pipedrive Users by matching each Milana email to the Pipedrive email. If a Milana user lacks a Pipedrive account, the migration engine assigns their records to the migration owner and flags the entry for user provisioning. Your team creates the Pipedrive User before go‑live, then reassigns ownership of migrated Deals, Persons, and Activities to the correct user, preventing orphaned records.

Milana matter statuses (Active, Pending, Closed, Dismissed) map to Pipedrive Deal stages via a value map. Each Milana status value is assigned to a corresponding Pipedrive stage in the target pipeline. Closed matters with a final disposition value map to Pipedrive's Won or Lost stage.

Milana custom matter fields (case-type codes, insurance policy numbers, lien amounts, etc.) require custom fields in Pipedrive. We create Deal custom fields for each Milana custom property, matching the data type where possible. Pick-list values in Milana become Pipedrive drop-down custom fields.