Migrate from CASEpeer to Salesforce Sales Cloud

CASEpeer contacts (called Clients) map directly to Salesforce Contacts. The client's name, email, phone, and address fields map to the corresponding Salesforce Contact fields. CASEpeer does not distinguish between Lead and Contact — all CASEpeer clients migrate as Salesforce Contacts unless your firm uses a separate referral tracking model.

CASEpeer Cases map 1:1 to Salesforce Cases. The case number, case name, case type, incident date, and description all map to Salesforce Case fields or custom fields. Case status maps to a custom pick-list because Salesforce's standard Case.Status values are not compatible with PI case lifecycle stages.

Every CASEpeer custom field defined on the Case object becomes a Salesforce custom field with the __c suffix. Field type is preserved — text fields become Text, date fields become Date, pick-list fields become Pick-list, currency fields become Currency. CASEpeer's type annotations guide the Salesforce field type selection during schema setup.

CASEpeer custom fields on the Client object (birth date, referred_by, etc.) migrate as Salesforce custom fields on Contact. Birth date becomes a Date field; referred_by becomes a Text field or a lookup depending on whether the referral source is another Contact. We generate a custom field creation manifest before migration.

CASEpeer calendar events and tasks map to Salesforce Tasks (for to-dos) and Events (for scheduled meetings). Original start and end times are preserved. CASEpeer task owners are resolved by email match against Salesforce users — unmatched owners are flagged before migration commits.

CASEpeer documents and attachments associated with cases and contacts are downloaded and re-uploaded to Salesforce Files, linked to the corresponding Case or Contact record. Salesforce's 25MB per-file limit applies. Files stored in CASEpeer's linked Dropbox folders require CASEpeer admin access to export before migration.

CASEpeer firms that use a firm-level organization record map it to a Salesforce Account. The firm name becomes Account.Name and the firm domain becomes Account.Website. If CASEpeer stores multiple office locations, each office can become a separate Account or be represented as Account.Address fields.

CASEpeer stores insurance_carrier_name and policy_number on the case. These migrate to Insurance_Carrier__c (Text) and Policy_Number__c (Text) custom fields on the Salesforce Case object. If your firm tracks multiple insurance carriers per case, a custom junction object or multi-select pick-list is used instead.

CASEpeer settlement amounts, lien amounts, and net settlement values map to currency custom fields on the Salesforce Case (Settlement_Amount__c, Lien_Amount__c, Net_Settlement__c). These are preserved for financial reporting continuity in Salesforce reports and dashboards after migration. The currency field type maintains proper decimal formatting and enables sum, average, and rollup calculations directly in Salesforce reports without requiring spreadsheet exports.

CASEpeer workflows and automations have no Salesforce equivalent and cannot be migrated. CASEpeer automations — such as deadline reminders, status-change triggers, and task-generation rules — must be rebuilt in Salesforce Flow. We export CASEpeer workflow definitions as a structured reference document to hand to your Salesforce admin for rebuild.