Migrate from Aderant Milana to Zoho CRM

Direct map. Zoho Contact stores the same fields Milana tracks for client and party contacts — name, email, phone, address. Milana contact create dates map to a custom Original_Create_Date__c field because Zoho's CreatedDate reflects migration time, not the original Milana record creation date.

Milana attorney and paralegal records may represent firm employees who should be Zoho CRM users. FlitStack resolves by email match against Zoho users. Unmatched attorneys are flagged for your Zoho admin to create as users or assign to a fallback OwnerId before migration commits.

Direct map. Zoho Account stores the same firm, company, and organization data Milana uses for client organizations and opposing parties. Multi-office law firms with hierarchical relationships map to Zoho's Parent Account field. Account type pick-list values (Client, Opposing Counsel, Court, Vendor) require value-mapping setup.

Milana Matters map to Zoho CRM Deals as the primary legal-unit record. Matter number and case caption map to Deal name. Milana's matter status (Active, Closed, On Hold) routes to Zoho Deal stage values. Legal-specific matter fields (jurisdiction, case type, presiding judge) become Zoho custom fields on the Deal module.

Milana's legal-specific custom matter fields have no Zoho CRM native equivalent. FlitStack creates Zoho custom fields on the Deal module — Jurisdiction__c (pick-list), Case_Type__c (pick-list), Presiding_Judge__c (text), Court_Rules__c (multi-select text) — and maps values field-by-field. These must be created in Zoho before migration validation runs.

Milana's docket events (filing deadlines, court hearing dates, statutory deadlines) map to Zoho Tasks. The task subject carries the Milana event description; due date maps to Zoho's Due Date field; priority maps from Milana's urgency flag to Zoho Priority (High/Medium/Low). Milana's court-rule reference is stored in the task description or a custom Court_Rule_Reference__c field.

Attorney hearings, depositions, and internal calendar events map directly to Zoho Events with original start and end times preserved. OwnerId resolves by email match to the Zoho user who is the attorney. All-day events and recurring events from Milana's rules-based calendar require separate handling in the migration plan.

Milana documents and file attachments are downloaded and re-uploaded to Zoho CRM's Attachments linked to the corresponding Deal (Matter) or Contact record. File size limits apply — Zoho supports up to 25MB per attachment; files exceeding this are flagged for manual delivery. Inline images in notes are rehosted.

Milana billing and e-billing records (time entries, disbursements, invoices) do not map to Zoho CRM's native data model. FlitStack preserves Milana billing records as a CSV export alongside the migration and stores the export location in a custom Milana_Billing_Export__c field on each Matter/Deal for reference. Rebilling in Zoho requires Zoho Invoice or a Zoho Creator app.

Milana custom objects beyond the standard set (conflict check records, trust ledger entries) map to Zoho CRM custom modules. The migration plan identifies each Milana custom object API name, counts its fields, and creates matching Zoho custom modules before migration. Custom object relationships that use N:N linking require Zoho's lookup field configuration.

Milana user records map to Zoho CRM users by email address — FlitStack performs an email-match lookup against Zoho user list. Records with no matching Zoho user are assigned to a designated fallback OwnerId and flagged in the pre-migration audit report so your admin can resolve ownership before the full run.

Milana contact-matter association roles (e.g., Opposing Counsel, Expert Witness, Court) map to a Zoho Deal custom pick-list field, Attorney_Role__c. If the role is a lookup to a specific contact record rather than a pick-list value, FlitStack creates a Zoho lookup field linking the Deal to the Contact record.