Migrate from MyCase to Salesforce Sales Cloud

MyCase contacts map 1:1 to Salesforce Contacts. Salesforce requires an AccountId on every Contact — contacts without a primary company in MyCase are attached to a default 'Unassigned' Account record or routed to a Salesforce Lead based on a status flag.

MyCase contacts marked as 'Prospective Client' or designated as 'Referral Source' are routed to Salesforce Lead rather than Contact, with the referral-source designation preserved as a Lead Source pick-list value. The routing logic evaluates the contact's client_status field — only active clients and matter-linked contacts become Salesforce Contacts. All other contact types (prospective, referral, inactive) land as Leads to maintain your pipeline visibility and marketing segmentation without cluttering your Contact object with non-client records.

MyCase companies map directly to Salesforce Accounts using the company name as the Account Name. Company hierarchies where a parent firm owns or branches into subsidiary organizations map to the Account.ParentId field, preserving the organizational chart structure. For contacts associated with multiple companies in MyCase, the primary company becomes the AccountId on Contact while additional affiliations are surfaced as Account Contact Relation junction records, maintaining N:N relationship fidelity across both platforms.

MyCase matters map to Salesforce Cases linked to the Account representing the client. The Case.RecordTypeId distinguishes matter type (Litigation, Transactional, Advisory). Each MyCase matter type requires a corresponding Salesforce record type so that status pick-list values, priority, and custom fields are scoped correctly per practice area.

MyCase matter type (e.g., Family Law, Personal Injury, Real Estate) becomes a Salesforce custom pick-list field Practice_Area__c on Case, keyed by the Case RecordTypeId. Each matter type needs its own record type in Salesforce so page layouts display the correct field set.

MyCase tasks map to Salesforce Tasks with the WhatId pointing to the Case (matter) record. Task priority, due date, and status map to Salesforce equivalents. Open vs. completed status is preserved; completed task completion dates are stored in the ActivityDate field.

Individual time entries from MyCase are aggregated by matter and stored in custom Number and Currency fields on the Salesforce Case record (Total_Billable_Hours__c, Total_Billable_Amount__c). The aggregation sums all billable hours and amounts per matter to populate these rollup fields for pipeline and profitability reporting. Detailed time-entry history — including date, attorney, description, and hourly rate — is preserved as a custom Time_Entry_Log__c child object linked to Case via a lookup relationship, ensuring audit trails and billing audits remain intact after migration.

MyCase Drive documents are re-uploaded as Salesforce Files attached to the corresponding Case record. File folder structure from MyCase is recreated as Salesforce Libraries or as a custom Folder_Path__c field on ContentDocument for navigation continuity. 25MB per-file Salesforce limits apply.

Every MyCase custom field on Contact, Company, or Case becomes a Salesforce custom field with the __c API name suffix. Custom fields must be pre-created in Salesforce Setup before migration runs — we deliver a setup plan listing each field's label, API name, data type, and pick-list values so your admin creates them in advance.

MyCase staff members (attorneys, paralegals, admins) map to Salesforce Users resolved by email address match. Unmatched MyCase owners are flagged before migration so your team either invites them to Salesforce first or assigns their records to a fallback Salesforce user.

MyCase notes attached to a matter map to Salesforce Notes (using the modern Note object, not the legacy Note) linked to the Case via the ParentId field. All rich-text formatting — including bullet points, bold/italic text, hyperlinks, and embedded tables — is preserved as HTML in the Salesforce Note Body field. The note title defaults to the first line of the MyCase note content, and the note's created date maps to the Salesforce Note CreatedDate to maintain historical chronology for matter documentation audits.

MyCase workflow tasks, automated calendaring rules, deadline triggers, and milestone logic have no direct Salesforce equivalent and cannot be migrated automatically. All MyCase workflow task templates and automation definitions are exported as a detailed reference document listing every workflow's name, trigger conditions, task assignments, escalation rules, and deadline calculations. Your Salesforce admin uses this reference to rebuild equivalent automation logic in Flow Builder, covering triggers on Case creation, time-based deadline updates, and automated task generation based on matter type.