Migrate from Court Clerk to Pipedrive

Each Court Clerk case becomes one Pipedrive Deal. The deal name uses the case_number or case_caption field. Pipedrive's Pipeline and Stage fields replace the court case status — a value mapping is applied during migration to translate court statuses into the firm's Pipedrive stage labels.

Individual parties (plaintiff, defendant, witness) map to Pipedrive People. The person's name, email, and phone pull directly from the party contact fields. For parties without contact data, the Person record is created with name only and flagged for enrichment. Enrichment can be performed later using FlitStack's built-in contact lookup or manually by the firm.

Corporate parties (business entities as plaintiff or defendant) map to Pipedrive Organizations. The organization name comes from the party_name field. Address data, if present, migrates to the Organization's address fields. If multiple corporate parties share the same name, FlitStack appends a unique identifier to prevent duplicate Organization records.

Attorneys are stored as People with a custom attorney_bar_number__c field. Their law firm appears as a linked Organization. The case receives a Person-Organization-Activity link to represent the attorney-of-record relationship. If the firm is new, FlitStack creates the Organization before linking it.

The link between a Case and a Party (e.g., defendant, opposing counsel) becomes a Pipedrive deal_person link. The link type (plaintiff, defendant, witness) is stored as a custom field (party_role__c) on the deal_person relationship so the role is visible in Pipedrive's activity timeline.

Case filings migrate as Pipedrive Activities with Type='Case Filing'. The filing date maps to the activity due date, and the filing description maps to the activity note body. Filing type (complaint, motion, order) is preserved in a custom field filing_type__c for filtering and reporting.

Court Clerk documents attach to Pipedrive Notes on the corresponding Deal. The note body contains the document description and filing reference; the actual file (PDF, Word) is downloaded from Court Clerk's storage and re-uploaded as a Pipedrive Attachment. Files over 25MB are split or linked via external URL custom field.

Court Clerk case types (civil, criminal, probate, family) have no native equivalent in Pipedrive. FlitStack creates a custom pick-list field (case_type__c) on the Deal object and populates it with the source case type value. The pick-list options are pre-configured in Pipedrive before migration runs.

Court Clerk marks certain cases or parties as confidential (juvenile, sealed, domestic violence). Pipedrive has no built-in confidentiality model. FlitStack creates a custom pick-list field (confidentiality__c) on both Deal and Person to preserve this flag. The firm's Pipedrive admin sets visibility rules after migration.

The originating court (e.g., 5th District Circuit Court, Wayne County Probate) migrates as a custom text field court_name__c on the Deal. This preserves jurisdictional context that Pipedrive's standard fields do not capture and is useful for reporting by court jurisdiction.

Court Clerk case owners (the clerk or attorney assigned) are resolved by email against Pipedrive users. Unmatched owners are flagged before migration — the firm either creates the Pipedrive user first or assigns their cases to a fallback owner. No deal lands without a Pipedrive owner.

Court Clerk internal case notes migrate as Pipedrive Notes attached to the Deal. Original note dates are preserved in the note body header. The note author maps to the Pipedrive user by email match; if no match is found, the note is attributed to a migration-created system user.

Scheduled hearings from Court Clerk migrate as Pipedrive Activities with Type='Meeting'. The hearing date maps to the activity due date; the judge or hearing room is recorded in the activity note. If Court Clerk exposes recurrence data, recurring hearings become separate Activities linked to the same Deal.