Migrate from The Case File to Pipedrive

Each The Case File case maps to one Pipedrive Deal. The case name becomes the Deal title, case status maps to Pipeline stage, and the responsible attorney resolves by email match to a Pipedrive user. Multi-party cases link to the primary party Person as the deal organizer.

Cases in 'Intake' or 'Inquiry' status route to Pipedrive Leads rather than Deals. This captures the pre-engagement pipeline step — a firm can run an intake pipeline in Leads and promote qualified matters to Deals once the engagement letter is signed.

Individual parties (plaintiffs, defendants, witnesses) map directly to Pipedrive Persons. Name, email, phone, address, and bar-association ID migrate as standard and custom fields. The party's role in the case (Plaintiff, Defendant, Expert Witness) is preserved in a custom field on the Person record.

Corporate parties including defendant corporations, insurance companies, employer entities, and other business organizations map to Pipedrive Organizations. Organization name, address, industry, and website migrate directly as standard fields; the party's case-specific role designation is stored as a custom Organization field. This ensures corporate parties retain their entity context within the Pipedrive CRM while remaining linked to the relevant case Deal.

The Case File party-role label (Plaintiff, Defendant, Opposing Counsel, Expert Witness, Insurance Carrier, Co-Counsel) has no Pipedrive native equivalent on Person or Organization records. FlitStack creates a 'Party_Role__c' custom pick-list field on both Person and Organization objects and maps each role value-by-value from the source. The role field is configured as a pick-list to maintain consistent categorization in Pipedrive reporting and filtering. During migration, each party record receives the appropriate role value from The Case File's party-role association table.

Documents attached to a Case download and re-upload to Pipedrive Files, linked to the corresponding Deal. FlitStack preserves the original filename, file type, and upload timestamp. Document Bates numbers and exhibit tags are stored in a custom field on the file record since Pipedrive Files has no native Bates metadata.

Court dates, filing deadlines, deposition schedules, and other case-related calendar entries map to Pipedrive Activities with type='Meeting' for court appearances and in-person events, or type='Task' for deadlines and administrative items depending on the source event type. Court name, courtroom, judge name, and filing deadline fields from the source become custom fields on the Activity record to preserve the legal calendar context within Pipedrive's activity tracking.

Every case-level custom property from The Case File is created as a matching Pipedrive Deal custom field. Field type (text, number, date, currency, pick-list) is matched from the source schema. FlitStack creates the field in Pipedrive via the /dealFields API endpoint and maps all values during migration.

Party-level custom properties including Insurance Policy Number, Deposition Date, Bar Number, License Information, and other party-specific data map to custom fields on the corresponding Person or Organization record in Pipedrive. FlitStack creates these fields via the /personFields or /organizationFields API endpoints before migration begins. The field type (text, date, currency, or pick-list) is matched from The Case File schema to ensure data fidelity during the transfer. Each custom field is then populated during the main migration pass with values pulled from the corresponding Party record.

Billable hours and invoice line items from The Case File can map to Pipedrive Products for firms that use Pipedrive for matter billing. Each billing entry becomes a Product linked to the Deal, with quantity and price reflecting hours and rate. Not activated unless the firm's Pipedrive plan includes billing integration.

The originating source of a new case—whether referral, website inquiry, marketing campaign, or walk-in client—maps to Pipedrive Deal Labels to enable source tracking and ROI reporting. Multiple source tags present in The Case File collapse into a single primary label for clean Pipedrive reporting; any secondary or tertiary source tags are stored in a custom 'Secondary_Source__c' multi-select or text field to preserve the complete source attribution history within the Deal record.