Migrate from Court Clerk to Zoho CRM

Each court in Court Clerk (e.g., 5th Circuit Court, County District Court) maps to a Zoho CRM Account record of type 'Court'. The Account Name stores the court name, and a custom field Court_Type__c captures whether it is a Circuit, District, Justice, or Municipal court. Multiple courts require separate Account records so Deals can link to the correct jurisdiction via AccountId.

Court Clerk parties migrate to Zoho CRM Contacts. Attorney parties also create an Account record for their law firm when firm name is present. A custom pick-list field Party_Role__c on the Contact stores the Court Clerk role type (Plaintiff, Defendant, Attorney, Witness, Bondsman, Guardian). For contacts without a firm, the AccountId links to a default 'Unrepresented' Account.

Court Clerk cases are the top-level migrated entity in Zoho CRM, mapped as Deals. The Deal Name defaults to the Case Number (e.g., '2023-CV-04192') for quick search. Filing Date migrates to a custom Date field Filing_Date__c. Case Type (Civil, Criminal, Family, Probate) maps to a custom pick-list Case_Type__c. Case Status maps to Deal Stage with value-by-value mapping (Active, Pending Judgment, Closed, etc.). The original Court Clerk case ID is preserved as Source_System_ID__c.

Court Clerk stores which judge is assigned to each case. Zoho CRM Deals support Contact Roles (Attorney, Decision Maker) but have no native Judge role. We add a custom pick-list Judge_Role__c on the Deal linking to a Contact record of type 'Judge'. The judge Contact is associated via Zoho's Related List, and Judge_Name__c (text) provides a fallback for cases where the judge is not a Zoho user.

Court Clerk's attorney-of-record field maps directly to Zoho CRM's built-in Contact Role 'Attorney' on the Deal. Both plaintiff and defendant attorneys are added as separate Contact Role entries on the same Deal. Attorney bar number and firm name stored as custom fields (Bar_Number__c, Firm_Name__c) on the Contact.

Court Clerk filings are stored as Zoho CRM Attachments linked to the corresponding Deal. Filing metadata (filing type — Motion, Order, Petition, etc. — and filer name) migrates as custom fields on the attachment record or as Zoho Notes with the filing type in the note title. Files larger than Zoho's 25 MB attachment limit are flagged for manual re-upload. Filing timestamps are preserved in the Note or as Deal_Activity__c dated entries.

Court Clerk financial obligations — fines, fees, restitution, and court costs — have no Zoho CRM standard equivalent. We create a Court_Obligations__c custom module with fields: Obligation_Type__c (pick-list), Amount__c (currency), Due_Date__c (date), Payment_Status__c (pick-list: Unpaid, Partial, Paid, Waived), and Related_Deal__c (lookup to Deal). This module is linked to the Deal so obligations appear in the Deal's related list. Payment history migrates as separate Obligation records or as notes on the obligation.

Court Clerk bond and bail records migrate as a Court_Bonds__c custom module linked to the Deal. Fields include Bond_Type__c (Cash, Surety, Property), Bond_Amount__c, Bond_Status__c (Active, Discharged, Forfeited), Surety_Name__c (Contact lookup), and Related_Obligation__c (lookup to Court_Obligations__c). This captures bond activity separate from financial obligations.

Court Clerk scheduled events — hearings, trials, status conferences, and sentencing dates — migrate as Zoho CRM Events with the original event date, time, and duration preserved. Event Subject names the event type (e.g., 'Motion Hearing — 10:00 AM'). Pre-trial tasks (e.g., 'File Answer by 2024-03-15') migrate as Zoho Tasks with a due date, linked to the Deal. The Deal lookup on both Event and Task maintains the case context.

Court Clerk minute entries and case notes migrate as Zoho CRM Notes attached to the corresponding Deal. Minute entry text is preserved in the Note body. The Note title follows a date-stamped convention (e.g., '2024-01-15 Minute Entry') for chronological sorting. Rich-text formatting is preserved where supported.

Court Clerk warrants and summons records migrate as a Court_Warrants__c custom module linked to the Deal. Fields include Warrant_Type__c (Arrest, Search, Subpoena), Issue_Date__c, Status__c (Active, Served, Quashed), and Related_Contact__c (lookup to the defendant or witness Contact). Service details stored as text fields.

Court Clerk user assignments per case resolve to Zoho CRM Deal Owner (the primary assigned clerk) via email matching to Zoho users. Secondary roles — Judge, Bailiff — are stored as custom Contact lookups (Assigned_Judge__c, Assigned_Bailiff__c) on the Deal. Users with no Zoho account are flagged pre-migration so your court administrator can create Zoho accounts or assign a fallback owner before data lands.

Court Clerk workflow automation — case status routing, deadline triggers, e-filing approval chains, and court-specific routing rules — does not migrate. These rules are Tyler-configuration artifacts with no Zoho CRM equivalent. We export your Court Clerk workflow definitions as a documented reference so your Zoho administrator can rebuild them using Zoho Workflow Rules and Blueprint. Priority automation rebuilds are scoped separately from data migration.