Migrate from CASEpeer to Nutshell

Each CASEpeer Party maps to a Nutshell Person record. The primary plaintiff on a case is flagged as the primary contact on the associated Deal. Other party types (medical provider, opposing counsel, witness) map to additional Person records with Party_Role__c set to distinguish their role in the case context.

CASEpeer Party records that represent organizations — medical providers, insurance carriers, opposing law firms, and similar entities — map to Nutshell Company records when the Party record contains an organizational name and corresponding contact information. Individual attorney parties and single-person entities remain as Person records with their contact details preserved. This organization-versus-individual distinction ensures that the correct CRM object type is used for each party type.

Each CASEpeer Case maps to one Nutshell Deal. The CASEpeer case name becomes the Deal name; the case number is preserved in Case_Number__c. The primary plaintiff Party is linked via a Deal-Person association in Nutshell. All other party People are associated to the same Deal with their Party_Role__c values.

CASEpeer custom intake form fields are tied to Case type. Since Nutshell has no custom fields on Deals, each custom field is migrated as a custom field on the Person record linked as the primary plaintiff. Your migration plan identifies the case type field first, then branches intake fields to the correct Person custom field group.

CASEpeer medical records have no Nutshell equivalent. We export them as structured JSON objects stored in a Medical_Records_JSON__c custom field on the associated Person record, with the original record type, provider, date, and summary fields preserved for reference. Medical records require a separate archive for document-level files.

CASEpeer documents attached to cases have no native document management counterpart in Nutshell. We export all documents to a compressed archive organized by case number and deliver the archive alongside the migration. A Document_Archive_URL__c custom field on the Deal stores the archive path or shared-link reference for access post-migration.

CASEpeer calendar entries — court dates, filing deadlines, depositions — map to Nutshell Events with the original date, time, and description preserved. Statute-of-limitations dates are stored as custom date fields on the Deal. Nutshell's Events do not support court-deadline reminders, so this requires post-migration reconfiguration in Nutshell's Tasks or a third-party calendaring tool.

CASEpeer case notes migrate as Nutshell Notes attached to the associated Deal record. Original timestamps and note author are preserved. If the note references a specific party, the note is duplicated on the corresponding Person record with a note referencing the case.

CASEpeer opposing parties and insurance carriers that are organizations map to Nutshell Company records; individual adjusters map to Person records. A custom Insurance_Role__c pick-list field on the Company or Person record captures whether the entity is an insurer, adjuster, or opposing party for case-context clarity.

CASEpeer intake forms are firm-specific and case-type-specific. We extract all intake form definitions and field values, then create corresponding Nutshell Person custom fields grouped by case type in the field naming convention (e.g., Auto_MI_Date_of_Loss__c). Your admin receives a field-map spreadsheet showing every intake field and its Nutshell destination.

CASEpeer user accounts (attorneys, paralegals, staff) are resolved by email match against Nutshell user accounts. Unmatched CASEpeer users are flagged before migration — your team creates corresponding Nutshell users or assigns records to a fallback Nutshell user to prevent orphaned activities and case assignments.

CASEpeer workflows, calendaring rules via CalendarRules, and intake-form conditional logic have no direct Nutshell equivalent due to platform-specific automation architecture. We export all workflow definitions and CalendarRules configuration as a structured JSON reference document. Your Nutshell admin uses this export to rebuild equivalent automations in Nutshell's workflow tools available on Pro and above. Complex automations involving multi-step conditional branching or court-deadline logic may require supplementary configuration or a third-party scheduling tool integration.