Migrate from CASEpeer to HubSpot

Casepeer client records map directly to HubSpot Contacts using standard field mappings. Client name, email, phone, address, and date-of-birth fields transfer directly to their corresponding HubSpot contact properties. A Casepeer_Record_Type__c custom property is set to 'Client' on each contact record to distinguish from opposing parties and other party types in HubSpot after migration.

Opposing parties (individuals) in Casepeer map to HubSpot Contacts with Casepeer_Record_Type__c set to 'Opposing_Party'. The opposing party's attorney name and law firm name are stored in custom text properties (Opposing_Attorney_Name__c and Opposing_Firm_Name__c). When multiple opposing parties exist on a single case, each one becomes a separate Contact linked to the parent Deal via HubSpot's association model.

Insurance carriers in Casepeer map to HubSpot Companies with the carrier's name, type, and policy information preserved. Carrier name, carrier type (such as auto, umbrella, health, or workers comp), and policy number migrate as custom properties on the Company record. Each carrier company receives a Company_Type__c property set to 'Insurance_Carrier' to enable filtering and segmentation across all carrier records in HubSpot.

Medical providers in Casepeer map to HubSpot Companies with Company_Type__c set to 'Medical_Provider'. Provider name, specialty, address, and contact information map directly to corresponding Company properties. The relationship between a specific provider and a specific case (which provider treated which client for what injury condition) is preserved using a custom junction object that links the Provider Company to the parent Deal.

Casepeer cases map to HubSpot Deals. Case name becomes Deal name (e.g., '[Client Last Name] v. [Defendant]'). Case status (Active, Settled, Closed) maps to Deal stage via value mapping. Case number, case type, incident date, and jurisdiction migrate as custom properties on the Deal.

Casepeer's case-type pick-list (Auto Accident, Premises Liability, Medical Malpractice, etc.) maps to a Case_Type__c custom property on the Deal. A HubSpot deal pipeline is created per case type when multiple distinct stages are needed; otherwise a single pipeline handles all case types with stage value mapping per type.

Casepeer liens have lien holder, lien amount, lien type, and status fields. A HubSpot custom object named 'Lien' is created with these properties. Liens link to the parent Deal via a Deal_Lien__c relationship property. Lien holder organizations link to the corresponding Company record.

Casepeer court dates and statutory deadlines become HubSpot Meetings. The meeting subject uses the court-date description, start time is the scheduled court date, and the HubSpot contact (client) is associated. A Court_Date_Type__c property distinguishes 'Court Hearing', 'Filing Deadline', and 'Statute of Limitations' events.

Case notes in Casepeer migrate to HubSpot Notes attached to the associated Deal. Original create date and author (user) are preserved. Timestamp and owner mapping ensure the note audit trail is intact in HubSpot. Notes with '@mention' tags become Engagement notes if the mention maps to a known HubSpot user.

Casepeer user accounts (attorneys, paralegals, admins) are matched to HubSpot users by email address. Unmatched users are flagged before migration. Records previously owned by an unmatched user are reassigned to a designated fallback HubSpot user to avoid owner-less records in HubSpot.

Casepeer custom intake field schemas per case type are translated into HubSpot custom properties on the Deal object. Each intake form definition is documented as a rebuild reference for HubSpot Forms and property groups. The rebuild reference includes field names, data types, and conditional logic from the source intake form.

Casepeer documents attached to cases (medical records, demand letters, court filings) are downloaded and re-uploaded as HubSpot Files linked to the parent Deal. File size limits (25MB per file in HubSpot) apply. Dropbox-stored files require re-linkage if the Dropbox integration is not rebuilt in HubSpot.

Casepeer leads or intake prospects who have not yet opened a case migrate as HubSpot Contacts with a Prospect_Status__c custom property. If a lead converted to a case in Casepeer, both the lead and the case record are preserved — the contact is linked to the resulting Deal.

Casepeer billing records (invoices, payments, trust ledger entries) migrate as a custom object named 'Legal_Invoice' linked to the parent Deal. Amount, status, date, and billing description fields map directly. Casepeer's LawPay integration for payment processing does not transfer — a new HubSpot-compatible payment integration must be configured post-migration.

Casepeer integrations (LawPay, Dropbox, CalendarRules, Kenect, etc.) cannot be migrated. Each integration requires a new setup in HubSpot or an equivalent tool. FlitStack documents every active integration as part of the pre-migration audit so the team can rebuild connections after go-live.