Migrate from Criminal Case Management to Salesforce Sales Cloud

The criminal case matter record maps directly to Salesforce Case. Original case create date migrates as Original_Case_Date__c custom datetime since Salesforce's CreatedDate reflects migration time. Case number from source becomes Case_Number__c custom field. Additionally, the original case status is stored in a custom field to preserve workflow context, and the case type determines the RecordTypeId for page layout selection.

Legal party records (defendants, complainants, witnesses) map to Salesforce Contact. The organization or agency associated with a party maps to Account. When a party is an individual with no organization, they land as Contact only with AccountId set to a default placeholder.

Attorney assignments on criminal cases map to Salesforce CaseTeamMember records with Role set to the source assignment type (Lead Counsel, Associate, Paralegal). Staff assignments without Salesforce user accounts are stored as Contact roles on the Case. Each CaseTeamMember record includes a User lookup linking to the matched Salesforce User, and the Role picklist values are predefined to match the source types, ensuring consistent reporting across the case team.

Scheduled hearings and court dates migrate as Salesforce Events with Subject containing the hearing type, StartDateTime from the source court date, and the associated Case linked via WhatId. Reminder settings are preserved as custom text fields. The Event’s Location field is populated with the courtroom information from the source, and any recurrence patterns for recurring hearings are documented in custom text for manual recreation in Salesforce Calendar.

Documents attached to criminal cases download from the source platform and re-upload to Salesforce Files. Each file creates a ContentDocument record linked to the Case via ContentDocumentLink with LinkedEntityId pointing to the Case record. File version history is preserved as custom text notes.

Criminal case bond details (amount, type, status, court) have no direct Salesforce equivalent. FlitStack creates a Bond_Information__c custom object with lookup to Case, migrating bond amount, bond type pick-list, posting date, and surety as custom fields. The bond status picklist mirrors the source statuses (Posted, Denied, Forfeited), and any surety company information is stored as a text field for reference.

Criminal charges linked to a case (statute, degree, description, plea, verdict) map to a custom Charge__c object with a master-detail relationship to Case. Charge status (filed, amended, dismissed) maps to a pick-list on the custom object. The statute code is stored as a text field for precise legal reference, and any amended charges retain a history note linking back to the original filing date.

Case notes and legal memos migrate as Salesforce Notes with Body containing the note content, ParentId linking to the Case record, and Title set from the source note subject or date. Rich-text formatting is preserved where possible. If the source note includes attachments, they are migrated as separate ContentDocumentLink entries linked to the same Case, ensuring all supporting documentation is accessible.

Witness and informant records map to Salesforce Contact objects. Source-specific flags (confidential, testifying) migrate as custom checkboxes. Contact is linked to the relevant Case via Case Contact Role or a custom junction object. Additional contact details such as address, phone, and email are mapped to standard Contact fields, and any role changes during the case lifecycle are tracked via multiple Case Contact Role records to maintain an accurate history.

Legal workflow rules (case-stage progression triggers, reminder automation, document generation) do not migrate. FlitStack exports rule definitions as JSON for your admin to reference when building equivalent Salesforce Flows. Workflow logic must be rebuilt in Flow or Process Builder. The exported JSON captures trigger criteria, action steps, and the order of execution, allowing your admin to map each rule to the appropriate Flow element and test thoroughly before activation.

Time entries, trust accounting records, and invoices have no Salesforce equivalent. We migrate billing description and totals as read-only custom fields or attached notes for reference. Firms requiring trust accounting must implement a dedicated legal billing solution post-migration and re-enter financial records. Each migrated billing entry records the transaction amount, currency, date, and a description field, preserving the original trust balance history for audit purposes. Firms may later integrate a legal billing platform such as Clio or Aderant to replace these reference fields with native billing records.