Migrate from CASEpeer to Zoho CRM

CASEpeer client records map to Zoho Contacts directly. Client name maps to Contact Name, email to Email, phone to Phone. Primary address maps to the standard address fields. No CASEpeer-specific status field translates to a Zoho standard field — stored as a custom pick-list field in Zoho for reporting clarity.

CASEpeer Cases have no direct Zoho equivalent — Zoho's standard Deals module is revenue-focused while CASEpeer Cases track legal status, court deadlines, and injury details. We create a custom Cases module in Zoho and map case fields one-by-one into custom fields on that module. The Cases module links to the Contact record via a lookup relationship.

CASEpeer Medical Providers are separate entity records with specialty, contact name, and phone. Zoho has no native medical provider object. We map these to Zoho Contacts with a custom Provider_Type pick-list set to 'Medical' or create a custom Providers module — the choice depends on how your firm queries this data. Provider specialty becomes a custom pick-list field.

CASEpeer Insurance Carrier records store carrier name, policy number, claim number, and claim status. Zoho Accounts provide the closest structure with the Account Name and custom fields for policy and claim details. We add a custom Account_Type value or create a separate custom module depending on whether your firm needs carrier-level reporting separate from general Account data.

CASEpeer opposing party records include party name and opposing attorney details. Zoho Contacts store the party name; opposing attorney information requires a custom field. If your firm tracks multiple opposing parties per case, a custom Parties module with a lookup to Cases handles the one-to-many relationship cleanly.

CASEpeer custom intake forms vary by case type and store referral source, case type designation, and intake date. These intake form values migrate as custom fields on the Zoho Cases module. We map each intake form field individually during the migration planning phase so no intake data is omitted.

SOL is a PI-critical field stored as a date in CASEpeer. Zoho has no native statute-of-limitations field. We create a custom date field (SOL_Date__c) on the custom Cases module. Note that Zoho's date field accepts ISO 8601 format (YYYY-MM-DD); we verify and format CASEpeer date values during the transformation step.

CASEpeer case notes map to Zoho Notes attached to the corresponding Cases record. Documents stored as CASEpeer file attachments migrate to Zoho Files, re-uploaded and linked to the case record. Zoho's file size limit is 25MB per file — files exceeding this threshold are flagged before migration so your team can split or compress before import.

CASEpeer records case activities as timestamped events with owner and subject. These map directly to Zoho Tasks (for calls and general activities), Events (for meetings with start/end times), and Calls modules. Original timestamps and owner assignments are preserved. Activity type mapping is determined by the CASEpeer activity category during field mapping.

CASEpeer user records map to Zoho Users by email address match. Before migration, we extract the CASEpeer user list and cross-reference it against Zoho user emails. Any unmatched owners are flagged for your team to either create Zoho user accounts or assign records to a fallback owner. No case or contact lands without a valid Zoho owner.

CASEpeer case statuses (Intake, Pending, Filed, Discovery, Mediation, Settlement, Closed) map to a custom pick-list field on the Zoho Cases module. Status values are mapped one-by-one — we recommend using identical labels so your team recognizes the values immediately in Zoho. Stage-change timestamps can be preserved in a secondary custom datetime field.

If CASEpeer is used for intake-stage leads before a case is opened, those records migrate as Zoho Leads. Lead fields (name, email, phone, source) map directly to Zoho Lead fields. Once a case is opened in CASEpeer, the corresponding Zoho Lead converts to a Contact and the Cases module record is created.