Migrate from LegalEdge to Freshsales

LegalEdge matters have no direct Freshsales equivalent. We map each matter to a Freshsales deal, pulling the matter title or case number into the deal name. All case metadata (court, judge, opposing counsel, statute of limitations) becomes custom fields on the deal record so the legal context is fully preserved in Freshsales.

Individual parties — plaintiffs, defendants, witnesses, opposing counsel — map to Freshsales contacts. The party's display name becomes the contact name. Phone, email, and address fields map directly when populated in LegalEdge. The party_type field maps to Freshsales contact roles on the associated deal.

Organizational parties (law firms, corporate defendants, insurance carriers) map to Freshsales accounts. LegalEdge may store minimal firm data — we create Freshsales account records and populate whatever fields LegalEdge provides. Any missing account fields are left blank for manual completion after migration.

LegalEdge links parties to matters with a role label (Plaintiff, Defendant, Opposing Counsel). We map these to Freshsales deal contact roles. When a party appears on multiple matters, we create one contact and link it to multiple deals with the appropriate role label per deal.

Freshsales has no native case type field. We create a custom pick-list field on the Deal object (Case_Type__c) and populate it with LegalEdge's case type values. If LegalEdge uses a free-text case type, we create a text field and preserve the original values for post-migration categorization.

Case numbers are court-assigned identifiers with no Freshsales equivalent. We create Case_Number__c as a custom text field on the Deal object. This field is indexed for searchability so users can locate a deal by its court case number without navigating through the matter title.

Court and judge information migrates to two custom text fields on the Deal: Court__c and Judge__c. If LegalEdge stores court as a structured pick-list, we create a pick-list field for Court__c to enable Freshsales reporting and filtering by jurisdiction, preserving the categorical nature of court data for downstream analytics.

LegalEdge litigation phases (Intake, Discovery, Trial, Settlement, Appeal) require a decision: map to Freshsales pipeline stages if the firm wants Kanban-style tracking, or preserve as a custom pick-list field (Litigation_Phase__c) if the stages are informational rather than workflow-driven. We surface this choice in the migration plan before the full run.

LegalEdge activity logs — notes, tasks, email records, appointments — map to Freshsales sales activities. Each activity retains its original timestamp and owner. The activity subject or description is preserved in the Freshsales activity body so the full narrative context is searchable post-migration.

Documents attached to LegalEdge matters download and re-upload to Freshsales Files, linked to the corresponding deal record. File size limits apply — Freshsales supports files up to 25MB per attachment. For documents exceeding this limit, we log a reference note and flag the record for manual handling.

LegalEdge users (attorneys, paralegals, administrative staff) resolve against Freshsales users by email address match. Unmatched users are flagged before migration so your team can invite them to Freshsales or assign their records to a fallback user. Legal role labels (Attorney vs. Paralegal) are preserved in a custom field on the Freshsales user record.

If LegalEdge contains custom matter objects (e.g., Insurance Claims, Lien Records, Settlement Agreements), we evaluate each for Freshsales equivalence. Custom objects with one-to-many relationships to matters map to Freshsales custom objects. Flat key-value custom fields on matters become custom fields on the corresponding Freshsales deal.