Migrate from LegalServer to Pipedrive

LegalServer Client records map to Pipedrive Person records. Every Client field (name, address, contact info) migrates as a Pipedrive Person field. Multi-party case clients each create their own Person record, independently linked to the same Deal. FlitStack resolves the Client's primary case context as a deal_name prefix so the Pipedrive record is identifiable post-migration.

LegalServer stores address components (street, city, state, zip) as separate fields on the Client record. Pipedrive Person stores a single formatted address string plus individual sub-fields (address, city, state, postcode, country). FlitStack concatenates LegalServer's address sub-fields into Pipedrive's address string and maps each component to the corresponding Pipedrive Person address sub-field. State is mapped as a pick-list value.

LegalServer Client records that represent organizational clients (non-individual applicants, corporate respondents, legal aid referral organizations) are identified by checking for a populated organization_name or legal_business_name field. These records create Pipedrive Organization records in addition to Person records, with the Person linked to the Organization via org_id. This requires a two-pass migration: Organizations are created first, then Persons are created with the Organization link.

LegalServer Case (Matter) records are the primary migration target and map directly to Pipedrive Deals. Case name becomes Deal title, case type becomes a Pipedrive custom pick-list field, case status maps to the nearest Pipedrive stage, and the case open date becomes the Deal's expected_close_date. Pipedrive's deal_value field maps from a monetary field on the LegalServer case if one exists; otherwise it is left blank and populated manually post-migration.

LegalServer practice area values (e.g., Housing, Family Law, Immigration, Benefits) have no direct Pipedrive equivalent. FlitStack creates a Pipedrive custom pick-list field (Practice_Area__c) on the Deal object, maps practice area values value-by-value, and uses practice area to determine which Pipedrive Pipeline the deal belongs to if multiple pipelines are configured. Teams with five distinct practice areas may opt to create five Pipedrive pipelines, each with its own stage set.

LegalServer case status values (Open, Closed, Pending, On Hold, etc.) are mapped to Pipedrive Deal Stage values. The mapping is value-by-value: LegalServer Open maps to the first Pipedrive stage, Closed maps to the Won stage or a configured closed stage, Pending maps to a mid-funnel stage, and On Hold maps to a stalled stage. Stage-entered timestamps from LegalServer are preserved as a custom datetime field on the Pipedrive Deal.

LegalServer Timekeeping entries (attorney hours logged per case) migrate as Pipedrive Activity records with type='Call' or a custom activity type label. The timekeeping entry's date maps to the Activity's due_date, the hours-minutes duration maps to a custom number field (Hours_Spent__c), and the timekeeping note maps to the Activity's note content. Multiple timekeeping entries for the same case generate multiple Activity records in Pipedrive, preserving the full billing history.

LegalServer case outcome values (Granted, Denied, Dismissed, Settled, Withdrawn) are mapped to a Pipedrive custom pick-list field (Case_Outcome__c) on the Deal. The case close date from LegalServer maps to the Pipedrive Deal's close_date field, so Pipedrive's stage and outcome together reflect the case disposition. Outcome notes migrate to the Deal's notes field.

LegalServer's Grant Management module — including billing type configuration (flat hourly, variable rate), fund balance tracking, and grant-to-case deduction rules — has no Pipedrive equivalent. FlitStack migrates the grant name, assigned grant code, and billing type as custom fields on the Deal for reference, but the billing logic, fund balance, and per-entry deduction calculations cannot function in Pipedrive. Finance teams must manage grant accounting in a dedicated accounting system post-migration.

LegalServer documents linked to a case via the document_id field are downloaded and re-uploaded to the corresponding Pipedrive Deal as file attachments. Files exceeding Pipedrive's per-file limit (25MB default on most plans) are flagged for manual download. The original document filename and case reference are preserved in the file metadata so the attachment context is not lost in Pipedrive.

LegalServer Contractor records (panel attorneys, outside counsel, investigators) that are stored in the Contractor Module migrate as Pipedrive Person records if the contractor is an individual, or as Organization records if the contractor is a firm. The contractor's subject-matter expertise and fee structure fields migrate as custom fields on the Pipedrive record. Contractor assignments to cases map as Deal activity entries noting the referral relationship.

LegalServer staff users (attorneys, paralegals, intake workers) are resolved by email match against Pipedrive user accounts. FlitStack builds a pre-migration user map: LegalServer user email → Pipedrive user ID. Unmatched users are flagged before migration so the team can either invite them to Pipedrive or assign their records to a fallback Pipedrive user. No case or activity lands in Pipedrive without a valid owner.