Migrate from The Plaintiff to Freshsales

The Plaintiff party records where type = 'Individual' map directly to Freshsales Contact records. Name, email, phone, address, and custom fields on the party record carry over. Standard fields like job title, mobile phone, and date of birth (when present) map directly, and the original party creation timestamp is stored in Original_Create_Date__c for historical reference. The Plaintiff party ID is stored as Source_System_ID__c for delta‑run de‑duplication.

Corporate party records map to Freshsales Account. Company name, domain/website, industry, employee count, and billing address fields map directly. The company website URL maps to the Freshsales website field, the industry picklist is converted via a value‑by‑value table, and jurisdiction or incorporation state is stored in a custom Jurisdiction__c field for compliance tracking.

The Plaintiff cases map to Freshsales Deals. Case status (Filed, Active, Closed) maps to Freshsales Deal stage values using a value-mapping table you define before migration. Case number, court name, and judge name migrate as custom fields on the Deal.

The Plaintiff allows multiple parties (Plaintiff, Defendant, Expert Witness, Opposing Counsel) linked to one case. Each role assignment merges into a Freshsales Deal Contact Role entry on the Deal, preserving the party-role label so you know who was on which side of the matter.

The Plaintiff documents attached to cases re-upload to Freshsales Files associated with the corresponding Deal record. We rehost files to Freshworks storage. Large files exceeding Freshsales plan limits are flagged and handled per your instructions (skip, compress, or upgrade storage).

The Plaintiff billable hours map to Freshsales Tasks with a custom billing flag and duration field. Billing amounts and invoice references from The Plaintiff migrate as custom fields on the Task. Native Freshsales invoicing is not activated — that requires Freshsales Suite or a separate billing tool.

Court dates and scheduled appearances from The Plaintiff migrate as Freshsales Events linked to the corresponding Deal (case). Original date, time, location, and event type (Hearing, Deposition, Filing Deadline) are preserved in Event fields and custom fields.

Opposing counsel details stored as party contacts in The Plaintiff migrate to Freshsales Contact records tagged with a custom Role = 'Opposing Counsel' field. These contacts are usable in Freshsales for conflict-checking and communication tracking but do not affect Deal pipeline stages.

The Plaintiff custom fields on Case objects (e.g., Insurance Carrier, Lien Holder, Statute of Limitations) require matching custom fields created in Freshsales before migration. We provide a field-creation checklist and can pre-create fields in your Freshsales test environment before the full migration run.

The Plaintiff workflow rules (case routing, status-change triggers, email notifications) have no Freshsales equivalent at the migration level. We export your workflow definitions as a configuration reference document for your Freshsales admin to rebuild using Freshsales Workflows (available on Blossom and above).

The Plaintiff reports built on case data do not transfer. Underlying case and party data migrates to Freshsales Deals and Contacts, so reports must be rebuilt in Freshsales Analytics. We provide a data dictionary mapping so your admin can reconstruct key reports from migrated fields.

Historical invoices from The Plaintiff migrate as records in a custom Invoice object we create in Freshsales (labeled as a custom module on Estate/Forest plans). Invoice line items, amounts, and payment status are preserved but Freshsales does not process new invoices natively — Freshsales Suite billing or a third-party tool handles post-migration invoicing.