Migrate from CASEpeer to HighLevel

CASEpeer's client record maps directly to HighLevel Contact. First name, last name, email, phone, and address fields carry over as direct field mappings. CASEpeer contacts without an associated case become HighLevel contacts with a blank opportunity link. Original CASEpeer contact ID stored as Source_Casepeer_ID__c for delta-run deduplication.

Each CASEpeer case becomes a HighLevel Opportunity. The CASEpeer case number maps to a custom field (Case_Number__c) on the Opportunity. Case name maps to Opportunity name. The Opportunity is linked to the Contact record created from the CASEpeer client. The attorney and paralegal assignments migrate as custom Contact fields (Attorney_Name__c, Paralegal__c) and are looked up by email match against HighLevel users.

CASEpeer's five predefined case stages — Initial Consultation, Under Investigation, Pending Litigation, Awaiting Settlement, Closed — must be mapped value-by-value to a HighLevel custom pick-list (Case_Status__c) that your admin creates on the Opportunity. FlitStack delivers the value map as part of the migration plan so the pick-list is ready before data lands. No status values auto-create in HighLevel.

CASEpeer stores attorney name and paralegal name per case. HighLevel has no native attorney field on opportunities. We migrate attorney and paralegal as custom text fields on the Contact record (Attorney_Name__c, Paralegal_Name__c) and resolve them by email against HighLevel users. If the attorney email has no HighLevel user match, the name is stored as text and flagged for admin review.

CASEpeer documents per case (Medical Records, Demand Letters, Court Filings) are downloaded from CASEpeer storage and re-uploaded as HighLevel opportunity attachments. The original CASEpeer folder path is preserved as a custom text field (Original_Folder_Path__c) on the attachment record so the folder hierarchy can be reconstructed in HighLevel or referenced during a future document migration.

CASEpeer case notes migrate as HighLevel Notes attached to the relevant Contact or Opportunity. The note body and original author (attorney or staff name) carry over. CASEpeer timestamps for note creation are preserved as Note attributes. Notes are not deduplicated by content — every CASEpeer note becomes a HighLevel note record.

CASEpeer's fixed insurance type field (Auto, Health, Liability, etc.) has no direct HighLevel equivalent. We create a custom pick-list field (Insurance_Type__c) on the Opportunity with the same values present in CASEpeer. Your HighLevel admin sets the pick-list options before migration runs so incoming records map cleanly.

CASEpeer's per-case medical treatment tracking table — provider name, record status, date sent, date received — has no equivalent in HighLevel's standard object model. We map it to a Custom Object (Treatment_Record__c) with a lookup relationship to the Opportunity representing the case. Provider name, record status, and date fields map as direct custom fields on the object.

CASEpeer calculates settlement demand amounts using its built-in formula engine. The resulting dollar amount migrates as a custom currency field (Settlement_Demand_Amount__c) on the Opportunity. The formula logic itself cannot migrate — it must be rebuilt in HighLevel using Custom Object math or a third-party calculation tool.

CASEpeer generates task sequences triggered by case milestones (Complaint Filed, Discovery Complete, etc.). These task templates cannot be exported via CASEpeer API in a runnable format. FlitStack captures the task template structure (task names, relative due dates, and milestone triggers) as a JSON reference file your team uses to rebuild the sequences in HighLevel Workflows.

CASEpeer stores threaded text message conversations per client. The message log (sender, timestamp, content) migrates as a series of Note records on the Contact in HighLevel, tagged with a custom field (Message_Direction__c: Inbound/Outbound) to preserve the two-way structure. Original message timestamps are retained. HighLevel's native Conversations tool starts fresh from the migration date.

CASEpeer syncs court deadlines via CalendarRules integration. Deadlines stored in CASEpeer's calendar are not accessible via the CASEpeer export API as independent records. We extract any deadline data present in the case notes field and flag it as a Note with a custom datetime field (Deadline_Date__c) for manual calendar entry in HighLevel.