Migrate from LegalEdge to Pipedrive

LegalEdge clients map 1:1 to Pipedrive People. Client name splits into first_name and last_name on the Person record. Email, phone, mobile, and address fields (street, city, state, zip) map directly. The Person's primary Organization is created from the client's firm name or corporate affiliation stored in the company_name field. If the client record represents a law firm rather than an individual, both a Person and an Organization are created and linked via organization_id.

LegalEdge client records that represent law firms or corporate entities generate an Organization in Pipedrive. Individual client contacts retain their Person record and link to this Organization via the Person's organization_id field. When a LegalEdge client has no firm affiliation, no Organization is created.

LegalEdge matters map to Pipedrive Deals. Matter name becomes Deal title (name field). Matter status maps to Pipedrive stage via value_mapping: Open/Active maps to an early stage, Pending/On Hold maps to a middle stage, Closed/Won maps to Won, Closed/Lost maps to Lost. Matter open date maps to Deal's add_time timestamp.

Each LegalEdge matter status value requires explicit mapping to a Pipedrive stage. Statuses like 'Active', 'Pending', 'On Hold', 'Closed Won', 'Closed Lost' map to corresponding stages in the primary Pipedrive pipeline. Custom matter statuses in LegalEdge require custom stage creation in Pipedrive before migration.

LegalEdge practice areas (e.g., Family Law, Corporate, Criminal Defense, Personal Injury, Immigration) have no native Pipedrive equivalent, so we create a custom pick-list field on the Deal object named Practice_Area__c matching LegalEdge's practice area values exactly. This field enables granular reporting by practice type and supports filtering the deal pipeline by legal specialization. During the pre-migration setup phase, we configure the pick-list values in Pipedrive to match LegalEdge's enumerated practice area list before the import script runs.

LegalEdge activities attach to matters. These migrate as Pipedrive Activities linked to the corresponding Deal (converted from the matter). Activity type (call, meeting, note, task) maps to Pipedrive's activity_type field. Original timestamps and assigned attorney owner are preserved on the Activity record.

LegalEdge billing records, outstanding balances, and trust account information cannot map to any native Pipedrive object. We capture the last billed amount and outstanding balance as custom currency fields on the Deal for reference. Full billing history is exported as a CSV companion file for offline reconciliation.

LegalEdge matters include court name and jurisdiction fields relevant to litigation tracking. Pipedrive has no native court or jurisdiction field. We create a custom text field on the Deal to store court name and a pick-list field for jurisdiction type. This supports legal teams tracking venue-specific pipeline performance.

LegalEdge document attachments on matters or clients re-upload to Pipedrive Files attached to the corresponding Person or Deal record. Files are downloaded from LegalEdge's storage, re-uploaded to Pipedrive, and linked to the target record. File size limits in Pipedrive apply (25MB per file default).

LegalEdge users (attorneys, paralegals, administrative staff) resolve to Pipedrive Users by email address match. Unmatched users are flagged before migration — your team either provisions them in Pipedrive first or assigns their records to a fallback owner. Active/inactive status maps from LegalEdge user configuration.

LegalEdge stores opposing counsel names and opposing party information on matters. These are captured as custom text fields on the Deal (Opposing_Counsel__c, Opposing_Party__c) since Pipedrive has no native opposing party concept. If the opposing party is a known organization, an Organization record is also created.

LegalEdge custom objects (e.g., Lien records, Insurance claims) with their own fields map to a custom field group on the Deal or Person depending on association. N:N custom object relationships in LegalEdge may require a custom Pipedrive field group for equivalent tracking.